Thank you for your work.

If you are interested to make this user friendly for non Nostr users, Iโ€™d recommend hiding all mentions of npub, nsec, etc. behind a more info.

Iโ€™d also skip the save the text file step (most non tech people have no idea where to save it and will forget about it). Go straight to the email step and offer an advanced mode.

Iโ€™d also skip the follow people step. This entire flow is in the way of me as a user to use the app I wanted to use in the first place. So steps need to be reduced to the strict minimum, unless explicitly asked by the user (eg. advanced mode).

TLDR:

# Sign up ๐Ÿ“

Name

Avatar (ideally, auto generated based on npub with option to upload)

[create account]

# Backup your account ๐Ÿ”

Email:

Password:

[Continue]

๐Ÿ‘‰ default should be creating a bunker and sending the bunker code along with the nsec by email. Iโ€™d refer to them as PIN and PUK to tap into something that people already know.

Skip (manual backup)

๐Ÿ‘‰ give people the ability to save the file and choose to create a bunker or not

# Success! ๐ŸŽ‰

- Learn more about Nostr

- Discover accounts to follow

[continue]

Reply to this note

Please Login to reply.

Discussion

I think that in this phase users need to be forced a little to read an learn more about the protocol, this is necessary to avoid bigger problems later. Said that, I'm evaluating a "compressed" version similar to your proposal, that maybe can be forced by clients that already have some internal onboarding resources. In the mass adoption phase this lightened version will surely be the default.

Thank you for the feedback!

I understand the intent. But itโ€™s what you want, not what the user wants when you are in between them and performing an action that requires them to create an account ๐Ÿ˜‰

So itโ€™s good to add links to read more for sure (Iโ€™d put that in the email), but not make it mandatory reading before proceeding. It will scare people.

Itโ€™s all about progressive learning.

Keep up the great work! โค๏ธ

It is not always necessary to give users what they want, a bit like children, it is for their own good.

All kidding aside, I myself am a fan of progressive disclosure and exploratory design, I will try to implement them, also taking into consideration that standard Nstart and the embeddable version may have completely different requirements.

Thank you again for the interesting discussion :)