Google One-Tap Android App Installs From Approved Third-Party Stores Outside U.S.
Google will enable one-tap Android app installs from approved third-party stores outside the U.S. starting December 1, 2026. The change applies only to devices running Android 17 QPR2 or later in supported countries and requires strict identity and malware-scanning controls.
Program Scope and Eligibility
The Registered App Stores program, announced in March, allows stores that pass identity checks and submit their full catalog to Google for ongoing malware scanning to receive the one-tap install feature. Stores must:
- be registered as an organization and keep developer identity verified under Android developer verification;
- send every version of its own app to Google for malware screening, matching the version published on the web and other channels;
- work to keep malware and other potentially harmful apps out of its catalog;
- fix major security flaws that come to its attention; and
- not block other app stores from being installed.
If a store meets these criteria, it gains automatic permission to install apps with one tap and to run background updates under the user’s own update settings.
User Interaction and Safeguards
Users must first enable the store to install apps. After that, each install and each update still requires explicit confirmation. Large downloads and background installs must show a visible notification while they run. If an install is started on another device, the store must display a notification that does not close automatically. The policy explicitly prohibits silent installs without user consent.
IT Administrator Controls
Administrators can block registered stores from being installed on managed devices. Google’s program pages do not state whether the block also applies to a store that is already installed.
Geographic and Version Constraints
The feature is available only in supported countries outside the U.S. and only on devices running Android 17 QPR2 or later.
Operational Impact for Developers and Store Operators
Store operators must maintain a clean catalog and submit every app version for malware screening. Failure to do so will prevent the store from receiving the one-tap install feature. Developers of apps distributed through these stores should verify that their app versions match the ones submitted to Google for scanning.
Monitoring and Logging Recommendations
Defenders should inspect the following logs:
- Device policy logs for store enablement events;
- Install and update logs for confirmation prompts and background update activity;
- Malware scanning reports from Google for catalog integrity; and
- Notification logs for large downloads and cross-device install alerts.
Next Steps for IT and Security Teams
- Verify that managed devices are running Android 17 QPR2 or later.
- Review the list of approved third-party stores and assess their catalog hygiene.
- Configure device policy to block registered stores if required.
- Monitor install and update logs for unexpected background activity.
- Ensure that notification policies enforce visibility for large downloads.
Open Questions
- Does blocking a registered store on a managed device also prevent background updates for apps already installed from that store?
- How will Google enforce the requirement that every app version matches the one submitted for malware screening?
The policy shift removes traditional confirmation screens for approved stores, potentially increasing install velocity but also raising the stakes for catalog hygiene. IT administrators can block registered stores on managed devices, but it is unclear if the block applies to already-installed stores. The requirement for visible notifications on large downloads or background installs provides a minimal user-visible safeguard.
Related coverage
- Magento Stores Hit by Scanner-Evasion JavaScript Loader Campaign
- Wasmtime Sandbox Escape Vulnerabilities Exposed