Court Ruling Eases Rival App Store Installs on Google Play

Table of Contents

• 1. Court orders Google to simplify rival app store installs
• 1.1 What this remedy looks like in practice
• 2. Epic Games Demonstrates Google’s Anticompetitive Practices
• 3. Removal of Unnecessary Friction in Installation Process
• 4. Impact on Search Results for Third-Party App Stores
• 5. Judge Donato’s Emphasis on User Experience
• 6. Potential Effects on Established Companies Like Amazon
• 7. The Future of App Distribution: A New Era for Android
• 7.1 Implications for Developers and Users
• 7.2 The Path Ahead for Rival App Stores

---

Court orders Google to simplify rival app store installs

• A federal judge ordered Google to remove “anticompetitive friction” that makes rival Android app stores harder to find and install.
• Epic Games demonstrated extra steps and confusing screens in court; Judge James Donato called some of them unnecessary.
• Google agreed to changes, including improving Play Store search results and replacing “view” with “install.”
• The judge pushed for fast implementation—within a week.

A month after Epic Games and Google appeared to have stepped back from their fight over Android app distribution, they were back in a San Francisco courtroom—where U.S. District Judge James Donato ordered Google to make it easier to install rival app stores on Android.

The order sits inside a longer-running remedy process. Nearly three years ago, a jury unanimously found Google held an illegal monopoly over Android apps. Almost two years ago, Donato concluded the way to unwind that monopoly was to “crack open” Android app distribution—requiring Google to carry rival Android app stores inside Google Play and to provide rivals access to Google’s full catalog of apps for several years.

Court Orders Faster Android Store Access

• Jury verdict (nearly three years ago): Google found to have an illegal monopoly over Android apps.
• Remedy phase (almost two years ago): Judge James Donato orders Google to “crack open” Android app distribution, including carrying rival stores in Google Play and providing access to Google’s full app catalog for several years.
• Program rollout (reported July 22, 2026): Google’s Play Catalog Access Program begins enabling qualified third-party app stores to be installed from within Google Play (US-only, as reported by outlets including TechCrunch and Ars Technica).
• Today’s hearing: Epic argues the remedy still contains “anticompetitive friction” in search and install flows; Donato orders specific UX/search changes and presses for implementation within a week.

What this remedy looks like in practice

In 2026, this court-driven opening has been implemented through Google’s Play Catalog Access Program, launched on July 22, 2026, which enables qualified third-party app stores to be installed from within Google Play (rather than via traditional sideloading flows). As described in reporting around the rollout, the program is currently US-only.

But in the latest hearing, the judge focused less on the broad architecture of the remedy and more on the practical experience a user faces when trying to find and install a competing store. Epic argued that, even with rival stores technically allowed, Google still makes the process cumbersome. Donato agreed, repeatedly framing the remaining hurdles as “anticompetitive friction” that should not be there.

Epic Games Demonstrates Google’s Anticompetitive Practices

Epic’s case in the hearing was built around a simple tactic: show, don’t tell. Epic lawyer Yonatan Even walked the courtroom through a live demonstration of how many steps it takes to install a third-party app store, and how Google Play’s interface choices can steer users away from competitors even when users are explicitly searching for them.

One example landed immediately with the judge. When Even searched Google Play for “store for apps,” the results did not surface third-party app stores. Instead, the search returned physical retail listings—prompting Donato to ask, “Wait, why did Walmart come up?” He followed with a blunt assessment: “That’s not good.”

Donato then issued a direct instruction: fix it, and not narrowly. He said he wanted “every possible variation” of the query that is even “only 70 percent properly phrased” to work as users would expect. Google’s counsel agreed to make that happen.

Epic also argued that Google’s design patterns—extra taps, extra screens, and detours away from standard search results—function as a competitive weapon. The point was not that users cannot install a rival store, but that the path is made just inconvenient enough to reduce adoption at scale.

Court Scrutiny of Play Store

