Epic Games, Inc v Google LLC

This page explains the public reasons in Epic Games, Inc v Google LLC [2025] FCA 901 and what they show about the dispute, the legal issues and the commercial setting. It does not present the case as a final public authority on liability because the written reasons are subject to a publication restriction apart from the oral summary and republication of that summary, and the publicly available text is truncated before the concluding analysis.

That matters because readers can see a detailed account of Epic's allegations, Google's Android arrangements and the statutory framework, but cannot safely confirm from the public material alone which pleaded claims ultimately succeeded or failed, what market definitions were finally accepted, or what relief may follow. The safest way to read this case is as a significant Federal Court judgment on digital platform competition issues whose final public outcome still needs careful checking.

Epic is a developer of entertainment software, including Fortnite. The public reasons say Google removed Fortnite from the Play Store on 13 August 2020, and that step provoked the litigation against Google. Epic's complaint was not simply that Google operated a successful app store. Its case was that Android, while open in theory, had been structured so that realistic large-scale distribution outside the Play Store was much harder in practice.

The reasons describe Android as a multi-sided ecosystem involving users, OEMs, carriers, developers and Google. Google made Android OS available under an open source licence through the Android Open Source Project. But the reasons also explain that open source Android did not include Google Mobile Services, or GMS, which included important Google apps and software tools. A device without GMS was described as functionally limited because many non-iOS apps were built using GMS APIs or SDKs and would only run as intended on devices with GMS installed.

That commercial reality mattered because OEMs wanting to distribute devices with GMS pre-installed had to enter into a MADA with Google. According to the public reasons, the MADA required pre-installation of certain Google apps including the Play Store, required those apps to be placed in specified prominent locations, imposed technical requirements, and required ongoing compliance with the Android Compatibility Commitment. The ACC, operating with the MADA, in general terms prevented OEMs that wanted to distribute devices with GMS Android pre-installed from also distributing devices running Android forks.

The reasons explain Google's position that anti-fragmentation and compatibility arrangements addressed the risk of device fragmentation and helped ensure a consistent experience for developers and users. Epic's case, however, was that these arrangements also helped preserve Google's control over Android app distribution. Epic further alleged that Google reinforced that position through incentive arrangements with OEMs and major developers, including revenue sharing and programs referred to in the reasons as RSA3s, MIAs, GVP and AVP.

On the developer side, Epic challenged the terms required to access the Play Store. The reasons say developers could not distribute through the Play Store without entering into a developer distribution agreement on essentially non-negotiable terms. Under that agreement, developers were prohibited from distributing rival app stores or apps that distribute other apps through the Play Store. Developers monetising Play Store apps through in-app purchases of digital content were required to use Google Play Billing, subject to limited exceptions. The agreement also included an anti-steering rule, so developers could not lead users from a Play Store app to another payment method.

Epic also relied on the practical difficulty of distributing apps outside the Play Store. The reasons state that in Australia during 2020, less than 3% of new apps downloaded to Android devices were directly downloaded or downloaded from an app store that was itself directly downloaded. The reasons identify three major barriers to direct downloading: discoverability, extra steps and warnings in the sideloading process, and functional limits around updates, at least until Android 12 changes in October 2021. Epic's point was that alternatives existed in theory, but not as realistic substitutes at scale.

The public reasons show that the Court was dealing with a major competition law dispute under the Competition and Consumer Act 2010 (Cth). The catchwords and introductory reasons identify alleged contraventions of s 46, as well as alleged contraventions of ss 45 and 47, and an alleged contravention of s 21 of the Australian Consumer Law. The case therefore raised questions about misuse of market power, restrictive conduct, tying, exclusivity-style effects, and unconscionable conduct.

Epic identified three relevant markets in its case against Google. First, a market for the supply of mobile OS licences to OEMs. Second, a market for the supply of services for the distribution of Android apps. Third, a market for the supply of services for facilitating payments for the purchase of digital content within Android apps. The reasons also note an alternative broader mobile app distribution market covering Android apps and native iOS apps.

The legal issue was not whether Google was entitled to run Android, license GMS or impose any rules at all. The real question was whether the combination of contractual conditions, technical restrictions and incentive arrangements had the purpose, effect or likely effect of substantially lessening competition, or otherwise contravened the pleaded provisions. The reasons also show that security, compatibility and technology constraints were central to the analysis. Google said some restrictions were necessary for security and ecosystem management. Epic said the same arrangements also protected the Play Store and Google Play Billing from meaningful competition.

That is an important point for businesses. Competition law often turns on commercial reality rather than labels. A term described as a security measure may still be examined for its competitive effect. A contract described as a licence may still be scrutinised if access to one product is used to shape competition in another. And a theoretical alternative may not count for much if users or suppliers face practical barriers that make the alternative commercially weak.

