Android Registered App Stores: One-Tap Installs Begin Dec. 1

Google has opened enrollment for its new Registered App Stores program, which gives qualifying third-party Android app stores a streamlined "one-tap" install flow with no secondary system confirmation screen, plus background auto-updates. The platform-level changes activate starting December 1, 2026, on devices running Android 17 QPR2 and higher — but, despite reporting that has treated this as a worldwide rollout, Google's own documentation lists roughly 140 markets as eligible at launch and does not include the United States, where the feature remains contingent on separate court approval.

What the Registered App Stores program actually does

Google describes a Registered App Store as a third-party app store that registers with the company "to access additional platform capabilities, including one-tap installs, while upholding core ecosystem trust, security, and performance standards," according to the Registered App Stores overview on the Android Developers site. Participation is entirely optional. A store that skips the program keeps operating exactly as sideloaded app stores do today — Google's documentation is explicit that "if a store chooses not to participate, it retains the same experience as any sideloaded app on Android."

The program sits alongside Android's existing developer verification rollout, which governs who is allowed to distribute apps at all. Registered App Stores status is a separate, additional layer on top of that: it changes how installs and updates feel to the end user once a store has already cleared Android's baseline distribution checks.

One-tap installs and background auto-updates, explained

Today, installing an app from a sideloaded store on Android typically requires the user to manually enable the REQUEST_INSTALL_PACKAGES permission in system settings, then approve a secondary confirmation screen for every install, and finally approve each update one at a time. Google's Registered App Stores requirements page lays out how that changes for enrolled stores:

• Permissions: Registered stores "automatically grant permission once verified," rather than requiring the user to flip a system setting.
• Installs: Users "can download and install apps directly from the store without secondary system confirmation screens" — the one-tap install.
• Updates: Apps "update in the background automatically with user control settings," instead of requiring manual approval for each new release.
• Notifications: Registered stores get notification capabilities to keep users informed of install status and update activity.

In short, a Registered App Store starts to feel, mechanically, much closer to the Google Play Store experience — tap once, the app installs, and future versions arrive without further prompts — while the catalog itself is still vetted by the store operator rather than Google.

Where it's actually available — and why "global" is the wrong word

This is the detail that has gotten muddled in secondary coverage. Google's original announcement, the March 2026 blog post titled "A new era for choice and openness," framed the rollout in sequencing terms: "This Registered App Store program will begin outside of the US first, and we intend to bring it to the US as well, subject to court approval." That framing has since hardened into a concrete regions list.

The Registered App Stores FAQ now states plainly: "Starting December 1, 2026, Registered App Store status is available on Android 17 QPR2 and higher devices" in a named list of roughly 140 countries and territories — from Albania and Argentina through the United Kingdom, Vietnam, and Zimbabwe. The United States does not appear anywhere on that list. The FAQ separately notes that Google runs a different, U.S.-specific effort — "Third-Party App Store on Play," described there as "available in the US only" — which is not the same program and does not carry the same one-tap mechanics.

Google also addresses edge cases around travel: a user's home account country determines which features are active, and "vacations or short-term international travel to unsupported regions won't disrupt existing one-tap installs or automatic updates." A permanent change of home address and account country, by contrast, causes the device to "automatically adjust feature availability" to match the new region.

Who can actually enroll

Google's requirements documentation sets a fairly high bar. Enrollment is "strictly restricted to verified Organization (Full Distribution) accounts in Android Developer Console" — individual developer accounts are explicitly not eligible. A store must also exist as a standalone, self-updating APK; "purely web-based wrappers or non-APK installation mechanisms are not eligible."

Beyond identity checks, Google requires enrolled stores to continuously share their entire hosted catalog — not just the store app itself — through a provisioned Cloud Storage bucket for ongoing malware scanning, and to carry certification under the App Defense Alliance's Mobile Application Security Assessment program. A higher bar, MASA Assurance Level 2, becomes mandatory from June 1, 2027, and a data-safety disclosure requirement using Google's App Metadata Bundle kicks in from December 1, 2027. Stores remain legally responsible for everything in their own catalogs; Google is explicit that it "won't moderate the content available within registered app stores" itself, limiting its role to the security-scanning layer.

On the technical side, a store's APK must target at least SDK level N-1 relative to the device's major Android version, declare the new INSTALL_PACKAGES_AS_REGISTERED_APP_STORE permission alongside the existing REQUEST_INSTALL_PACKAGES, and handle the standard intents Android expects of an app-store client.

