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!

i assumed this was a merkle thing tbh

where in the user flow do you think it makes sense to put the save action?

weird internet kid. word rotator. yapping on /okbanger. playing with @wannanaplabs. curating in /cameron | dev + vet + HBS. 
seemore.tv/cameron 🫡

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)