Apple introduces ‘Time Allowances’ categories (iOS 27): why the new Social Media questionnaire matters for age rating and distribution

Original post (source): Apple Developer News - “Introducing Time Allowances” (June 8, 2026)

• https://developer.apple.com/news/?id=0d2gpmml

What Apple is doing

Apple is adding Time Allowances in iOS 27, iPadOS 27, and macOS 27. These are parental controls that group apps into categories like Entertainment, Games, and Social Media, so parents can manage time spent across those categories.

The key nuance: Apple says Time Allowance categories are different from App Store categories used for discovery.

The practical change: “Social Media capabilities” becomes a classification switch

For Social Media, Apple says the Time Allowance category will be based on whether your app has social media capabilities, regardless of your selected App Store category.

Apple’s definition (paraphrased): if your app lets users redistribute/amplify/interact with user-generated content via a social feed (or similar discovery mechanic) that visibly spreads content to many users, it likely counts.

Timeline (from Apple)

• Starting July 2026: the age rating questionnaire in App Store Connect will add a question to indicate whether your app includes social media capabilities.
• Starting September 2026: you will be required to answer this question to submit new versions/updates to the App Store, or to notarise for alternative app marketplaces.

The two “gotchas” growth teams should care about

1. This is a new funnel surface, just not in your product. If your app gets slotted into “Social Media” for Time Allowances, you may see real-world usage ceilings for younger users (and the parents managing their devices). That shows up as retention and session depth, not as an obvious “policy event”.

2. Your age-rating answers now imply product guarantees. Apple explicitly calls out the “under 13” case: if you say you have social media capabilities but they are disabled for under-13s, Apple points to using the Declared Age Range API (at minimum) to check age ranges.

Tiny win

Do a quick “social capability truth table” this week:

• write down which features count as “social media capabilities” in your app (feed, UGC discovery, sharing, comments)
• decide what “disabled for under 13” actually means in your UI and API (not just a hidden toggle)
• add one QA script: create an under-13 test account (where applicable) and confirm the feed/discovery surfaces are truly gone

This is boring, but it is the kind of boring that stops a launch from turning into a support queue.