12 SEP 2026 — Apple now requires every developer to declare whether an app includes social media capabilities before they can ship an update. Say yes and the app gets a minimum age rating of 13+, a Social Media content descriptor on its store page, and a place in the Time Allowance category for Social Media. The definition is functional, so a great many apps that do not consider themselves social are about to discover that Apple does.
What counts as social media
Apple's wording is the thing to read rather than the summary. The declaration covers "the ability to redistribute, amplify, or interact with user-generated content through a social feed or similar discovery methods", and it gives the example of "feeds that allow users to engage with and amplify user-generated content through features such as views, likes, comments, and shares".
Nothing in that turns on what kind of app you are. It turns on whether you have a feed of user-generated content that other users can amplify.
The net is wide once you apply it. A fitness app whose activity feed lets friends give kudos qualifies on the same reading as a recipe app with user photos and comments, a shopping app whose reviews tab ranks by helpfulness, a game with a leaderboard and shareable clips, or a language-learning app with a community forum. Each has redistribution, amplification and a discovery surface, which makes each plausibly a 13+ app.
The category you chose does not matter
Apple states this explicitly: the Time Allowance category for Social Media "will be based on whether your app or game offers social media capabilities, regardless of the category selected in App Store Connect".
That sentence is the substance of the change. Time Allowance is the mechanism behind parental screen-time limits, and until now a parent capping "social media" was capping the apps that had filed themselves under a social category. A teenager's three hours of social feed inside an app listed under Health & Fitness or Shopping did not count against it.
Classifying by capability closes that gap, and it is hard to see another way of closing it. An app's chosen category reflects how it wants to be found; its features reflect what a child will actually encounter.
It reaches apps Apple does not distribute
The requirement applies to submissions to the App Store and to notarisation for distribution on alternative app marketplaces.
That second clause carries more weight than it appears to. Alternative marketplaces exist because European regulation required Apple to permit them, and notarisation is the security review Apple retained over apps it does not sell. Age-rating policy now travels through that channel too, which means Apple's definition of social media applies to apps distributed by its competitors.
European regulators will have to decide whether that is a safety measure extending sensibly across the platform or a content-policy lever operating through a security checkpoint.
The 13+ floor is the blunt part
A minimum rating sets a bar rather than judging what is behind it, which makes it crude by construction.
The same 13+ now attaches to an open feed where strangers post to strangers and to a closed one where a dozen friends compare step counts. The second carries a fraction of the risk that motivated the rule, and it takes the same rating and the same exclusion from younger users.
The reasoning is defensible. Telling an open feed from a closed one, or a moderated feed from an unmoderated one, takes judgement that no questionnaire can collect, and across millions of apps that judgement would be applied unevenly or not at all. Apple has chosen a rule it can enforce over one it could only approximate.
There is one route out, but it is narrow. A developer who declares social media capabilities but disables them for anyone under 13 is not placed in the Time Allowance category for Social Media for those users — but only if the app uses the Declared Age Range API, at minimum, to check how old its users are.
Read that as a trade rather than an exemption. Apple is offering relief from the category in exchange for age assurance, which means a developer who wants to keep younger users has to start determining their ages. That is a larger engineering and privacy commitment than accepting the rating, and for a small team with a comments field it will usually be the more expensive of the two options.
The cost still lands somewhere. Some low-risk apps will lose their under-13 audience, and the developers most affected are small ones who added a comments field years ago and must now choose between removing it, taking the rating, or building age checking.
Where national rules already point this way
This policy arrives in a region where national governments have been legislating toward the same goal by different means.
Indonesia has moved on a minimum age for social media, and Malaysia on age verification. Those are national rules directed at platforms. Apple's is a platform rule directed at apps, applied globally, and arriving first — which means that for a period, the operative definition of "social media" on a great many phones in Southeast Asia will be Apple's functional test rather than any statute.
For parents the practical effect is the useful one: a screen-time limit on social media is about to start catching apps it previously missed. For developers in the region the effect is a rating change they did not ask for, on an app that has not changed.
The declaration is the risk
The questionnaire itself opened on 9 July, which gave developers roughly two months before answers became mandatory. Developers are being asked to self-assess against a definition with real edges, and both wrong answers are costly.
Declare yes when you did not need to and you take a 13+ floor, exclusion from younger audiences, and a descriptor on your product page. Declare no when the feature arguably qualifies and you have made a false statement in a review process, which is the kind of finding that escalates beyond a rating correction.
For a borderline app, Apple has not published enough detail to resolve the question. The best guidance is to look at the feature the way a parent would. If a teenager can spend an hour in it consuming and amplifying what other users posted, the answer is probably yes whatever the app is called.
What to watch
The first thing to watch is how many ratings move. The story becomes measurable in the number of apps that shift from 4+ or 9+ to 13+ over the next few months, and whether they cluster in unexpected categories.
And whether enforcement is by declaration or by review. If Apple only checks the box you ticked, the policy is a self-report with a penalty attached. If reviewers start reclassifying apps that declared no, the definition will get tested quickly and in public.
View author profile → · Editorial policy
