iOS 27 is out, and Screen Time got its biggest rework in years. Most of the coverage is aimed at parents, which makes sense, because most of what shipped is aimed at parents.
So here is the version nobody wrote: what actually changed if the person you are blocking is yourself.
Short answer. Two changes genuinely help. One thing did not change, and it is the thing that breaks most self-imposed limits. And the headline feature everyone is writing about does not apply to you at all.
Change one: limits now cover a category, not an app
This is the real improvement, and it fixes the single most common way self-blocking fails.
The old model was per app. You capped the app that was eating your evenings. Then you deleted it and reinstalled it, or you found a different one, or you used the web version, and the limit did not follow because the limit was attached to a specific app.
iOS 27 lets a Time Allowance sit on a whole category. Entertainment. Games. Social Media. An app installed after you set the cap inherits it instead of arriving with a clean slate.
That matters because the reinstall loop was never about willpower. It was a design flaw. Your limit was a list, and you were always one download ahead of your own list.
Do this first: move your limits up to categories. If you have six per-app limits, you almost certainly want two category limits instead.
Change two: your week can look like your week
App access can now vary by day as well as by time. Different rules Tuesday evening versus Saturday morning.
This sounds minor and is not. Most blocking setups fail because they are written for an average day that does not exist, so the schedule is either too loose to do anything on a weekday or so tight that you switch it off on the weekend. Once you switch it off, it is off.
A schedule you do not resent is a schedule that survives. Now you can build one.
What did not change: Ignore Limit
Here is the part worth being blunt about, because it is not in Apple's release notes.
When an App Limit runs out, iOS still shows you a screen with a way past it. One more minute. Remind me later. Ignore the limit for the rest of today. In iOS 27, that screen is still there.
If you have never set a Screen Time passcode, that is a one-tap dismissal of the limit you set this morning. The limit is not really a limit. It is a speed bump with a button on it, and at 9pm you will press the button, because the version of you that set the limit and the version of you hitting it are not negotiating as equals.
Turn this on now: open Settings, then Screen Time, then App Limits, tap the limit, and switch on Block at End of Limit. The one-minute extension stops being offered and the app just locks.
This one toggle does more for self-control than everything else in the release combined, and almost nobody knows it exists. We went deeper into why in Screen Time App Limits vs Actually Blocking an App.
What is not for you: Ask to Browse and contact approval
The two features getting the most attention need two people.
Ask to Browse holds back a website you have not visited before until it is approved. Contact approval holds back a new contact in Messages, FaceTime or Phone until it is approved. Both are good designs, and both work because the person requesting and the person approving are different people.
When you are both people, the pause is theatre. The request arrives, you approve it, four seconds have passed. That is faster than the urge you were trying to interrupt, so nothing was interrupted.
Apple built a parental-controls system this year and built a good one. It is a different problem from wanting to stop opening the same feed ninety times a day, which we wrote about in Ninety-Six Times a Day.
One thing to check: what category your worst app is in
Category limits are only as good as the categories, and an app's category is chosen by whoever made it.
Plenty of apps that behave exactly like social feeds are not filed under Social Networking. Some are Utilities. Some are Photo and Video. Some are Shopping. A cap on Social Media does not touch any of them.
Before you trust a category limit, check the App Store listing for the two apps you actually lose time to. If they are filed somewhere unexpected, you need a blocker that works from your list rather than Apple's taxonomy.
The ten-minute version
Update, then do four things. Replace your per-app limits with category limits. Turn on Block at End of Limit for every one of them. Build a schedule that differs between weekdays and weekends so you do not resent it by Friday. Then look up which category your two worst apps are actually in.
That gets you most of what iOS 27 can do for self-control. The gap it leaves is the same gap it has always left: every lock on the device opens for whoever holds the passcode, and that is you. Closing that gap is the whole reason Appblox exists.
Frequently asked questions
Does iOS 27 remove the Ignore Limit button? No. When an App Limit runs out, iOS 27 still shows a screen offering a one-minute extension, a reminder later, or ignoring the limit for the rest of the day. Turning on Block at End of Limit in that limit's settings removes the extension, so the app simply locks instead.
Do third-party app blockers still work on iOS 27? Yes. Blockers are built on Apple's FamilyControls and ManagedSettings frameworks, and iOS 27 left both in place, so nothing breaks when you update.
What are Time Allowances in iOS 27? A Time Allowance caps a whole App Store category, such as Entertainment, Games or Social Media, rather than one app at a time. An app installed later inherits the existing cap instead of arriving with no limit on it.
Can I block apps on iPhone without knowing the Screen Time passcode? Not with Screen Time alone, because you are the person who set the passcode. A blocker that does not offer an instant override is the practical answer when the phone you are restricting is your own.