
For Android users in selected markets outside the United States, the process of using third-party app stores may become less fragmented. Google has created a voluntary registration track for those stores, and approved participants would no longer face every routine installation confirmation. The goal is a smoother sideloading experience while keeping scanning, policy disclosure, and user-support obligations attached to store operators.
Only stores operating in specified regions outside the United States can apply. An applicant cannot use a personal Android developer account; it must hold an Android developer enterprise account. The program also requires a $10,000 annual fee and compliance with Google's security and operation requirements.
Application path can be summarized as:
Before the program, a user normally had to enable installation from the third-party store in system settings and then confirm additional system dialogs for each app install. Once a store is registered and verified, the system would grant the relevant install permission automatically, so the extra confirmation screens could disappear when installing from that store. Registered stores could also trigger background automatic updates according to user settings and display download progress or status notifications.
The same registration can simplify installing the store itself. If a store has completed Google registration, sideloading its client should present a less cumbersome installation flow, rather than requiring users to navigate extra steps before they can install third-party apps.
The new install experience takes effect on December 1, 2026 on devices running Android 17 QPR2 or later.
Google requires every registered store to submit its full app catalog and subsequent updates for malware scanning. Any application that fails scanning may not be distributed or updated through a registered third-party app store.
Operators must publish a privacy policy, developer agreement, and security rules. They also need channels for intellectual-property handling, illegal-content reporting, and user support. In addition, they must maintain their own content-review mechanism and remain responsible for the entire app library.