Google will start global Android developer verification in January 2027, with Xiaomi, OPPO, vivo and other stores

Text
iHOLYSHITVISUAL / TECHIndustry changesiHOLYSHIT / ILLUSTRATION
iHolyShit illustration

In a Nov. 19, 2026 Android Developers Blog post, Matthew Forsythe, Google’s director of product management for Android app safety, said Android developer verification will begin a global rollout in January 2027 with seven app distributors: Google Play, Galaxy Store, Honor, OPPO, Xiaomi, Transsion, and vivo. Protections will then expand over several months to all countries and all installation sources on certified Android devices. Google itself reports that apps registered since verification opened to everyone in March already represent more than 99% of global Android app installs; that is a company figure, not an independent audit. Full distribution requires a one-time $25 registration fee; limited distribution is free, and the official blog says the authorized-device cap has been raised from 20 to 50.

In January 2027, apps from developers who have not completed identity verification and app registration will start to lose the normal installation path on certified Android devices worldwide. In a Nov. 19, 2026 post on the Android Developers Blog, Matthew Forsythe, Google’s director of product management for Android app safety, wrote that the global rollout will begin in January 2027 with seven app distributors: Google Play, Galaxy Store, Honor, OPPO, Xiaomi, Transsion, and vivo. Over the following months, the company said, user protections will “gradually expand to all countries” to cover “all installation sources on certified Android devices.”

In the same post, Google offered its own progress figures: since verification opened to everyone in March 2026, “millions of apps have been registered globally,” and those apps “represent over 99% of all Android app installs globally.” That is a company-reported statistic, not an independent audit, and the post does not give an exact registration count or a detailed methodology. Google also wrote that registering an app “takes less than ten minutes,” which is likewise the company’s own claim. The official Chinese post is the same announcement.

Google announced Android developer verification in 2025 as an extra security layer meant to make it harder for bad actors to spread harm repeatedly. After more than a year of work with industry partners, the protections went live on Sept. 30, 2026, in participating stores in Brazil, Indonesia, Singapore, and Thailand. Google’s developer-verification documentation says that first phase covered those four countries, participating stores, and certified devices running Android 8 (API level 26) or higher. What is new in the Nov. 19 post is that a previously open-ended “2027 and beyond” global expansion has been narrowed to a January 2027 start, with the same seven distributors named again. Ars Technica, writing the same day, said Google is moving ahead despite numerous objections from developers and users.

The mechanism breaks into three ledgers. The first is identity and registration. Google’s official help page says full distribution requires a one-time $25 USD registration fee and has no cap on installs; limited distribution has no registration fee. The Nov. 19 official blog adds that limited-distribution accounts for students and hobbyists launched in August, require neither a registration fee nor a government-issued ID, and that the sharing limit has been raised from 20 authorized devices to 50. The help page still mentions a 20-device cap; the updated figure in the same-day official blog is the one used here. Individuals seeking full distribution must also submit a government-issued photo ID and proof of address, and verify an email address and phone number with a one-time password. Organizations must provide a Dun & Bradstreet D-U-N-S number, a website verified in Google Search Console, and official organization documents. The document examples on the help page are for applicants in the United States; requirements elsewhere may differ.

The second ledger is enforcement on the device

The second ledger is enforcement on the device. The Nov. 19 official blog refers to “certified Android devices” and “all countries,” and does not, in that post, name any country as excluded. Ars Technica added that the verifier system service has already been rolled out to Google-certified devices running Android 8 or higher, which, in that publication’s words, accounts for just about every Android device outside China and Russia. The third ledger is the exception path: Google says it built an “advanced flow” that lets experienced users install unregistered apps if they accept the risk, while keeping guardrails against social-engineering scams. Both Ars Technica and Android Authority describe that bypass as more than a simple toggle, with a 24-hour wait; the Nov. 19 official blog does not state that interval, so the waiting time is attributed to those two outlets. Ars also wrote that only popular app IDs will be cached on devices, and that other installs may require a connection to Google’s servers — that is the publication’s account, not a sentence from the official blog that day.

If the official timetable holds, the first change in early 2027 will be listing and installation in the seven partner stores, with other installation sources on certified devices following later. Google has placed itself on the security side of the ledger: if registered apps truly already account for more than 99% of global installs, the global rollout will look, for most users, like turning completed registrations into a mandatory gate. The people who get stuck are the remaining long tail — unregistered independent developers, apps on open-source registries, and anyone who still wants to install packages outside the stores. Google has already published guides for open-source registries and app distributors, which amounts to saying that path still runs through registration, not anonymous distribution.

Layer by layer, the immediate pressure falls on developers who must produce a government ID or corporate documents to keep distributing widely, and on students and hobbyists confined to 50 authorized devices. Ars Technica also judged that developers in sanctioned nations may be unable to verify their identities and thus locked out of distribution; that is the publication’s inference, and the official blog that day did not develop the point. On the other side, Google Play and the app stores of Honor, OPPO, Xiaomi, Transsion, vivo, and Samsung are scheduled to be the first enforcers. The naming of those Chinese companies refers to their role as app distributors on certified devices; it is not evidence that Android phones in the mainland China market have already been brought into the same Google-certified system. For ordinary users, the near-term change is more likely to be a longer path for unregistered apps, not a sudden failure to install the apps they already use. The announcement itself is not a claim that the rule will be in force in every country on January 1, 2027. Google wrote that the rollout will “begin” and then “gradually expand” over the following months.

iHolyshit review

What I care about is not how tidy the self-reported 99% figure looks, but whether the remaining install path is actually shut in 2027. Over the next 6 to 12 months, three things can be checked: by June 2027, whether the seven partner stores list only verified apps; by the second half of 2027, whether unregistered apps still have a normal install path on certified devices in major markets that does not require a day-long wait; and whether, when Google’s “all countries” language is carried out, markets such as mainland China that do not primarily run on Google’s certified stack are carved out. If the first two items follow the official route, this announcement will have turned sideloading from a default capability into a reserved exception. If January is only announced, and enforcement is still “gradually expanding” at year’s end, today’s global timetable will have been a communications calendar.

Share this article

What do you think of this story?

Anonymous feedback, up to 5 reactions per article.

Reader comments

Comment without signing in, or sign in to display your member name.

Discuss the technology and the story. Hate, politics and war, threats, abuse, personal accusations, sexual content, ads, links and personal information are not allowed.

0/500

No comments yet. Be the first to share.

Sources