Guide · 7 min read

An app blocker you can't uninstall

If you're searching for this, you already know the problem: you've installed a blocker before, and at 1 a.m. you removed it in eleven seconds. This isn't about willpower. It's about who holds the key — and in almost every app, that's still you.

Why almost every blocker can be turned off

On Android, a blocking app is just… an app. In the operating system's eyes there is no difference in authority between Instagram and "the app that blocks Instagram." They sit on the same layer, with the same permissions model.

So the blocker can be closed, its accessibility permission revoked, or the whole thing uninstalled — by you, in seconds, without any friction. Some apps add a "strict mode" or a password, but the lock lives on the same device, guarded by the same person it's meant to stop.

This is the structural reason blockers fail. Not weak features — aweak position in the system.

What "can't be uninstalled" actually requires

For a restriction to survive a craving, it has to be enforced from a layer you can't casually reach. On Android that layer exists: it's thedevice owner role — the same mechanism companies use to manage work phones.

When a blocker holds that role, three things change:

• It can't be uninstalled from the phone in the normal way.
• Blocked apps become unreachable, not just hidden — search, voice assistant and notifications can't open them either.
• The escape routes close too: installing a replacement, safe mode, changing the clock to fake the end of a timer, or wiping the phone.

That last point matters more than people expect. A restriction is only as strong as its weakest bypass — and "just reinstall it" or "just change the date" are bypasses most blockers leave wide open.

The catch: it can't be set up from the phone

Android deliberately forbids an app from granting itself this role — for obvious security reasons. It has to be assigned from a computer, over a cable or a local wireless connection, during setup.

This is why blockers like this are rare: the setup is heavier than tapping "install." But that friction is exactly what makes it work.Something that installs in one tap can be undone in one tap.

"Isn't that just locking myself out?"

A lock with no key creates panic, and panic makes people factory-reset their phones. A good design isn't a cage — it's a delay:

1. A free window at the start. For the first 24 hours you can edit your list freely or leave with no waiting — because nobody picks the right app list on the first try.
2. An exit you define in advance. You decide during setup how long the wait should be if you want out. When you ask to stop, the clock starts and the phone returns to normal on its own — no permission from anyone, no support ticket.

Cravings are measured in minutes; decisions in days. Putting time between them is the entire mechanism.

What it should never do

Device-owner access is powerful, so what a tool refuses to do matters as much as what it does. A blocker in this category should not read your messages, track your location, monitor your screen, or collect browsing history — and it shouldn't need any of those permissions to block an app. If a product asks for them, that's a red flag, not a feature.

Also worth knowing: Android shows a "device management" notice on every phone with this role, listing what an administrator could do. That list describes capabilities, not actions. You can verify what's actually applied on your own phone under Show policies.

Quick comparison

← All guides