The EU just fined Google €890m for blocking Play Store 'steering' — what it changes for app pricing

The European Commission fined Google €890 million on 23 July 2026 for Digital Markets Act breaches, including €430 million specifically for stopping Android app developers steering users to cheaper payment options outside Google Play — a decision that will reshape 'app store fees' and 'alternative billing' search activity for anyone commissioning a mobile app.

On 23 July 2026 the European Commission fined Google €890 million for Digital Markets Act violations — €460 million for favouring its own search services, €430 million specifically for preventing Android app developers from directing users to cheaper payment options outside Google Play. It’s the first DMA penalty of this size against Google, and the Commission has given it 60 days to end the restrictions or face ongoing penalties of up to 5% of worldwide turnover.

The Play Store half of the ruling is the part that matters for anyone building or commissioning a mobile app. “Steering” — telling a user inside your app that they can pay less by going to your website — has been technically restricted or buried behind friction on Android for years, mirroring Apple’s equivalent App Store rules. This fine, arriving three months after Google opened its Play catalogue to third-party US app stores and started cutting service fees for developers using external billing, is the clearest signal yet that the regulatory pressure pushing both major platforms toward genuinely open payment steering isn’t slowing down.

For founders weighing app economics, that matters beyond the headline. A platform where you can legally tell users “pay 15-30% less on our website” changes the calculation on whether a native app, a web app, or both makes sense for a given product — and it changes what “app store fees” should mean in a build budget in 2026 versus two years ago.

So what

If you’re scoping a new mobile product, this is worth factoring into the commissioning conversation now rather than after launch: steering rules, alternative billing support, and platform fee structures are moving targets across both iOS and Android, and the right architecture decision today depends on where those rules land, not where they’ve been. That’s exactly the kind of platform-strategy question we work through with clients before writing a line of code — see how we approach iOS & Android development, or get in touch if you’re weighing up platform and payment strategy for a new build.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

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