iOS 27 App Store requirements: age ratings and SDK deadline

Two Apple changes landed this month that turn routine app maintenance into a planning question. From September 2026, App Store Connect requires answers to new age-rating questions about social media capabilities before any new app or update is accepted. And from April 2027, every iOS app uploaded must be built with the iOS 27 SDK. Neither of these iOS 27 App Store requirements is difficult. Both can block a release that someone assumed was a quick fix.

The questionnaire you now have to answer

On 9 July 2026, Apple Developer News announced that the age rating questionnaire in App Store Connect includes questions about an app's social media capabilities. Apple's wording on timing is explicit: beginning in September 2026, responses will be required when submitting new apps or updates to the App Store, or when submitting apps for notarisation for alternative distribution.

Apple defines a social media capability as the ability to redistribute, amplify or interact with user-generated content through a social feed or similar discovery method.

The reason is Time Allowances, a parental control in iOS 27, iPadOS 27 and macOS 27 that gives parents more flexible ways to manage time their children spend in apps across categories including entertainment, games and social media. For the system to apply those limits correctly, Apple needs to know which apps behave like social media.

Why a form can block a hotfix

The questionnaire itself takes minutes. The problem is when it is first encountered.

Consider the usual pattern. A production bug is found on a Friday afternoon, a fix is built, and the submission reaches App Store Connect — where it cannot proceed until someone answers questions about social features. The developer submitting the build often cannot answer them, because whether a community tab, a comments section or a shared activity feed counts as a "social feed or similar discovery method" is a product and compliance judgement, not a technical one.

So the practical advice is simple: answer the questionnaire now, deliberately, for every app you maintain, rather than at the moment an urgent update is waiting on it.

The definition is broader than it sounds

Many apps that nobody would describe as social media have features that may fit Apple's definition. Deciding requires honesty about what the app does.

• User reviews and ratings that other users browse.
• Community or discussion sections, including those inside commerce, learning or fitness apps.
• Activity feeds showing what other users have done or shared.
• Shared content such as user-uploaded photos, recipes or routines surfaced to other users.
• Comment threads on content, even if the main content is produced by the business.

Whether any of these crosses Apple's line depends on whether user content is redistributed or amplified through a feed or discovery mechanism. A private note visible only to its author is not the same thing as a public comment surfaced to strangers. Where it is genuinely unclear, it is worth writing down the reasoning behind the answer, so the next person to submit an update does not reopen the question.

Getting it wrong in either direction has a cost. Under-declaring risks review problems and parental controls that do not apply as parents expect. Over-declaring may mean an app is grouped with social media under a child's time limit when it should not be — a real consideration for education and family apps.

The April 2027 SDK deadline

The second change was announced on 9 September, when Apple opened submissions for apps built for iOS 27, iPadOS 27, macOS 27, tvOS 27, visionOS 27 and watchOS 27. Apple also set minimum requirements: starting in April 2027, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 27 and iPadOS 27 SDK or later, with equivalent rules for tvOS, visionOS and watchOS.

This is an annual pattern, and it is still the deadline most often underestimated. Building against a new SDK means moving to the corresponding Xcode, updating third-party dependencies that may not yet support it, re-testing on current devices, and dealing with behaviour changes and new design conventions that arrive with the SDK. For an app with native modules or an older cross-platform framework version, that can take weeks rather than days.

9to5Mac's coverage of the submissions opening is a useful reminder of the timing: the new tooling is available now, and the months before April are the comfortable window.

Meeting the iOS 27 App Store requirements: a short plan

1. List every iOS app you maintain, including internal and white-label apps, and who has App Store Connect access for each.
2. Answer the age-rating questionnaire now for each app, with product and compliance input, and record the reasoning.
3. Schedule the iOS 27 SDK migration well before April 2027, starting with a build on the new Xcode to discover dependency problems early.
4. Check third-party SDKs — analytics, payments, maps, crash reporting — for iOS 27 support.
5. Run a full regression on current devices, including new hardware such as the dual-screen models that need their own layout work, as we covered in foldable iPhone development.

If your builds do not depend on a single machine, the SDK move is easier to schedule; that was part of the case for cloud builds without a Mac. Either way, keeping apps current with platform requirements is the ongoing cost of owning them — the maintenance side of iOS app development that decides whether an urgent fix ships in hours or waits on a form.