Exploring some enhancements for the nostr:npub1dx5q2el8nd4eh3eg9t2e25fd7zuqg7zxz6ldkc3uzgh66ss2yc6st288sj send flow. My current focus is on unifying the processes for sending lightning and ecash. I believe that eliminating the need for users to choose between ecash or lightning before reaching the send screen is an improvement. What do you think?
Discussion
Neuromancer is a great book 🤙
Send ecash: Users must first choose the ecash option using the toggle switch. Since most users probably want to send payments via Lightning, setting Lightning as the default payment method and then allowing users to select ecash seems like a reasonable trade off. https://m.primal.net/HhQr.mp4
To me this is just the difference in push vs pull.
Send ecash is push to someone
Pay ln invoice is pull from somebody
This is really good framing.
fyi look at how macadamia has four distinct paths
receive/send being ecash
mint/melt being lightning invoices
I love Macadamia! I'll take a deeper look at their information architecture. My biggest concern with using "mint" as an action to create ecash is how the word can be confused with an ecash mint. I'd also like to see how users react to 4 options. It makes sense to me ,but I worry about less ecash fluent users.
I love the minimal ux, different language use to get used to
i do like that those distinctions are top order and remove the secondary choices you were trying to resolve
perhaps something like:
add
send
receive
pay lightning
Love the unified approach, it boils it all down into a single view that leads to an action with one click! 🔥 My muscle memory would love this
Thanks. The feedback you collected was a major push. I think it's a step in the right direction. Next, I'd like to see how this design adapts to smaller screens. I'm jamming on the design right now, particularly how the keypad and keyboard's slide-up functionality will perform on smaller devices.