Count the notifications you received yesterday and how many required action within the hour. For most people the ratio is dismal — dozens of interruptions for a handful of things that genuinely could not have waited.
That is not an accident or a personal failing. Notifications default to on because engagement is what apps are measured on, and an app that never interrupts you is an app you use less. Every default was chosen by someone whose interests differ from yours.
What changed in 2026
- Focus modes matured. Per-context notification profiles moved from a novelty into something people actually configure and use.
- Summarised delivery spread. Batching non-urgent notifications into scheduled digests became a standard platform feature rather than a third-party trick.
- AI assistants added their own channel. A new category of proactive suggestion arrived, with its own defaults, on top of everything else.
- Permission prompts stayed manipulative. Apps continued asking at moments calculated to get a yes, and re-asking after updates.
Reset to zero first
The instinct is to work down the list turning off the worst offenders. That fails, because the list is long, the bad ones are not obvious in the abstract, and attention runs out around item fifteen.
Invert it. Turn everything off at the system level, then re-enable only what earns it.
Most phones let you disable notifications for all apps in one place. Do that. Then live with it for a few days.
What happens is informative. A small number of things you genuinely miss will make themselves known — you will notice you were not told about something that mattered. Re-enable those. Everything else, which is most of it, you will not miss at all, and that absence is the answer.
Subtracting from zero works because the default becomes off and each exception requires a reason. Pruning a long list leaves the default as on and requires a reason to remove each one, which is much weaker.
The one-hour test
For each candidate, ask: does this need my attention within the hour?
Almost nothing does. A message from a family member might. A calendar alert for something starting soon does. A system alert about a security event does.
A social media like does not. A marketing message does not. An app suggesting you have not used it lately certainly does not. A work email — genuinely — does not, in nearly every job. Email is asynchronous by design, and treating it as real-time is a choice that costs a great deal of attention.
| Category |
Interrupt? |
| Calls and messages from named people |
Yes |
| Calendar events starting soon |
Yes |
| Security alerts on financial accounts |
Yes |
| Delivery arriving now |
Usually |
| Email |
No — check on your schedule |
| Team chat |
No — unless on call |
| Social media |
No |
| News |
No |
| App engagement prompts |
Never |
The middle rows are where people resist most. Chat applications in particular feel urgent and are designed to, and almost every message in them could wait an hour without consequence.
Badges, banners, and the rest
A notification is several settings, and silencing one leaves the others working.
Sounds are the loudest interruption and the easiest to turn off.
Banners interrupt visually, which is nearly as disruptive as sound if you are looking at the screen.
Badges — the red dot with a number — are the subtlest and arguably the most effective at pulling attention. They persist, they accumulate, and they generate a low-level pull every time you unlock. Turning off sound and banners while leaving badges enabled changes much less than it feels like it should.
Lock screen appearance determines whether you see it just picking up the phone.
Turn off all four for anything that failed the one-hour test. Partial measures produce partial results.
Focus modes are worth the setup: a work profile allowing only calls from specific people, a personal profile, and a sleep profile allowing essentially nothing. Configure the exceptions carefully — most platforms let a repeated call from the same number through, which handles the genuine emergency without opening the door generally.
Common mistakes
- Pruning instead of resetting. Attention runs out before the list does.
- Leaving badges on. The quietest and most persistent pull.
- Treating email and chat as urgent. Neither is, in almost any job.
- Doing it once. Updates re-enable things and add new categories.
- Accepting the permission prompt reflexively. Apps ask at the moment most likely to get a yes.
- No exception for genuine emergencies. Then you disable the whole thing the first time you worry about missing something.
- Not applying it to the computer too. Desktop notifications interrupt work more directly than phone ones.
FAQ
Will I miss something important?
Set up emergency exceptions — specific people, repeated calls — and the honest answer is that you will miss things that were never important. The category of "urgent, only reachable by notification, and genuinely could not wait an hour" is much smaller than it feels.
What about work expectations?
Response-time expectations are a conversation with your team, not a notification setting. Most teams have no actual requirement for immediate response outside an on-call rotation, and many people discover the expectation they were serving was one they invented.
How often should I redo this?
Every few months, and after any major OS update. Apps quietly add notification categories and updates re-enable things.
Does this help with screen time?
It addresses the interruption side rather than the deliberate-use side. Most unplanned phone pickups start with a notification, so removing them removes the trigger — which is a different mechanism from limiting time and generally more effective. See digital decluttering.
Where to go next
For the broader cleanup this fits into, read digital decluttering. For reducing the marketing messages that generate many of these, email aliases explained, and for the physical setup that affects focus as much as software, desk ergonomics.