By the time deletion happens, it’s weeks later.
For people building mobile products: – What usually triggers the mute? – Is it notification volume, relevance, timing… or something else? – Have you found reliable signals before this happens?
Genuinely curious what others have seen.
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.
Nowadays, yes — with a couple notable exceptions, discussed below.
In the past, I immediately accepted / allowed notifications for apps like task managers and calendar — because I figured I needed alerts about important deadlines and appointments so I wouldn't miss them! But now even on those I allow badges but not notifications, because I realized that needing them meant I wasn't doing what I needed to do: work in such a way that I know the deadlines by heart and I fulfill them early, and work from my calendar (also knowing it more or less by heart, having a good sense of time, and disciplining myself to stay on track / on schedule and to respect time agreements I made with others and/or myself). Practicing and developing the discipline was what I needed, and the notifications were a crutch and further atrophied my self-management and executive function. (And too many notifications kept me in a tizzy and interfered with my work anyway — a vicious cycle!)
Now the exceptions I mentioned. In my first response I said that I only want to get notifications from Messages. That wasn't entirely accurate. If I set a timer (say, for a work period) or a fleeting reminder (say, to remind me that my laundry needs to be switched to the dryer in an hour) then I want to hear a notification. That also goes for the one third-party app I downloaded, kept, and use with "notifications": a wake-up alarm that uses haptics only, vibrating to wake me up without disturbing my significant other. The unifying threads of these examples are that they are time-based; notifications are essential to the apps' functionality (e.g., you can't have an alarm without some kind of alert or notification); and I'm still specifically directing the apps to notify me about one-off items. None of these notify me without my say-so, and I never get an unexpected notification from them.
> Have you ever kept an app around without notifications because the pull was strong enough on its own?
Well, if I understand the question correctly, since I default to no notifications, every app still on my phone got kept because it proved its value and non-annoyance / user respect over time.
If instead you're asking whether I immediately decided to keep an app always and forever because it was so valuable, no: apps can and do change, and my needs change, so apps are always on the chopping block and must perpetually provide value. And I regularly review all my apps for that value and delete ruthlessly.
Muting notifications means "I don't need this thing to interrupt me". Deleting means "I don't need to use this thing ever".
Those are very different and separate things - I have plenty of apps that I use regularly and yet they do not have notifications enabled because there would be no value from that.
I think a lot of product discussions collapse engagement into notifications, when in reality many useful tools are pull-based by nature. I personally have apps I use weekly that would be worse if they ever notified me.
Maybe the mistake is assuming interruptions equal usefulness, when for many apps the value is exactly the opposite: being available, predictable, and quiet until needed.
Almost all app notifications are worthless noise. Unless I know I need notifications from an app (which is rare), I mute notifications on install. If I've forgotten, then first time an app gives me one. This happens whether I'll ultimately delete the app in the end or not.
A lot of teams treat notifications as a default feature instead of something that has to earn its place. From the builder's side, it’s often framed as keeping users engaged, but from the user's side, it’s just another interruption competing for attention.
What I find interesting is that muting often just means I’ll use this when I need it. That often gets lost when teams look at notification opt-out as a negative metric.
