Google Opens the Play Store Catalog to Third-Party App Stores: What US Developers Must Do

Starting July 22, 2026, Google will begin sharing your app and game listings — name, icon, description, screenshots, and videos — with any third-party US Android app store enrolled in its new Play Catalog Access Program.

The change stems directly from the Epic v. Google antitrust order and was first flagged to developers on June 22, 2026, giving a 30-day window to opt out before the default "opt-in" behavior kicks in.

For app marketers and ASO teams, this isn't just a legal footnote — it changes who controls your metadata, where your listing can appear, and how discovery and brand risk need to be monitored going forward. Here's exactly what's changing, what your options are, and what to do before the deadline.

Quick Facts

• What: Google Play will make enrolled US developers' app/game listings — including icons, descriptions, screenshots, and videos — available to registered third-party US Android app stores
• When: Rollout begins July 22, 2026; developers were notified June 22, 2026
• Where: US apps and games only, distributed to enrolled US third-party Android app stores
• Price / Key Spec: No new fee for the catalog-sharing itself; Google Play's standard service fee still applies to any download completed through this mechanism
• Why it matters: The default setting is opt-in — if you take no action in Play Console, your listing goes live on third-party stores automatically on July 22

What Is the Play Catalog Access Program? / What Changed?

The Play Catalog Access Program is Google's mechanism for complying with the US court order in the Epic Games v. Google antitrust case. Rather than requiring every third-party Android app store to independently scrape or rebuild app listings, Google will now expose a feed of developer-approved (or default-included) US app and game metadata to any third-party store that formally registers for the program.

Once a third-party store enrolls, it can surface your app's name, icon, description, screenshots, and promotional video inside its own storefront — effectively giving competing Android marketplaces a ready-made catalog on day one, without the years-long bootstrapping problem alternative stores have historically faced. Critically, the download itself is not decentralized: when a user installs your app through one of these third-party listings, the transaction is still fulfilled through Google Play, under Google Play's standard terms, and Google Play's service fee still applies. In other words, this is a discovery and distribution change, not (yet) a payments or billing change.

Developers manage their participation entirely inside Play Console, under Settings > Catalog Settings, where three options are available. If no option is selected by July 22, Google defaults every US listing to being shared.

Catalog Access Deep-Dive

What Gets Shared

The listing package third-party stores receive mirrors what already lives on your Play Store page: app/game title, icon, written description, screenshots, and any promotional video assets. No pricing, review, or ranking data is part of the feed — this is purely the ASO-facing creative and metadata layer, the same assets your team already tunes for Play Store conversion rate optimization.

How Downloads Actually Work

A user browsing a registered third-party store sees your listing rendered natively in that store's UI, but tapping "install" routes the transaction back through Google Play. That means Play Protect scanning and Google's standard security review still apply to the install itself — the third-party store is functioning more as a discovery front end than as an independent distribution channel, at least for stores that stay compliant with the program's rules.

Developer Choices in Play Console

Four things determine what happens to your listing after July 22:

• Publish all my app listings on all third-party app stores — maximum reach, but you're opted into every enrolled store, including ones you haven't vetted for content or brand-safety policies
• I'll manage all third-party app stores individually — granular, per-store control, best for teams that want to selectively pursue distribution partners (e.g., gaming-focused storefronts)
• Do not publish any of my app listings on any third-party app stores — full opt-out; your listing stays exclusive to Google Play
• Do nothing — this is not a neutral choice. Google will auto-enroll your listings in the default sharing behavior starting July 22

Before vs. After: What Changes on July 22

Opt-Out Deadline & Availability

There is no cost to opt out, opt in selectively, or do nothing — the "cost" is entirely strategic. The opt-out window closes July 22, 2026, and the setting lives in Play Console under Settings > Catalog Settings. Google has said the choice can be changed at any time going forward, so this isn't a one-shot, irreversible decision — but whatever setting is active on July 22 determines your default exposure from day one of the program.

What This Means for Developers

