Android developer verification expands globally in January 2027
Google plans to extend Android developer verification to every country starting in January 2027, bringing apps distributed beyond participating app stores into the scope of the program. Developers who have not verified their identity with Google and registered their apps will no longer receive the normal installation experience on certified Android devices.
The rollout begins with seven distributors: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo. Google says the requirements will spread over several months to every installation source, including sideloaded apps and open-source registries. That makes the change relevant not only to app publishers using major stores, but also to developers distributing their own software and users who install it from elsewhere.
From four markets to a global rollout
The protections first went live on September 30 for participating stores in Brazil, Indonesia, Singapore and Thailand. Google said it had spent more than a year preparing with distributors and Android communities. Matthew Forsythe, Google’s director of product management for Android app safety, described the coordination as part of that preparation.
Verification became available to all developers in March. Google says millions of apps have been registered since then, representing more than 99% of Android installs worldwide. The remaining unregistered apps account for less than 1% of installs, according to the company. Although that share is small in aggregate, individual developers whose apps are in that group will need to assess how the change affects distribution.
The policy connects app distribution to verified developer identity: developers must establish their identity with Google and register the apps they distribute. The stated consequence for unregistered apps is a change to the normal installation experience on certified devices. Google has not described that in the supplied rollout details as removal of the apps from all devices or as a ban on their existence, so organizations should distinguish the installation change from broader claims about app availability.
What developers need to review
Google says app registration takes less than ten minutes. It has also introduced limited distribution accounts for students and hobbyists. Launched in August, those accounts do not require registration fees or government ID checks. Google increased the number of authorized devices with which such developers can share apps from 20 to 50.
Teams that manage numerous apps can automate registration-related work through continuous integration pipelines, the automated systems used to build and ship software. Google provides two APIs for this purpose: the Android Developer ID Status API and the Android Developer Console API. These options may be especially relevant to organizations that need to track developer status or handle app administration as part of established release processes.
Google Play publishers should also check whether they distribute the same app through other channels. Google says an app distributed outside Play must be registered even if it is already available in the Play store. Developers maintaining software in open-source registries can consult Google’s separate guidance for registering existing and new apps.
For enterprise IT and mobility teams, the expanding scope means app inventories should account for installation sources, not just the organization’s primary app store. Teams can identify internally used or business-critical apps distributed through sideloading or registries, confirm who maintains them, and coordinate with those developers about registration. These are practical review steps based on the rollout’s stated coverage; Google’s announcement does not specify an enterprise exemption.
An advanced installation option
Google says it is also creating an advanced flow through which experienced users can choose to install unregistered apps after accepting the risk. Forsythe said the design is intended to preserve safeguards against social-engineering scams affecting everyday users while allowing a route for users who knowingly want to proceed. The available details do not explain the flow’s exact prompts, eligibility conditions or technical implementation.
The advanced option may matter to people who rely on software outside conventional app stores, but it does not remove the need for developers to understand registration requirements. Organizations should follow Google’s rollout guidance as it expands, check the status of apps they depend on, and prepare developers who distribute Android software through multiple channels for the January 2027 start and subsequent expansion.