Google sets rules for one-tap installs from third-party Android stores
Google will allow approved third-party Android app stores to install applications with one tap and deliver updates in the background from December 1. The capability will be available through its Registered App Stores program on devices running Android 17 QPR2 or later in supported countries, which exclude the United States.
Today, Android users must enable a third-party store as an installation source and then confirm every app installation and update. Once a store is approved, it will receive the installation permission automatically. Updates can run in the background, subject to the user’s existing update settings.
Google announced the Registered App Stores program in March alongside changes it said resolved its disputes with Epic Games. Participation is optional. Stores that do not join can continue operating under Android’s existing installation flow.
Approval combines faster distribution with catalog controls
To qualify, a store must be registered as an organization and maintain verified developer identity through Android developer verification. It must provide Google with its full catalog, every new application and every update for ongoing malware screening. The store must also submit every version of its own app, matching the versions distributed through its website and other channels.
Registered stores remain responsible and liable for all content in their catalogs. They must work to keep malware and other potentially harmful apps out, remediate major security flaws brought to their attention, and avoid blocking, interfering with or concealing other app stores and Android security notifications.
Admission also carries a $10,000 annual fee, payable before Google begins its review. A store that misses a requirement, including payment, can be removed until it resolves the issue. Google says it will give notice and an opportunity to correct the problem first.
User consent and enterprise restrictions remain
The new process does not permit silent installation without consent. Stores must obtain explicit user approval for every installation. Large downloads and background installations must display a visible notification while they are running. If an installation begins from another device, the store must show a notification that does not automatically close.
IT administrators can block registered stores from being installed on managed Android devices. Google’s published program material does not specify whether that control also blocks a registered store that is already present on a device.
Google will charge additional fees for catalog screening and cleanup when more than 1% of a store’s install attempts, or more than 2% of its apps, are found potentially harmful during a 30-day period. Its pages do not explain the scanning method, turnaround time for submitted apps or the results shared with stores.
Verification infrastructure expands separately
Approved stores also gain access to the Android Developer ID API, which can check whether an app comes from a verified developer and can be installed. Google recommends that stores block applications that fail this check.
Android developer verification is a separate program. Since September 30, certified Android devices in Brazil, Indonesia, Singapore and Thailand have checked whether apps from seven participating stores originate with verified developers. Google plans to extend those checks globally in 2027.
Availability is determined by a user’s home country, so a short trip to an unsupported country does not disable one-tap installation or automatic updates. Android 17 QPR2 is a quarterly platform release; its latest build was released as a beta on October 16, and Google has not announced a final-release date. Businesses should review managed-device restrictions, approved-store policies and user guidance before the streamlined installation model becomes available in their operating markets.