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!

weird internet kid. word rotator. building /seemore. yapping on /okbanger. curating in /cameron + pdfproject.org | 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)

i assumed this was a merkle thing tbh

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

personality hire 🌈🤙 fullstack & ux, building /uno

or "allow notifications" "allow camera permissions" "allow microphone access" "allow to discover other devices on your network" all at app start 😭

related: I think I’ve had to turn off everyone’s notifications for being too aggressive

i agree with you i don't like it and am always more surprised and grateful when they add it on the flow nicely

yeppp! i shifted my onboarding, thanks for the push

Agreed, they should leave the “add” part at the end of it so you only do it if you like it or find it useful

this is the new 

follow me / my channel to use my frame

which also resulted in instant nope/perma-ignore from me.

playing /bracket, assisting /bracky, talking /greatbooks

Mechanically the only difference is typing out a full email address and a button press vs one single button press. Both are high friction if the entire UI is blocked out before I even know what I'm signing up for.

Incorporating into any flow is totally reasonable! In the context of the airdrop, my personal ideal would be:

1) open app
2) claim airdrop button
3) loading state
4) confirmation state that has a "Enable notifications" button which evokes the add app modal

But putting 4) before 2) seems fair.

My gripe is how the very first thing some apps do is just evoke the modal, unprompted and not giving the user a second to explore. It encourages hasty button pressing which is how so many people in crypto get burned signing malicious transactions.

This pattern is not dissimilar to dapps that are walled behind a connect button. It's annoying but at least it doesn't evoke a system level UI.

I needed this letter :)

Do you think adding the app is really similar to providing email? (The former seems way, way lower friction)

Let me steelman the counter-approach: When Bracket has *real* users (ie, the are actively using our product) it's difficult to notify them of important things in their account (eg, they earned money or time-sensitive event is coming up). Things we think they would genuinely want to know.

Users dont understand that there is this benefit to adding app (and it would be kinda bulky to communicate it during high-churn moments). So we add it to flows that users are motivated to complete (eg, claiming their first airdrop.

Not arguing this is ideal; your point stands. Just trying to paint a picture of a reason this is done that doesnt have to do with vanity metrics.

Impact

@ozengk.eth just staked $impact on @sdv.eth's cast.

Support @ozengk.eth's nominees by subscribing to auto-fund their curation.

Opt out of /impact nominations in frame

Banjarmasin, Banjarmasin City, South Kalimantan, Indonesia