Google Play's Rival App Stores Start Rolling Out in the US

Google is reported to be beginning the next phase of its US compliance changes under the Epic v Google injunction this month, moving beyond the alternative billing access this column covered earlier in October and into the harder structural piece: giving rival Android app stores catalogue access alongside Google's own. The exact scope and timeline Google is following are not fully public, and buyers should treat specifics as provisional until Google's own developer communications confirm them. But the direction is now settled law, following the Supreme Court's refusal to pause the injunction, and Google Play rival app stores becoming a real distribution option in the US is worth planning for even before every detail is locked down.

What is reported to be changing

The injunction from the Epic v Google case requires Google to let rival app stores access the Play catalogue rather than forcing every alternative store to rebuild its own listings from scratch, alongside the alternative billing and link-out provisions already rolling out. Late this month, Google is reported to be beginning the technical changes that make that catalogue access real in the US market specifically, ahead of any broader international rollout. This is a distinct, slower-moving thread from the billing changes: allowing a user to pay through a different system inside an existing Play listing is a narrower technical change than letting an entirely separate storefront surface and distribute that same catalogue of apps.

Why this thread moves more slowly than billing

Alternative billing is largely a checkout-layer change: a different payment processor sits behind a purchase flow a user already reached through Play. Rival store catalogue access is a distribution-layer change, and it touches questions billing did not have to answer, including how app updates propagate across stores, how a rival store's own review and moderation standards interact with Google's, and how installs originating in a rival store get attributed back to the campaign that drove them. None of that infrastructure existed before this year in the US market at any real scale, which is why Google Play rival app stores access is landing as a phased rollout rather than a single toggle.

What changes for a UA buyer this quarter

Almost nothing changes for a campaign running today. No major rival Android store has confirmed a US catalogue integration live yet, and even once one exists, a new distribution channel takes time to accumulate meaningful install volume, particularly for titles that are not already major franchises with an audience motivated to seek out an alternative store deliberately. The medium-term risk sits in measurement rather than volume. If a rival store surfaces the same catalogue Google does, but with different data-sharing terms, a UA team's blended CPI and ROAS numbers could start including a small but growing share of installs that a standard MMP integration was never built to attribute cleanly, which is a slow-building measurement gap rather than a sudden one.

What to prepare, given how much is still unconfirmed

• Ask your MMP directly whether their SDK has a defined path for attributing installs sourced through a rival Android store once one goes live, rather than assuming existing Play attribution automatically extends.
• Watch for the first rival store to confirm a live US catalogue integration, since that will be a far more useful signal of real timeline than anything in Google's own phased announcements.
• Keep app store optimisation efforts focused on Play for now, since it remains the default and by far the highest-volume surface, but note internally which competitors' apps show up first on any rival store that does go live, as an early signal of who is testing distribution diversification fastest.
• Revisit the same operating posture UA Ledger set out in Google Play Alternative Billing Compliance Starts Now: model the change now while it is cheap to plan for, rather than waiting for volume that justifies urgency, because the infrastructure decisions namely attribution integrations take longer to build than the volume takes to arrive.

Google Play rival app stores: a worked example

Take a hypothetical mid-size publisher, Studio E, with a top-twenty grossing hybrid-casual title on Android in the US. Today, essentially all of Studio E's Play Store installs are attributed cleanly through its MMP's standard Play integration. If a rival Android store gains catalogue access and begins surfacing Studio E's title without any coordination from Studio E itself, a small share of installs, say a hypothetical 2% to 4% in the first few months based on how modestly earlier alternative-store launches elsewhere have scaled, could start arriving through a path the MMP was never configured to track. Blended CPI would tick down slightly as those untracked installs raise the total install count without a matching increase in tracked paid spend, which looks like an efficiency gain on a dashboard but is actually a measurement gap. Studio E's correct response is not to chase that channel with paid spend prematurely. It is to ask its MMP now, before any rival store reaches meaningful US volume, exactly how attribution for a rival-store install would work, so the eventual gap is a known and monitored one rather than a silent distortion in the CPI trend line.

Google Play rival app stores: what to watch next

Three signals will indicate this thread is moving from legal fact to operational reality. The first is any named rival Android store publicly confirming a live US catalogue integration with Google, rather than the general framework Google is reported to be building toward. The second is whether any MMP publishes a defined attribution path for rival-store installs ahead of that first integration going live, which would suggest the measurement industry sees this as imminent rather than speculative. The third is whether Google's own developer communications narrow the currently vague scope and timeline into specific dates, since a firm date would be the clearest sign the phased rollout described this month has moved from early technical work into a publishable schedule.

The pattern across both threads

Billing and rival store distribution are being treated by Google as two separate compliance obligations moving on two different timelines, and buyers should track them the same way rather than folding them into a single "Play compliance" story. Billing changes have already started reshaping payment cost lines for the publishers using them. Rival store distribution is still mostly a legal and technical fact rather than an operational one, but Google Play rival app stores gaining catalogue access this month is the step that eventually makes it operational, and the buyers who have already asked their measurement vendor the attribution question will be the ones ready when a first rival store actually goes live with volume worth measuring.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• The Epic-Google settlement on Play fees: what buyers get
• Google Play Alternative Billing Compliance Starts Now