Android Registered App Stores: What Changes for Sideloading

On this page

Google has opened enrollment for Registered App Stores, the Android program that gives third-party app stores a more streamlined way to reach users. The practical point is narrow. Stores that enroll get a new install flow, while stores that stay out keep the sideloading experience Android has today. The new flow goes live on December 1, 2026, but only on Android 17 QPR2 and later, and only in supported regions outside the United States.

What actually changes

For an enrolled store, the change is friction. Android Authority reports that enrolled stores can offer one-tap installs with no secondary system confirmation screen, plus automatic background updates and download progress indicators. Google’s FAQ adds a detail that matters on real phones: large downloads and background installations must run as foreground services with a visible notification, so the system cannot quietly kill them.

The real trade-off is the vetting, not the install button. To enroll, a store has to document its policies on intellectual property, illegal content and privacy, publish a privacy policy for users and developers, and keep ongoing malware controls in place. Ars Technica and Android Authority both report an annual fee of $10,000, payable before Google reviews the application. The requirements page also sets an App Defense Alliance certification requirement that takes effect on June 1, 2027.

Our reading, which is an editorial judgment and not a Google claim: the fee and the certification will filter out small hobbyist catalogs, but they do not prove that every app in an enrolled catalog is safe. The number to watch is the malware threshold. If more than 1% of install attempts, or 2% of the apps in a catalog, are found to be potentially harmful over a 30-day period, Google assesses variable fees. That metric, not the install animation, is where a store’s security posture will show up.

Check these before you trust a store

  • Your Android version. Support starts with Android 17 QPR2. Ars Technica reports that Google expects that release on Pixel phones in the coming weeks.
  • Your country. The FAQ lists the supported regions starting December 1, 2026. It does not name the United States, Italy, Germany, France or Spain, although it includes a “Rest of the World” entry, so check the list instead of guessing.
  • The store itself. Enrollment is optional. A store that has not enrolled keeps today’s install flow, so read the store’s own announcements before assuming the new flow applies to it.
  • Managed devices. IT administrators can block Registered App Stores on managed devices.
  • Updates after a reinstall. If an enrolled store is uninstalled, the apps it installed stop receiving automatic updates. Reinstalling the same store restores update ownership without new prompts, as long as no other store has updated those apps in the meantime.

Sideloading is not going away

Registered App Stores is a separate track from developer verification, so do not read one as the other. Google’s developer verification page says protections for users installing apps from participating stores began on September 30, 2026, in select regions on certified Android devices, and that user protections will roll out globally in 2027. Google has also previewed an advanced flow for power users who want to download unverified apps. Enrolling a store changes how that store’s own installs work, and nothing else.

For a related Italian read on the Android side of third-party stores, see our F-Droid 2.0 coverage.

In short

  • Enrollment for Registered App Stores opened on October 27, 2026. It is optional.
  • From December 1, 2026, enrolled stores get one-tap installs and automatic background updates on Android 17 QPR2 and later.
  • The United States is not on the FAQ region list. Check the list for your own country.
  • Enrollment requires documented policies, ongoing malware controls and a reported $10,000 annual fee.
  • Stores that do not enroll keep today’s sideloading flow.

Sources

AUTHOR

IT specialist, developer and systems engineer with a long history across code, Linux servers, retrocomputers and e-learning platforms. On AndroidLab he brings a technical, pragmatic eye: less brochure smoke, more attention to infrastructure, usability, privacy, updates and the real consequences of manufacturers' choices.

Leave a Comment