Epic-Google Ruling: Installing Rival App Stores Gets Easier

Installing a rival app store on Google Play required more steps than necessary — until August 2026. Epic Games's live courtroom demo exposed three friction points, from search results to the install button; Judge James Donato called them "unnecessary" and gave Google one week to fix them. In this piece we examine, with sources, where the epic google decision rival app store process came from, what the court ordered, and how it intersects with the developer-verification requirement that took effect in the same period.

💡 Pro Tip: Before applying to the Play Catalog Access Program, read the official fee and eligibility page on support.google.com — the $5,000 fee concerns only companies with "store operator" status, not individual developers.

Table of Contents

• The three-year chain of litigation that led to the ruling
• The August 2026 hearing: a live demo that proved the friction
• Google's objection and Donato's answer
• The fixes the court ordered and the implementation timeline
• How this intersects with developer verification
• The real cost of distributing through an alternative channel
• Who this makes sense for, and who it doesn't: an assessment
• How to verify this in your own environment
• Next steps to watch
• FAQ
• What's changing on Play after the Epic-Google ruling?
• Does distributing through an alternative store make sense for a TR developer?
• How many steps does installing a rival store take now?
• Is Android Developer Verification the same thing as this ruling?
• Did Google appeal this ruling — what happened?
• Conclusion
• Sources

The three-year chain of litigation that led to the ruling

This story's roots trace back to a long-running case against Google's control over Android app distribution. In December 2023, a jury found Google had built an illegal monopoly in Android app distribution through the Play Store and had harmed Epic. About a year later, on October 7, 2024, Judge James Donato issued a permanent injunction to enforce that verdict.

That order was designed to remain in force for three years, from November 1, 2024 to November 1, 2027, and it barred Google from eight practices: notably, sharing revenue with parties distributing rival stores, making Play Billing mandatory, and blocking rival Android app-distribution platforms from being hosted inside Google Play (source: theregister.com, 2024-10-07). Google appealed the ruling, and Lee-Anne Mulholland (VP of regulatory affairs) argued in a blog post that these changes would weaken Android's ability to compete with the Apple ecosystem.

The key detail from this two-year gap: the injunction's scope was limited to the US only — as The Register reported, the order applies "only in the US." That's why the ruling should still be read as a "US-market-specific" development; it carries no direct obligation for markets outside the US, including Turkey.

By July 2026 the debate had shifted to a different axis: Google had proposed replacing the permanent US injunction with a sideload-based "Registered App Stores" model. Judge Donato "was skeptical he should abandon his original permanent injunction in favor of Google's proposed 'Registered App Stores' that users would have to sideload"; Google withdrew that modification request and agreed to implement the original order.

For the rest of the world, Registered App Stores remains a separate, still-planned program (source: theverge.com/policy/965792). As a result, the Play Catalog Access Program took effect on July 22, 2026 — third-party US stores can now access Google Play's app catalog. The first concrete step came on August 10, 2026: Aptoide Games became the first rival store distributed through Google Play.

In 9to5Google's testing, installing the store itself behaved "like a normal Android app"; no extra security prompt was requested when installing an app from the store either — the only additional step was confirming the "Install" prompt (source: 9to5google.com, 2026-08-10).

The August 2026 hearing: a live demo that proved the friction

The rival store was now visible inside the Play Store, but Epic didn't think that was enough. At a hearing in San Francisco on August 13, 2026, Epic's lawyer Yonatan Even showed the courtroom a live walkthrough of the real install flow. When a term like "store for apps" was searched on Google Play, the results showed physical stores like Walmart instead of rival digital stores. Judge Donato's reaction was clear: "Wait, why did Walmart come up?" he asked, then said, "That's not good" (source: theverge.com/policy/979852, 2026-08-13).

As the demo continued, two more friction points emerged. When a user wanted to install a rival store, they first had to tap "View," then find the "Install" option on a separate screen — an extra step that a normal Play Store app doesn't have. Donato criticized this too: "You don't get that when you're looking at Apple Music." The third point was that searching for "app store" or directly for "Aptoide" routed the result to a separate banner that had to be clicked, instead of a plain listing; the judge summed this up as "there's a friction there that has no purpose whatsoever."

Let's summarize the three friction points in a before/after table:

Google's objection and Donato's answer

Google's lawyer reminded the court that Epic and Google had already agreed app stores are a special category with elevated permissions, arguing an extra warning step was therefore reasonable. Donato disagreed: the warning on the third-party store page was already sufficient, and letting users find directly what they searched for wouldn't be confusing. Google's counsel agreed to the first two changes; the third, Donato ordered despite that objection.

The fixes the court ordered and the implementation timeline

Donato wanted the changes implemented quickly: "Have it done by a week from today. If there's some problem with that, let me know." So the deadline was exactly one week from the hearing date: all three changes had to be completed by August 20, 2026. The exact date Google shipped the changes was not publicly disclosed.

