Does Your iOS App Count as Social Media Now? Apple’s September 2026 Rule Explained

Short answer: Apple’s new App Store question is not asking whether your app calls itself a social network. It asks whether people can redistribute, amplify, or interact with user-generated content through a social feed or a similar discovery system that spreads that content to many users.

That distinction can pull in apps that would never choose “Social Networking” as their App Store category: community products, creator tools, games with public feeds, hobby apps with discovery pages, or other products where likes, comments, reposts, reactions, search, or ranking help user posts reach a wider audience.

Apple added the questions to App Store Connect on July 9, 2026. Beginning in September 2026, developers will have to answer them when submitting a new app or update to the App Store, or when submitting an app for notarization for alternative distribution. Apple’s public notice does not specify an exact September day.

Rules check — August 11, 2026: This guide uses Apple’s current developer documentation. Apple says these features and requirements can change, and regional age-rating rules can differ.

What Apple means by “social media capability”

Apple’s definition is narrower than “anything with users” but broader than “an app whose main purpose is social networking.”

The current App Store Connect age-rating reference separates several capabilities:

The important point is that these are not interchangeable labels.

An app can have chat without operating a social feed. It can host user-generated content without giving users ways to amplify it. Conversely, an app whose primary App Store category is Education, Games, Productivity, Music, or something else can still have social-media capabilities.

Apple explicitly says its new Time Allowance classification for Social Media is based on the features the app offers, regardless of the app category selected in App Store Connect.

A practical five-question test

Before opening App Store Connect, map the product rather than guessing from its brand or category.

1. Can users create content other users can see?

If no, the social-media question is unlikely to be the main issue.

If yes, continue. Public posts, videos, photos, reviews, discussions, comments, profiles, clips, creations, or other user-made material can all be relevant depending on how they are distributed.

2. Is that content broadly discoverable?

Apple’s wording focuses on content that can be spread to many users, not merely a private exchange between two people.

A one-to-one message is therefore different from a public post that appears in a community feed or searchable discovery page.

3. Can users interact in ways that affect visibility or distribution?

Apple specifically lists examples such as:

• reposting;
• liking;
• commenting;
• reacting;
• making UGC more visible through a feed, community, search, or other sharing/discovery tools.

If those mechanics help content circulate beyond its original audience, the product is much closer to Apple’s definition.

4. Is there a feed or a feed-like discovery surface?

Do not interpret “feed” too literally.

Apple says “a social feed or similar discovery method.” A ranked community page, public search, trending section, creator-discovery view, or another surface that visibly spreads user content can matter even if the UI is not an endless TikTok-style feed.

5. Are those features available to users under 13?

If the app has social-media capabilities but disables them for people under 13, Apple provides a separate declaration path. That choice has implementation consequences, including age-range checks.

Examples: likely yes, likely no, and needs review

This is a product-screening framework, not an App Review ruling.

The safest internal question is not “Are we a social network?” It is:

Can a user’s content become more visible to many other users because of social interaction or discovery mechanics inside the app?

What changes if you answer yes

Apple’s Time Allowances announcement says an app that declares social-media capabilities will be placed in the Social Media Time Allowance category and receive a minimum age rating of 13+ under the standard path.

The app will also display a new Social Media content descriptor in the age-ratings section of its App Store product page.

Time Allowances are a parental-control feature in iOS 27, iPadOS 27, and macOS 27 or later. Apple describes them as age-tailored starting points that parents can adjust. Importantly, the Time Allowance category is separate from the App Store category used for discovery.

So changing an app’s primary category does not solve the classification question. The underlying capability is what matters.

What if social features are disabled for users under 13?

Apple has created a specific option for this case.

If social-media capabilities are disabled for anyone under 13:

• the app is not placed in the Social Media Time Allowance category for those under-13 users;
• the app remains in the Social Media Time Allowance category for users 13 and older;
• Apple says developers must use the Declared Age Range API at a minimum to check users’ age ranges before enabling the social features;
• the rest of the age-rating questionnaire still contributes to the app’s final rating, and Apple says this route may result in an overall rating below 13+ depending on the responses.

This is not the same as adding a birthday field and trusting whatever date the user types.

Apple’s Declared Age Range API lets an app request an age range rather than an exact birthdate. Developers specify age gates, and the system can return bounds such as under 13, 13–15, 16–17, or 18+, depending on the gates requested and the user’s response.

For children in Family Sharing, a parent or guardian can control whether age-range information is shared. Apple also notes that declaration methods and regulatory behaviour can vary by region.

The biggest implementation mistake: treating this as paperwork only

For some apps, answering the questionnaire truthfully may be all that is needed.

For apps choosing “social media disabled for users under 13,” however, there is product logic behind the declaration. The app needs a real age-aware gate before social features are enabled.

A simple implementation review should trace the user journey:

