I like how Kiwi is on the cutting edge and offers Login with Nostr connect. But, it is challenging to explain these options, especially to new users.
I've been continuing to mull over the sign-in flow for Nostr apps. It seems more complex than the legacy system because of the need to account for more than one method of authentication: extension, public/private keys, nostr connect.
https://void.cat/d/YFiXaAVnb54ifi9FKmtsui.webp
Even if one method becomes standard in the future, I think there's still a question of how to accommodate users who continue using older methods. Examples and more thoughts in thread 🧵. cc nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac / nostr:npub1x6gxrjdpacjc62x3y0e4lyfedzyy65kyj29t0026g4z0el2g70esc0rtxj
Tags: #ux #design
Discussion
I like Coracle's approach in promoting one method for signing in as primary and having other options hidden behind a button or dropdown. The question here, would be what is the primary method that is best to promote? Is this just something that needs to evolve over time?
I like how Habla's modal explains how things work and provides links to helpful resources, but it is a lot to parse in one go and may be overwhelming to users.
Also related, does it make sense to try and align on a particular logo & colors for recognizability when signing in? The value would be that users can see a common logo across apps and quickly realize, "Ok, I've used this before, I know I can log in here."
That’s why added Tony’s article to explain more. Also what’s lacking right now is onboard for new users.