China app store monopoly

Apple's China AIGC Declarations Turn the App Store Into a Compliance Gate, Which Makes Its Commission Dispute More Pressing

Apple now requires AIGC and security-assessment declarations from covered China apps. The rule has a statutory basis, but it adds to the gatekeeper power developers are contesting.

Apple's China AIGC Gate and the Open Fee Dispute People of Internet Research · China 48 Developers in SAMR complaint China-based iOS developers asked S… 25% Apple China commission now Down from 30% after a March 2026 c… 31 Jan 2027 Deadline for existing apps Existing covered apps must submit … 1 Sep 2025 Labeling rules in force since Article 14 sets the effective date… peopleofinternet.com
Apple's China AIGC Gate and the Open F… People of Internet Research · China 48 Developers in SAMR complaint 25% Apple China commission now 31 Jan 2027 Deadline for existing apps 1 Sep 2025 Labeling rules in force since peopleofinternet.com

Key Takeaways

Apple has added a compliance page to App Store Connect for apps distributed in mainland China. According to TechNode's report, which relays IT Home, developers of apps that offer AI-generated or synthetic content, such as chatbots, image and video generation, or voice and face editing, must submit AIGC filing declarations. So must developers of apps with features that need a security assessment, who must show that the assessment is complete. New apps must provide the information when they are submitted for review. Existing apps have until 31 January 2027.

This is not a case of Apple inventing a rule. It is Apple implementing one, and that distinction matters for how we judge it.

The strongest case for the requirement

Beijing has put app stores on the hook by statute. Article 7 of the Measures for Labeling AI-Generated Synthetic Content, issued by the Cyberspace Administration of China (CAC), the Ministry of Industry and Information Technology, the Ministry of Public Security and the National Radio and Television Administration, took effect on 1 September 2025. It says app distribution platforms must, at listing or review, require developers to state whether they provide AI generation or synthesis services. Where they do, the platform must verify the developer's labeling materials.

So a store that did nothing would be exposed. The supportive reading is simple. Apple is giving developers a structured, predictable way to comply, rather than leaving enforcement to ad hoc takedowns. Developers who have seen apps removed without explanation can reasonably prefer a published checklist to an opaque review. A clear declaration with a clear deadline is better than arbitrary rejection.

There is also a precedent for the alternative. In 2023, as the Interim Measures for the Administration of Generative AI Services approached their 15 August effective date, generative AI apps were pulled from the China App Store. A form is gentler than a purge.

Where the gatekeeper problem begins

The rule itself is state policy. What deserves scrutiny is the layering. Under the Interim Measures, Article 17 requires providers of generative AI services with public-opinion attributes or social-mobilisation capacity to complete security assessments and algorithm filings. Article 7 of the labeling measures asks the store only to verify labeling materials. TechNode reports that Apple's page goes further in practice. It accepts security-assessment records and reports, and developers using third-party AI technology may need to submit an authorisation or usage agreement. We could not confirm from Apple's own documentation how far the verification goes, and the fields and penalties are not described in the reporting. Both points will determine whether this is a narrow check or a broad one.

The risk is scope creep through a private chokepoint. The Interim Measures' penalty provision, Article 21, runs through regulators, and it ends in warnings, correction orders and, for serious cases, suspension of the service. An app-store gate is faster and less visible than any of that. A listing can be frozen before a developer has a hearing, a reasoned decision or a route to challenge it. Because the store is the only practical distribution channel on iOS, Apple's interpretation of an ambiguous category such as 'features needing a security assessment' effectively becomes law for that developer.

There is also a cost-of-compliance asymmetry. Large model providers with legal teams can assemble filings. A solo developer who wraps a licensed model for photo editing, or who adds an AI-written caption feature, faces the same 31 January deadline and a risk of delisting for getting a self-classification wrong. Proportionate regulation would scale the burden to the risk. A binary declaration with delisting as the penalty does not.

The timing and the open complaint

The change lands while a competition dispute is still open. In June 2026, 48 China-based iOS developers sent an open letter to the State Administration for Market Regulation, asking it to investigate Apple for abusing market dominance. They allege Apple failed to deliver a promised lowest commission rate for the Chinese market. Apple currently charges 25% on paid apps and in-app purchases in China, down from 30% after a cut in March. The Small Business and Mini Apps Partner rate fell from 15% to 12%. The developers argue that allowing third-party app stores, as Apple does in the EU under the Digital Markets Act, would push the effective commission as low as 5%. That 5% is their projection, not an Apple rate. As far as we could verify, no formal SAMR investigation has been announced.

The two matters are formally separate. They are not economically separate. Each new compliance function the state assigns to Apple's store strengthens the case that the store is an indispensable control point. It also gives Apple a reason to present itself as a cooperative partner of regulators rather than a target of them. We have no evidence that this is deliberate, and we do not claim it is. But a gatekeeper that enforces state rules at the distribution layer is harder to unwind with competition remedies than one that merely sells access.

What proportionate design would look like

First, publish the criteria. Developers need a plain-language definition of which features count as requiring a security assessment, and a statement of which specific measure triggers each requirement. Second, offer an appeal path. A delisting for a classification dispute should come with a stated reason and a time-limited review. Third, give a grace period for good-faith errors, since correction orders are the regulator's own default remedy under Article 21 of the Interim Measures. Fourth, keep the compliance function from becoming a moat. If alternative distribution were allowed, as the developers' letter requests, compliance duties could attach to the developer and to each distributor, rather than to one store that is also the toll collector.

None of this requires rejecting the aim of labelling synthetic content, which has a legitimate transparency rationale. The concern is the architecture. When one company controls distribution, enforces state rules, and sets a 25% toll, the compliance form and the commission rate stop being separate issues.

What to watch

Three things will settle this. First, whether Apple publishes its own developer documentation, since the current account is secondhand. Second, how many apps are delisted after 31 January 2027, and whether any arrive with an explanation. Third, whether SAMR acts on the June complaint. Until then, developers should treat the declaration as a legal filing, not a form.

Sources & Citations

  1. CAC: Measures for Labeling AI-Generated Synthetic Content (2025)
  2. CAC: Interim Measures for the Administration of Generative AI Services (2023)
  3. TechNode: Apple adds generative AI compliance filings in China
  4. MacRumors: Chinese developers' SAMR complaint against Apple