What Apple Screen Time can and cannot do — an honest guide for parents

Where Screen Time actually lives

There are two routes to the same screen, and both are current. From your own iPhone or iPad, Settings ▸ Family ▸ tap your child ▸ Screen Time gets you there; so does Settings ▸ Screen Time ▸ Family ▸ tap your child. Once your child is in a Family Sharing group and you are the organiser or a designated parent or guardian, you can make every one of those changes from your own device without touching theirs.

Apple renames these menu items more often than you would expect — the family list has appeared under "Family Sharing", "Family", and inside Screen Time itself across recent releases — so if a set of instructions does not match your screen, look for the same idea one level up rather than assuming the feature has gone.

The step that decides whether any of this holds is the Screen Time passcode. It is four digits, it is not your device passcode, and it is what stops a limit from being switched off by whoever is holding the phone. Set it, do not reuse the code your child watches you type at the lock screen, and add your Apple Account as the recovery route so that forgetting it is an inconvenience rather than a factory reset.

The setup order that avoids doing it twice

• Set it up from your device, not theirs — Configuring Screen Time on the child's own device, as that device's owner, leaves the settings in reach of the person you are setting them for. Going through Family Sharing puts them on the other side of a passcode only you know, and lets you change them later from your kitchen rather than from their bedroom.
• Downtime before App Limits — Downtime is a window — bedtime, the school morning — in which everything blocks except phone calls and whatever you put on the Always Allowed list. It does most of the work that parents think they need per-app limits for, and it needs deciding once rather than app by app.
• Always Allowed is the floor, so set it deliberately — Whatever you leave on that list stays reachable during Downtime and outside any limit. Messages, Phone, the camera, the school apps: this is the part of the phone your child never has to earn or ask for, and a system without a floor reads as a punishment however carefully you explain it.
• App Limits last, and by category first — A limit on the Games or Social category survives the arrival of a new app; a limit on five named apps does not. On iOS 26, App Limits are reported to accept a value of zero minutes, which turns a limit into an outright block — useful for a specific app, and a blunt instrument for a category.
• Content & Privacy Restrictions is a separate job — Age ratings, web filtering, purchases and whether apps can be deleted all live in their own section and are not touched by any of the time controls. Doing it in the same sitting saves the second sitting.

What Apple opened up in iOS 15

Before iOS 15, the only software allowed to block an app on an iPhone was Apple's. Third-party parental controls worked around it with VPN profiles and MDM configurations, which is why so many of them were unreliable, and why several were removed from the App Store. In iOS 15 Apple published the Screen Time API and let other developers drive the real thing.

It arrives as three frameworks. FamilyControls handles authorisation and gives the app a picker through which a parent chooses apps and categories. ManagedSettings applies the shield — the lock screen iOS draws over a blocked app. DeviceActivity schedules the whole thing, so a shield can go up or come down at a chosen moment from a system extension that runs whether or not the app is open.

That last detail is the reason the mechanism is worth anything: enforcement does not depend on the app staying alive. A child who force-quits the chore app, or restarts the phone mid-session, still meets the shield when the scheduled moment arrives, because the schedule belongs to iOS rather than to the app.

Built-in Screen Time versus what another app can add

What no third-party app can do, however it is marketed

• Enforce anything outside Apple's framework — There is no second route. An app that blocks apps on iOS is calling ManagedSettings, and an app that claims a capability the framework does not expose is either describing its Android build or describing nothing.
• Monitor messages, calls or browsing history — The SMS and call-log monitoring that Android parental-control tools advertise has no iOS equivalent, for any developer, at any price. Apple's own Communication Limits control who can be contacted; they do not hand the contents to anyone.
• Read the Screen Time report your child generates — DeviceActivityReport lets an app render Apple's usage data inside an extension that the containing app cannot read out. The parent sees the chart; the developer never receives the figures. That is a deliberate privacy design, and it means no third-party app can promise you analytics that Settings does not already show.
• Set itself up remotely from a parent's phone — Authorisation has to be granted on the device being managed, and the app picker has to be used there too. A parent can approve the request from their own device when a child Apple Account asks, but the selection of which apps are shielded is made on the phone that will be shielded.
• Replace the conversation — The framework will do exactly what it is told, at the moment it is told to. What a chore is worth, and what happens on the evening it did not get done, has no API and never will.

Where a pure limit breaks down

A limit is a ceiling. It says what is forbidden and it says nothing at all about what your child can do about it, which means the interesting part of the day — the part where they want more — has no answer inside the system. What happens instead is that iOS offers an "Ask For More Time" button, that button sends a request to you, and you are now a queue. The negotiation you installed Screen Time to end has been moved onto your lock screen and given a notification badge.

The second failure is subtler. Once the limit is the only rule, every good day and every bad day produce exactly the same 60 minutes. A child who spent the afternoon on their homework and a child who spent it arguing arrive at the same ceiling, so the ceiling stops carrying any information. It is still worth having — a floor and a ceiling are genuinely useful — but it is a boundary rather than a system, and a boundary is something to push against.

And a limit is enforced by whoever holds the passcode, which puts a parent back in the room as the person doing the enforcing. That is the position that produces the fifth "five more minutes". Nothing in Apple's controls changes it, because Apple's controls were never designed to; they are a boundary tool, and they are a good one.

The gaps nobody writes down — including ours

• App tokens are bound to the device that produced them — The identifiers Apple hands an app when a parent picks which apps to shield are opaque and local. They cannot be sent to another phone, which means each child device has to make its own selection and shields only itself. We learned this the direct way during QA on 31 July 2026: choosing apps on the parent's phone shielded the parent's phone. KlusQuest now ships a one-tap escape from exactly that mistake, but the underlying constraint is Apple's and applies to every app in the category.
• Revoking permission may not ask for the Screen Time passcode — Developers have reported on Apple's own forums that a child can withdraw a third-party app's Screen Time authorisation in Settings without being challenged for the passcode, when the permission was granted individually rather than through Family Sharing. Authorising through Family Sharing with a child Apple Account, and setting a passcode your child does not know, is what closes that door.
• The shield cannot hand the child anywhere useful — Apple does not permit the lock screen over a blocked app to open a different app. So the button a child taps cannot take them back to the app that granted the time to earn more — it can only close what they were in. Every app in this category has this limitation and none of them advertise it.
• Anything you did not select stays open, always — This is a feature, and it is also a thing parents discover at the wrong moment. The shield covers exactly the apps and categories you picked. A game installed next Tuesday is not in that selection unless you picked the category rather than the app.
• The plumbing is young — The Screen Time API is a 2021 framework carrying real families' evenings, and the developer forums have open threads about tokens changing identity between the app and its extensions. It is reliable enough to build on — we did — but anyone telling you this layer is bulletproof has not read the forums.

What a system without Screen Time looks like

It is entirely reasonable to decide you do not want to hand app-blocking powers to a third-party app, and for a nine-year-old on a shared iPad the enforcement is often solving a problem that does not exist. The honest question to ask of any app in this category is what remains when you say no.

For KlusQuest the answer is a parent-managed voucher, and it is a supported mode rather than a broken one: the chores, the approvals, the earned balance, the daily maximum and the quiet hours all work identically, and you are the one who says the time has started and the time is up. Most of the value was never in the locking — it was in the child being able to see what they had earned without asking, and in that number being a fact rather than an opinion.

Questions parents ask about Screen Time