Apple just redefined 'social media' for the App Store — and it could reclassify apps that don't think of themselves that way

Apple added social media questions to the App Store Connect age rating questionnaire on 9 July 2026, and from September answers become mandatory — any app with a feed, comments, or user-generated content that others can discover gets a 13+ rating and a new Social Media label, whether or not 'social' is in the pitch.

Apple updated the age rating questionnaire in App Store Connect on 9 July 2026, adding questions about whether an app has “social media capabilities” — defined as the ability to redistribute, amplify, or interact with user-generated content through a feed or similar discovery method. Answering is optional today. From September 2026, it’s required for every new app, every update, and every app submitted for notarization on alternative marketplaces. Apps that qualify get a minimum 13+ age rating and a new Social Media content descriptor on their App Store listing, regardless of what category the app is filed under.

The definition is broader than “social media” sounds in a pitch deck. A fitness app with a community feed, a marketplace with buyer reviews others can browse, a habit tracker with a shared leaderboard, a healthcare app with a patient community forum — none of those would call themselves social networks, but each plausibly meets Apple’s bar for “redistribute, amplify, or interact with user-generated content through a feed.” The one carve-out: if the social features are disabled for under-13s, the app avoids the under-13 Time Allowance category, but the classification question and descriptor still apply above that age.

So what

If your product has any feature that surfaces one user’s content to other users — comments, feeds, reviews, shared boards, community discussion — this is worth checking against Apple’s definition before your next submission, not after a rejection or a surprise 13+ label lands on your store listing. It affects App Store search placement, parental control visibility, and the age gate your onboarding needs to handle. This is exactly the kind of platform-policy detail that gets missed when a build is scoped purely on features and not on App Store compliance — the kind of gap our iOS & Android work is built to catch before submission, not after. If you’re planning a release with any community or UGC element, get in touch and we’ll check it against the current rules before you build the wrong assumption in.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work