How to actually block apps on Android (and why most methods fail)

There are about six ways to stop yourself opening an app on Android, and they are not interchangeable. Most of them fail in the same place: they intervene either too early, before the urge exists, or too late, once you have already seen the feed. This is a survey of what each one actually does at the moment your thumb moves.

1. Uninstalling the app

The most effective option, and the least usable one. It works because it removes the app rather than guarding it — there is nothing left to open.

Where it breaks. Most distracting apps have a web version that is one tab away, and many of them are also apps you genuinely need a few times a week. Reinstalling takes forty seconds, which is well inside the window of a bad decision. Uninstalling is a good move for one or two apps you have decided you are finished with. It is not a system.

2. Android's Focus Mode (Digital Wellbeing)

Google's built-in option. You pick "distracting apps", turn Focus Mode on, and those apps are paused: their icons grey out and tapping one shows a system screen.

What it gets right. It is free, it is on every modern Android phone, and it genuinely prevents the app from launching.

Where it breaks. Focus Mode has a "Take a break" button that lifts the pause for five minutes, and it is right there on the blocking screen with nothing between you and it. That is the whole mechanism: the moment you meet the block is exactly the moment your motivation to remove it is highest, and the removal costs one tap. It also has no notion of a session with a duration you committed to — you turn it on, and you turn it off.

3. App timers

Digital Wellbeing lets you cap an app at, say, thirty minutes a day. When the budget is spent, the app is paused until midnight.

Where it breaks. A daily budget is not a block, it is a rationing scheme — and rationing puts the decision at the wrong end of the day. You spend the thirty minutes in the first hour after waking, and the rest of the day has no protection at all. It also does nothing about the reflex itself: opening the app to check the timer is opening the app.

4. Greyscale and notification hygiene

Turning the screen monochrome, and turning off every non-human notification, genuinely lowers the pull of a feed. Colour is a large part of what makes a scroll rewarding.

Where it breaks. Nothing here stops you. It reduces the urge; it does not intervene when the urge wins. It is a real and worthwhile layer, and it should sit underneath something that actually blocks, not instead of it.

5. Launcher tricks

Hiding apps from the home screen, burying them in folders, removing the search bar. This adds a few seconds of friction.

Where it breaks. The friction disappears in a week, because you learn the new path. Anything that relies on you forgetting where something is has a short half-life.

6. A blocker built on the accessibility service

This is the category most third-party blockers on Android — including Deep Focus — belong to. The app registers an accessibility service, Android tells it when a new window comes to the front, and the app covers that window if the package matches your list.

What it gets right. It is the only approach that reacts to the app opening rather than checking on a schedule, so nothing slips through between two checks and you never see a frame of the feed. It runs in the system rather than in the blocker's own process, so killing the blocker does not lift the block. And it needs no draw-over-other-apps permission — an accessibility overlay is allowed to cover the screen on its own.

Where it breaks — and what to look for. Three things separate a good implementation from a bad one.

• Does it cover the system bars? A blocking screen that reaches under the status and navigation bars swallows their touches. The notification shade stops opening, home and back stop answering, and its own button becomes the only way off the screen. That is not a strict mode, it is a bug — and it is the reason some blockers feel frightening to try.
• What does it do with your notifications? An app hidden behind a blocking screen that still buzzes and stacks badges is half blocked. The shade is one pull away. A blocker worth using either postpones those notifications or admits it does not touch them.
• How narrow is the permission? An accessibility service can be configured to read window content or not to. There is no reason for a blocker to need the content of your screen — only the name of the app that opened. Check what the app says it does with the grant, and prefer the one that says the narrow thing.

What to do with this

Layer them, and put the right one at the right distance from the urge.

Greyscale and notification hygiene lower the baseline. Uninstalling handles the one or two apps you are done with. And for the hours that actually matter — the block of deep work you scheduled, the evening you promised yourself — use something that intervenes at the instant of the reflex, holds for a length of time you committed to in advance, and does not put a five-minute escape hatch on the screen you meet when your motivation to escape is at its peak.

That last part is the whole design brief. Deep Focus makes leaving cost a deliberate second tap and your streak, and never makes it impossible — because a block you cannot leave is not a stricter block, it is a phone you cannot trust in an emergency.