Apple has introduced a new submission requirement: any app or game with social media capabilities — think feeds, comments, direct messaging, or user-to-user content sharing — must now declare that fact before Apple will accept a new version, and before it will notarize the app for distribution through alternative marketplaces. Apps with the capability get a new “Social Media” content descriptor added to their age rating on the App Store product page.
Why this catches founders off guard
Most teams don’t think of a lightweight comment section or an in-app activity feed as “social media” — it’s a feature, not a category. But Apple’s classification is capability-based, not intent-based: if the functionality exists, the declaration is required, regardless of whether social interaction is the app’s main purpose. A healthcare app with a patient community forum, a marketplace app with buyer-seller messaging, or a fitness app with shared workout feeds could all fall under this requirement without anyone on the team having planned for a “social app” review process.
The alternative marketplace angle
The requirement is tied explicitly to notarization for third-party app stores, which have been expanding in the EU and UK under regulatory pressure this year. That means the declaration isn’t just an App Store formality — it’s now a gate for any distribution route Apple controls, direct or otherwise.
So what
If you’re scoping a build with any user-generated content, messaging, or feed-style feature, add “does this trigger the social media descriptor” to your pre-submission checklist now, not the week you’re meant to ship. Getting the classification wrong risks a rejected submission and a delayed launch. This is exactly the kind of platform-compliance detail we build into project scoping from day one — see our iOS & Android development work, or get in touch if you’re planning a build with social or community features.