Android Registered App Stores: One-Tap Installs Guide

Android users outside the United States will soon install apps from approved third-party stores with a single tap. Google opened enrollment for its Registered App Stores program on 27 October 2026. The simplified experience launches on 1 December 2026 for devices running Android 17 QPR2 and higher.

This change stems from ongoing competition cases. It gives verified stores OS-level features while keeping malware scanning and policy checks in place. Participation remains optional for store operators.

What Registered App Stores Offer Users

A Registered App Store is a third-party marketplace that completes formal verification with Google. Once approved, it gains platform capabilities that standard sideloaded stores lack.

Users of registered stores get:

• One-tap installs without extra system confirmation screens
• Automatic background updates, similar to Google Play
• Download progress indicators
• Notification support so the store can surface important status changes

Non-registered stores continue to work as they do today. Users must still grant install permissions manually and confirm each install.

The user’s home country determines availability. Short trips abroad do not interrupt existing one-tap installs or updates. A permanent move to an unsupported country removes the features.

Geographic Availability and Requirements

Support starts 1 December 2026 on Android 17 QPR2 and later. The program covers dozens of countries, including India, Brazil, Indonesia, Japan, South Korea, Canada, Australia, Mexico, and many others. It excludes the United States and most of Europe for now.

The US exclusion relates to separate court remedies that require Google to distribute certain third-party stores inside Google Play itself. Outside the US, the Registered App Stores path applies.

Device requirements are straightforward:

1. Run Android 17 QPR2 or a newer build.
2. Have a Google account whose home country is in a supported region.
3. Install a store that has completed registration.

Pixel phones are expected to receive the necessary QPR2 builds in the coming weeks. Other manufacturers will follow their own schedules.

How Store Operators Enroll

Store developers must use a verified Organization account in Android Developer Console. Individual accounts cannot register a store.

The process has five main stages:

1. Submit an interest form with organization details, distribution links, and the Google Account linked to Developer Console.
2. Complete pre-qualification. Google checks organization legitimacy, package name ownership, and brand details.
3. Pay the annual registration fee of $10,000. Payment is required before full review begins.
4. Upload the store APK for malware scanning, provide mandatory policy URLs, and share the complete app catalog for ongoing scanning.
5. Receive activation once approved. Status updates to Registered App Store in the console.

Required public links include a privacy policy, trust and safety policy, developer agreement, intellectual property dispute process, illegal content removal channel, parental controls explanation, government request intake process, and customer support channel. Documentation must be in English.

Stores must also achieve Mobile Application Security Assessment (MASA) certification at AL2 level by 1 June 2027 and renew it annually. They must continuously upload new and updated APKs to a Google-provisioned Cloud Storage bucket for scanning.

If an application is rejected, operators can appeal or contact support through the official form.

What Changes for Everyday Installs

On a supported device, installing a registered store follows a simplified screen. The system confirms the store is registered with Android, lists the capabilities it receives, and links to its terms, privacy policy, and support.

After the store is installed, apps from that store install with one tap. Updates arrive in the background without per-update prompts, provided the user has not disabled automatic updates in the store’s settings.

If you uninstall the store and later reinstall it, it automatically reclaims update ownership for its previously installed apps, as long as no other store updated them in the meantime.

Enterprise administrators can still block Registered App Stores on managed devices through administrative controls.

Differences from Standard Sideloading

Feature	Registered App Store	Standard Third-Party Store
Install permission	Granted automatically after verification	User must enable Install unknown apps manually
Install confirmation	One-tap, no secondary system screens	Manual confirmation for every app
Updates	Background automatic (user-controlled)	Manual approval per update
Catalog scanning	Continuous malware scanning by Google	No automatic catalog sharing required

These differences apply only in supported regions on Android 17 QPR2+. Elsewhere, the classic flow remains.

Tips for Users

• Check your Android version and QPR level before expecting one-tap behavior. Search Settings for system update or about phone.
• Confirm the store is registered before relying on automatic updates. Non-registered stores still require manual steps.
• Review the store’s privacy policy and trust and safety rules, which must be public and linked during the install flow.
• Keep Play Protect enabled. Registration does not replace device-level protections. See our guide on Android Advanced Protection for stronger device-level controls.
• If you travel frequently, remember that short trips do not disable the features, but a permanent country change does.

Tips for Store Operators

• Prepare all required policy URLs before starting the interest form. Incomplete declarations slow review.
• Budget for the $10,000 annual fee and potential additional review costs if malware issues arise.
• Automate catalog uploads to the provisioned Cloud Storage bucket using service accounts and the Google Cloud CLI or client libraries.
• Plan for MASA AL2 certification well before the 1 June 2027 deadline.
• Monitor application status badges in Android Developer Console (Draft, In review, Registered, Rejected).

Conclusion

Android Registered App Stores give verified third-party marketplaces a cleaner installation experience starting 1 December 2026 outside the United States. Users gain one-tap installs and background updates. Operators must meet security, policy, and fee requirements.

The program remains optional. Stores that skip registration continue under existing sideloading rules. For most users in supported countries on recent Android 17 builds, the change reduces friction when using alternative stores while preserving Google’s scanning requirements.

Check Android Developer Console and the official Registered App Stores documentation for the latest enrollment status and regional list, as the program continues to evolve.

Sources

• Overview of Registered App Stores — Android Developers
• Enroll as a Registered App Store — Android Developers
• Frequently asked questions — Android Developers
• Requirements — Android Developers
• Android developer verification preview video — Android Developers YouTube channel