Android will block unverified apps starting in March 2027

Android will block unverified apps starting in March 2027

Starting in March 2027, Android will fully enforce its block on apps from developers who have not verified their identity and registered their apps with Google. The global rollout will begin in January and affect installation sources on certified devices running Android 8 or later, although an advanced option for installing unverified apps will remain available.

The measure changes the process for distributing apps outside Google Play: it will also cover APKs and third-party stores. Google presents verification as a layer of protection against malware and scams, but the change adds steps for both app publishers and people installing them.

From four countries to all installation sources

The global rollout will begin in January 2027 and expand over the following months. Android Central reports that full enforcement is scheduled for March 1, 2027; Google's help documentation says verification will expand globally to all apps on certified Android devices during 2027.

The first phase began on September 30, 2026, in Brazil, Indonesia, Singapore, and Thailand. There, the requirement initially applied in participating stores. Xataka Móvil reported that when this phase began, the requirement covered certain partner stores, but not browser downloads; the planned expansion will extend checks to all installation sources.

Google Play and six third-party distributors are participating: Galaxy Store, Honor, Oppo, Xiaomi, Transsion, and Vivo. The stores involved include HONOR App Market, OPPO App Market, Palm Store, V-Appstore, and GetApps. Verification will also cover apps distributed directly and open-source app registrations, according to Help Net Security.

The requirement applies to certified devices running Android 8 or later. Google excludes AOSP devices and those that are not certified; regions where Google Mobile Services is unavailable and territories subject to applicable trade sanctions are also exempt.

Android developer verification walkthrough — Android Developers

Verified identity and registration for every app

To distribute an app under the new system, developers must verify their identity and register their apps. Xataka Móvil specifies that registration requires submitting an identity document and paying a $25 fee. Google says millions of apps have already been registered, accounting for more than 99% of Android installations worldwide.

Matthew Forsythe, Google's director of product management for Android App Safety, also cited this percentage, according to Europa Press. Help Net Security estimates that apps not yet registered account for less than 1% of installations. For the creators of those apps, however, the global proportion does not change the impact: on devices covered by the rule, an unregistered app will no longer have the normal installation experience.

Google maintains limited distribution accounts for students and hobbyists. These let them share apps without paying the fee or submitting an official document. The free limit has increased: Xataka Móvil and Android Central say apps can be shared with up to 50 authorized devices, compared with the previous limit of 25 mentioned by Xataka Móvil; Help Net Security, meanwhile, cites an increase from 20.

For teams that manage many apps, Google offers automation tools. Help Net Security identifies two interfaces: Android Developer ID Status API and Android Developer Console API, designed to be integrated into continuous integration processes. Google has also published a specific guide for registering new or existing apps distributed through open-source repositories.

Manual installation will involve a 24-hour wait

If an app comes from an unverified developer, the system will warn the user and block its normal installation. On certified devices, Android Developer Verifier, a Google service installed on the phone, will check whether the app is associated with a verified developer.

The alternative is the so-called advanced flow, intended for experienced users who accept the risk. It is not an instant permission: users must enable developer settings, go through warning screens, confirm that no one is coercing them, restart the phone, and wait 24 hours before authorizing the installation, according to Xataka Móvil and Android Central.

Google describes the wait as a safeguard against coercion-based scams. Forsythe summed up the goal in Help Net Security:

“We built an advanced flow that allows experienced users to install unregistered apps when they choose to accept the risk, while keeping critical guardrails in place against social engineering scams for everyday users,”

— Matthew Forsythe, Google's director of product management for Android App Safety

Xataka Móvil says ADB, Android's debugging mode, will be the only immediate shortcut for installing unverified APKs. Google's documentation confirms that the advanced flow can be started from the phone's settings and includes security checks and a waiting period.

Partner stores and the scope of the change

Google has also coordinated with the manufacturers' stores participating in the rollout. Xataka Móvil says the stores will be able to display verified apps when the corresponding toggle is enabled. The expansion, however, is not limited to those platforms: the goal is for checks to cover all installation sources, including external downloads.

The policy was announced in 2025, according to Android Central, and verification opened to developers in March, according to Help Net Security. Google argues that requiring a real identity makes it harder for malicious operators to distribute malware anonymously and republish harmful apps. The company says the requirement had already been in place on Google Play for years before being extended to third-party stores.

The initial expansion does not mean a simultaneous change worldwide: the rollout will take several months. Android Central gives March 1, 2027, as the planned date for full enforcement; Google places the global expansion in 2027 and describes a gradual rollout following the phase in the initial four countries.

Questions for developers who cannot verify their identity

It remains unclear how the system will affect people who cannot validate their identity, including developers in countries under sanctions, an issue Xataka Móvil raises as unresolved. Google's help documentation specifies that the requirement does not apply in territories subject to applicable trade sanctions or where Google Mobile Services is unavailable.

There is also a technical dependency for installing apps from small creators: the phone needs an internet connection to query Google's servers and check registration, according to Xataka Móvil. The company has not yet clarified in that article how all cases involving developers who cannot complete verification will be handled.

For users, the immediate timeline is January 2027, when the global expansion will begin. For those who want to install an unregistered app on an affected device, the documented alternative will remain the advanced flow, with its checks and a one-day wait.

Sources: Xataka Móvil, europapress.es, Help Net Security, Android Central, Android Help (Google)