Couple things we can do that I’ve proposed several times:
1. Legacy labels next to new ones eg. (username = npub). Then rename username in app.
2. Remove key gen entirely and generate it for them. It’ll be a slight surprise in how that works but nothing that can’t be explained.
I’ve provided designs and more details on each concept. Dunno if anyone listened.
I'm fairly new to the space, so I'm likely behind on the conversation. I'd like to see those designs if you could share a link or a pic.
I was mostly comparing modals from snort, amethyst, and astral when ideating on this version. And, so far I haven't seen username used as a label.
Ya will get for you. No, nobody has used the term username. I wrote a note on all of this a while ago; not sure how to dig it up short of scrolling forever.
I think it’s not only incorrect, it’s also confusing. “Why is my username so weird? And why was it chosen for me? How do I change it to something sane?”
npub is a username strictly only in the sense of being a unique identifier, but is neither the value people use to locate/refer to users nor is it human readable.
Eventually npubs will probably be abstracted away.
I’m not sure if it is confusing. I guess one way would be to actually test on someone.
Give helper labels that assist in understanding without changing the definition of an npub;
And as a secondary experiment remove the signup step entirely and just generate keys for user, then explain what just happened.
Maybe ‘shareable identifier’ for npub.
And optionally if they want a Nostr Username, let them setup a NIP-05. It’s literally just a username in all aspects (I think) - login, sharing, search, comparing accounts if identical other info, auto-complete, etc. ability to setup a username later.
And then secret/recovery/master private key (or similar) for nsec. Ideally nsec backup is an in-app action after initial setup - “keep your account safe, sync to cloud, save to password manager, write down seed words”. Setup 100% complete.
Check the flow first, then look at the “depreciated” page
