SerpApi.Org
Android users in the United States can now find and download third-party app stores directly from within Google Play for the first time — but every app those stores surface will still install through Google's own infrastructure, at Google's prices, under Google's security pipeline. That is not a limitation that slipped through the cracks. It is the deliberate architecture of the Play Catalog Access Program, which went live today, July 22, 2026, as the first court-ordered catalog interoperability mandate ever imposed on a major U.S. mobile platform.
The structural implication matters: rival stores that enroll in the program become competing discovery surfaces — they can surface apps and let users initiate downloads — but they cannot compete on the delivery mechanism, the security scanning, or the fee. Every download still routes through the Play Store's Inline Install API, through Google Play Protect's scanning pipeline, and at the service fee rates that Google sets. Whether that architecture represents the beginning of genuine Android app store competition, or a court-ordered arrangement that preserves Google's most profitable controls while appearing to open up, will be the defining question of the months ahead.
A Six-Year Legal Battle Produced a Structural Remedy
The program's origin is a sequence of courtroom defeats that Google could not reverse. In August 2020, Epic Games deliberately added a direct payment option to Fortnite on Android, bypassing Google's mandatory billing system. Google removed Fortnite the same day. Epic immediately filed suit, seeking not damages but structural change — access to a platform it argued Google had illegally monopolized.
In December 2023, a nine-person federal jury in San Francisco found for Epic on all counts, ruling that Google had illegally monopolized both Android app distribution and in-app billing. Unlike the parallel Epic case against Apple — in which a judge largely ruled for Apple — the Google case was decided by a jury that found the conduct categorically anticompetitive. The verdict covered both app distribution and payment processing. Google's internal "Project Hug" subsidy program, which had paid phone manufacturers and carriers to keep rival stores off devices or degraded, was central evidence at trial.
Judge James Donato of the U.S. District Court for the Northern District of California issued a permanent injunction in October 2024. On July 31, 2025, the Ninth Circuit unanimously affirmed both the jury verdict and the injunction. What distinguishes this remedy from prior regulatory actions in the app-store space — in Europe, South Korea, and India — is its scope. Those earlier actions targeted payment steering, allowing developers to point users toward cheaper payment options while leaving the distribution architecture intact. The Donato injunction attacked the architecture itself.
What nearly changed that: in November 2025, Google and Epic announced a proposed settlement that would have modified the injunction's terms. By March 4, 2026, they had filed revised proposed modifications. But the court's own independent economist, Professor Nancy Rose of MIT and formerly Deputy Assistant Attorney General at the DOJ's Antitrust Division, filed a declaration on July 12, 2026, finding that the proposed settlement could eliminate important competitive provisions embedded in the original injunction. On July 15, 2026, both Google and Epic jointly withdrew their proposed modification.
Google's statement at the time: the company withdrew the motion "rather than prolonging this process which creates uncertainty for the ecosystem," adding that it "continues to comply with the US Court's injunction." The governing legal order today is Judge Donato's October 2024 permanent injunction — not a negotiated settlement.
What Rival Stores Get — and What Google Keeps
The program operates in two technical layers. The first is catalog data. Google produces a daily snapshot of the Play Store catalog — app names, icons, descriptions, screenshots, and metadata — and makes it available via Google Cloud Storage. Enrolled stores access this via a Google Cloud Storage URI, using the gsutil tool or programmatic API calls. Optional intra-day APIs for more frequent updates are promised but not yet published as of today's launch.
The second layer is where the architectural asymmetry becomes concrete. When a user finds an app through an enrolled third-party store and taps to install, the store triggers an Android Intent pointing to Google Play's package (com.android.vending) using a deep link formatted as a Play Store URL. This is the Inline Install API. The Google Play app receives the intent and handles the actual download. The third-party store is not in the installation chain — it surfaces the listing and hands off the install request. Google Play Protect scanning, Google's signing key verification, and Google's service fee all apply to the resulting download, identical to a direct Play Store install.
Stores are required to disclose to users that apps in their catalog come from Google Play before initiating the Inline Install API. They cannot charge users additional fees for downloading catalog-access apps. They cannot host APKs independently. The integration guide for third-party stores using the Inline Install API is listed as "coming soon" in today's official documentation — meaning the actual install pipeline integration for enrolled stores may not be technically available from day one even as the catalog data is.
Who Qualifies and What Enrollment Costs
Third-party stores that want catalog access face a specific requirements bar. They must be U.S.-based, registered as an organization, and operate as open marketplaces with publicly accessible, non-discriminatory policies that mirror Google Play's across restricted content, intellectual property, privacy, malware, ads, and user experience categories. They must also offer their own apps — not only catalog-access content — to qualify as legitimate storefronts rather than catalog fronts.
The security threshold is measurable: stores cannot have a malware installation-attempt rate above one percent, measured across all devices globally over a rolling 30-day window. Exceeding it can result in loss of catalog access.
The cost is higher than the draft initially characterized. Enrollment requires $5,000 upfront for a security and policy review during onboarding, plus $5,000 annually to maintain catalog access — a total of $10,000 in the first year. Google notified developers on June 22, 2026, that their listings would begin flowing to qualifying stores by default on July 22, unless they actively opted out.
How Developers Control Their Participation
Three settings are available through Play Console under "Settings > Catalog Settings": publish all listings to all enrolled stores, manage access on a per-store basis, or opt out entirely. Developers can change this preference at any time, including after today's launch.
For developers with content-sensitive apps — age ratings, regional restrictions, enterprise-only distribution — the opt-out warrants consideration. Enrolled third-party stores must maintain their own content policies, not Google Play's. A store that passes Google's malware and fraud thresholds may still apply different standards for age ratings, parental controls, or regional content restrictions. Developers whose apps carry specific policy requirements should confirm that any store displaying their listing applies equivalent safeguards before remaining in the default opt-in.
Enterprise or business-to-business developers with apps intended for specific organizations may also find the opt-out appropriate, regardless of content sensitivity. Apps designed for internal distribution simply may not belong in consumer-facing alternative storefronts.
Commission Rates: What the Fee Structure Actually Looks Like
The fee restructuring announced March 4, 2026, and effective from June 30, 2026, in the U.S., UK, and European Economic Area replaced the prior flat 30 percent commission model. The new structure is tiered rather than flat. Developers pay 10 percent on their first $1 million in annual revenue, regardless of payment method. Above that threshold, the service fee is 20 percent on new installs and 25 percent on existing installs. An additional 5 percent billing fee applies only when developers use Google Play's own payment system — developers routing payments through alternative billing providers avoid that charge.
For downloads completed through catalog-access stores, Google's same service fees apply. The catalog access mechanism adds no additional commission layer, but also provides no fee reduction. A user who finds an app through a rival store and installs it through the Inline Install API pays the same transaction fees to Google as a user who found the same app through Google Play directly.
The geographic rollout of the new fee structure extends through 2027: Australia, Japan, and South Korea are scheduled to follow by the end of 2026, with global completion targeted for September 2027.
What Changes for Users, and What Doesn't
Starting today, users in the United States can find qualifying third-party Android app stores listed inside Google Play and download them directly — the same way they would download any other app. Previously, installing an alternative Android store required navigating the sideloading process: enabling "install from unknown sources" in device settings, locating the store's APK from an external web source, and manually installing it. That friction kept rival stores functionally invisible to most Android users.
The practical significance of that change depends on whether rival stores build experiences compelling enough to draw users who have years of habit with Google Play's interface and recommendation algorithms. Catalog access solves what market economists call the cold-start problem: a new two-sided marketplace needs both content (apps) and users simultaneously, and neither arrives first. By giving enrolled stores access to Google Play's full catalog from day one, the injunction dissolved the chicken-and-egg barrier that has prevented any rival store from scaling meaningfully against Google Play on Android.
What catalog access does not solve is the warm-start problem of established habit, account integration, and payment credential storage. Users who already have payment methods saved in Google Play, app purchase history, and subscription management there have no immediate incentive to switch storefronts even if a competing store is now visible. Competing stores will need to differentiate on discovery quality, curation, community, exclusive content, or developer relationships to change that behavior.
A Parallel Tension: The Developer Registration Mandate
The Play Catalog Access Program opens one door to alternative Android distribution. A separate Google policy, announced in late 2025 and set to take effect in September 2026, could close another. Under that policy, all Android developers would be required to register with Google, provide government identification, and pay a fee before their apps can be installed on any certified Android device — including apps distributed entirely outside Google Play, through stores like F-Droid, the Amazon Appstore, or Samsung's Galaxy Store.
F-Droid, the nonprofit open-source Android app repository that reviews apps to exclude advertisements and trackers, has said the registration mandate would effectively end its ability to operate. The Electronic Frontier Foundation, the Free Software Foundation, Article 19, Fastmail, and Vivaldi are among the organizations that signed an open letter to Alphabet's leadership opposing the mandate, arguing that Google is extending gatekeeping authority beyond its own marketplace into distribution channels where it has no legitimate operational role.
Google has said the policy is a security measure designed to stop malware. Critics note that Google Play itself has repeatedly hosted malware: in 2025, 224 malicious apps carrying an ad fraud campaign were removed from the Play Store after more than 38 million total downloads. The developer registration mandate is currently under active opposition from regulators including the European Commission's DMA enforcement team.
What the Apple Case Adds to the Picture
The Google Play catalog opening lands alongside an ongoing confrontation at Apple that adds legal weight to the same structural argument. Apple was found in contempt of its own injunction in the parallel Epic v. Apple case after implementing a 27 percent commission on external purchases in a way that rendered its anti-steering provisions ineffective. The Ninth Circuit upheld that contempt finding in December 2025. Apple's appeal is before the Supreme Court, which granted certiorari in June 2026 for arguments expected later this year or in early 2027.
Together, the two cases establish that both dominant U.S. mobile platforms are now under federal court orders requiring structural changes to how they operate. For regulators in Europe, the UK, Japan, and South Korea who are enforcing their own open-platform mandates, the Play Catalog Access architecture provides the first working implementation reference for what catalog interoperability at scale actually looks like — with its capabilities and its limitations both visible.
The Donato injunction's legacy is what it attacked: not a commission rate, but the architectural barriers that made genuine competition against Google Play structurally impossible. Whether the architecture the program puts in place proves sufficient to enable that competition, or whether the Inline Install pipeline and the concurrent developer registration mandate together create new barriers to replace the ones the courts removed, are questions that will take years of market behavior to answer.
Frequently Asked Questions
What is the Play Catalog Access Program, and how is it technically different from sideloading?
The Play Catalog Access Program gives enrolled U.S. Android stores daily snapshots of Google Play's full app catalog — names, icons, descriptions, screenshots — via Google Cloud Storage. When a user taps to install an app through one of those stores, the store triggers an Android Intent pointing to Google Play's own app (com.android.vending) via the Inline Install API. Google Play handles the actual download, running Play Protect scanning and applying its service fee exactly as it would for a direct Play Store install. Sideloading, by contrast, involves installing an APK directly from a non-Google source without Play's infrastructure. The practical difference: catalog access is architecturally safer than traditional sideloading because Google's security pipeline remains in the chain — but it also means rival stores cannot differentiate on the delivery mechanism itself.
What happened to the Google-Epic settlement that was announced in early 2026?
Google and Epic announced a proposed modification to the injunction in March 2026, but Judge Donato had appointed MIT economist Nancy Rose as an independent court expert to evaluate whether any settlement served the public interest, not just the two parties. On July 12, 2026, Rose filed a declaration finding the proposed settlement could eliminate key competitive provisions. On July 15, both companies jointly withdrew the proposed modification. The governing order today is Judge Donato's original October 2024 permanent injunction. The fee restructuring (20 percent on new installs, 10 percent on subscriptions, plus optional 5 percent billing fee) was announced separately by Google in March 2026 as a global business policy and went into effect June 30, 2026, regardless of the settlement outcome.
Can developers stop their apps from appearing in rival stores?
Yes. Through Play Console's Settings under "Catalog Settings," developers can choose to publish to all enrolled stores, manage access per-store individually, or opt out entirely. The default is publication to all enrolled stores — developers who took no action before July 22 are included by default. The preference can be changed at any time, and the opt-out takes effect immediately. Developers with apps carrying age ratings, regional restrictions, or enterprise-only distribution should review whether their content policies match those of any enrolled rival store before remaining in the default state.
What does "Google still controls every download" actually mean for users?
It means the competitive differentiation between rival stores and Google Play is limited to discovery — how apps are surfaced, recommended, and presented — rather than the delivery mechanism. When a user installs an app from an enrolled rival store, the rival store is not hosting that app or managing the installation. Google Play runs the install. Google Play Protect scans for malware. Google collects the service fee. A rival store cannot offer a faster download, a different security approach, or a lower price on the installation itself. The competition that the program enables is for users' attention and loyalty on the front end — the store interface, curation, community features, and developer relationships — not for the back-end infrastructure that has generated most of Google Play's revenue for years.
Related Articles
