The App Store Checkbox That Ages Up Your App
There's a new question in App Store Connect, and starting this month you can't ship without answering it. Every developer submitting a new app, an update, or an app for notarization has to declare whether the app has "social media capabilities." Say yes and two things follow: a Social Media descriptor lands on your App Store page, and your app picks up a minimum 13+ age rating.
Apple added the question to the age rating questionnaire in July, which gave everyone a couple of months to think it over. September is when thinking stops.
The definition is wider than the name
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. Read that again, because it doesn't say "social network." It says feed.
That catches a lot of software that has never thought of itself as social. A fitness app with a leaderboard where people post workouts. A recipe app taking community submissions. A game with a scrolling wall of player creations. Apple has been clear that the Time Allowance category keys off capability, not off the category you picked in App Store Connect — calling yourself a productivity app buys you nothing.
Games get hit hardest. A title whose actual content is fine for a nine-year-old can end up at 13+ because someone bolted a community feed onto it.
There's a way out, and it costs something
One exemption exists. If your app has social features but shuts them off completely for users under 13, it drops out of the under-13 Social Media Time Allowance category.
The catch is what that takes. Go that route and you have to use Apple's Declared Age Range API, at minimum, to check a user's age band before those features switch on. Which means dodging the rating requires building age assurance into your app — you're reading an age range Apple hands you rather than collecting documents, but you're still adding a gate that wasn't there before.
So: accept the higher rating, or do the verification work. Neither is free, and both want engineering time this month.
Why now
This isn't happening in a vacuum. Meta just settled with US states for $18 billion over teen safety, agreeing to changes including a two-hour daily cap for under-18s that only a parent can lift. Governments are passing age-verification and under-16 rules on their own schedules. Age assurance is where the whole industry is currently being squeezed.
Apple's line throughout has been that it shouldn't be the one checking everyone's ID — the platform supplies the age signal, apps decide what to do with it. The Declared Age Range API is that argument written as code. The September deadline turns the argument into infrastructure, because now thousands of developers have a very concrete reason to adopt it.
What to actually do about it
Ask one question: does your app show user content to other users? If yes, you're answering yes, and 13+ is your floor unless you gate those features by age. And if you sell to schools, to families, or anywhere a 4+ rating is part of the pitch, that shift isn't a compliance detail — it's a product problem with a deadline attached.
The paperwork is a single question. The decision underneath it isn't.
Image: Brett Jordan, via Pexels
