Android Registered App Stores Program: Who Actually Gets One-Tap Installs Starting Dec. 1

Google opened applications this week for its Android Registered App Stores (RAS) program, a certification that lets approved third-party stores install apps with a single tap and update them in the background, similar to how the Play Store already works (dig.watch, this week). The feature itself doesn't show up for users until December 1, 2026, and even then only on phones running Android 17 QPR2 or later, in a set of "select regions" Google hasn't fully named, through stores that have actually applied and been approved.

The program skips the United States entirely. There, third-party stores reach users through Google Play under a separate antitrust remedy, and nothing in this week's reporting identifies a single store that's been accepted into RAS yet (Ars Technica, this week). Here's what actually determines whether the one-tap experience lands on a given phone.

Three conditions have to line up at once:

• A home country inside Google's supported list, described only as "select regions" outside the U.S. and Europe, with no full list published yet.
• A device already running Android 17 QPR2 or later, which anyone can check under Settings right now.
• A third-party app store that has applied to RAS and been formally approved, something no current report identifies.

What the Android Registered App Stores program actually changes

Using a third-party app store on Android today means manually enabling it in system settings, then confirming every install and every update by hand (The Hacker News, this week). RAS removes those repeated prompts, but only for stores Google has approved. Once accepted, a store can install apps with one tap and update them quietly in the background under the user's existing update settings, the same way the Play Store does.

Google told dig.watch that accepted stores will get "preferential treatment on the Android platform," and said the program was first announced earlier this year, in March, alongside changes the company said resolved its disputes with Epic Games (dig.watch, this week; The Hacker News, this week). Joining is optional: stores that skip the application, or don't get accepted, keep operating exactly as they do today.

Getting approved isn't just a checkbox. Store operators have to meet a list of requirements, including protecting intellectual property, removing illegal content, and publishing privacy policies for both users and developers, and they have to submit documentation in English along with a copy of every app in their catalog (Ars Technica, this week).

Android 17 QPR2: the version gating one-tap app installs

The feature is tied to a specific platform release, Android 17 QPR2 or later. The latest beta build landed two weeks ago, on October 16, and Google's own release notes still give no date for the final, stable version (The Hacker News, this week).

Google has said QPR2 support is expected to reach Pixel phones first, "in the coming weeks" (Ars Technica, this week). Nothing in the cited reporting lays out a rollout schedule for other manufacturers. Phones on older Android versions can't get the one-tap behavior at all, regardless of region, because Google has tied it specifically to this one quarterly release (dig.watch, this week).

Practically, that means checking the Android version under Settings before assuming anything changes on December 1. A supported country and an approved store won't matter if the phone hasn't received QPR2.

Eligible regions, and why the U.S. and EU play by different rules

Google describes RAS as covering "select regions" that include dozens of countries outside the U.S. and Europe, but there's no complete, named list in the reporting so far (dig.watch, this week). Eligibility follows a user's home country rather than physical location, so a short trip abroad won't turn off one-tap installs or background updates for someone whose account is tied to a supported country (The Hacker News, this week).

The U.S. sits outside RAS entirely. Third-party stores there can instead be distributed through Google Play, under antitrust remedies tied to Google's Epic Games case. Those court-ordered remedies took effect last year, in early November 2025, after Google lost its appeal and the Supreme Court declined to stay the injunction (ProMarket). Google's own program for listing third-party stores inside Google Play has been running since July 22, roughly three months ago, and Aptoide is the only store identified in the cited reporting so far (Ars Technica, this week; The Hacker News, this week).

Europe runs on a third framework altogether. Alternative app distribution there goes through the EU's Digital Markets Act rather than RAS, and nothing in the reporting confirms whether RAS adds anything on top of what the DMA already requires (dig.watch, this week). U.S. and EU users are covered by those separate rules, not by this program, no matter how the RAS rollout plays out.

What stays the same: consent, managed devices, and stores that skip the program

One-tap doesn't mean silent. Google's rules still require explicit user consent for every install, and RAS stores "must not install apps silently without user consent" (The Hacker News, this week). Large downloads and background installs have to show a visible notification while they run, and an install kicked off from another device has to trigger a notification that doesn't auto-dismiss.

Work and school devices get a carve-out. IT administrators can block registered stores from being installed on managed devices, though Google's program pages don't say whether that block also applies to a store already installed before the policy kicks in (The Hacker News, this week). None of these benefits extend to stores that stay outside the program. They keep running on today's multi-step confirmation process, since joining RAS is entirely optional.

What Google's security screening does and doesn't prove

Dropping confirmation screens raises an obvious question: does one-tap convenience trade away security friction? Google's answer leans on two mechanisms. Registered stores have to submit their full catalog, plus every new app and update, for ongoing malware screening, and they're required to register as a verified organization (The Hacker News, this week).

Stores also get access to the Android Developer ID API, a tool that checks whether each app in their catalog comes from a verified developer; Google recommends blocking installs that fail the check. That developer verification system is a separate, earlier-stage program currently in its first phase with seven app stores. Certified devices in Brazil, Indonesia, Singapore, and Thailand have been checking for verified developers since September 30, about a month ago, and Google plans to extend the checks worldwide in 2027 (The Hacker News, this week).

None of this amounts to independent proof that a given store is safe. Google's program pages don't describe how submitted apps are actually scanned, how fast new uploads get checked, or what the checks turn up. Each store also stays fully liable for its own catalog, since Google says it won't moderate the content itself (The Hacker News, this week).

What joining actually costs a store

Participation runs $10,000 a year, due before Google even begins reviewing an application (dig.watch, this week; Ars Technica, this week). Dig.watch frames that upfront cost as a potential barrier for smaller competitors trying to get in.

Google also builds in ongoing enforcement. If more than 1% of a store's install attempts or more than 2% of its catalog gets flagged as potentially harmful over a 30-day window, those thresholds trigger additional screening and cleanup fees, not automatic removal (The Hacker News, this week). Removal instead follows a failure to meet any requirement, including late payment, and Google gives notice along with a chance to fix the problem first.

No approved or pending store has surfaced in the reporting so far, and it's unclear whether names like Epic Games Store, Samsung Galaxy Store, Amazon Appstore, or F-Droid plan to enroll. Approval is also only one gate: a store still needs to operate in a supported region, and the user still needs eligible Android software, before any of this shows up on a real phone.

What to check before December 1

December 1 is when Google's program technically goes live, not a guarantee that one-tap installs will appear on any particular phone that day. Checking the Android version under Settings is the easiest thing to rule in or out right now. U.S. readers should look at Google Play's existing third-party store listings under the separate Epic remedy, where Aptoide is currently the only store named in the reporting. EU readers should keep tracking DMA-based alternative-store rights rather than RAS. Until Google publishes the regional details and a specific store confirms RAS approval, there's no way to verify access on any single device in advance.