The short answer
From 22 July 2026, approved third-party Android app stores in the US can distribute apps straight from the Google Play catalog, and a developer's US listings are enrolled automatically unless they opt out. It is the practical effect of Google dropping its fight over the 2024 injunction in Epic Games v. Google. Distribution terms and Google's service fee stay the same as a normal Play download — what changes is where your app can be installed.
For any team shipping to Android, this turns a one-storefront assumption into a multi-storefront reality. The immediate task is a deliberate opt-in-or-out decision before the date, plus the plumbing to track installs and push updates across stores. This is exactly the kind of release-and-distribution work that sits inside Android app development, not a marketing afterthought.
What happened on 15 July?
The long-running antitrust fight known as Epic Games v. Google — formally In re Google Play Store Antitrust Litigation — produced a 2024 jury verdict and injunction requiring Google to open Android distribution. Google had been seeking to modify how that injunction was implemented. On 15 July 2026, it stopped. In Google's words, "We've agreed with Epic to withdraw our motion to modify the US Court's injunction rather than prolonging this process which creates uncertainty."
Dropping the motion leaves the original order in force, and Google has now set a concrete switch-on date. Its own guidance to developers is blunt: "Starting on July 22, 2026, your US apps and games listing(s)…will be made available to third-party US Android app stores." For a decade the Play Store was, for practical purposes, the single front door to an Android device that had not been manually sideloaded. That assumption is what changes next week.
This is not the same as Android always having allowed sideloading. The novelty is that rival storefronts can now surface and install apps from Google's own catalog, using the same listing you already maintain in Google Play Console. A user who prefers a third-party store can get your app there, with your metadata, without you publishing to that store yourself.
How the Play Catalog Access Program works
Google's mechanism is the Play Catalog Access Program. Approved third-party stores can request access to the US Play catalog and offer those apps through their own storefronts. Critically, the apps are distributed "on the same terms as a direct Play download," and Google's service fee continues to apply — so the billing and revenue mechanics developers already know do not change by default. What the third-party store provides is an alternative discovery and install surface, not a different commercial deal.
The bar to become a participating store is not trivial. Reporting on the program indicates stores must confine distribution to US users, publish clear and non-discriminatory trust-and-safety policies, grant open access to all eligible developers, and keep malware below roughly 1% of install attempts. They also pay Google a fee for security and policy reviews — reported at around $5,000, split between an onboarding charge and an annual charge. Because the precise figures and conditions come from early reporting, confirm them against Google's official Play Console documentation before you build a plan around a specific number.
The opt-out default is the real story
The detail that matters most to engineering teams is not the legal history — it is the default. Multiple reports agree that US app and game listings become available to participating third-party stores automatically, unless the developer opts out. In other words, doing nothing is a decision: your app ships into the new distribution channel on 22 July by default.
For many products that is fine, even welcome — more reach at no change to your economics. But "do nothing" is the wrong way to arrive there. A regulated FinTech or HealthTech app, an enterprise-only app, or a brand that cares precisely where it appears may have good reasons to keep distribution consolidated, and those teams need to opt out deliberately before the date. Either way, the choice should be made on purpose, in the Play Console, not discovered after the fact in an analytics dashboard.
There is a second-order point too. Once your app can be installed from several storefronts, a single install-source assumption in your analytics, your attribution, and your update logic stops holding. If your release process quietly assumes "everyone got this from Google Play," now is the moment to check that assumption — because from next week it may not be true for a growing slice of your US users.
What it means for US & EU mobile teams
Strip away the courtroom framing and three practical signals remain. First, distribution is fragmenting, and it is not just a US story. In the EU, the Digital Markets Act has already forced Google and Apple to permit alternative app stores and sideloading. The US move is a different legal route to a similar outcome: the era of one dominant front door per platform is ending. Teams shipping to both markets should design for many storefronts rather than patch for each one as it appears.
Second, the work is in the pipeline, not the store listing. Multi-store distribution puts pressure on the unglamorous parts of mobile delivery: making sure a security patch or forced update reaches users regardless of where they installed, keeping install and revenue attribution coherent across sources, and verifying that features gated on Play services still behave. A well-structured cross-platform or native release process absorbs this; a brittle one springs leaks.
Third, discovery and trust become competitive levers. More storefronts means more places to be found — a genuine upside for games, content and consumer apps chasing reach — but also more places where a spoofed or repackaged clone could appear. Watching for unauthorised listings and keeping your legitimate build easy to identify is now part of the job. Match the distribution choice to the product, get the delivery pipeline right once, and 22 July becomes an opportunity rather than a fire drill.
A pre-22-July readiness checklist
None of this requires re-architecting your app — it is the diligence that turns a platform change into a routine review:
- Make the opt-in/opt-out call. Decide, per app, whether US catalog sharing fits your product, brand and compliance posture — and set it deliberately in Play Console before the date.
- Audit install attribution. Confirm your analytics can distinguish and correctly credit installs that arrive via third-party stores, so growth numbers stay trustworthy.
- Verify update delivery. Ensure forced updates and security patches reach users regardless of install source; do not assume the Play update path covers everyone.
- Check Play-services dependencies. Test that features relying on Play Integrity, billing or other Google services degrade gracefully where expected.
- Set up clone monitoring. Watch for unauthorised or repackaged listings of your app across stores, and make your legitimate build easy to verify.
- Write down the decision. Record which apps opted in or out and why, so an audit or a stakeholder question is a lookup, not an investigation.
This is not legal advice, and the right path depends on your product, your markets and your compliance obligations. But the direction is clear: Android distribution is opening up, the default is on, and the teams that move first will treat 22 July as a deliberate configuration choice — not something that happened to them.
Frequently asked questions
What changes for Android app distribution on 22 July 2026?
From 22 July 2026, Google's Play Catalog Access Program lets approved third-party Android app stores in the US distribute apps and games from the Google Play catalog on the same terms as a direct Play download, with Google's service fee still applying. In practice, a US developer's existing Play listings are made available to these rival storefronts automatically unless the developer opts out. The change stems from the 2024 injunction in Epic Games v. Google, which Google stopped contesting on 15 July 2026.
Do developers have to do anything, or are their apps auto-listed?
By default, US app and game listings become available to participating third-party stores automatically; developers who do not want their apps distributed that way must actively opt out through the Play Console. That makes the opt-out decision a deliberate one to take before 22 July rather than a setting to ignore. Distribution terms and Google's service fee remain the same as a standard Play download, so billing and revenue mechanics do not change by default.
Does this apply outside the United States?
The Play Catalog Access Program is US-only for now: third-party stores can only target US users, and only US listings are shared. However, the direction of travel is global. In the EU, the Digital Markets Act already forces Google and Apple to permit alternative app stores and sideloading, so teams shipping to both markets are increasingly managing distribution across several storefronts rather than one.
What are the requirements for a third-party store to join?
Reporting on the program indicates that participating stores must limit distribution to US users, publish clear and non-discriminatory trust-and-safety policies, offer open access to all eligible developers, keep malware below roughly 1% of install attempts, and pay Google a fee for security and policy reviews (reported at around $5,000, with an onboarding charge and an annual charge). Exact terms should be confirmed against Google's official Play Console documentation before planning around them.
Should mobile teams opt in or opt out of catalog sharing?
It depends on the product. Broader distribution can mean additional reach and discovery, especially for games and content apps, at the cost of less control over where the brand appears and how updates propagate. Regulated or security-sensitive apps may prefer to keep distribution consolidated. The important point is to decide deliberately before 22 July, instrument install attribution across stores, and make sure updates and security fixes reach users wherever they installed the app.
Sources
9to5Google — Google is opening the floodgates to third-party app stores on Android (15 July 2026)
Android Authority — Android's biggest store-within-a-store shakeup starts next week
TechTimes — Epic and Google jointly withdraw Play Store settlement; rival Android app stores to open July 22