launch/sign-in → request or obtain permitted age range → determine allowed experience → enable/disable social features → handle declined or unavailable age data safely

The exact flow depends on the product and region, but the declaration should match what the app actually does.

If the App Store answer says under-13 users cannot access social capabilities while the app still exposes the feed before the age check, the metadata and product behaviour are no longer describing the same experience.

A pre-September submission checklist

Developers do not need to redesign every community feature automatically. They do need to classify the current product deliberately.

1. Inventory every UGC surface

List where users can create or publish:

• posts;
• comments;
• reviews;
• photos or videos;
• audio;
• shared creations;
• public profiles;
• forum topics;
• community messages.

2. Mark the distribution mechanics

For each surface, record whether users can:

• like or react;
• comment;
• repost/share;
• follow creators;
• rank or vote;
• search public UGC;
• discover popular or recommended UGC;
• make an item more visible through engagement.

This is the part most likely to answer Apple’s new question.

3. Separate private communication from public amplification

Do not automatically classify DMs, customer-support chat, team collaboration, and public social discovery as the same feature.

Apple’s own taxonomy separates Messaging and Chat, User-Generated Content, and Social Media.

4. Decide the under-13 policy

Choose the actual product policy before choosing the App Store answer.

If social features are available to everyone who otherwise meets the app’s age requirements, declare that accurately. If the product disables them for under-13 users, make sure the age-range gate exists and is tested.

5. Test the Declared Age Range path if you need it

Apple provides documentation and sandbox support for age assurance. Test at least:

• under-13 response;
• 13+ response;
• declined sharing where applicable;
• unavailable/error handling;
• feature access after an age range changes;
• parental-control behaviour relevant to the supported regions.

6. Re-open App Store Connect before the next submission

The questionnaire is already available. Waiting until the release is ready for review creates avoidable risk if the answer reveals an implementation gap.

Apple says the response becomes required for submissions beginning in September 2026, so teams shipping around that period should review it now rather than assume an old age-rating setup will carry forward unchanged.

Do likes or comments automatically make an app “social media”?

Not every isolated interaction should be classified from a single keyword.

Apple’s definition combines interaction with user-generated content and a feed or similar discovery method that visibly spreads content to many users.

That means product context matters.

A comment visible only inside a tiny private workspace is not the same distribution model as comments that push a public post into a recommendation feed. A star rating on a product page is not automatically equivalent to a follower-based creator network.

For borderline cases, document the actual mechanics and use Apple’s current wording rather than relying on examples from unrelated apps. If the classification materially affects a release, App Review or Apple Developer Support is a better escalation path than guessing from forum posts.

What remains uncertain

Three areas deserve caution as September approaches.

Apple has not published an exact September enforcement day

The public developer notices say “starting September 2026” or “beginning in September 2026.” As of August 11, the cited public pages do not give a specific calendar date.

Treat September submissions as in scope rather than planning around an assumed September 1 or September 30 cutoff.

Borderline discovery systems will require judgement

Apple gives clear examples—likes, comments, reactions, reposts, feeds, communities, search—but real products combine these in unusual ways. The presence of UGC alone does not answer every case.

Regional ratings can differ

Apple’s age-rating system includes region-specific rules. A product that receives one global rating can display a different regional rating where local classification requirements apply. Verify the calculated result in App Store Connect instead of assuming one number applies everywhere.

What to watch next

The useful signals over the next few weeks are practical rather than speculative:

1. whether Apple adds an exact September enforcement date;
2. whether App Store Connect or App Review documentation adds more examples for borderline social/discovery features;
3. whether the Declared Age Range implementation guidance changes as iOS 27 approaches general availability;
4. whether developers see new App Review feedback that clarifies how community, marketplace, creator, and game-discovery features are classified.

Until then, the low-risk move is to map the feature set against Apple’s published definition and make the product behaviour match the declaration.

Bottom line

Apple is not turning every app with comments into a social network. It is introducing a more explicit classification for apps where user-generated content is socially interacted with or amplified through feeds and discovery systems that spread it to many people.

For most teams, the next step is a 20-minute feature audit:

1. find every UGC surface;
2. mark every amplification/discovery mechanism;
3. separate private messaging from broad distribution;
4. decide whether under-13 users can access social features;
5. implement and test Declared Age Range where required;
6. answer the new App Store Connect questions before the September submission window catches the release team by surprise.

The app’s marketing category is not the deciding factor. Its actual interaction model is.

Sources

Checked August 11, 2026:

• Apple Developer — Age rating questionnaire now includes social media questions (July 9, 2026)
• Apple Developer — Introducing Time Allowances
• Apple Developer — What’s New for the App Store
• App Store Connect Help — Age rating values and definitions
• App Store Connect Help — Set an app age rating
• Apple Developer Documentation — Declared Age Range
• Apple Developer Documentation — Requesting people’s age range information in your app