What the Epic Injunction Opens—and What It Does Not
This series examines the antitrust remedy produced by Epic Games’ litigation against Google, and the way Google now describes that remedy in Google Play’s US policies. The practical question is simple to ask but easy to answer badly: when a court says a platform must open itself to competition, what can developers, users, and rival app stores actually do? A useful answer must separate legal permission from practical access, and it must show which parts of the Android system each change affects.
The short answer is that the injunction opens controlled alternatives around Google Play. Developers gain room to discuss outside availability and prices, use a payment method other than Google Play Billing, or send users to external content. Rival stores gain a legal path toward Play’s catalog and Android users. But Google Play does not vanish from these routes. The opening remains bounded by the United States, specified mobile and tablet uses, enrollment, safety measures, developer choices, reporting, service fees, and a legal transition that is not fully settled in the supplied documents.
“Open” is not one switch
The word “open” hides several different changes. The first concerns communication. Google’s US policy update says it will not prohibit developers from telling users about an app’s availability or price outside Google Play, linking to an outside download, or linking to a transaction. That changes what a developer may say and where a user may be directed.
The second concerns payment inside a Play-distributed app. Google says it will not require Google Play Billing for all such apps or prohibit other in-app payment methods. A developer can therefore have another billing system alongside Play Billing, or in place of it, if they join the relevant program and meet its conditions. That is a change in payment choice, not necessarily a departure from the Play distribution channel.
The third and fourth changes concern app distribution itself. The injunction described by the Ninth Circuit requires Google to let third-party Android app stores access the Play catalog. It also bars Google from prohibiting those stores or distribution platforms from being distributed through Google Play. One provision addresses the supply of apps; the other addresses a rival store’s path to users. They are related, but neither is the same as an external payment link.
This distinction matters because an alternative can exist on paper and still be too weak to compete. A developer website may offer a download, yet users may not find it, trust it, or complete the process. A rival store may have a good interface, yet lack the catalog that attracts users. A different payment processor may be technically available, yet still require support, refunds, reporting, and fees. The relevant question is not merely whether a door exists. It is whether the door changes the bottleneck that kept Google Play powerful.
Google Play sits between two dependent sides
The subject is easier to understand as a two-sided platform. Google Play connects Android users who want apps with developers who want users. A large catalog makes Play more attractive to users; a large user base makes it more attractive to developers. Each side strengthens the other. This is the network effect at the center of the court’s account.
That structure helps explain why the remedy has more than one opening. If a rival store receives apps but cannot reach Android users, its catalog does not solve the whole problem. If it can reach users but has only a thin catalog, users have little reason to switch. Distribution competition therefore has a supply side and a user side. Catalog access works on the first; distribution of rival stores through Play works on the second.
The same platform logic also explains why billing and distribution are separate legal questions. A developer might continue to distribute an app through Play while offering another payment method inside the app. Or the developer might use Play to reach users but link them to a browser for an outside purchase. Those choices concern how value is exchanged after the user has reached the app. A rival-store remedy concerns who can provide the app and how that store reaches the user in the first place.
Android’s architecture makes the distinction especially important. Unlike Apple’s iOS, Android is publicly available and licensed to many phone manufacturers. In principle, Android supports direct downloads and other app stores. The Ninth Circuit nevertheless described practical barriers: default settings that disable direct downloads, repeated warning screens, and arrangements that favored Play’s placement. In the trial record summarized by the court, users attempting to download Fortnite directly faced more than 15 steps, and 35% of those who began the process abandoned it after warning messages. Those are historical findings, not a current measurement of every Android device. Their significance is conceptual: technical possibility does not guarantee effective reach.
The diagram is a compact map, not a claim that every route has identical rules. The billing and external-link routes are described in Google’s current US programs. Catalog access and rival-store distribution arise from the court’s remedy and are being operationalized through named Google programs. The legal source, user path, and conditions must be checked separately whenever a new policy announcement appears.
The court order is not the same thing as a help page
The Ninth Circuit’s opinion supplies the legal architecture. After the jury found Google liable in markets for Android app distribution and Android in-app billing, the district court entered a nationwide, three-year injunction. As the appellate opinion describes it, the order prohibits several arrangements that insulated Play from competition: conditioning payments or access on launching first or exclusively on Play, conditioning OEM placement on excluding other stores, sharing Play revenue with distribution entrants in ways that discourage competition, and requiring Google Play Billing for all Play-distributed apps.
The order also contains affirmative remedies. Google must permit third-party Android app stores to access the Play catalog, and it may not prohibit the distribution of third-party Android app distribution platforms or stores through Play. The court accepted these measures because the alleged harm was not only a high fee or a single blocked transaction. It included network effects that had been strengthened by exclusionary conduct. In the court’s reasoning, temporarily lowering the barriers to catalog and user access was a reasonable way to reduce those effects.
Google’s help pages provide the operational layer for some of this opening. The alternative-billing page describes an opt-in US program for digital content and services. The external-content-links page describes another opt-in route that can lead to an outside purchase or to an app download whose installation and updates are not managed by Play. Both pages retain user-protection requirements. They call for support and dispute or refund processes, and they preserve reporting and service-fee obligations once those requirements take effect.
That operational layer is important because the injunction does not mean that every developer can ignore platform accountability. The current pages limit the programs to eligible apps or games serving US users and, in the described programs, to mobile or tablet form factors. External destinations must explain where the user is going, must not mislead them, and must meet additional requirements when they distribute an app. Alternative billing must be implemented through the program, and a developer using it alongside Play Billing must keep Play Billing consistently accessible.
Nor is the current policy picture necessarily final. Google’s update says that on March 4, 2026, Google and Epic entered a new settlement agreement and asked the district court to enter a revised Modified Injunction. The same page says current policies and programs remain in effect and gives July 22, 2026 as the effective date for the third-party US store programs. It also says reporting and relevant service fees will begin on October 1, 2026 for developers enrolled in the US external-content-links and alternative-billing programs. These are source-reported milestones, not a substitute for the text of the requested revised order.
The result is a more precise picture than either extreme. It is wrong to say that the injunction changes nothing: Google’s stated US rules now recognize outside communication, alternative billing, external content links, and distribution-side programs that were central to the dispute. It is also wrong to say that Google Play has become an unregulated marketplace in which every route is automatic, costless, or available worldwide. The legal remedy opens particular channels because of particular findings, while the operating programs place conditions around those channels.
The most reliable mental model is therefore controlled interoperability. Google remains the intermediary, but the court has required it to stop using certain contractual and technical levers to keep alternatives out. Developers and rival stores receive more room to reach users, supply apps, and choose how transactions occur. At the same time, safety, support, privacy, developer control, reporting, and cost recovery remain part of the system. To understand why those specific doors were ordered open, the next question is how Google Play acquired the gatekeeping position that made Fortnite’s dispute much larger than one game’s payment experiment.