Why iPhone Screen Time limits don’t work — and what does

The three reasons App Limits fail

1. Timing. An App Limit fires after your allowance is spent. By then the habit has already won — you got the thirty minutes, and the limit only decides whether you get thirty more. For an autopilot habit, the moment that matters is the tap, and App Limits never touch it.

2. The escape hatch. When the limit screen appears, it offers “Ignore Limit → One more minute / Remind me in 15 minutes / Ignore for today”. That is a one-tap bypass, and after a week it becomes a reflex you no longer notice. Apple added a Screen Time passcode to slow this down; most people know their own passcode.

3. It counts the wrong thing. Limits measure minutes. The problem is usually opens — forty small visits, not one long one. Forty visits of 45 seconds never trigger a 30-minute limit and still cost you the whole afternoon in fragments.

What iOS 27 changed (and didn’t)

iOS 27 rebuilt Screen Time around families: Time Allowances by category, Ask to Browse, weekly schedules, mandatory child accounts under 13. All of it is a parent managing a child’s phone. For an adult managing their own, nothing changed: App Limits still fire after the fact and still have the ignore button.

Android 17, meanwhile, shipped Pause Point — a ten-second pause before a distracting app opens. Same diagnosis, opposite fix. On iPhone, that fix only exists as third-party apps.

Settings that make Screen Time slightly better

1. Set a Screen Time passcode you genuinely don’t know: have a partner or friend set it. This is the only way “Ignore Limit” costs anything.
2. Under App Limits, turn on “Block at End of Limit” — without it the limit is a suggestion.
3. Set limits at 5 or 10 minutes, not 30. The point is to make the interruption arrive early, not to ration.
4. Use Downtime with an allowed-apps list for the evening; it is the one Screen Time feature that acts before you open anything.

These help at the margin. None of them changes the timing problem.

What actually works: friction before the app opens

Every approach that beats App Limits shares one property: it acts when you tap the icon, before the feed loads. The free version is a Shortcuts automation (guide below). one sec adds a breathing pause. Opal goes further and blocks on a schedule. Cortex app adds a five-second micro-intervention — a breath, a typed sum, a trivia question or your own usage numbers — then asks why you’re opening the app and scores the decision.

The difference between these and App Limits is not strength. Opal is stronger than a limit; Cortex app is deliberately weaker — you can always continue. The difference is when they act. A five-second pause at the door beats a hard wall at minute thirty because it meets the habit where it lives.