Starting July 22, any qualifying third-party Android app store in the United States can tap into the Google Play catalog and offer those apps to users, Google has confirmed. The move, first reported by Engadget and detailed on Google’s new Play Catalog Access Program page, is the latest consequence of the 2023 Epic Games antitrust settlement. But don’t expect a free-for-all. Every download will still be routed through Google Play’s own servers, Google’s service fees will apply, and the privilege of entry will cost each store $10,000 in the first year alone.

The New Third-Party Store Rules, Explained

Google’s new program doesn’t mean you’ll see the Play Store’s 3 million apps suddenly sprout on a dozen alternative stores overnight. Instead, it sets up a controlled pipeline: approved external stores can list apps that developers already submitted to Google Play, but the actual installation package is fetched from Google’s servers via the Play Store app. Think of it as a storefront-within-a-store—the rival shop handles discovery, but Google handles delivery and security.

To qualify, a third-party store must:

  • Submit to a security review and pay a one-time $5,000 onboarding fee.
  • Pay an additional $5,000 annually to maintain access to the Play catalog.
  • Target only U.S. users; the catalog cannot be used to distribute apps outside the country under this program.

Google sent a notice to developers that their existing Play listings “may be made available to these external Android app stores.” Developers can’t opt out individually—their apps appear in the catalog feed to approved stores by default. Google has not yet detailed any per-app opt-out mechanism in its public documentation; developers concerned about brand safety should monitor the official policy updates.

The program replaces an earlier proposal called “Registered App Stores,” announced in March 2026, which would have made it easier for sideloaded stores to be installed by users. Google and Epic have now withdrawn that proposal from court review, allowing the current catalog-access model to move forward without further litigation.

For Android Users: More Stores, But the Same Install Button

If you’re an Android user in the U.S., on July 22 you might see app recommendations or storefronts from companies like Samsung, Amazon, or niche gaming platforms suddenly offering titles that were previously exclusive to Google Play. The experience will be seamless in one sense: when you tap “install” in a third-party store, your phone will download the app via Google Play’s infrastructure, triggering the same permission dialogs, malware scans, and installation flow you’re used to.

That continuity is intentional. Google argued in court that its control over distribution protects security, and this model preserves that argument. The third-party store gets to build its own user experience and brand, but it can’t bypass Play Protect or Google’s installation verification. For users, the main change is choice—you might find apps curated by your carrier, a game store, or a payment provider, all offering potentially different promotions or billing options.

Speaking of billing: because Google already opened the Play Store to alternative payment systems as part of the settlement, any of these third-party stores could direct you to a developer’s own website to pay, or use an alternative processor. Google’s commission on applicable purchases dropped from 30% to 10% in many cases, and developers can now show external purchase links inside their Play listings. So if you buy a digital item through a third-party store that uses a non-Google billing flow, the developer might pass some savings on to you—or not. The price is set by the developer, not the store.

For Developers: A New Visibility Channel, but Not Without Cost

If you’ve already published an app on Google Play, your app listing will automatically become available to all approved third-party catalog-access stores—unless Google carves out an opt-out later. That means your app could show up in, say, the Samsung Galaxy Store or a future Epic Games Store for Android, without any technical work from you.

The flip side: you’re still paying Google’s service fee when a user installs your app through one of these stores, because the download is fulfilled by Google Play. And if the third-party store charges its own distribution fee, you could face double-dipping—paying both the store’s cut and Google’s reduced 10% commission. Google’s documentation hasn’t clarified whether it will forbid such double fees, but early versions of the program terms focus only on Google’s own charges.

For developers who rely on in-app purchases, the landscape gets more complex. The third-party store could integrate its own billing system, which would mean a completely different revenue-sharing arrangement. Google already allows alternative billing globally, so any store could theoretically skip Google’s billing altogether and charge whatever it wants, as long as the download itself still goes through Play. Developers should review their distribution agreements and check whether being listed in external stores triggers any new obligations—especially regarding customer support, data handling, or content ratings.

If you’re concerned about brand consistency or licensing restrictions (for example, if your app uses assets licensed exclusively for Google Play distribution), contact your legal team. Some licenses may require renegotiation when your app appears in additional storefronts. Keep an eye on the Google Play Console for any new controls that may let you manage catalog access on a per-store basis.

What Windows Users and IT Admins Should Know

No Windows PC or Microsoft Store is directly affected on July 22. This program is about Android app distribution to Android phones and tablets in the U.S. However, the Windows ecosystem has a few connection points worth noting.

For home users: If you run Android apps on your Windows 11 PC via the Windows Subsystem for Android (which Microsoft has deprecated but still works for many) or through Google Play Games on PC, the apps you install still come from Google Play or the Amazon Appstore. The July 22 change doesn’t bring third-party stores to those emulation layers, because Google’s program covers only stores on actual Android devices. That said, if a third-party store gains traction on phones, developers could eventually list Windows-compatible Android apps through the same store—but that requires Google to extend the program to those platforms, which isn’t on the roadmap.

