On #damus team has an onboarding feature request +design ready: immediately upon profile creation new user sees draft post including intro yourself prompt including #introductions tag.
If bot is done incorrectly it could turn off new users who might experience a bot interaction as their first nostr interaction. New user might think there are only bots, and there are no real people on nostr. This is especially true if onboarding mechanisms are not improved for finding other people.
agreed, was exploring a zapping idea
I think the onboarding experience needs to be thought-out beyond damus (i.e. damus' UX should be considered as one piece of the whole onboarding experience)
what I'm saying is that we need tooling to discover/welcome high-quality #introductions posts
imo, the onboarding flow should prompt users to write in the introductory post something significant about what they are interested in to try and connect those users as quickly as possible to what they care about and not just dump them on the ever-present #bitcoin topic
Agree.
Working nip-50 search, follow hashtag, hashtags in profiles discoverable by search as user profiles interested in a certain topic move in this direction.
āTopicsā discovery without relying on hashtags is not explored afaik. Being wary of algos, this more detecting topics in notes, and classifying said note under said topic.
wait, #nostr is the orange pill to #bitcoin ?
š š©āš š«š©āš
ofc!
ā”ļøā”ļøā”ļø zaps are a foundation of a value4value culture
regardless of your understanding or thoughts on bitcoin, onboarding flows should address zaps, and give people that choice with the least amount of friction
Zaps onboarding is needed, and pending definition. Both damus, and across nostr
šÆ we need to help people discover niches based on their interests, so they can dive in and express themselvesā¦
We donāt need one perfect solution, but an amalgamation of many different pieces that support someoneās experience of #nostr, no matter which client they are using.
Every improvement helps, and can get tied in to other efforts, including introductory postsā¦
This is where that bridge between design and development should be built, translating development into design.
If thereās development of lists or groups of people to follow, can we make that part of the onboarding process?
If thereās stronger search and data discovery based on topics, hashtags, trends, relaysā¦ how we can we help make search intuitive? how do we display search suggestions?
If thereās other back-end capabilities that are already getting built to help people discover #nostr, how can we, as designers, help you display that?
We need to have more of these kinds of conversations to guide the designing journey to whatās most needed.
This is what nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is working on
I am all for this kind of discussions; a lifetime ago I used to do user onboarding consulting; it's a topic I'm extremely passionate about (I know, my apps don't show it... one thing at a time! šš )
Thank you for your time & feedback.
From your wide perspective of #nostr development, which aspect of onboarding needs the most help?
How can we help with NDKās design layer?
