Steve
@sdv.eth
Devs, If the first thing your mini app does is prompt me to save it before I even get to see what it does, I'm gone. I refuse to succumb to the dark pattern popularized by publication websites that prompt you to fork over your email when you haven't even finished the article. Enjoy your inflated user metrics!
10 replies
6 recasts
67 reactions
Cameron Armstrong
@cameron
i assumed this was a merkle thing tbh where in the user flow do you think it makes sense to put the save action?
1 reply
0 recast
5 reactions
Steve
@sdv.eth
I think this all might be a consequence of the boilerplate example that people first build with. If it were me, I'd add the prompt after the user does the one big thing they're supposed to do. Or if the app is complex enough have it in a settings page where the user can toggle Warpcast notifications (which is imo the main use case for saving in the first place)
2 replies
0 recast
6 reactions
artlu 🎩
@artlu
but but but I spent so much time building user settings I didn't get to the core of the mini app functionality/appeal. seems like 1000 different (partial) settings across all the varying build quality is bad UX. the kebab outside of the frame, where it's easy and user-owned to remove/turn off notifs, I like that pattern
1 reply
0 recast
1 reaction
Steve
@sdv.eth
That I can agree with! Ideally imo the app should reflect those user-owned settings you mentioned, on top of any specific settings the app has. Of course with in reason, analysis paralysis and user customization should be balanced!
0 reply
0 recast
2 reactions