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.
#amethyst is my favorite client. I love this viewpoint as well
I understand what you’re saying Vítor (and agree), but I think the issue goes well beyond that.
I wish I had an android so I could try out amethyst
I agree with you.
Respect for using the exclusive OR operator in a verbal argument 🤝
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.
🫂
This is a bad take. App developers should curate the user experience they believe is best. No matter what optionality you feel is necessary.
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.
The user experience is satisfied with the function, now they can choose to keep it or not.
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.
I'm all for onlyzaps , but if we want this protocol to be successful and grow we need that too. We need this to be friendly and welcoming not to be like some billionaires boys club. All respect for what you do for the amethyst app 🫡
I am only just having a look at all of this, and the learning curve, even for someone familiar with the concepts, is a lot. It has still taken me a whole day to figure out wth is going on and probably have 10 IDs now lol... still don't know what a Zap is. heh. Anyway, there is always that tension between normie uptake and viability and I hope various projects can help with that onboarding gap to what is a great product.
Personally, I am just excited to see people working so hard and agree that optics is paramount. Anyway, I hope to persevere and help where I can (hope you don't mind me jumping in and replying here to test/find people/get events etc working). I'm one of those 30-year Unicorn Design and people-people, not an engineer, but giving it a good shot. Onya, folks. You're all doing great.
I'd be surprised if the decision to implement #onlyzaps (or not) would actually be a reason to really change clients for that many people. I'd prefer not having likes but I'm not switching from Amethyst either way personally.
Likes are fake/cheap attention. Let the money speak.
#zapsonly
#[1]
I hope that someday amethyst can implement #onlyzaps though. Reacting can easily be done in notes via text and emojis or jpegs or gifs with any client
Seems like a waste of time to even bother building them as an event type(?) honestly 😅
