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 secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

GitHub now reports how often developers act on Copilot code review comments

On 5 November 2026 GitHub added code review metrics, including an addressed rate, to the Copilot usage metrics API. For AI software development buyers, it is the first first-party number for how much AI review feedback is acted on.

Read ›

Dependabot can now keep AI agent skills and prompts up to date

GitHub's Dependabot gained Agent Package Manager (APM) support on 3 November 2026, treating AI agent skills, prompts and instructions as dependencies that need updating like any other software.

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