UK CMA: proposed commitments from Apple and Google on app review, ranking, data use, and iOS interoperability
A readable summary of the UK CMA’s proposed app store commitments, what ‘fair, objective and transparent’ could mean in practice, and why devs should care.
Original announcement (source): GOV.UK / Competition and Markets Authority - “CMA secures commitments from Apple and Google to improve fairness in app store processes and enhance iOS interoperability” (Feb 10, 2026)
The core idea
The UK’s Competition and Markets Authority (CMA) is consulting on a package of proposed commitments from Apple and Google aimed at improving fairness, transparency, and certainty for UK businesses that rely on the App Store and Google Play.
This matters because it targets the two areas that cause the most day-to-day pain for teams shipping apps:
- process opacity (reviews, rejections, ranking visibility)
- platform gatekeeping (what you can and cannot integrate with on iOS)
The CMA says views are welcome by 3 March 2026, and (subject to feedback) the commitments would take effect from 1 April 2026.
What the commitments cover (in plain English)
1) App review: fewer “because we said so” decisions
Apple and Google would commit to reviewing apps in a fair, objective and transparent way, and not disadvantaging apps that compete with their own.
Why it matters: if you have ever been stuck in a review loop, predictability is the difference between “marketing plan” and “missed launch”.
2) App ranking: less room for silent self-preferencing
Similar principle applied to store rankings: fair, objective, transparent, and no preferential treatment.
Why it matters: ranking shifts can look like an ASO problem when they are actually a platform policy or enforcement issue.
3) Data use: don’t weaponize developer data
The CMA calls out safeguarding data gathered during app review and not using it unfairly.
Why it matters: teams worry about asymmetric information, especially where a platform competes with third parties.
4) iOS interoperability: a clearer path to request access
Apple would improve how developers request interoperable access to iOS/iPadOS features and functionality, and commit to considering requests fairly and objectively.
Why it matters: this is the part that could unlock new product experiences (especially for fintech and wallets) if it turns into meaningful access, not just a better form.
The practical takeaway for growth teams
Policy changes are not abstract. They change:
- how risky a launch calendar is
- how you plan experiments (if approvals are unpredictable)
- what “distribution” even means in a market
Tiny win: if you operate in the UK, map your top 3 platform dependencies (payments, identity, wallets, deep links, alternative distribution). Then note which ones would benefit from clearer interoperability rules.
Read the original: https://www.gov.uk/government/news/cma-secures-commitments-from-apple-and-google-to-improve-fairness-in-app-store-processes-and-enhance-ios-interoperability
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.