The risk factor said it first. For years Apple's annual reports described App Store regulation as a general, forward-looking hazard. The fiscal 2025 Form 10-K, filed October 31, 2025, is more specific: it references an investigation into 'whether the Company's new contractual requirements for third-party app developers and app marketplaces' meet regulators' standards. Source: Apple Inc. Form 10-K (FY2025), surfaced via EdgarBeast, the SEC filing data API & evidence index.
Read that as a product-strategy signal, not just a legal one. The phrase 'new contractual requirements' is the tell. When jurisdictions forced Apple to permit alternative marketplaces and external app distribution, Apple did not simply open the gate; it wrote a new set of terms — core technology fees, entitlements, notarization rules — designed to keep the App Store's economics intact under the new regime. Those terms are now the regulated object.
That is the structural pattern worth naming. Each remedy Apple ships in response to a mandate becomes the surface area for the next inquiry. The 2024 10-K already flagged disputes over 'how developers may communicate and promote offers to end users' — the anti-steering fight. The 2025 language moves one layer up: from how developers talk to users, to the contract that governs whether they can use an alternative marketplace at all.
For the product itself, the consequence is that the App Store is becoming a regulated utility with a tariff schedule rather than a single take-it-or-leave-it storefront. Developers in the affected regions now choose among Apple's business terms; the 'new contractual requirements' are effectively a menu. The filing's disclosure tells you Apple expects that menu to be contested term by term.
The contrast with Apple's older framing is the whole story. The 2022 10-K could still say that 'for the vast majority of applications, developers keep all of the revenue they generate on the App Store.' That sentence reads as a defense of the status quo. By 2025 the defense has shifted from 'most developers pay nothing' to 'our compliance terms are lawful' — a quieter, more defensive posture that the risk factor records before any keynote will.
Follow the filing, not the demo. The next time Apple announces a developer-friendly policy 'where required by law,' the question to ask is which contractual requirement it adjusts — because that requirement, per Apple's own 10-K, is already under examination.