Replying to Avatar UNCLE ROCKSTAR

Thanks to everyone that chimed in and provided feedback. My setup now is:

Desktop: #[1] + #[2]

I can zap someone in less than 3 seconds, the only aimed click is on Pay button. If you can set it up on desktop, do it, the best UX right now.

iOS:

#[3] + #[4]

Takes more than 5 seconds to go through all the screens, still good UX when you set it up and get used to it.

Android:

#[5] + #[6]

This one is a bit of cheat because it goes to lightning address setup in profile, not to post itself. But, I'm trying to optimize for zapping speed on mobile, so will keep it until there is faster option.

Happy ⚡zapping⚡!
Avatar
hopey 2y ago 💬 1

How about amethyst and wos? Two clicks.

Reply to this note

Please Login to reply.

Discussion

Avatar
UNCLE ROCKSTAR 2y ago 💬 1

Gotta try amethyst... but I need mobile wallet that works like Alby:

- Sends zap without any intervention

- I don't need to wait in it's UI, can get right back to Nostr client

Avatar
Wallet of Satoshi 2y ago 💬 2

Hmm what if we had a configurable sats limit in WoS, under which the wallet would “autopay”, bypassing the confirmation button?

We don’t want to autopay everything since a rogue large zap could drain your wallet… but if you are willing to take the risk up to a certain amount, why not?

Avatar
Bones 2y ago 💬 1

Could the user set the amount?

Avatar
UNCLE ROCKSTAR 2y ago

Yes, you have amount setting in client like Damus.

Avatar
UNCLE ROCKSTAR 2y ago 💬 1

That's exactly what we need!

If user turns on "autopay" below certain amount optimize for as speed and then ⚡ Zap from #[8] (or any other client on mobile) will be very close to 👍 Like.

Avatar
UNCLE ROCKSTAR 2y ago 💬 1

#[8] take a look how this currently works on my desktop with #[9]

https://snort.social/e/#[10]

With WoS on mobile you could pull off even better UX:

1. most apps don't have "customize zap size" popup so you get to handle event immediately after tap

2. you get the whole screen for effect... could turn it into cool & quick ⚡ ZAP ⚡ animation!

3. return as fast as possible to client so user can continue browsing