Ofcom has widened its review of app store fees, opening the evidence-gathering phase to submissions from developers as well as the platforms themselves. The regulator is examining the commission Apple and Google charge on in-app purchases and whether those terms amount to a barrier to entry for UK developers.

What has changed

Previously the review was focused on the terms offered to consumers. The widened scope brings in the commercial relationship between platforms and developers: commission rates, payment processing requirements, and the rules that prevent apps from directing users to cheaper payment options elsewhere.

Ofcom has also asked for evidence on how quickly apps are removed from stores and how much notice developers get, which is the complaint that surfaces most often in developer surveys.

Why it matters

The headline commission is 30 per cent, dropping to 15 per cent for smaller developers and for subscriptions after the first year. That is a large cut of revenue for a small software business, and it sits on top of payment processing, tax and marketing.

For a UK developer selling a £5 app, the difference between 30 per cent and 15 per cent is the difference between a viable product and a hobby.

The arguments the platforms make

The platforms argue that the commission pays for distribution, payment processing, fraud prevention and the review process, and that the rate is comparable to high street retail. They also point out that the alternative, side-loading, brings malware and payment fraud, which is the argument the Android verification rules are built on.

The counter-argument is that the commission is not a payment for service but a toll on a market with two gatekeepers, and that a developer cannot choose to be distributed without accepting it.

What Ofcom can actually do

Ofcom's powers here come from its role as the UK's digital markets regulator. It can open investigations, require information, and in principle impose conduct requirements or fines. What it cannot do quickly is change global app store economics, and any remedy will be contested.

The realistic outcomes are narrower than the headlines suggest: requirements on transparency, on notice periods for removal, and possibly on allowing external payment links in specific circumstances.

What developers should do now

  • Keep records of removal decisions and notice given, because evidence is what this process runs on
  • Check your revenue split and model a 15 per cent scenario, which is the most likely favourable outcome
  • Review your payment flow so that adding an external link later is a configuration change, not a rebuild

What consumers should take from it

If commission falls, prices may not. The more reliable consumer benefit is choice: being able to pay through a browser, and being able to move purchases between platforms. Our explainer on the Android app verification rules covers the security side of the same argument.

FAQ

Will app prices fall if the commission falls? Not automatically. Developers set prices against demand, not cost.

Is this the same as the EU's Digital Markets Act? Related but separate. The UK regime is its own process with its own remedies.

When will there be a decision? No timetable has been published, and consultations of this kind typically run for months.

The bottom line

A widened review is not a ruling, and the most useful thing about it is the evidence it forces into the open. For developers, that means documenting the things that currently go unrecorded. For everyone else, it is the beginning of a process that will be slow and narrower than expected.

Further reading: Ofcom's consultation documents and the CMA's digital markets work.