Skip to content
TrustList
News

Android developer verification goes worldwide from January 2027

Editorial

By TrustList Editorial

Google will extend Android developer verification worldwide from January 2027 with seven app distributors, then to every installation source on certified devices over several months; unregistered apps lose the normal install path.

About Android developer verification goes worldwide from January 2027

Android developer verification goes worldwide from January 2027

19 November 2026: Google will take Android developer verification worldwide from January 2027. In a post on the Android Developers blog, Matthew Forsythe, director of product management for Android app safety, said the global rollout will begin with seven app distributors: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo. Protections will then expand gradually to all countries and to all installation sources on certified Android devices over several months.

Not yet independently verified. This rests on Google's own Android Developers blog post of 19 November 2026, read on 20 November. Google gives January 2027 as the start but no exact day, and does not give the order in which countries follow; the registration figures are Google's own. We will update this when it can be confirmed, and remove this note.

What has already happened

Google announced developer verification in 2025 as a way to make it harder for bad actors to keep spreading harmful apps under new names. Verification opened to every developer in March 2026, and user protections went live on 30 September for participating stores in Brazil, Indonesia, Singapore and Thailand. Google says millions of apps have been registered since March, and that they account for over 99% of all Android app installs worldwide.

What developers have to do

Developers who have not verified their identity and registered their apps can do so now; Google says registering an app takes less than ten minutes. Once protections reach a market and an installation source, apps that are not registered lose the normal install experience on certified devices. This matters most for companies that distribute Android apps outside Google Play, such as through their own website, an enterprise download page, a partner store or an open-source registry: those apps must be registered too.

Google lists several tools added this year:

  • Limited distribution accounts for students and hobbyists, with no registration fee and no government ID, and a sharing limit raised from 20 to 50 authorised devices.
  • Android Developer ID Status API and Android Developer Console API, so teams with many apps can register them from their continuous integration pipelines.
  • An advanced flow that lets experienced users install unregistered apps if they accept the risk, while keeping guardrails against social engineering scams for everyday users.
  • New guides for open-source registries and for app distributors.

What to do before January

Businesses that ship Android apps to staff, customers or field devices outside Google Play should check now that the developer account behind each app is verified and that every package name is registered. Build pipelines that sign and publish APKs can use the new APIs to check registration status automatically. Teams that rely on unregistered internal tools should plan either to register them or to brief users on the advanced flow, keeping in mind that Google has not said exactly when each country and installation source will be covered.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in