Your Licensed Android Listings Went to Rival Stores on 22 July. Nobody Asked Your Licensor.

On 22 July 2026, Google began sharing US Play Store listings with rival Android app stores by default. If you license APK games, your whole catalogue moved too. The opt-out sat in a Play Console setting most licensees never opened, and the default was yes.

Nobody in the licensing chain signed anything. Nobody negotiated it. A court told Google to open the catalogue, Google emailed developers a month's notice, and the switch flipped on a date. That is a distribution change arriving through a default rather than a decision, which is a category of risk most licence agreements were never drafted to handle.

📅 What Google Actually Did

This is the compliance tail of Epic v. Google. Judge James Donato's permanent injunction — modified and re-entered on 4 March 2026 — forces Google to stop blocking rival Android app stores and to open Play's catalogue to them. Google and Epic jointly withdrew their proposed settlement modification in July 2026 and Google moved to comply with the original order instead.

Two separate programs came out of that. One lets competing app stores be distributed inside Google Play. The other — the Play Catalog Access Program — hands your listing data to those stores. Google notified developers on 22 June 2026 and set the deadline a month out.

What travels is specific. Per Google's own Play Console help page, from 22 July 2026 your US listings, "including the name of your apps and games, their icons, their description, and any screenshots and videos you provided to Google Play, will be made available to third-party US Android app stores."

The control lives in Play Console under Settings > Catalog Settings, with three options: publish all listings to all enrolled stores, manage access store by store, or opt out entirely. And then the sentence that matters: "If you do not choose an option, Google Play will begin to provide your app listing(s) to third-party US Android app stores starting on July 22, 2026."

Silence was consent. For a licensee running dozens or hundreds of published APKs across one or more developer accounts, silence was almost certainly what happened.

The shop window moved. The shelf did not.

Before anyone panics: the binary is not being redistributed. Google's page is explicit that downloads still complete "through Google Play on the same terms as any other download," and that "Google Play's service fee will continue to apply." A rival store surfaces your listing, categorises it, curates around it — and then hands the install back to Play.

Scope is narrow too. The order covers apps on mobile and tablet form factors serving users in the United States. If your licensed catalogue isn't published to US Play users, nothing happened to you on 22 July.

🏪 So Far, Exactly One Store Has Turned Up

On 10 August 2026, Aptoide Games became the first rival app store distributed through Google Play in the US in over a decade, as reported by TechCrunch. Aptoide's platform carries more than 40,000 Android applications and around 25 million monthly active users.

That is one store, games-focused, at a scale that is real but not Play-sized. The Epic Games Store — the obvious candidate given who brought the case — had not confirmed a listing date as of mid-August. So the honest read today is: your listings are syndicated to a small set of destinations, currently one confirmed.

The reason to care anyway is duration and direction. Trade coverage puts the injunction's life at roughly three years from the point catalogue-access technology is fully functional, which would run to around mid-2029; Google's own developer documentation states no end date at all. Treat it as a multi-year window with open onboarding, not a one-off event. The number of stores holding your listing metadata is a number that only goes up.

📜 Your Licence Names Channels. This Is Not One of Them.

Pull any competent APK licence and you will find distribution scoped in one of three ways: a named platform ("Google Play"), a named channel type ("app stores operated by Licensee"), or a permitted-territory-plus-permitted-platform grid. The clause exists because the licensor is selling you a slice of reach, and the slice has edges.

So: did syndication breach a licence that names Google Play?

Most of the time, on most drafting, no. The install runs through Play. The fee runs through Play. Functionally you are still distributing through the named platform; a third-party store is acting as a discovery surface in front of it. If your clause is written around distribution, you are probably fine.

Two other clause families are where this actually bites, and they are the ones nobody reads:

• Marketing and materials clauses. Language like "Licensee shall not permit any third party to reproduce or display the Materials without prior written approval" does not care whether a binary moved. Your icon, screenshots and store copy are the Materials. They were reproduced by a third party. That is a plain reading, and it does not require anything to have gone wrong for it to be true.
• Approval clauses. Character and brand licences routinely require sign-off on placement, not just artwork. Approval was granted for a Play listing. It was not granted for a listing inside a storefront the licensor has never heard of.

There is also a question of who made the choice, and it is less obvious than it looks. If you publish licensed APKs under your own developer account, you are the developer of record and the default landed on you. If a licensor publishes and you resell, they own it. If a white-label operator or an agency set up the account years ago and still holds the credentials, a fourth party owns a decision about your catalogue and does not know it. That last case is more common than the industry admits, and it is the one worth checking first.

