13+: The New Rating Floor for Apps With Social Feeds, Starting September

Apple will require a 13+ age rating for any app that includes a social feed, starting this September, according to PPC Land's report on the change moving through App Store Connect. We build apps that touch feeds and comment threads, so the story landed on our desk the usual way: a link in Slack, then an hour spent re-reading our own age rating questionnaires.

PPC Land's headline says it plainly: Apple forces a 13+ rating on apps with social feeds from September. That's the whole claim we're working from, and we're treating it as a floor rather than a ceiling until Apple publishes its own wording on the change.

What Counts as a Social Feed Under the New Rule?

The report doesn't hand down a formal definition, so we're reading "social feed" the way a reviewer likely will: a scrolling timeline of other people's posts, open comment threads, or anything that surfaces user-generated content back to a wider audience inside the app. A private message thread between two people probably sits outside that. A public wall where strangers can post and reply almost certainly sits inside it. Until documentation catches up with the policy, we're erring toward the broader reading for anything we ship.

Where Does the 13+ Threshold Show Up?

PPC Land's piece points to App Store Connect as the mechanism, which tracks with how age ratings have always worked there: developers answer a content questionnaire, and the system calculates a rating from those answers. This change raises the floor for one specific trigger — the presence of a social feed — rather than rewriting the whole form. For teams that already answered yes to feed-related questions, the new minimum should apply once the update takes effect.

How Are We Rechecking Our Own App Queue?

Field notes, honestly: we pulled every app we maintain, opened App Store Connect, and reread each questionnaire line by line. We flagged anything with comments, shared boards, or a feed of other users' content, including features we'd treated as secondary rather than central. A couple of older answers needed a second look because the feature set had grown since we first filed them. None of this required new code. It required someone sitting with the questionnaire and answering it honestly, which is the discipline this policy seems built to force.

Which Questions Does the Report Leave Open?

PPC Land's report doesn't say whether Apple will retroactively flag apps already live with feeds, or whether September is a hard cutoff for new submissions only. It also doesn't say how strictly reviewers will police edge cases, like a comment section on a single post versus a full scrolling timeline. We're watching for Apple's own documentation rather than guessing at enforcement details the source doesn't cover.

Why a Rating Floor Matters to a Small Studio

A rating bump isn't a redesign, but it changes who can download an app and how a listing reads to a parent scanning search results. For a team our size, the honest move is treating the questionnaire the same way we'd treat any other store requirement: answer it accurately, recheck it when a feature changes, and don't wait for a rejection to discover the floor moved under us.

When Do We Lock This Into Our Launch Checklist?

We're adding the 13+ check to every launch checklist going forward, next to the usual device-permission and screenshot review. It's the same instinct that pushed us to run down what a widely shared quote card actually said before treating it as fact, or to look twice at a keyboard complaint before assuming it applied everywhere. A policy change from Apple deserves the same patience: read the primary report, update the checklist, and recheck before the deadline instead of after a rejection notice.