Google just cut Play Store fees and opened Android to rival app stores — what it changes for commissioning

Google has replaced its flat 30% Play Store fee with a lower, market-specific billing fee (5% in the UK) and opened Android to registered third-party app stores, rolling out in the UK, US and EEA from 30 June 2026 — a real shift in the economics of shipping and monetising a mobile app.

Google has overhauled how Android apps get distributed and paid for. The old flat 30% Play Store commission is gone, replaced by a lower, market-specific billing fee — 5% in the UK, US and EEA — and developers can now choose Google Play Billing, an alternative in-app payment processor, or simply link out to their own website checkout. Alongside that, a new “Registered App Stores” programme lets rival Android app stores that pass Google’s safety benchmarks offer a simplified install flow, instead of the friction-heavy sideloading process that discouraged most users from ever leaving Google Play. The changes started rolling out on 30 June 2026, with UK developers among the first covered.

This is the practical end of the Google v. Epic dispute, and it changes the commercial maths of an Android app before a single line of code is written. A subscription or in-app-purchase business that assumed a 30% cut now has room to route payments elsewhere and keep more margin — but it also means more app stores in the ecosystem, more places an app needs to appear, and more billing paths to test and support.

So what

If you’re scoping a new Android app or re-negotiating monetisation on an existing one, this is the moment to revisit your billing architecture rather than defaulting to whatever was standard eighteen months ago — the fee structure that made that decision has changed under you. It’s a conversation worth having early, at the platform and API design stage, not after launch. Talk to us about iOS & Android development that accounts for this from day one, or get in touch to scope a project.

← All research

More research.

MAI Code 2 and MAI Code 2 Flash arrive in GitHub Copilot, including a model for free-plan users

GitHub has added Microsoft's MAI Code 2 and MAI Code 2 Flash to Copilot across editors, the CLI, the cloud agent and mobile, with administrators able to control access through model policy.

Read ›

GitHub Copilot team customizations are generally available: set default agent plugins for a whole team

GitHub has made team customizations generally available, so team maintainers and organisation owners can set approved Copilot agent plugins as defaults for every member of a team.

Read ›

Claude Code 2.1.330: scheduled tasks run for 30 days, risky rm commands ask first, and enterprise sign-in arrives

Claude Code 2.1.330 extends scheduled tasks and /loop from 7 to 30 days, makes more destructive rm commands ask for approval, and adds sign-in for organisations managed in Anthropic's Enterprise Admin Console.

Read ›

OpenAI's GPT-6.2 Astra and Sol are generally available in GitHub Copilot, with a code review focus

GitHub made OpenAI's GPT-6.2 Astra and GPT-6.2 Sol generally available in Copilot for agentic coding and code review. GitHub reports early tests catching more real issues.

Read ›

Copilot code review adds adaptive effort and secret detection in public preview

GitHub's Copilot code review can now choose Lite, Balanced or Max effort per pull request and flag exposed secrets, both in public preview. Azure DevOps support is generally available.

Read ›

Claude Code 2.1.329: /code-review now covers the whole branch, and saved scheduled tasks need rescheduling

Claude Code 2.1.329 makes /code-review review the whole branch against the default branch and adds fixes for Code Mode and sign-in. Saved scheduled tasks mostly need setting up again.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work