🎨 The Asset That Moved Is the One Brands Control

Look again at the list of what gets syndicated: name, icon, description, screenshots, video. For an unbranded match-3 that is marketing collateral. For a licensed character title, that list is close to a complete inventory of the assets a brand's approval pipeline exists to govern.

Style guides for character IP do not stop at "use the approved artwork." They cover adjacency — what the character can appear next to — and context, and co-branding, and whether a mark can appear in a curated list alongside third-party products. A rival app store's category page is exactly the kind of surface those rules were written for.

And Google says the quiet part in its own documentation: "third-party US Android app stores are not governed by Google Play's content and other policies, and may have their own content and other policies." Which is legally unremarkable and operationally significant. Play's content rules are the reason a brand was comfortable in the first place. Those rules do not travel with the listing.

Whether a Play content rating travels either is not something the developer documentation addresses. If you run kids' or family titles under licence, that is a question to put to your licensor and to the enrolled stores directly rather than to assume in either direction.

🧮 What This Does Not Change

The counterweight, because over-reacting to this costs real money too:

• No new build. No re-signing, no new package name, no separate APK to maintain per store.
• No second billing integration. Play handles the transaction as before.
• No new SDK, no new consent surface, no new crash-reporting split.
• No new store account to open, no new review queue to wait in.
• Nothing outside the US, and nothing outside mobile and tablet form factors.

That is the whole point. The cost here is not engineering, which is why it will get skipped. Engineering costs produce tickets. Contractual and relationship costs produce nothing at all until the day a licensor's brand team runs a search and finds their character in a storefront nobody told them about.

✅ The Twenty-Minute Audit

1. Enumerate the accounts. Every Play developer account carrying licensed titles, including any a contractor, agency or former partner set up. If you cannot list them from memory, that is the finding.
2. Read the current state. Settings > Catalog Settings in each console. Untouched means enrolled. Write down what you find before you change anything.
3. Search the licences. Grep the PDFs for: distribution platform, permitted channel, marketing materials, approval, sublicense, third party. Ten minutes per agreement.
4. Split the catalogue. Unbranded originals you fully control: leave them enrolled. Free incremental discovery with no downside is not a thing to refuse. Branded and character titles: opt out, or use per-store control, until you have written approval.
5. Tell the licensor first. One paragraph: what the court ordered, what the default did, what you set it to. Being the person who reported it is worth more than being right about the clause.
6. Fix it at renewal. Add language covering platform-mandated syndication of listing assets. This will happen again, in other jurisdictions, under other remedies, and you would rather have a clause than an argument.

🔭 Defaults Are Becoming Your Distribution Strategy

For most of Android's history, where a licensed catalogue appeared was a decision someone made and could point to in a contract. That assumption is quietly expiring. Between the EU's Digital Markets Act and a US injunction with years left to run, the surfaces your apps appear on are increasingly set by remedies, defaults and enrolment deadlines rather than by a deal.

Aptoide is not the story. The story is that a licensee's distribution footprint can now widen without anyone in the chain choosing it, on a schedule set by a court and a console setting. The discipline that follows is unglamorous: treat "where is this title listed" as a fact you check on a cadence, not a clause you rely on. Monthly, not at renewal. It is the same reason you monitor which territories your licensed Android games are actually serving, rather than trusting the geo-restriction you configured two years ago.

Concretely, this week: open Play Console, check Catalog Settings on every account, and split your catalogue into "fine as is" and "needs an email." Most operators will find the split is 90/10 and the whole job takes an afternoon. The ones who skip it will find out from a licensor instead.

🌲 Where Forestry Games Fits

Forestry Games has licensed games since 2017 and its catalogue of 1,049 titles spans HTML5 and Android APK games, with titles published on Google Play and the App Store. Because it develops HTML5 games in-house and works with branded IP, licensing questions like this one — which channel a grant actually covers, who is the publisher of record, what happens to listing assets — come up constantly on the licensor side of the table.

If you are sizing an Android catalogue and want the distribution scope written down rather than assumed, the full catalogue and the licence and pricing terms are the place to start; for buyers who want to publish under their own name and control their own store presence, the source code options are the relevant route. Ask what the grant covers before you sign, not after a court changes the shape of the shelf.