Nostr

#[0] on #damus we are discussing how to open source #

design more with #[2] Sasha and team.

A bigger #nostr effort outside of damus that came up: what if we have a FOSS nostr design kit, similar to nostr-dev-kit by #[4] #[5] . The nostr design kit, similar to nostr dev kit, would reduce the friction and effort in launching micro apps.

Design kit -> Less friction-> more experimentation-> more #nostr micro apps -> greater nostr network effects and value for current and prospective nostriches.

This could have common components for websites, and/or apps. For instance create key, login with key flows etc.. Bitcoin has the bitcoin design community, which has the visual language of btc, wallet templates, flows, and best practices etc.

Are you or anyone working on a nostr design kit?

#design

#ndk

jonb 2y ago

Definitely like this coordination! Conversation on the onboarding piece is ongoing in this doc by nostr:npub1kuc70777tsvj67fl75s2dmy376t97hv05xmyuyshzzy6vhj5q5jstv0eyw: https://docs.google.com/document/d/1GUNGN7wTr3tNBOE3eCy0T3BTyKhrDay2vd8a0b7ryBk/edit?usp=drivesdk

Reply to this note

Please Login to reply.

Discussion

elidy 2y ago

Thank you for sharing, JonBasa.

PABLOF7z 2y ago

I made a few notes on that doc.

Note that I see quite some disagreement with Gene (sorry, don't know the npub, but would be nice to tag him here)

I don't think this disagreements need to be bridged. Likely, the combined result will be worse that executing exclusively on either direction.

I want to see multiple onboarding apps/widgets, competing and implementing all kinds of weird visions, not some generic, appease everybody thing.

Would be nice if the onboarding widgets generated a tag so that we could get some stats on churn from each onboarding widget + app.

elidy 2y ago

I agree that #nostr design components should be highly customizable. #nostr should not be a place for cookie cutter clients.

To reach something like what you are suggesting would probably take a community with multiple designers addressing the same issue on their own, testing their own choice of the nostr clients pie, and then coming together with a file to show their ideas. Perhaps like you’d see in a poetry or writing workshop. Perhaps something like what #[10] and #[11] are suggesting.

It could be a weekly challenge, and what gets created and redesigned with feedback would go into a designs repository any developer could use.

We’d run into trouble if it’s just one pair of designer eyes and one view of #nostr. We need a joint designer effort + developers to voice their needs & test designs + continuous feedback.