The practical takeaway: if you're searching for an app store through the Play Store and results still show the old behavior, that doesn't mean Google is ignoring the order — a gradual rollout may be underway. To verify what's changed on your own device, follow the steps in the "How to verify this in your own environment" section below.

How this intersects with developer verification

Android developer verification — a completely separate program that happens to fall in the same period — is easily confused with this ruling; there are two distinct obligations getting mixed together here.

The first is global and it covers you too: the 2026-09-30 line on Google's policy deadlines page says "you must register your Play apps in Play Console ... to avoid global removal from Google Play." In other words, an unregistered app can be removed from Play regardless of which country it's published in. Google states that "99%" of apps are already registered automatically, and the rest need to be checked from the Play Console Home page (source: support.google.com/googleplay/android-developer/answer/9934569).

The second is regional: the on-device verification that blocks installs took effect on September 30, 2026 only in Brazil, Indonesia, Singapore, and Thailand; Google announced it will expand these protections globally in 2027 (source: android-developers.googleblog.com, 2026-06-18). So Turkey is not in this first wave — but that applies only to the device side; Play Console registration is still mandatory for a TR developer too. While the Epic-Google case makes installing a _rival store_ inside Play easier, developer verification tightens identity checks across _all_ install paths; for details see our Android developer verification piece.

You can keep a simple checklist to track your own apps' registration status:

1{
2  "checklistItem": "Play Console developer verification registration",
3  "deadline": "2026-09-30",
4  "sourcePage": "support.google.com/googleplay/android-developer/answer/9934569",
5  "autoRegisteredShare": "99%",
6  "actionIfMissing": "Manually register the app from the Play Console Home page",
7  "consequenceIfSkipped": "The app may be removed from Google Play globally",
8  "affectsTurkeyFirstWave": false
9}

This isn't an API call — it's just an example showing which fields you need to track. To see your actual status, you need to log into your own account in Play Console.

The real cost of distributing through an alternative channel

"Installation got easier" doesn't mean "it became free and unconditional." According to Google's official Play Catalog Access Program page, third-party US stores that want to join must meet these requirements: distribute only to the US, be registered as an "organization," offer a non-discriminatory policy open to all eligible developers, and prevent the distribution of malware — with the numeric threshold The Verge cited: "no more than 1 percent of 'install attempts' can be malware."

The store operator also pays Google a $5,000 upfront fee for security and policy review; to keep access, they must pay this fee again annually (source: support.google.com/googleplay/android-developer/answer/17117200).

This cost concerns not an individual app developer but the store _operator_ — meaning a company like Aptoide. A simple calculation shows how the total cost grows across the three-year injunction window:

1// Source: support.google.com/googleplay/android-developer/answer/17117200
2// "$5,000 upfront service fee... pay this fee on an annual basis thereafter"
3const upfrontFeeUsd = 5000;
4const annualRenewalFeeUsd = 5000;
5 
6function totalProgramCost(yearsOperating: number): number {
7  if (yearsOperating < 1) return upfrontFeeUsd;
8  // Year 1 = upfront fee, each subsequent year = renewal fee
9  return upfrontFeeUsd + annualRenewalFeeUsd * (yearsOperating - 1);
10}
11 
12console.log(totalProgramCost(1)); // 5000
13console.log(totalProgramCost(2)); // 10000
14console.log(totalProgramCost(3)); // 15000

Gathering the timeline into one table makes the stages of the case, and which date matches which event, clearer:

Who this makes sense for, and who it doesn't: an assessment

This section is interpretation drawn from the sourced data — there's no direct "who's this for" analysis in the court record. The annual $5,000 fee and the strict eligibility requirements (organization registration, non-discriminatory policy, low malware rate) look like an affordable cost for large, corporate store operators — and indeed, an established player like Aptoide was the first to enter.

For an independent developer to set up their own "store" and join this program looks impractical, given the organization-registration and annual-fee requirements; it's clear who benefits: this program is for _companies that build stores_, not individual app developers.

For an individual iOS or Android developer, the real question lies elsewhere: which store you sell through, at what commission rate, and on what billing infrastructure. From that angle, our Google Play Billing v7 guide and our strategy for earning $1M on the iOS App Store piece, which covers revenue with concrete numbers, focus on issues that affect your daily workflow far more than this rival-store news does. Short-term, the Epic-Google case doesn't bring a new obligation to the developer; it brings a new alternative route at Play's _distribution layer_.

How to verify this in your own environment

If you're wondering whether the changes Google was ordered to make have reached your device, you can check manually on your own Android device or emulator with the steps below. These are standard adb commands; they don't need any special Google API.

