So, What Does the Epic Injunction Actually Open?
The subject is the affirmed Epic Games remedy against Google’s control of Android app distribution and in-app billing, together with Google’s current description of how that remedy operates for US users. The final judgment is precise: the injunction opens several controlled routes through Google Play, but it does not turn Play into a neutral, unbounded marketplace or remove Google’s platform role. To understand what has changed, one must ask which participant gains access, which bottleneck is lowered, what legal or policy source creates the route, and what conditions still govern it.
The direct answer: four doors, not a dissolved gate
The first opening is informational and financial. Google’s current US policy page says that, for apps on mobile and tablet form factors serving users in the United States, Google will not prohibit developers from communicating about an app’s availability or price outside Play, linking to an outside download or transaction, using an in-app payment method other than Google Play Billing, or communicating about that method. It also says Google will not require a developer to set a price based on whether Play Billing is used. These changes give developers more room to tell users that another option exists and to make that option reachable.
The second opening is alternative billing inside a Play-distributed app. Google’s US program allows eligible developers of apps and games offering digital content or services to use another billing system instead of or alongside Play Billing. That weakens the old connection between distribution through Play and mandatory use of Play’s payment system. It does not remove Play Billing, and it does not move the app into another store. It changes the payment interface while leaving the distribution relationship largely intact.
The third opening is external content linking. An eligible Play-distributed app can link US users to external content, including an outside purchase or a download of an app whose installation and updates are not managed by Play. This is broader than choosing another payment processor because it changes the user’s destination. It creates an opportunity to transact or distribute elsewhere, but it also creates responsibility for explaining the destination, protecting personal information in URLs, preventing deceptive redirects, and making an external app’s identity and installation conditions clear.
The fourth and most structural opening is on the distribution side. The injunction described by the Ninth Circuit requires Google to permit third-party Android app stores to access the Play catalog and bars Google from prohibiting the distribution of third-party Android app distribution platforms or stores through Play. The first measure gives rival stores a path to a credible library of apps. The second gives them a path to users who are accustomed to obtaining software through Play.
These openings accompany prohibitions on specific forms of exclusion. The order, as described by the court, bars Google from using certain revenue-sharing or conditional-access arrangements to protect Play, including conditions involving launching first or exclusively on Play and OEM placement that excludes other stores. It also prohibits a blanket requirement that all Play-distributed apps use Google Play Billing. The remedy therefore does two things at once: it takes away tools that can insulate Play from competition and creates interfaces through which alternatives can become viable.
That is what the injunction opens. It opens communication, payment choice, external destinations, catalog access, and rival-store reach. It does not promise that every developer can use every route without enrollment, that every store receives automatic access, or that every outside destination is safe or commercially successful.
Why the four doors belong together
The distribution and monetization provisions are different because they address different sides of Google Play’s power. Google Play sits between Android users and app developers. A large catalog attracts users, and a large user base attracts developers. That feedback loop gives the platform network effects.