"Approved stores get the features from December 1, but only on devices running Android 17 QPR2 or later in supported countries, which do not include the US."
How installs and updates will change for third‑party Android stores
Beginning December 1, third‑party app stores that are accepted into Google's Registered App Stores program will be able to install apps with one tap and push updates in the background on qualifying devices. Today, users must enable a third‑party store to install apps and then confirm every install and every update; under the new arrangement, a store that has been approved "gets that permission automatically once it is approved, and its updates run in the background under the user's own update settings." Large downloads and background installs must show a visible notification while they run, and if an install is started on another device the store must show a notification that does not close automatically.
Registration, identity checks, and the $10,000 fee
Google requires stores to register as organizations and to keep their developer identity verified under Android developer verification — "Google's identity check for app developers." Stores must pay a $10,000 yearly fee, due before Google starts its review. Each store remains responsible and liable for everything in its catalog; Google says it "won't moderate the content in registered stores." A store that fails to meet any requirement, including paying on time, can be removed from the program after notice and an opportunity to fix the issue.

The cyber insurance questionnaire just landed. Now what?
SOC 2, HIPAA, insurance renewals - someone has to own security strategy. Nubivance provides fractional CISO leadership without the full-time salary.
Get a security leadCatalog scanning, screening thresholds, and enforcement charges
To qualify, a store must send Google its full catalog and every new app and update for ongoing malware scanning. Google will charge additional fees to screen and clean up a catalog if more than 1% of install attempts or more than 2% of a store's apps are found to be potentially harmful over a 30‑day period. Google's program pages explicitly require stores to "work to keep malware and other potentially harmful apps out of its catalog" and to "fix major security flaws that come to its attention." The program pages do not describe how submitted apps are scanned, how quickly new uploads are checked, or what results the checks produce.
Android developer verification, the Android Developer ID API, and rollout limits
Registered stores will get access to a Google tool, the Android Developer ID API, to check whether each app in their catalog comes from a verified developer and can be installed; Google recommends stores block installs of apps that fail the check. Android developer verification is already in its first phase with seven app stores. Since September 30, certified Android devices in Brazil, Indonesia, Singapore and Thailand have checked that apps from those stores come from verified developers; Google plans to extend the checks worldwide in 2027. Availability of one‑tap installs and automatic updates follows each user's home country, and short trips to unsupported countries do not turn those features off.
What this means for end users, third‑party stores, and IT administrators
- End users: on supported devices running Android 17 QPR2 or later, approved stores will offer fewer friction points for installs and background updates — but users still keep explicit consent controls, and the program requires that stores "must not install apps silently without user consent."
- Third‑party stores: joining the Registered App Stores program is optional; stores that opt in must submit comprehensive catalogs, accept ongoing malware screening, pay the entry fee, and remain liable for catalog content. Stores that stay out will continue to operate under the existing per‑install confirmations.
- IT administrators: administrators can block registered stores from being installed on managed devices, though Google's program pages do not say whether that block applies to a store that is already installed.
Google announced the Registered App Stores program in March alongside changes it said resolved its disputes with Epic Games. The schedule now puts a practical deadline on stores that want the streamlined user experience: they must be approved before December 1 and able to serve users running Android 17 QPR2 or later — a platform update whose latest version, released October 16, is still a beta with no final release date provided in Google's notes. The policy creates a concrete but conditional pathway for third‑party stores to reduce install friction while keeping responsibility, liability, and ongoing malware screening squarely with the stores themselves.