For IT professionals managing Android fleets: The bigger risk is app sourcing confusion. An employee could be lured to install a familiar app from an unfamiliar storefront that looks legitimate because it draws from the Play catalog. While the download still passes through Google Play’s security stack, the store itself might collect additional data, push alternative payment flows, or present non-curated ads. Your existing Mobile Application Management (MAM) and Mobile Device Management (MDM) policies, which typically restrict installations to managed Google Play, won’t automatically recognize these third-party store apps as safe unless the store is explicitly allowed.

Action steps for IT admins:
- Review your app allow-listing and your MDM settings: confirm that “Unknown sources” or “Install unknown apps” restrictions cover all third-party store APKs. The program doesn’t automatically make a third-party store an Android system app—users will need to sideload the store’s installer, which you can block.
- If your organization uses Android Enterprise with managed Google Play, apps from third-party stores won’t appear there by default. However, a personal profile on a work device might still access these stores. Use work profile policies to block side-loading in the personal space if needed.
- Monitor the list of approved third-party stores that Google eventually publishes. Not all stores will be equally reputable; knowing which ones have passed Google’s security review will help you advise users or set conditional access policies.
- For Windows-adjacent scenarios: If your organization runs Android apps on Windows through Amazon Appstore or Google Play Games, those environments remain separate from this change. But keep an eye on Google’s future plans—if PC-based Android stores eventually join the program, your app lifecycle management could shift.

How the Epic Settlement Forced Google’s Hand

This program wasn’t dreamed up in a product strategy meeting; it’s a court-ordered remedy. In December 2023, a jury found that Google held an illegal monopoly over Android app distribution and in-app billing. Following that verdict, Google and Epic Games negotiated a slate of changes to Google Play policies. The settlement, finalized in early 2026, required Google to lower barriers for rival stores and billing systems.

Key milestones:
- March 2026: Google announced global policy changes allowing alternative billing and external purchase links, along with a reduced 10% commission for many subscriptions and in-app purchases. It also unveiled the “Registered App Stores” idea for easier sideloading.
- April–June 2026: Epic and Google clashed over the implementation details, with Epic arguing the changes didn’t go far enough. The Registered App Stores proposal was put on hold.
- July 15, 2026: Google quietly launched the Play Catalog Access Program page and notified developers. Engadget broke the news, and soon MobileSyrup confirmed that the U.S.-only rollout starts July 22.
- September 2027 (target): Google’s documentation hints at a broader global rollout of all settlement-related changes by this date, though the company hasn’t committed to a firm schedule.

The Epic settlement also required Google to pay $700 million into a settlement fund, with $630 million going to consumers and $70 million to states. But the operational changes—like this catalog access—are what reshape the market.

What to Do Now: An Action Plan

If you’re an Android developer:
- Log in to the Google Play Console and read the “Catalog Access” section in any new policy notices. Verify whether your app’s listing will be automatically shared and whether there are any trademark or brand-protection controls you can set.
- Update your commercial agreements with third-party stores (if you already have them) to account for the Google fulfillment model. Clarify who handles refunds, customer data, and tax remittance.
- If you use copyrighted fonts, images, or licensing that assumes Play Store-only distribution, check your licenses—some may require renegotiation when your app appears in additional storefronts.

If you’re an everyday Android user:
- When you see a familiar app in a new store, pause before installing. Confirm that the store’s app listing looks legitimate. Because the actual download comes from Google Play, the app’s digital signature is validated, but the store’s own interface could host phishing links or ads.
- You don’t have to use these stores. Google Play remains the default and most secure path. If a third-party store offers a discount or an exclusive feature, weigh that against the risk of sharing your payment info with yet another entity.

If you’re an IT administrator:
- Immediately update your Android enterprise security documentation to include the existence of catalog-access stores. Notify your user base about the change and remind them of your organization’s policy on non-Play Store installations.
- Enable Google Play Protect’s “Scan apps with Play Protect” and “Improve harmful app detection” settings in your MDM, which can help catch malicious sideloaded stores.
- Consider using Android’s “Advanced Protection” mode for high-security roles, which restricts app installation to verified sources.

For Windows users who run Android apps:
- No immediate action. But if you later hear that a Windows Android emulator or Google Play Games on PC supports third-party stores, evaluate the security risk just as you would on a phone.

What’s Next: A Slow Global Rollout

While U.S. users see the change first, Google has stated that the Play Catalog Access Program will expand to other countries “at a later date.” Internal roadmap documents, cited by MobileSyrup, suggest a complete global rollout of the entire Play Store restructuring by September 2027. That includes not only catalog access but also worldwide availability of alternative billing and external links. Canadian users, for instance, will have to wait—Google Canada did not provide a timeline when asked.

For now, the playbook is clear: Google is giving up just enough control to satisfy the court order while keeping its technical and financial hooks firmly in place. The $5,000 annual fee and mandatory Play fulfillment ensure that no store can become a true competitor overnight. Whether any major player—Amazon, Samsung, Epic—takes the bait remains to be seen. Epic has long wanted its own store on Android without Google’s involvement; this program still requires Google’s involvement for every download, which may not be enough for Tim Sweeney’s vision.

But for millions of U.S. users, the July 22 start date means their Android phone is about to get a little more like the Windows desktop: a place where app stores compete, even if the landlord still collects rent.