How app blocking actually works on iPhone

There are two very different things sold as "app blocking" on iPhone, and they behave nothing alike at the moment you actually need them.

The first is a reminder. The app watches what you are doing and nudges you — a banner, a countdown, a screen you can swipe past. It works while you are cooperating and does nothing when you are not, because the app doing the watching has no authority over anything.

The second is a shield. The app hands your rules to iOS, and iOS covers the app. Nothing to swipe past, because the app you are trying to open does not open.

Only the second survives the moment it is built for. Everything below is about how that one works.

Why a real block holds with the app closed

Once a shield is on, iOS is enforcing it, not the app that set it. You can close that app, swipe it out of the app switcher, or leave it untouched for a week — the block holds, because nothing about the enforcement depends on it running.

This is also the fastest way to test a blocker before you trust it. Set a block, force-quit the app that set it, then try to open something you blocked. If the shield is still there, the enforcement is real. If it is not, you bought a reminder.

The four ways to start one

Underneath, every block is a rule about when. There are four shapes, and the useful ones are the triggers you never have to remember to fire:

• Schedule — a recurring weekly window. Weekday mornings, or every evening after nine.
• Location — on arriving at, or leaving, a saved place. The office, or the gym.
• Usage limit — once you pass a daily time cap you set for that app.
• Instant — right now, for as long as you choose.

They combine, and that is where they stop feeling like a blunt instrument: a block that requires both a schedule and a place only holds at the office on a weekday morning, and leaves the same apps alone on a Sunday.

You can shield individual apps, whole categories, and websites.

What happens after a restart or an iOS update

This is the failure nobody warns you about, and the one that quietly costs you months.

Restarts, iOS updates and permission resets can all clear the registrations an app holds with the system. The rule still exists in the app's own database, so the interface still shows a block — but nothing is registered with iOS any more, and nothing is being enforced.

The fix is for the app to check its own state against what iOS actually holds and repair the gaps, rather than assuming that what it registered once is still there. That is what Motiv does. It is worth asking of anything you are comparing, because the symptom is invisible: a block that silently stopped meaning anything still looks exactly like a block.

Getting past your own block, on purpose

A block you genuinely cannot escape becomes a block you delete in frustration at the worst possible moment — and deleting the app takes every other block with it.

The design that survives contact with a real bad day makes escaping deliberate rather than impossible. In Motiv, hitting a shielded app lets you through only after clearing friction you chose in advance: waiting out a countdown, writing down why you need it, typing an exact phrase, or entering a code from your authenticator app. Bypasses are capped per day, and the whole thing can be switched off with a never bypass option.

The friction is doing something specific. You choose the rules while calm, and the distracted version of you meets them later. That gap is the entire mechanism.

When blocking stops: what to check

Almost always a permission, and a well-behaved app will have warned you already. In this order:

1. Screen Time access — iOS Settings → Screen Time. If it is off, nothing can be shielded at all.
2. Location — a location block needs "Always" with precise accuracy to switch while the app is closed. iOS grants this in two steps, and the second prompt only appears when you next arrive somewhere, so this one is easy to have half-finished.
3. Notifications — if these are off, you never received the warning that something stopped enforcing, which is why you are reading this instead of a push notification.

If all three look right, it is worth asking for help rather than rebuilding your setup.

What to ask of any blocker

Four questions, and they are all answerable in about five minutes with the app installed:

• Does the shield hold with the app force-quit? If not, it is a reminder.
• What happens after a restart? Ask whether it re-checks its registrations, or assumes.
• What does it do when a permission is revoked? Silence is the wrong answer.
• How do I get past it on a genuinely bad day? "You can't" means you will delete it.

Motiv's answers are on how it works, and the constraints every app in this category shares are in the Apple limits guide.