I ran some usability tests on 3 nostr clients to get an idea of where new people are struggling. The testing was meant primarily for UI/UX issues. Keep in mind the same of people is small (10) so it may not give us a complete picture.
For each test, I took down notes and counted how many times people pointed out various issues. I then tallied them up to get a general idea of the problem areas:
Terminology issues - 19
UI issues - 15
Discovery issues - 12
Key issues - 12
Perception issues - 8
Lack of content - 5
Didn’t read - 4
Possible major bug - 3
Terminology refers to people who indicated being confused about some of the nostr terms. Among most confusing things were: Keys, relays, Nostr address, nostr, lightning address.
Except for one occasion, everyone was universally lost on those terms and did not have enough information to understand them. People didn’t even know what nostr is (understandably so given that the clients are not named nostr).
UI issues is a broad category of various UI problem areas. My summarized findings point out all of the issues users faced while trying the apps.
Perception issues is my way of defining how people are perceiving the apps. Most people compared them to Twitter. But some have attributed other things like “for trading bitcoin” or “for gambling” among other assigned purposes. Whether that’s an actual problem or not is up to developers to decide, but if you want your apps to appeal to everyone, that’s something to think about.
Discovery issues are where people couldn’t find what they were tasked with - for example finding interesting notes or people.
Key issues encompass a range of problems people ran into such as not knowing if their keys are saved, or how to recover them, or what they mean in the first place. One person logged in with their npub without write permissions and couldn’t do any other tasks, showing a lot of frustration in the process.
Lack of content is just that…
Didn’t read - means they skipped whatever screen was there just to sign up quickly. Most people did not read, though one did. This is important because we need to think about how to make things easy to understand without much reading.
There were a bunch of bugs which could fall under UI issues, but on 3 occasions there were major bugs where the user could not do anything to advance forward. This underscores the importance of testing clients on various operating systems and browser configurations.
The current test findings are in a Google sheet, and I’m happy to share with any developer who’d like to see them. For testers’ privacy reasons I will not share a public link here. DM me if you’d like a link.
Karnage
npub1r0…sq9ac
2023-12-13 00:59:21
Author Public Key
npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9acPublished at
2023-12-13 00:59:21Event JSON
{
"id": "57e538305ca4bda8cc5d8297172d87d7cfbafae1e04bac70b06ab241b2aeb235",
"pubkey": "1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411",
"created_at": 1702429161,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"nostrdesign"
],
[
"t",
"usability"
],
[
"t",
"ui/ux"
]
],
"content": "I ran some usability tests on 3 nostr clients to get an idea of where new people are struggling. The testing was meant primarily for UI/UX issues. Keep in mind the same of people is small (10) so it may not give us a complete picture. \n\nFor each test, I took down notes and counted how many times people pointed out various issues. I then tallied them up to get a general idea of the problem areas:\n\nTerminology issues - 19\nUI issues - 15\nDiscovery issues - 12\nKey issues - 12\nPerception issues - 8\nLack of content - 5\nDidn’t read - 4\nPossible major bug - 3\n\n\nTerminology refers to people who indicated being confused about some of the nostr terms. Among most confusing things were: Keys, relays, Nostr address, nostr, lightning address. \n\nExcept for one occasion, everyone was universally lost on those terms and did not have enough information to understand them. People didn’t even know what nostr is (understandably so given that the clients are not named nostr).\n\nUI issues is a broad category of various UI problem areas. My summarized findings point out all of the issues users faced while trying the apps.\n\nPerception issues is my way of defining how people are perceiving the apps. Most people compared them to Twitter. But some have attributed other things like “for trading bitcoin” or “for gambling” among other assigned purposes. Whether that’s an actual problem or not is up to developers to decide, but if you want your apps to appeal to everyone, that’s something to think about.\n\nDiscovery issues are where people couldn’t find what they were tasked with - for example finding interesting notes or people. \n\nKey issues encompass a range of problems people ran into such as not knowing if their keys are saved, or how to recover them, or what they mean in the first place. One person logged in with their npub without write permissions and couldn’t do any other tasks, showing a lot of frustration in the process. \n\nLack of content is just that…\n\nDidn’t read - means they skipped whatever screen was there just to sign up quickly. Most people did not read, though one did. This is important because we need to think about how to make things easy to understand without much reading. \n\nThere were a bunch of bugs which could fall under UI issues, but on 3 occasions there were major bugs where the user could not do anything to advance forward. This underscores the importance of testing clients on various operating systems and browser configurations.\u2028\u2028The current test findings are in a Google sheet, and I’m happy to share with any developer who’d like to see them. For testers’ privacy reasons I will not share a public link here. DM me if you’d like a link. ",
"sig": "01d57a1d1b3bb00a521c2e81bc378df308e69ffadee0f24f76c413d0c09fee905a9a068a61a67560bcedb2df98b791034f542c1d6ed0d697615d26a796222a1e"
}