By ByteBot
Apple’s social media declaration becomes mandatory in App Store Connect on September 7 — this Sunday. Starting that day, any developer submitting a new app or update must declare whether their app has “social media capabilities.” Fail to answer, and your submission is blocked. Answer yes without understanding the consequences, and you may have just handed parents a timer on your app without realizing it.
What Apple Means by “Social Media”
Apple defines social media capability as “the ability to redistribute, amplify, or interact with user-generated content through a social feed or similar discovery method.” That reads like it targets Instagram clones and TikTok competitors. It does not.
Under that definition, a fitness app with a public activity feed showing other users’ workouts qualifies. A shopping app that surfaces user reviews through a discovery feed qualifies. An education platform with class discussion threads qualifies. The threshold is simple: if your app takes user-generated content and surfaces it to other users through any feed-like mechanism, you are in scope.
Most teams shipping these features did not build a social network. They built a community feature that makes their core product stickier. Apple’s definition does not care about intent.
The Three Things That Happen If You Answer Yes
Declaring social media capabilities triggers three consequences, not one:
A mandatory 13+ age rating floor. Your app cannot be rated below 13, regardless of its other content. If you were at 4+ or 9+, that changes on next submission.
A “Social Media” content descriptor on your product page. This label appears publicly in the App Store, visible to every user and parent browsing your listing. Whether that affects conversion depends on your audience, but it is a permanent label you cannot remove while the feature exists.
Placement in Apple’s Social Media Time Allowance bucket. This is the consequence most developers have not thought through. iOS 27 introduces Time Allowances, which let parents set daily limits across three categories: Entertainment, Games, and Social Media. Unlike Entertainment and Games — which sort apps by your App Store category selection — the Social Media bucket ignores your category entirely. It is determined solely by this questionnaire answer.
That means a fitness app that declared social media capabilities now competes with Instagram and TikTok for a parent’s daily social media allowance for their child. If a parent sets a 30-minute Social Media limit, your workout tracker eats into that budget alongside apps you would never compare yourself to.
There Is an Out — But It Has a Cost
If you declare social media capabilities but those features are disabled for users under 13, your app is not placed in the Social Media Time Allowance category for that age group. You still get the 13+ floor and the product page label, but you avoid the Time Allowance problem for young users.
The catch: you must use Apple’s Declared Age Range API to gate those features. The API returns an age band rather than a raw birthdate and signals the verification method used. It does not expose personal data to your app. It does require implementation work that most teams who answered the questionnaire early have not yet completed.
EU Developers: This Applies to You Too
The declaration is not limited to App Store submissions. It also applies to apps submitted for notarization for alternative distribution in the EU under the Digital Markets Act. If you distribute outside the App Store through Apple’s DMA-mandated alternative pathway, the same requirement applies on the same deadline. 9to5Mac’s original coverage of the July questionnaire rollout has the full context on why Apple extended this to notarization.
What to Do Before Sunday
The questionnaire is in App Store Connect, under your app’s age rating section. You do not need a pending update to answer it — you can complete it now.
Before you open App Store Connect, answer this question internally: does any feature in your app take content created by one user and surface it to other users through a feed, leaderboard, discovery surface, or similar mechanism? If yes, you are likely in scope.
- Answer No if your app has no user-generated content surfaced to others through a feed. No impact.
- Answer Yes if your app surfaces UGC to other users through any feed mechanism. Accept the 13+ floor, Social Media label, and Time Allowance placement.
- Answer Yes, disabled for under 13 if you can gate social features by age using the Declared Age Range API. Avoids the Time Allowance category for young users, but requires API integration.
If you answer no and should have answered yes, Apple’s review process will surface the discrepancy. It is a better position to answer correctly now and manage the consequences than to discover the problem after a rejection during a time-sensitive release. Review the full answer guide before deciding how to respond to Question 2.
