nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 nostr:npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgup
https://cdn.satellite.earth/21c85ac6117ee34c4480b655f50a940921266ed57fbc69b782463804b3354cda.mov
Exploring #V4V UX for app releases.
#zaptheapp
Discussion
Dude this is sick!
Question as download times are variable. Must tap done to close the zap dialog, right?
Yeah! This is epic! Should be implemented if it can.
Yup, exactly ✅.
You will have zaps in your face and be happy 😜
Maybe nitpicking but why would you zap a release you haven't yet used?
How about something like "enjoying this app"? And zap goes to previous release?
I try to stay away from telling people what a zap is supposed to be.
To us it now mostly means a reward to the publisher for the content they published. But once we start actually interacting with them (i.e. letting the publisher reply, quoting them, etc...) they'll probably start serving many more use cases:
- Feature requests
- Questions (where the response from the publisher has a market price)
- Reviews
- Zapvertising
- ...
I can imagine several of these types of zaps happen before the user has even opened the new release + I want the UX of zapping the release after installation/use to be very similar anyway.
To your point, I still need to find a way to give more intuitive access to the previous release 💯