Avatar
Niel Liesmons
a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be
Designer that codes. Also #WordStudy #Dadstr #Farmstr

Explaining DVM's to normies with the literal Vending Machine analogy is a surprisingly effective way to make them grasp the innovation of both Bitcoin ⚑ and Nostr πŸ’œ .

Gets them excited too, in my experience at least πŸ‘Œ

πŸ”” Notification design, some ideas to improve readabilty:

Comments:

πŸ‘‰ Show just enough of your own note to give context, except for pics

πŸ‘‰ Display them like they're displayed in the feed (in this case with a thread under your note)

πŸ‘‰ Display the buttons for the common actions (comment, zap, share, react)

Zaps:

πŸ‘‰ Display the usernames

πŸ‘‰ Bundle per post

Sharing:

πŸ‘‰ Show max two lines or so of the Quoted notes, just to give context

Reactions:

πŸ‘‰ No need to display usernames

πŸ‘‰ Bundle per emoji

Graph:

πŸ‘‰ Parallel bars are probably not the most beautiful solution for this, but this is the most accurate and readable way I can think of.

Note: You can combine these all in one notification feed if needed (not my preference)

Figma: https://w3.do/tOKCF6CY

#nostrdesign

Bunker Onboard Flow

https://cdn.satellite.earth/470239b92fe3e2ebc76ec88826194ed57d6b958dcf2c6642c0238825a1f3450d.mov

Ideas:

- Freemium model could be a good fit, given the marginal cost of running bunkers.

- We can use the Recovery email users provide for delaying the whole "Back Up Your Keys" aspect and sending those hints to their inbox

- The more things that are automatically set up for the user after signup, the better. For example: 2 premade policies (basic & advanced), one login for each of these policies, ...

Questions:

- Are custom domains possible nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft ? Or is that hard to find the right bunker then and it has to be username@bunkername.com?

- Where are the copywriters on Nostr? We need 'em πŸ˜‰

- nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 , is this something you'd still be up for πŸ‘‰ https://w3.do/xvk10h_5 ? Feedback = very welcome.

#nostrdesign #nsecbunker

Z + S + ⚑ = zap.stream

#logo #logodesign

Is there a way to un-delete events?

Bonkers Bunkers

Not sure how to integrate the "Host your own" option in the Price tier UI. #nostrdesign

Replying to Avatar HoloKat

So.. brainstorming on music integrations, what would make for an amazing experience for both users and artists? 

Throw out your ideas here!

Just off the top of my head, brainstorming out loud here:

Two buttons, one to like, one to subscribe (ongoing support is better than one time payments).

For individual songs, we’ll want a clear zap button that’s hard to miss. A secondary follow button might be nice too, or a like button might work well if we can use that to discover other music.

Upon song ending, it would be amazing to recommend other music either from that artist, or from others that the artist recommends. This could be autoplay or manual. This is a great marketing loop for everyone participating and a good way to discover something the artist you’re supporting likes.

Mini playlist renders either within the timeline or within other parts of UI would be cool. Of course, this is probably easier said than done, but imagine being able to listen to entire playlists instead of a single song. People could then curate playlists and share. This could be done within another specialized client that is specifically designed to do this well. Bonus points if you can just share this elsewhere and it renders nicely even outside of nostr.

For clients with multiple column UIs, it would be amazing if you could add a player as a widget of sorts and that pulls your playlist, or others’s playlists.

Speaking of playlists, how do we give them their own pages? Make playlists linkable from anywhere.

What other wild behavior can nostr enable? What is possible now that wasn’t then? 

Is this difficult to make? I don’t know, you tell me. I’m just throwing out ideas to see if any resonate with the shadowy supercoders πŸ˜…

πŸ‘‰ Third button = Add to Playlist button

πŸ‘‰ Conversations (preferably chat-like UI) around songs and playlists (in the music player UI that show up as comments in social feed apps)

πŸ‘‰ Profile page with Live Events, Merch and more of things where the actual money is made.

Agree Shifts to either being productive or being jealous.

Replying to Avatar brugeman

Take a look at this prototype. It's a Nostr signer web-app - it works in your browser, doesn't need extensions, and stores your keys locally.

I love the recent ideas by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 about OAuth-like nostr signup/login flows, but OAuth is so smooth because it works on the web - no extensions or apps needed. And the only Nostr web-signing option we had until now was to give custody of your keys to a remote nsecbunker, or paste nsec into every app.

This app, though, is a pure web app, and it does signing locally. It uses NIP46 just like nsecbunker, so it shouldn't be too hard for apps to start supporting it - the one that already works is Snort. With nip05 names added on top we can make signup/login flows that are very smooth and users would only deal with email-like usernames and passwords, without the custody of keys by third-parties.

Ok, let's watch the demo. Your eyes will bleed, but it's a prototype. Maybe #nostrdesign team would help us turn it into something pleasant.

https://video.nostr.build/b3bbcd1aa40ca6d1a3175f6690171e859dc85d41d7f4878b1bbc8f9b9c264fa9.mp4

This approach technically works across devices, but that's unreliable on mobile if device is locked, plus your devices are offline sometimes, so the best way would be to have this app store keys on each of your devices so that at least one instance of the signer is always online (on the device you're using right now). That's why this app has built-in password-protected cloud sync for keys.

It's open source.

App: https://login.nostrapps.org

Client: https://github.com/nostrband/noauth

Server: https://github.com/nostrband/noauthd

This can work across devices πŸ‘€ damn that's cool!

And haha, yep a design upgrade is needed here 😜

Both! πŸ˜‰ I think I can design it so that the code can basically be the same for web & mobile.

WIP: https://w3.do/fj3CLVVd Still drawing it out, but feel free to give feedback and steer me in certain directions.

I'm imagining it from the perspective of a company (Coinkite f.e.) that would want easy sharing options of the different logins to send to their employees etc.

Holy cow, yes that makes a lot of sense! Thanks for that insight man πŸ™