|
Speaking as a user, and offering my own preferences / process FWIW: My goal is to simplify and have as few apps as possible. If I download a new app, it's always on probation. It needs to reduce my cognitive load, save my time, make my life appreciably better. If it doesn't, or if the juice isn't worth the squeeze, I delete it. Regardless, I immediately default to no notifications. Don't ask me to turn on notifications: I'm not an idiot, so I figure the app has some notification mechanism if I want it; and I figure I can activate it in a place called Settings; so I'll handle it myself if I decide to later, thanks. The insult to my intelligence just wasted seconds of my life and limited attention and mental bandwidth, none of which I'll ever get back — so, strike 1! I prefer to poll. If polling is not enough, I'll set up scheduled notifications. If that's not enough (maybe the app is Messages or one that alerts me that my house is burning or my children have been kidnapped — who knows!) then I'll turn on notifications. But even on Messages — perhaps the only app I want to hear go ding — I mute notifications for a lot of contacts/threads. So if the app isn't helpful; or stops being helpful; or becomes a burden, through annoying notifications or otherwise — sayonara. |
The part that stands out to me is how default notification prompts feel like an insult to intelligence rather than a value exchange. A lot of teams treat “turn on notifications” as a growth lever, when for users like you it’s already strike one.
Have you ever kept an app around without notifications because the pull was strong enough on its own? Or is the bar now basically “silent by default, prove value first?”
Trying to understand whether mute is more about notification behavior specifically or a broader signal that the app hasn’t earned ongoing attention yet.