Apple pushes back on the UK’s ‘steering’ proposal: why payments is turning into a UX and support problem
Per a Reuters report via 9to5Mac (July 29, 2026), Apple is arguing the UK CMA’s proposed ‘steering’ rules are effectively price regulation. For app teams, the practical work is not the policy debate. It’s the link-out UX, trust, and support surface area if steering becomes real.
Original post (source): 9to5Mac - “Apple pushes back against UK proposal to loosen App Store payment rules” (published July 29, 2026)
What’s happening (at a high level)
9to5Mac is summarising a Reuters report: Apple submitted a response to a UK Competition and Markets Authority (CMA) consultation, pushing back on proposed rules that would:
- allow developers to link users to alternative payment options (“steering”)
- allow Apple/Google to still charge a commission, but only if it is judged “fair and reasonable”
Apple’s position, per Reuters, is that this becomes a kind of price regulation and a highly intrusive form of business management.
The practical impact for app teams
Whether you love or hate the policy direction, the “work” for operators is downstream.
If steering becomes more viable in the UK, you get a new stack of problems that are mostly not legal problems:
1) Link-out UX becomes part of your conversion funnel
You are effectively introducing a new step between intent and purchase.
That step has to handle:
- trust (“am I about to get scammed?”)
- continuity (“am I still buying the same thing?”)
- cross-device reality (people click on mobile, finish on desktop)
2) Measurement gets messy fast
If the purchase happens off-platform, you will feel the pain in:
- attribution and cohorting
- refund/chargeback reconciliation
- “user says they paid but app is locked” support tickets
3) Support volume is the hidden tax
Even a small % of “payment confusion” creates a lot of tickets.
This is where the policy change becomes a cost issue. The question is not just “do we save fees”. It is “what does it do to support load, and what happens to refund rates”.
Tiny win
Write a UK-only steering readiness checklist (one page):
- the exact link-out copy you would use
- how you will confirm entitlement inside the app (including edge cases)
- the three support macros you will need on day 1
If you cannot answer those, you are not ready to treat steering as a free win.
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.