MOBILE July 29, 2026 · 4 min read

Google Play Catalog Sharing Is Live: Your Android App Listings Are Now on Rival Stores

Google's Play Catalog Access program went live July 22—your app listing may now appear on third-party US Android stores by default. Here's how to check your enrollment status and what it means for your ASO strategy.

By the AppsOps news desk · July 29, 2026 · Original source ↗

As of July 22, 2026, your Android app listing — including its name, icon, description, screenshots, and videos — may now be visible inside rival US Android app stores, by default. Google's Play Catalog Access program went live on that date as part of a court-ordered antitrust remedy, and unless you visited Play Console before the deadline and opted out, your store listing was enrolled automatically.

This is a meaningful structural shift for anyone running Android ASO. Your Play Store metadata is no longer exclusive to Google Play — it's now a distribution asset that third-party US storefronts can surface to users, even though every download still routes through Google Play's infrastructure (and Google's service fee still applies). Here's what you need to understand and what to do next.

What Changed on July 22

The Play Catalog Access program stems from a December 2023 jury verdict in Epic Games v. Google, which found that Google's conduct in maintaining barriers against competing Android app stores violated federal and California antitrust law. The Ninth Circuit unanimously affirmed both the verdict and the permanent injunction in July 2025, requiring Google to open its Play Store catalog to third-party US Android storefronts and barring exclusive first-launch deals with developers.

Practically, this means:

Third-party US Android stores that enroll in the program receive your app's name, icon, short description, long description, screenshots, promotional video, and feature graphic.
Users who find your app on a third-party store and tap "install" are routed through Google Play's Inline Install API — so the download still happens through Play, Google Play Protect still scans the APK, and Google's standard service fee still applies.
Developers who did not opt out by July 22 were auto-enrolled.

Check Your Opt-In Status in Play Console Now

If you haven't already, navigate to Play Console → Settings → Catalog Settings. You'll see three choices:

Publish all app listings to all enrolled third-party stores (the default if you missed the deadline)
Manage stores individually — choose which enrolled stores receive your listing
Do not publish to any third-party stores — opt out entirely

You can change this setting at any time. If you operate a health, finance, or enterprise app with strict distribution control requirements — or if you have a minimum age gate you can't guarantee third-party stores will enforce — opting out may be the right call. For most consumer apps, staying enrolled likely makes sense: more discovery surfaces at no additional cost, with the download infrastructure remaining with Google.

What This Means for Your ASO Strategy

Traditional Android ASO has always been about ranking and converting within Google Play. The catalog-sharing program changes one half of that: your metadata now functions as a storefront on platforms you didn't design for, without any guaranteed parity in how they render or rank it.

A few things worth auditing now:

Screenshots may display differently in third-party store UIs — different surrounding chrome, different card layouts, possibly different aspect ratio handling. If your creative relies on Play's specific dark background or card format to land the visual message, test how it reads in isolation.
Short description (the 80-character field) is likely the primary text hook in third-party listing surfaces, not just a secondary line below your title in Play search. It should work as a standalone value proposition, not a complement to your long description.
Localization carries over. If your listing exists only in English and a third-party store serves multilingual users, you'll appear English-only while competitors with localized metadata and screenshots convert better across multiple surfaces simultaneously. This is one of those cases where investment in localization compounds across platforms.

What About Discovery and Ranking?

It's not yet clear how third-party stores will rank or surface apps drawn from the Play catalog — their discovery algorithms are their own, and their user bases are currently small relative to Google Play. Reports suggest the first stores to enroll are smaller, US-focused Android marketplaces. Early data on install volume flowing from third-party surfaces should appear in Play Console acquisition reports over Q3 2026, though Google has not yet confirmed whether cross-store attribution will be broken out in any dashboard view.

The October 1 Billing Compliance Deadline

Separately: Google also notified developers enrolled in US external content links or alternative billing programs on July 22 that they must begin reporting transactions and paying applicable service fees starting October 1, 2026. If your app has been participating in the alternative billing program in the US, that testing window closes in roughly 10 weeks. Review which of your apps are enrolled and confirm your reporting infrastructure is ready — this is a billing compliance matter, not optional.

Action Checklist for This Week

Log into Play Console → Settings → Catalog Settings. Confirm you know your enrollment status for every app in your account.
Audit your short description and first two screenshots — they need to work as a standalone first impression, not a second screen alongside Play's native listing context.
If you serve non-English markets, review localization coverage. Your regional pricing and localized metadata are now working on more surfaces; gaps cost you more than they used to.
If you participate in US alternative billing, mark October 1 as a hard compliance date.

Sources and further reading