Epic and Google just abandoned their app-store settlement — a $5,000-a-year fee is what's left standing

Epic and Google jointly withdrew their proposed alternative settlement on 15 July, leaving the original 2024 court injunction as the governing order for Google Play's third-party app store rollout on 22 July — and confirming the $5,000 annual fee those stores will pay to access Android app listings.

We flagged Google Play’s Catalog Interoperability change on 12 July: from 22 July, a US Android app’s store listing is shared automatically with any compliant third-party app store unless the developer opts out. What’s changed since then is the legal path underneath it. On 15 July, Epic and Google jointly withdrew the alternative settlement they’d proposed earlier this year, which means the original 2024 court injunction from the Epic v. Google antitrust case is now the operative order — not a negotiated compromise. And the commercial mechanics that fall out of that injunction are now public: third-party stores pay Google a $5,000 onboarding fee plus $5,000 a year for the policy and security reviews that let them plug into the Play catalog, on top of keeping malware under 1% of install attempts and operating exclusively within the US.

For app owners, the practical deadline hasn’t moved — it’s still 22 July, it’s still opt-out-by-default, and it’s still a five-minute check in Play Console under Settings > Catalog Settings. What’s new is confirmation that this isn’t a temporary arrangement pending further negotiation; it’s the settled legal and commercial shape of Android app distribution in the US going forward, and the $5,000 fee sets a real floor on how many “compliant” third-party stores are likely to show up asking for your listing.

So what

If you haven’t made the Catalog Settings call yet, this is confirmation it’s worth doing properly rather than waiting to see if the rules change again — they just got more permanent, not less. For most apps, wider listing exposure across a small number of serious, fee-paying storefronts is a reasonable trade; for apps built around single-storefront exclusivity or tight brand control, opting out explicitly is the safer default. If you need a hand auditing your app’s platform settings ahead of changes like this, see our iOS & Android development work or get in touch.

← 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