• Live demo in court: Epic’s Yonatan Even walked through the Play Store experience step-by-step to show how discovery and installation can be slowed down.
• Search mismatch example: Searching for “store for apps” surfaced physical retailers instead of third-party app stores, prompting Judge Donato: “Wait, why did Walmart come up?” followed by “That’s not good.”
• Breadth of fix demanded: Donato ordered Google to support “every possible variation” that’s “only 70 percent properly phrased,” and Google’s counsel agreed.
• UX friction called out: Donato objected to extra steps like “view” before “install,” treating them as unnecessary “anticompetitive friction.”

Removal of Unnecessary Friction in Installation Process

The hearing zeroed in on interface steps that, in the judge’s view, add delay without adding meaningful safety. One of the clearest examples: users currently have to press a “view” button before they can press an “install” button when choosing to install a third-party app store.

Donato compared that flow to mainstream apps users already trust and understand. “You don’t get that when you’re looking at Apple Music,” he noted, signaling that Google’s extra step was not a neutral design choice but a differential burden placed on a specific category of competitor.

His instruction was straightforward: “Make that install, not view.” Google agreed.

The broader theme was that friction can be anticompetitive even when it looks minor in isolation. A single extra click, a confusing label, or a detour to a special page can be the difference between a user completing an install or abandoning it—especially on mobile, where attention is short and the default option is always one tap away.

Donato’s approach suggests the remedy is not just about allowing rival stores in principle, but about ensuring they are treated like normal apps where possible—without special obstacles that discourage ordinary users from following through.

Direct Install From Listings
Before (as demonstrated in court)
1) User finds a third-party app store listing in Google Play.
2) User taps “View.”
3) User lands on a detail page.
4) User taps “Install.”
After (what Donato ordered)
1) User finds a third-party app store listing in Google Play.
2) Primary action is “Install” (no extra “View” step).
Checkpoint to confirm the change: the first tap from the listing should start installation the same way it does for typical apps (e.g., no mandatory intermediate screen just to reach the install button).

Impact on Search Results for Third-Party App Stores

Search visibility became a central battleground. Epic showed that even when users search for “app store,” or for “Aptoide” (described as the first rival store to make it into Google Play), Google does not present a normal list of apps.

In the current rollout, Aptoide Games is the first rival app store listed in Google Play under the new program—and, as of mid-August 2026, it remains the only one publicly available there.

Instead, Google surfaces a banner that users must click through to reach a dedicated third-party app store page. Epic argued that this breaks the expected behavior of Play Store search: type what you want, get a list of relevant apps.

Even warned that the impact goes beyond small newcomers. If established companies believe they will be shunted into a special, less-visible search experience—rather than appearing in ordinary results—they may decide it’s not worth launching a store at all. In court, Amazon was raised as an example of a large company that might hesitate if the distribution channel comes with a built-in discoverability penalty.

Judge Donato agreed the design did not make sense. He questioned why the Play Store would treat app stores differently at the search layer, especially when the user is clearly asking for one. He ordered Google to fix the issue, rejecting the idea that users should be diverted into an “are you looking for…” style experience before they can reach what they searched for.

Sanity-Check Play Store Search
Quick ways to sanity-check Play Store search behavior (the issues raised in court)

• Search: “store for apps” → Do third-party app stores appear, or do unrelated physical retailers dominate?
• Search: “app store” → Do you get a normal list of apps, or a banner/detour to a dedicated third-party store page?
• Search: “Aptoide” → Does it surface like a typical app result, or require an extra click-through?
• Try a “70% phrased” variation (e.g., “apps store,” “store apps,” “app stores”) → Do rival stores still show up as expected?

What to note: whether the first screen behaves like standard Play search (direct results) versus a special interstitial experience.

Judge Donato’s Emphasis on User Experience

Donato’s comments made clear he sees user experience as a legal and competitive issue, not a cosmetic one. When the judge looked at Google’s prompts and intermediate screens, he repeatedly asked what purpose they served—especially when the user’s intent was unambiguous.

Google’s attorney responded that Epic and Google had already agreed app stores are a special category of apps with advanced permissions. Donato did not dispute that app stores can carry elevated risk. But he argued that the warning on the third-party app store page itself was sufficient—meaning Google did not need additional “are you sure?” layers that effectively second-guess the user’s search.

