Google notified Android developers on 22 June 2026 that, to comply with a US court order in the Epic v. Google case, Play will begin making US app and game listings available to registered third-party Android app stores from 22 July 2026 — unless the developer opts out first.
What actually changes
Once the deadline passes, participating third-party stores can surface a developer’s listing — title, description, screenshots, metadata — to their own users. Downloads still route through Google Play under the same terms as a direct install; the app itself doesn’t move. Developers get three choices in Play Console’s Catalog Settings: publish to all third-party stores, manage each one individually, or opt out entirely. The default, if you do nothing, is inclusion.
Why this matters even though it’s US-only for now
The ruling only covers US listings today, but it’s the clearest sign yet that the “walled garden” model of app distribution is under real legal pressure, not just EU-driven (the EU’s Digital Markets Act forced similar changes to the App Store in 2024). Anyone building an Android product with US ambitions now has an active distribution decision to make before 22 July, not a passive default to accept — and precedent set here tends to travel to other jurisdictions eventually.
So what
If you’re commissioning or maintaining an Android app with any US user base, check your Play Console Catalog Settings before the deadline — the default behaviour may not be the one you want. And if you’re weighing whether iOS, Android or both make sense for a new build, distribution policy shifts like this are exactly the kind of thing that should factor into the platform conversation early, not after launch. See how we scope platform decisions on the services page, or get in touch to talk through your build.