Every app installed on a certified Android phone will soon need a name behind it. Google says its Android developer verification scheme, which went live in Brazil, Indonesia, Singapore and Thailand on September 30, 2026, will expand to all apps on certified Android devices worldwide in 2027.
The four-country launch was the test run. Under it, installs from seven app stores are checked: Google Play, Honor’s HONOR App Market, the OPPO App Market, Samsung’s Galaxy Store, Transsion’s Palm Store, vivo’s V-Appstore and Xiaomi’s GetApps. Google’s Android developer verification guide says the checking will “soon be expanded to all third-party Android app stores” before the global step.
What developers have to do
The requirement has three parts. Developers who only publish outside Google Play sign up for a new Android Developer Console; Play developers are registered automatically through the Play Console. Everyone then proves who they are with official documents, and registers each package name by supplying an APK signed with their private key, which ties the app to the account.
Organisations need a D-U-N-S number and a website verified through Google Search Console. A full distribution account in the Android Developer Console costs $25, the same as Play’s registration fee, according to Google’s developer verification FAQ.
Three routes, compared
Google offers three ways to ship an app once the rules apply. The differences matter most to hobbyists and small open-source projects:
- Full distribution: identity check required; the app can go out through any store or a company website, and users notice nothing new.
- Limited distribution: no ID needed and no fee; the app can reach up to 20 devices, aimed at students and personal projects. Users accept an invitation from a developer they know.
- Unregistered apps: still installable, but only after the user turns on a new “advanced flow” on their phone.
How the advanced flow works
Sideloading, the practice of installing an APK from outside an official store described in Wikipedia’s entry on sideloading, does not disappear. It gets slower on purpose. The FAQ lays out the steps: switch on developer mode, answer a check that nobody is coaching you, restart the phone and log back in, then wait a one-time 24 hours before confirming with a fingerprint, face recognition or PIN.
Google’s stated reason is scams. Its FAQ says fraudsters “often pressure victims into making immediate security changes while on a live call,” and that the 24-hour pause “breaks that sense of urgency.” After setup, users can allow installs from unverified developers for seven days or indefinitely, tapping “Install Anyway” past a warning each time.
Two exceptions stay in place. Installs through the Android Debug Bridge (ADB) need no registration and skip the waiting period, and apps pushed to managed company devices through an organisation’s own store are exempt.
Which phones are covered
The rules apply to certified Android devices running Android 8, API level 26, or newer, and arrive through Google Play services rather than a full system update, the FAQ says, in an entry updated on November 10, 2026. The checks do not run on devices physically located in comprehensively sanctioned countries, where Google cannot verify local developers.
Developers testing Android builds on other hardware may also want our look at how Meta got Google’s Cuttlefish virtual device running on Apple silicon Macs, and owners of older Pixels can check when the Pixel 6 reached the end of its update promise.
Google has not given a single global start date on its developer pages; its rollout timeline lists the worldwide phase simply as “2027 and beyond.”
Sources
- Android developer verification, Google, Android Developers, 2026
- Frequently asked questions: Android developer verification, Google, Android Developers, 2026
- Sideloading, Wikipedia, 2026
Image: Océanos y dados, CC0 via Wikimedia Commons
This article was produced with AI assistance and reviewed by our Editorial Desk. How we work.