The public reasons are especially useful because they identify the specific documents and conduct that mattered. For OEMs, the key arrangements included the MADA, the ACC and anti-fragmentation arrangements. These were said to govern access to GMS, pre-installation of Google apps, placement of those apps, technical compliance and restrictions connected with Android forks. The reasons also refer to incentive arrangements under which some OEMs received a portion of Google's advertising revenues, and in some cases a portion of Play Store revenues, subject to conditions including compliance and limits on pre-installing or promoting competing app stores.

For developers, the key document was the developer distribution agreement. The public reasons say this agreement was essentially non-negotiable and that it prevented distribution of rival app stores or apps that distribute other apps through the Play Store. It also required use of Google Play Billing for in-app purchases of digital content in Play Store apps, subject to limited exceptions, and included the anti-steering rule. The reasons further refer to Games Velocity Program and Apps Velocity Program agreements with certain large developers considered by Google to be at risk of distributing outside the Play Store.

What makes this commercially significant is that the case was not framed around one isolated clause. It was about the interaction between many features of the Android ecosystem. Pre-installation and prominent placement could affect user behaviour. Compatibility commitments could affect OEM choices. Play Store rules could affect rival app stores. Billing requirements could affect payment competition. Anti-steering rules could affect how developers communicate with users. Technical warnings and update limits could affect whether direct downloading was a realistic substitute. In competition analysis, that kind of cumulative architecture can matter more than any single document viewed alone.

Businesses should also notice the Court's attention to real-world evidence. The public reasons refer to download shares, the practical difficulty of discoverability, the number of steps in sideloading, and the functional limits of directly downloaded apps. That shows how competition disputes in digital markets often depend on evidence about user behaviour, defaults, friction and commercial incentives, not just formal legal rights.

The public orders confirm several important procedural points. Beach J gave judgment on 12 August 2025. The further hearing of the proceeding was stood over to a date to be fixed. Costs were reserved. Most importantly, the Court ordered that, apart from the oral summary given at the time of delivery and any republication of that summary, disclosure and publication of the written reasons and their content were restricted to the parties' external legal advisers in this proceeding and in related proceedings, subject to further order.

That means the public can see that this was a substantial liability judgment delivered after a lengthy joint trial involving Epic's claims against Google, related claims against Apple, and class actions concerning alleged overcharging of commissions. The public can also see the broad shape of Epic's case against Google and the legal framework the Court was addressing. But the public material does not safely reveal the final disposition of each pleaded claim. It is therefore not appropriate to state here that Google was found liable, or that Epic failed, on any specific issue unless and until that can be confirmed from a complete public source.

For business readers, the practical message is that procedural status matters. A case can be highly informative even when the final public position is incomplete. Here, the public reasons are still valuable because they show the kinds of conduct the Court considered important in a digital platform competition case. But if you need to rely on the case for a precise legal proposition, such as the accepted market definition or the final treatment of a payments tie, you should wait for a confirmed public basis to do so.

This case is useful well beyond the app economy. If your business controls a platform, marketplace, software environment, reseller network or payment channel, the public reasons show the kinds of features that can attract competition scrutiny. These include default placement, restrictions on rival access, tying one service to another, anti-steering rules, technical friction that makes alternatives harder to use, and incentive arrangements that discourage counterparties from supporting rivals.

That does not mean every restrictive term is unlawful. The public reasons themselves show that security, compatibility and ecosystem management can be legitimate concerns. But businesses should ask whether their arrangements are proportionate and whether they go further than reasonably necessary. A rule that protects users may still create legal risk if it also blocks realistic competition more than needed. A payment requirement may be easier to defend if it is limited and justified, and harder to defend if it is paired with anti-steering and no practical alternative route to customers.

If you are a platform operator, review your contracts as a system rather than clause by clause. Ask how pre-installation, prominence, technical settings, payment rules and commercial incentives work together. If you are a supplier or developer dealing with a larger platform, keep evidence of the practical barriers you face. Courts and regulators often care about what happens in the real world: how many steps users must take, what warnings they see, whether updates work smoothly, whether alternatives are discoverable, and whether terms are genuinely negotiable.

Boards, founders and product teams should also recognise that product design can have legal significance. Defaults, warning screens, update pathways and customer communication rules are not only user experience choices. In the right circumstances, they can become part of a competition case. That is especially true where a business already has a strong position and uses multiple levers at once to shape how customers and counterparties behave.

This page is based on the Federal Court judgment record for Epic Games, Inc v Google LLC [2025] FCA 901, dated 12 August 2025. The public material identifies the parties, the hearing dates, the broad allegations, the contractual arrangements in issue, the markets pleaded, the statutory provisions engaged and the orders made on publication, costs and the further hearing.

The public material is enough to explain the commercial story and the legal issues with confidence. It is not enough to publish a definitive public statement of the final findings on each pleaded contravention. Readers should therefore treat this page as a careful explainer of the dispute and its significance, not as a final public liability note.