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?

Reply to this note

Please Login to reply.

Discussion

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.

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 🙏.