📄️ Error Handling
Apps are bound to have errors. We can help people avoid the stress of errors by designing in ways that prevent errors from happening in the first place and lessen the impact of the error once it occurs. The following are some good practices when it comes to error handling.
📄️ Impostor Prevention
Since nostr doesn't have central servers and there is no way to authenticate any users, we run into the challenge of preventing impostors on the protocol. Some solutions have been devised, though none are perfect yet. Here we'll explore various concepts such as NIP5 (not a good prevention mechanism) along with other ways of preventing impostors.
📄️ Logged Out View
A "logged out view" simply refers to the demo, trial or freemium version of the app. No login is required to see the contents of the app.
📄️ Onboarding
There are a few ways to approach onboarding. Regardless of our preferred approach, we should consider the progressive disclosure design principle.
📄️ Private Key Safeguarding
There is no password reset in Nostr. The moment the user leaks their keys, it’s game over and a new npub has to be created.
📄️ Relays
Relay discovery, continues to be a highly debated topic in the nostr community, primarily because the entire decentralization of the protocol depends on how people discover relays.
📄️ Sharing
Sharing outside of nostr makes nostr grow faster. I didn't mean to rhyme, but it's true.
📄️ Sign In / Sign Up Screens
Logging in with Extensions
📄️ Zaps
What are they?