Nostr Web Client

My conclusion in the #OnlyZaps experiment is that it should be an app's choice and not a user's choice.

Apps can optimize for offering reactions [x]OR or not offering reactions. Doing both well at the same time (giving the user a choice to enable or not) is a herculean (UX) effort for the small teams we have today.

Don't like the choice your client has made? Find and fund another client that aligns with your choice. I can guarantee you will be better served.

johnny 2y ago

Your conclusion is very respectable, it is not far from reality in app development, however the user must always have the option of whether or not to enable a specific function. If not, it’s better to never develop or implement it. #onlyzaps I love and more to be able to activate or deactivate it whenever I want as a user.

🫂

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 2y ago

Then I should have never developed Amethyst. The app doesn't allow many user choices on purpose.

johnny 2y ago

That’s why it has its large number of users who want everything it offers them and others who want to have the functions and their options to activate them or not.

tina 2y ago

😔😔

geodesic 2y ago

This is a bad take. App developers should curate the user experience they believe is best. No matter what optionality you feel is necessary.

geodesic 2y ago

A lot of people think the app is the product. Its not. The user experience is the product, and the app is merely a vessel.

johnny 2y ago

The user experience is satisfied with the function, now they can choose to keep it or not.

johnny 2y ago

That’s why client who chose to place that functionality thought it would improve the experience of their users and gave them the option to activate them or not.