He illustrated the point with a plainspoken analogy: there is no need to ask a user whether they really want the thing they searched for—whether it’s a game store or “a glass of water.” In other words, informed consent can be achieved without steering.

Donato also pushed back on the idea that users would be confused by getting what they asked for. He noted that when people search inside major app stores, they often get “one thing you were looking for and ten things you don’t want.” Against that reality, he suggested, a direct result for a rival store is unlikely to be the confusing part.

His conclusion was unequivocal: “Take off the ‘are you looking for’ screen, there’s no purpose for that. There’s friction there.”

Potential Effects on Established Companies Like Amazon

Epic’s argument about Amazon was less about any single company and more about incentives. If Google Play’s search and install flows treat third-party stores as second-class apps—hidden behind banners, extra confirmations, and nonstandard pages—then even well-known brands may decide the economics and effort do not justify participation.

That matters because the remedy Donato is trying to enforce is designed to create real competition in Android app distribution, not merely symbolic alternatives. A market where only niche players can tolerate the friction is not the same as a market where major platforms can compete on discovery, curation, and user trust.

In court, Epic framed the banner-and-detour approach as a structural disadvantage: rival stores lose the ability to appear in normal app search results, which is one of the main ways users find software in the first place. If a company like Amazon believes it would be pushed into a special lane—rather than competing on equal footing for search visibility—it may choose not to launch or promote a store through Google Play at all.

Donato’s response suggests he understands that competition depends on distribution mechanics. If the Play Store is the front door for Android apps, then how that door is labeled—and how many locks are added for certain entrants—can determine whether rivals ever reach meaningful scale.

The Future of App Distribution: A New Era for Android

Implications for Developers and Users

The judge’s order is narrowly focused—remove specific points of friction, fix search behavior, streamline install buttons—but the implications are broader. If rival stores can be discovered through ordinary searches and installed through ordinary flows, users gain practical choice rather than theoretical choice.

For developers, the stakes are tied to reach. A rival store that users can actually find and install becomes an additional distribution channel. But if discovery is suppressed by design, developers may never see enough user adoption to justify supporting alternative marketplaces.

Donato’s insistence on fast changes also signals ongoing oversight: the remedy is not “set and forget.” It is being tested against real user journeys, in real interfaces, with the court willing to intervene when the experience appears engineered to discourage competition.

The Path Ahead for Rival App Stores

The immediate next step is compliance: Google has agreed in court to make specific changes, and the judge wants them implemented quickly. After that, the larger question is whether rival app stores can build momentum once the biggest obstacles are removed.

Epic’s courtroom demos underscored a key reality of platform competition: small design decisions can have outsized market effects. If rival stores are treated like normal apps in search and installation—without extra detours—Android’s distribution landscape could become meaningfully more open.

But the judge’s language also hints at what will be watched next. If new forms of “friction” appear—new banners, new prompts, new nonstandard flows—the court has signaled it will not accept them if they lack a clear purpose beyond slowing rivals down.

Signals of Real User Parity
What to watch next (signals that the remedy is working in day-to-day use)
1) Search parity: Rival stores appear in ordinary Play Store results for common intent queries (e.g., “app store,” “store for apps,” and close variations).
2) Install parity: The primary action from a listing is “Install,” without extra “view” steps that don’t exist for comparable mainstream apps.
3) Detour removal: Fewer interstitials like “are you looking for…” when the user’s query is explicit.
4) Participation: More than one third-party store joins the program (a practical test of whether the channel is attractive, not just technically available).
5) Stability over time: Changes persist across updates—no new UI patterns that reintroduce the same friction in a different form.

Viewed through the lens of digital distribution and payments economics, small UX and permission-flow decisions can materially change adoption and unit economics at scale—a perspective informed by Martin Weidemann’s work building and scaling technology businesses in regulated, multi-stakeholder environments across Latin America.

This article reflects publicly available information at the time of writing about a court hearing and related coverage of how Google Play surfaces and installs third-party app stores in the US. Play Store interface details and timelines may change as Google updates its behavior and as court oversight continues. If you’re verifying the experience, compare what you see in the current Play Store UI on your device with the behaviors described here.