The enrollment process and what it costs

Per the enrollment guide, stores start by submitting Google's Registered App Store interest form with organization identity details and distribution links. If Google pre-qualifies the account — checking developer verification status, package-name ownership, and "brand legitimacy" — the organization is invited into the Android Developer Console to formally apply. That application involves uploading the store's own APK for malware screening (which must exactly match what the store distributes elsewhere), submitting policy URLs, and granting access to the catalog-ingestion storage bucket before finally accepting the Registered App Store terms of service and paying the fee.

That fee is a flat $10,000 per year, due to initiate the eligibility review and again at each annual renewal, which Google reminds participants about 30 days ahead of the deadline. Non-payment, after notice and a chance to remediate, is grounds for removal from the program — at which point installed apps from that store stop receiving automatic updates on users' devices, though they aren't removed.

The Android 17 QPR2 tie-in

The one-tap and auto-update mechanics are platform features baked into Android itself, not just a Play Store policy, which is why Google has tied their activation to a specific OS build: Android 17 QPR2 or newer, matching the quarterly platform release (QPR) cadence Google uses to ship mid-cycle Android updates. Devices running earlier Android 17 builds, or older versions covered by the broader Android 17 rollout, won't get the Registered App Store install experience even if a store they use has successfully enrolled — the OS-level hooks simply aren't present yet on those builds.

Why this exists: the Epic Games settlement

Registered App Stores isn't a standalone product decision — it's a direct output of Google resolving its long-running antitrust fight with Epic Games. In the same March 2026 post that first described the program, Sameer Samat, President of Android Ecosystem, wrote that alongside new Play billing flexibility and lower service fees, "we have also resolved our disputes worldwide with Epic Games." The Registered App Stores framework is the mechanism Google built to satisfy the settlement's requirement for a less friction-heavy way to install competing app stores, while still letting Google impose its own security and quality gate on which stores get that easier flow.

What this means for app stores and users

For a store operator, enrolling is a trade: pay the annual fee, accept ongoing catalog scanning and liability for everything it distributes, and in return get an install and update experience that no longer scares users off with warning screens at every step. For users in the roughly 140 eligible markets, the practical change arrives gradually — only stores that actually complete enrollment and pass Google's technical evaluation will offer the one-tap flow once December 1 arrives, and only on phones already updated to Android 17 QPR2 or later. Stores that don't bother enrolling, or that fail the eligibility bar, continue operating exactly as they do today, with the standard manual-approval sideloading flow untouched.

Enterprise controls and what happens if a store is removed

Google's FAQ also spells out two practical edge cases that enterprise IT teams and everyday users will care about. On managed devices, IT administrators retain the ability to block installation of Registered App Stores entirely — the feature doesn't override existing enterprise mobility management policies, so a company that locks down sideloading today can keep doing so after December 1.

For individual users, removing a Registered App Store doesn't remove the apps it installed. Those apps stay on the device, but they stop receiving the automatic background updates that made the Registered App Store experience convenient in the first place. Reinstalling the same store can reclaim that update ownership — but only "provided no other store updated those apps in the interim," per Google's documentation, which suggests Android is tracking which store last touched a given package for update purposes, not just which store originally installed it.

Google also reserves the right to revoke Registered App Store status outright. Falling below the quality and safety bar — excessive malware in the catalog, failure to pay the annual fee, or violating the program's trust-and-safety rules — triggers deregistration after notice and a chance to remediate, at which point the store reverts to the standard, manually-approved sideloading experience for its existing and future installs.

What's next

With enrollment now open, the near-term signal to watch is which app stores actually clear Google's pre-qualification and technical review before the December 1 activation date — Google has not published a public list of approved Registered App Stores. The bigger open question is the United States: Google's own language ties U.S. availability to "court approval" it doesn't yet have, so American users and developers should expect the one-tap experience to arrive later, and on different terms, than the roughly 140 markets getting it at launch. Watch for Google to publish updated enrollment numbers, and for any U.S. court filings that would extend the program domestically, in the months after the December 1 activation date.

Written byNadia Osei

Nadia Osei covers mobile and consumer gadgets for Pandromeda: smartphones, tablets, smartwatches, earbuds and smart-home devices. She tracks launches, software updates and pricing across Apple, Google, Samsung and the rest, and builds comparisons from the manufacturers' published specifications.

More from Nadia OseiAll Mobile & Gadgets coverage