1# Check whether a rival store like Aptoide Games is installed on your device
2adb shell pm list packages | grep -i aptoide
3 
4# Deep link that goes straight to the Play Store's third-party store page
5# (the access method Google's support page calls "deep-links")
6adb shell am start -a android.intent.action.VIEW \
7  -d "market://details?id=com.aptoide.android.aptoidegames"
8 
9# Watch live which permission/package events fire during installation
10adb logcat | grep -i "PackageInstaller"

If you want to see how much time has passed since the September 30, 2026 registration deadline, a simple date difference is enough; the block uses python3 instead of the GNU-specific date -d, so it also works on macOS:

1python3 - <<'PY'
2from datetime import date
3deadline = date(2026, 9, 30)
4print("Days since the deadline:", (date.today() - deadline).days)
5PY

Next steps to watch

Three threads are worth following. First, the exact date Google shipped the one-week fix ordered on August 13, 2026 was never disclosed. Second, Google had said it would appeal the October 7, 2024 ruling and seek to stay the injunction (source: theregister.com, 2024-10-07); despite that, the Play Catalog Access Program required by the order took effect July 22, 2026 (source: theverge.com/policy/965792), and the order's three-year window closes November 1, 2027. Third, the sideload-based model proposed to replace the US injunction was withdrawn; the Registered App Store program announced for the rest of the world remains on the table as a separate track.

These points mark the boundaries of the "rival store installation got easier" headline: what got easier is US-specific, the result of a legal process, and still requires ongoing enforcement tracking — not a permanent, universal change.

FAQ

What's changing on Play after the Epic-Google ruling?

On August 13, 2026, Judge James Donato ordered the removal of three friction points that made it harder to find and install rival app stores on Google Play: search results correctly showing rival stores, a direct "Install" button being shown for installation (removing the previous "View" step), and removal of the "are you looking for" intermediate redirect screen. This is a friction-reduction layer added on top of the Play Catalog Access Program, which has been in effect since July 22, 2026.

Does distributing through an alternative store make sense for a TR developer?

For now, largely no: the injunction and the Play Catalog Access Program cover only US users and store operators distributing to the US. The annual $5,000 participation fee also concerns the company building the store, not an individual app developer. In contrast, the Play Console registration requirement is global; publishing from Turkey doesn't exempt you.

How many steps does installing a rival store take now?

After Donato's order, it comes down to a single "Install" button — equivalent to installing a normal Play Store app. Before the order, the user first tapped "View," got redirected to a separate page, then found the "Install" option. The exact date Google shipped this change was not publicly disclosed.

Is Android Developer Verification the same thing as this ruling?

No, it's a separate program, and it splits into two parts on its own: Play Console registration is globally mandatory; device-side verification started on September 30, 2026 only in Brazil, Indonesia, Singapore, and Thailand, with Turkey in the 2027 global wave. While the Epic-Google case makes installing a rival store _inside_ Play easier, developer verification tightens identity checks across all install methods (Play, rival stores, sideloading).

Did Google appeal this ruling — what happened?

Yes, Google appealed the 2024 permanent injunction ruling; Lee-Anne Mulholland, VP of regulatory affairs, argued this would weaken Android's competitiveness and said the company would seek to stay the injunction pending appeal (source: theregister.com). Despite that, in July 2026 Google withdrew its request to replace the US injunction with a sideload-based "Registered App Stores" model and agreed to implement the original order; the Play Catalog Access Program took effect on July 22, 2026 (source: theverge.com/policy/965792).

Conclusion

The Epic-Google ruling didn't make installing a rival store inside Play completely frictionless in one stroke — it's a gradual, US-specific chain of fixes produced by a three-year legal process. Every step, from the December 2023 jury verdict to the August 13, 2026 friction order, clarifies exactly what the court required; the date Google shipped the changes was never disclosed.

You can also check out our other pieces on this topic: Android developer verification and the sideload era, Apple's new DMA requirements in the EU, Google Play Billing v7 guide, App Store Optimization basics, and what to do after the Google Play API 36 deadline.

Sources

• Judge orders Google to make rival app store installs easier — The Verge — live demo and Donato quotes from the August 13, 2026 hearing
• Google ordered to open Play Store for three years — The Register — full text of the October 7, 2024 permanent injunction and Google's appeal statement
• Play Catalog Access Program — Google Play Console Help — official fees, eligibility requirements, and registration steps
• Policy Deadlines (policy deadlines calendar) — Google Play Console Help — the 2026-09-30 Play Console registration row, the global-removal warning, and the auto-registration rate
• Android developer verification: Building a safer ecosystem together — Android Developers Blog — the BR/ID/SG/TH timeline for device-side verification and the 2027 global expansion
• Google and Epic give up fighting — third-party Android app stores are coming next week — The Verge — the withdrawn "Registered App Stores" modification and the 1 percent malware threshold
• Judge says rival app store situation "not acceptable" — 9to5Google — a corroborating second source for the August 2026 order
• Google Play Store starts distributing third-party Android app stores — 9to5Google — Aptoide Games going live as the first rival store