Product2 publishers3 min readPublished
Apple ships iOS 27 parental controls that wait for the whole family to update
The Child Account tools in iOS 27, iPadOS 27 and macOS 27 put a parent's approval in front of new websites, contacts and downloads, and every device in a Family Sharing group has to be on the 27 releases first.
The Product Desk · Product desk
What happened
- Apple's new child safety suite went live on September 14, 2026 with iOS 27, iPadOS 27 and macOS 27, covering the content kids see, who they can talk to and when they get their apps.
- All of the controls sit inside a Child Account, which Apple requires for children under 13, or the local equivalent minimum age, and makes available for children up to 18.
- Communication Safety, until now limited to nudity, blocks detected gore and violent content in shared images and videos and in live FaceTime calls.
- Parents can build their own app categories and move apps between them, and daily limits can be shared across a category such as Games or set individually.
- The new Screen Time experience only reaches a household once every device in its Family Sharing group runs the 27 releases, watchOS 27 and visionOS 27 included.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- constraint The slowest device in a household sets the date the new regime turns on, so no app team can assume a given child is running under these gates until an old Apple Watch or headset gets updated.
- decision For five years of a user's life the Child Account is the parent's choice, so a teen onboarding flow has to work identically inside and outside it.
- exposure Time spent in your app becomes a weekly summary line reviewed by someone who can cut it, and I would expect the app with the fastest-rising minutes to be the first one moved to a tighter category.
- precedent Apple's age-tailored suggested allowances give parents a default number to start from, so an app that needs more than the suggestion is arguing against a figure Apple says came from expert research.
A kid on iOS 27 taps a link in Safari, the page does not load, and the request lands in a parent's Messages thread for approval [7]. That is one of three approval gates named in this release. The other two are Ask to Buy, which already requires a parent's approval before downloads and in-app purchases, and a new setting that makes a child ask before connecting with a new contact [8][9][1].
Apple previewed most of this in June at the WWDC26 keynote [2], and describes the result as a "new suite of powerful, intuitive, and easy-to-use tools that helps parents create safer digital experiences for their kids" [3]. The shipped mechanics are narrower and more useful than the sentence. Schedules decide which apps are available at which hours, and the schedule can differ by day of the week [11].
Setup starts a new Child Account with a small set of essential apps, a recommended starter set, or a parent's own pick of which Apple apps the child gets from the outset [6]. Third-party apps arrive after that, and a parent can attach a time allowance at the moment they approve one through Ask to Buy [17].
Apple's design assumes the parent keeps coming back. The redesigned Screen Time offers controls to pause a device or reopen it for a limited period, and to switch between schedules on the spot [13]. Apple says the rebuilt architecture syncs parental controls more quickly across the devices in a Family Sharing group [12].
The change with the longest reach into product decisions is a single line in the release notes. Websites associated with an app can automatically follow that app's time allowance [18]. A mobile web fallback no longer buys back minutes for a child who has run out of them. Apple's newsroom post and 9to5Mac's account both stop at Safari when they describe Ask to Browse. Apple has not said whether developers get a signal that an app is running under an allowance. Apple says some features may not be available in all regions, all languages, or on all models [22].
For a team shipping on Monday, each core flow sorts on two axes: whether it needs a permission only a parent can grant, meaning a download, a new contact or a new website [7][8][9], and whether it spends down a category allowance the parent controls [17]. Flows in neither box are unaffected. Permission-only flows put a parent's response time inside your time-to-first-value, so they need a visible waiting state that does not look like a crash. Allowance-only flows have their session length set by someone else's budget, and depth per session matters more than sessions per week. Flows in both boxes have two people in the activation path, and the measure of whether they work is how often the second person approves.
What to watch
- Whether Apple gives developers a signal that an app is running inside a Child Account or under a time allowance.
- Whether the rule that every Family Sharing device run the 27 releases, watches and headsets included, gets loosened.
- What numbers the Apple and American Academy of Pediatrics guidance attaches to age-tailored allowances.