Nostr Web Client

My UX thoughts my first time using this, just 30 minutes into it.

1. Searched Nostr in App Store and had no idea I should be downloading Damus.

2. Could use an explanation of the different input fields on sign up - Was confused why “Brian” was available. Low popularity or can multiple people have the same username because of (what I am assuming is) a unique public key?

3. Searching via a long public key was scary bc I couldn’t see it all in the search bar. If it can’t all be seen, then just say “copy successful”

4. How do I find people that I don’t know personally but want to listen to?

5. What level of accessibility has been take into account?

Reply to this note

Please Login to reply.

Discussion

Account deleted 2y ago

The beauty of Nostr is that the UX depends on the client you use to connect.

Brian was available because many can share the same name. This is where the NIP 05 identifier comes in. @ adresse for your npub.

Search for tags of your interest. Once you follow enough plebs give primal.net a go to look at network view (the pleb you follow AND the plebs they follow) to hunt for more profiles of interest.

Welcome to Nostr! #plebchain is here to help settling in the need be.

elsat 2y ago

Thanks for the feedback Brian.

1. Captured your comment on explicitly adding nostr to damus title, or subtitle

2. What exactly would you change? There is a relatively succinct description of what public, and private key are. Perhaps an indication if something is unique, and/or immutable?

3. Great suggestion. Documented as area for improvement: https://github.com/damus-io/damus/issues/1108

4. Discovery, and onboarding are two areas team is looking at. In the near term investigating discovery of npub by way of twitter handle, hashtags discovery, profile suggestions

5. Accessibility: we periodically have specific requests. For instance, there have been improvements on disabling animations toggle, dynamic text font size support. Do you have a specific request?

Brian 2y ago

Hey!

For #2 I’d recommend an additional information CTA, so it does t take up real estate but allows new users to platform to educate themselves.

For #5 I’d recommend finding a screen reader user who is also a developer to help build out requirements. Otherwise, correct labels, logical page structure, logical focus order, and make alt text input for UGC images easy and prioritized will all be a great start.

elsat 2y ago

Thanks for the suggestions. For keys, I’ve suggested to team to consider something akin to a “unique” label. I also have something more engaging in mind.

For accessibility I have to educate myself a bit to define the user stories. I jotted down your suggestions on github, and will continue from there. If you are a dev, or know anyone interested in contributing, #damus loves PRs 🙏.