1. Audit your Play Console settings now. Confirm your Catalog Settings selection before July 22 — don't rely on the default.

1. Re-check your listing assets. Since your description, screenshots, and icon are about to circulate more widely, this is a good moment to run a full metadata and creative audit — tools like FoxData's App Data API can help pull and monitor your current listing data programmatically across markets.

1. Track where your listing actually shows up. Once third-party stores start pulling your catalog data, monitoring becomes a discovery problem as much as a legal one.

1. Loop in legal/compliance early if your app operates in a regulated category, since third-party stores may not enforce the same content policies Google Play does.

What This Means for App Marketers & ASO Teams

1. Your Play Store metadata is now doing double duty. Titles, descriptions, and screenshots optimized purely for Google Play search ranking will now also represent your app inside third-party storefronts with different layouts and algorithms — worth reviewing with FoxData's ASO Impact Analysis tools to see how metadata changes ripple through visibility.
2.  
3. Keyword strategy doesn't automatically transfer. A description tuned for Play Store keyword density may not perform the same way in a third-party store's own search logic — this is a good trigger to revisit your approach with dedicated keyword research tools.
4.  
5. Agencies managing multiple client accounts should treat this as a new reporting line item — enrollment status, opt-out decisions, and cross-store visibility are now part of the ASO conversation. FoxData's agency data solutions can help track this at scale across client portfolios.
6.  
7. Indie and small teams without dedicated ASO resources can start with FoxData's free ASO tools to get a baseline read on current listing performance before third-party exposure begins.
8. Watch keyword and category performance metrics over the following weeks — a sudden shift in install source or ranking behavior post-July 22 is worth diagnosing with app keyword analytics rather than assumed to be Play Store-only noise.
9.  

What This Means for Consumers

For everyday Android users, the visible change is subtle at first: third-party app stores will start looking more like Google Play, with recognizable app names, icons, and screenshots instead of sparse or incomplete listings. That should make legitimate third-party stores more usable and easier to trust. The tradeoff is that as users get more comfortable browsing outside Google Play, they may also become more comfortable installing from storefronts that don't apply the same content review standards. Since the install itself still routes through Google Play in compliant scenarios, users retain Play Protect scanning — but only for stores that follow the program's rules, which won't cover every third-party marketplace that pops up in this newly opened landscape.

Frequently Asked Questions

When does the Play Catalog Access Program launch?

Third-party US Android app stores can begin accessing enrolled developers' Play Store listings starting July 22, 2026. Google notified developers of the change on June 22, 2026, giving a 30-day window to review and adjust Catalog Settings before the rollout.

Does opting out cost anything?

No. Choosing any of the three Catalog Settings options — publish to all, manage individually, or opt out entirely — is free and can be changed at any time in Play Console.

Does this affect Google Play's service fee?

No. Even when a download originates from a third-party store's listing, the transaction is still completed through Google Play under Google Play's existing terms, and the standard service fee continues to apply.

How does this compare to Apple's App Store rules?

Apple's ecosystem remains considerably more closed; the Epic v. Apple ruling did not produce an equivalent catalog-sharing mandate. Google's changes stem from a separate case, Epic v. Google, where courts found Google's Play Store practices anticompetitive in ways the Apple ruling did not replicate.

What should developers do to prepare?

Log into Play Console before July 22, review Settings > Catalog Settings, and make an explicit choice rather than relying on the default. Pair that decision with a fresh audit of your listing metadata and screenshots, since those assets are about to reach a wider, less controlled set of storefronts.

Bottom Line

July 22, 2026 marks the point where Google Play's app and game catalog stops being exclusive to Google Play - a direct consequence of the Epic v. Google antitrust order. Whether that's an opportunity or a risk depends entirely on the choice developers make in Play Console before the deadline, and on how well their ASO metadata is prepared for a wider, less controlled discovery surface. FoxData will continue tracking how third-party store visibility affects keyword rankings and install attribution in the weeks following rollout — bookmark this page for updates.