On this page · 12 sections
- What is new in iOS 27
- Feature 1: a redesigned Screen Time
- Feature 2: Ask to Browse
- Feature 3: Time Allowances
- Feature 4: an expanded Communication Safety
- Feature 5: approve new contacts
- Feature 6: the Declared Age Range API for developers
- When iOS 27 and these features arrive
- How parents can set these up
- How eCorpIT can help
- FAQ
- References
Summary. On June 8, 2026, Apple previewed a long-overdue overhaul of Screen Time and parental controls for iOS 27, iPadOS 27, and macOS 27. Six changes matter most for families: a redesigned Screen Time with simpler setup, Ask to Browse, Time Allowances, an expanded Communication Safety that now blocks violent content as well as nudity, approval before children connect with new contacts, and a privacy-protective Declared Age Range API for developers. Communication Safety stays on by default for users under 18, and Apple says Time Allowances will suggest limits by age, citing the American Academy of Pediatrics and other child-development experts. The developer side builds on age ratings that now span 4+, 9+, 13+, 16+, and 18+, with age-range sharing already live for new Apple Accounts in Utah as of May 6, 2026 and Louisiana from July 1, 2026. The stakes are not small: the parental-control software market is worth around $1.8 billion in 2026. Dr. Sumbul Desai, Apple's vice president of Health, said the aim is technology that "enriches their lives, while helping keep them safe." Here is each feature, in plain terms, for parents and for the developers who build family apps.
What is new in iOS 27
Screen Time has needed this for years. The redesign groups the controls parents actually use, adds a simpler setup that suggests a starter set of essential apps for a child's device, and makes the day-to-day adjustments less fiddly. The bigger story is the new controls layered on top: finer time limits, web-browsing approval, contact approval, and a stronger content filter. Most features arrive after installing the Screen Time update on iOS 27, iPadOS 27, and macOS 27, which Apple is expected to release later in 2026.
There is also a competitive signal in the redesign. Built-in Screen Time getting genuinely good raises the bar for the third-party family and parental-control apps that filled the gap while Apple's tools stagnated. The parental-control software market, worth around $1.8 billion in 2026 and growing at a double-digit annual rate, was built partly on Apple's past weaknesses here. Developers in that space now have to offer something the system tools do not: cross-platform coverage, richer reporting, parent coaching, or specialized controls. The same Declared Age Range API and age-rating tiers that power Apple's features are available to them, so the differentiation has to come from product depth rather than from filling a basic gap.
The six features split cleanly into parent-facing controls and a developer-facing tool. The table below is the quick version, and the sections after it explain each one.
| Feature | What it does | Who sets it up |
|---|---|---|
| Redesigned Screen Time | Simpler setup, clearer controls, starter apps | Parent, on the child's device |
| Ask to Browse | Child requests approval to visit new sites | Parent approves requests |
| Time Allowances | Per-category time limits with age-based suggestions | Parent, by app category |
| Communication Safety | Blurs nudity and now blocks violent content | On by default under 18 |
| Approve new contacts | Child asks before connecting with someone new | Parent approves contacts |
| Declared Age Range API | Shares an age range, not a birthday, with apps | Developer requests, parent allows |
eCorpIT covered the builder's view of these controls in our iOS 27 parental controls developer guide, and the wider release in the iOS 27 features and device requirements overview.
Feature 1: a redesigned Screen Time
The old Screen Time buried useful settings under layers of menus, which is part of why so many parents set it up once and gave up. The iOS 27 version reorganizes the controls around what parents do most: set limits, approve requests, and review activity. Setup is guided, and for a new child device it can suggest a recommended set of essential apps rather than leaving a parent to assemble one from scratch.
For a parent, the practical change is that the features below are now reachable without hunting. For a developer, the redesign signals that Apple is investing in the family layer of the platform again, which raises the bar for third-party Screen Time and family apps to stay clearly useful alongside the built-in tools.
Feature 2: Ask to Browse
Ask to Browse extends the familiar "ask" model to the open web. When a child tries to visit a site that is not already allowed, they can send a request to a parent, who approves or declines it. It is the same approval pattern parents already know from app downloads and purchases, applied to web browsing, which is where a lot of unsupervised content actually lives.
The value is that it replaces a blunt all-or-nothing web filter with a workable middle path. Instead of blocking the web wholesale or leaving it open, a parent can let a child request access to specific sites and build an allow-list that fits the child's age. That is closer to how families actually negotiate screen access.
Feature 3: Time Allowances
Time Allowances give parents more flexible limits than a single daily cap. Parents can set time by category, including Entertainment, Games, and Social Media, so a child can have more room for one kind of app and less for another. Apple says it will offer suggested allowances based on a child's age, citing health research and guidance from child-development experts, including the American Academy of Pediatrics.
This is a meaningful shift from one number for the whole device to limits that match how children actually use apps. A parent who is comfortable with more reading or educational time but wants tighter limits on social media can now express that directly, rather than approximating it with a single blanket limit.
Feature 4: an expanded Communication Safety
Communication Safety is the on-device feature that detects sensitive content in Messages and FaceTime and blurs it, with guidance for the child on what to do next. It is enabled by default for users under 18. The iOS 27 update widens what it catches: in addition to blurring nudity, it will now intervene when violent or graphic content is detected in shared images and videos.
Two points matter for parents. First, the detection runs on the device, so Apple is not viewing the content to make it work. Second, because it is on by default for accounts registered to under-18 users, the protection applies without a parent having to find and enable it, which closes the common gap where a safety feature exists but is never switched on.
Feature 5: approve new contacts
iOS 27 lets parents require approval before a child connects with someone new across Messages, FaceTime, and Phone. When a child wants to start communicating with a new contact, the request goes to the parent, who allows or declines it. Parents can manage the list of who their children can reach, which addresses contact from strangers at the point it starts rather than after the fact.
For younger children especially, this turns the contact list into something a parent curates with the child rather than a default-open channel. It pairs naturally with the content protections in Communication Safety: one controls who can reach the child, the other handles what arrives.
Feature 6: the Declared Age Range API for developers
The sixth change is for the people who build apps. The Declared Age Range API lets an app request a user's age range, for example whether they are under 13 or 16 to 17, without learning the child's date of birth. When an app needs age information, it shows a permission prompt similar to those for location or camera, and the app receives only the range. Parents in a Family Sharing group can allow or require children to share an age range with apps, and can revoke that permission later.
This sits on top of the expanded App Store age-rating system, which now spans 4+, 9+, 13+, 16+, and 18+. The rollout is partly driven by law: age-range sharing is already active for new Apple Accounts in Utah as of May 6, 2026 and in Louisiana from July 1, 2026, as Apple aligns with a growing set of state child-safety rules.
| App Store age rating | Intended audience |
|---|---|
| 4+ | Suitable for all ages |
| 9+ | Mild content, older children |
| 13+ | Teens and up |
| 16+ | Older teens and up |
| 18+ | Adults only |
For developers, the design goal is to build age-appropriate experiences while collecting as little personal data as possible. Requesting an age range instead of a birthday is the privacy-protective default, and it is the pattern to follow when an app needs to tailor content or features for younger users. We cover the implementation details in our iOS 27 parental controls developer guide.
Why these changes are arriving now
The timing is not only product-driven. Through 2026, Apple has been rolling out age-assurance tools worldwide to comply with a growing set of child-safety laws, and several US states now require app stores or developers to verify or share age information. Utah and Louisiana are the first where new Apple Accounts share an age range with apps through the Declared Age Range API, on May 6, 2026 and July 1, 2026, and more states are expected to follow. Apple's approach, sharing a coarse age range and keeping content detection on the device, is a deliberate answer to those laws that tries to meet the legal requirement without building a database of children's birthdays or scanning their messages in the cloud. For parents, the upshot is that these controls are becoming a standard part of the platform rather than an optional extra.
When iOS 27 and these features arrive
The features ship with the Screen Time update on iOS 27, iPadOS 27, and macOS 27. Apple typically releases the new iOS version in September alongside new iPhones, with developer and public betas through the summer. For the current release timeline, see our guide to the iOS 27 release date and public beta. Parents who want these controls in place for a new school year should plan to update once the Screen Time update is available.
How parents can set these up
None of this helps if it stays off, so setup matters. The starting point is a Child Account, which Apple requires for children under 13 and supports for users up to 18, configured through Family Sharing. Once the child's device is on iOS 27 and the Screen Time update is installed, the redesigned setup walks a parent through the essentials and can suggest a starter set of apps.
From there the practical order is straightforward. Turn on Time Allowances and accept or adjust the age-based suggestions for Entertainment, Games, and Social Media. Enable Ask to Browse so new sites need approval. Confirm Communication Safety is on, which it is by default for under-18 accounts, and turn on contact approval so new contacts route to a parent first. Review the weekly activity summary rather than reacting to every request, and adjust limits as the child grows. The goal is a setup a parent revisits a few times a year, not a daily negotiation.
What these features do not do
It helps to be clear about the limits, because no control replaces conversation. On-device detection in Communication Safety reduces exposure to nudity and now violent imagery, but it is not perfect and can miss or over-flag content. Ask to Browse and contact approval depend on the child using the managed device and account, not a friend's phone or a separate browser. Time Allowances shape how long a child spends, not the quality of what they watch or read. And an age range shared with an app tells a developer roughly how old a user is, not whether a specific piece of content suits that particular child. Treat these tools as a strong default layer that buys a parent room to focus on the harder, human part.
India-specific considerations
For Indian families and for developers serving Indian users, the age-range approach lines up with where India's law is heading. The Digital Personal Data Protection Act, 2023 places specific obligations around processing children's personal data, including verifiable parental consent for users under 18 and limits on tracking and targeted advertising to children. The Declared Age Range API's design, sharing a range rather than a birthday and keeping detection on-device, fits the data-minimization principle the DPDP framework rewards. A family app aimed at Indian users should treat age-appropriate design and parental consent as defaults, not add-ons. Our DPDP consent-manager readiness guide covers the consent mechanics in detail.
How eCorpIT can help
eCorpIT (eCorp Information Technologies Private Limited) is a senior-led technology consultancy in Gurugram, founded in 2021 and assessed at CMMI Level 5. Our iOS teams build family, education, and Screen Time apps that adopt the Declared Age Range API, respect the new age-rating tiers, and align with DPDP children's-data rules, using on-device and data-minimizing patterns by default. We design apps aligned with child-safety and privacy requirements rather than claiming certifications we do not hold. To build or review a family app for iOS 27, contact our team.
FAQ
References
Last updated: June 29, 2026.
