Android developer verification is a Google program that asks people who distribute apps to verify their identity. Protections start in four countries on 30 September 2026 and expand worldwide in 2027 and later. Google's page mentions an advanced flow for power users to install unverified apps, but we could not confirm details.
What the program is
Google describes developer verification as an extra security layer meant to deter bad actors. Developers verify through the Android Developer Console if they distribute only outside Google Play, or through Play Console if they distribute on and outside Play. The page says Play automatically registers 99 percent of apps.
There are limited distribution accounts for students, teachers and hobbyists. Per the page, they let you share apps with up to 20 devices without a government issued ID or registration fee. Fees may apply to other account types, and the page does not state amounts.
The published timeline
- August 2026: developer APIs, limited distribution accounts and the power user advanced flow launch.
- 30 September 2026: protections begin for installs from participating stores in Brazil, Indonesia, Singapore and Thailand, on certified devices running Android 7 or later.
- 2027 and beyond: verification expands globally to all apps on certified Android devices.
What we could not confirm
The page does not say whether sideloading or ADB installs stay possible. It refers to an advanced flow for people who want to download unverified apps and points to a separate Google post for details. Read that post before advising anyone. Also check whether your device is certified, since the protections apply to certified devices.
What to do if you ship APKs outside Play
- Check which path applies to you, Android Developer Console or Play Console.
- Register your package names and signing keys as the process requires.
- Update your download page so users know what to expect on install.
- Keep publishing your signing certificate fingerprint and a hash, so users can still verify the APK with apksigner.
What to do if you install APKs
Expect the install flow to change over time, and expect more prompts. Read each one. Prefer the store route when the app is available there, and use the checks in Google Play or APK, which to choose when it is not.
How to stay current
This program is new and still rolling out, so details will change. Bookmark Google's page, note the dates above, and re-check before each release cycle. If you advise customers or colleagues on installing apps from outside a store, put a review date on that advice, and avoid promising that a particular install route will still work later. State what you know today and what you have not confirmed.
Quick check
Does verification mean Google reviews my app's code?
The page describes identity verification of developers. It does not describe code review.
Is sideloading going away?
We could not confirm that from the page we read. It mentions an advanced flow for unverified apps. Check Google's current guidance.
Sources
Last reviewed: 19 October 2026.
