← Blog

Android Developer Verification for Indie Developers: 2026 Guide

Android now requires verified developers for installs in 4 countries and globally from 2027, here is what indie devs in India and elsewhere must do

GAROONO · BLOGAndroid DeveloperVerification for IndieDevelopers: 2026 Guidegaroono.in

From today, some Android phones will refuse to install apps from developers Google has not verified
Next year that goes global, India included
If you only publish on Google Play, you are probably fine, but "probably" is not a plan

Here is what changed, what you actually need to do, and the one mistake that can lock you out of your own app

What changed on September 30, 2026

Google now requires apps to be registered by verified developers before they can be installed or updated on certified Android devices in Brazil, Indonesia, Singapore and Thailand (Android Developers Blog)
Google says it will roll the requirement out globally from 2027 (Android Developers Blog)

For now it covers installs from the participating stores, Google Play among them
Apps sideloaded directly or shipped through other stores are not affected yet, but Google recommends verifying before the global rollout (Android developer verification FAQ)

30 Sept 2026 Brazil, Indonesia, Singapore, Thailand 2027 onwards Global rollout, India included
Source: Android Developers Blog, March 2026

Do you need to do anything?

If you publish only on Google Play

Google says that if you have completed Play Console's developer verification, your identity is already verified and eligible Play apps are registered for you automatically (Android Developers Blog)
Open Play Console, confirm your account verification is complete, and check that each app shows as registered
That is a two minute job, do it today

If you use Play App Signing

Good news, Google says apps using Play App Signing are part of the automatic registration (Android developer verification FAQ)

If you share APKs outside Play

This is where indie devs get caught
Direct APK downloads from your website, betas shared on Telegram, or builds on other stores all need a verified developer once the global rollout reaches your users

The mistake that locks you out: Google says if you lose your signing key, you won't be able to register your packages (Android developer verification FAQ)

Back up your signing and upload keys somewhere safe tonight
If an old app was never enrolled in Play App Signing, check where its key lives before 2027

Which account type do you need?

Your situation What to use Cost
Apps only on Google Play Your existing Play Console account Nothing new
APKs on your site or other stores Full distribution Android Developer Console account $25 fee
Apps for family, friends or a small group Limited distribution account, up to 20 devices, no government ID Free
Publishing as a company Organisation account with a D-U-N-S number Takes up to 28 days

Sources for the table: the $25 fee, the 20 device limit and the D-U-N-S timing all come from Google's help centre (Android Developer Console Help)
If you plan to register as a company, start the D-U-N-S request now, not in December 2026

What developers in India should do now

India is not in the first four countries, so nothing changes for your users this year
It is part of the 2027 global rollout, so use the quiet months to get ready

For individual developers in India, Google Play accepts an Indian passport, driving licence, voter ID or PAN card as photo ID (Google Play Help)
Your proof of address has to show your name and address exactly as they appear on your developer profile (Google Play Help)
A mismatch between the name on your PAN and your profile name is an easy way to get stuck, so fix that first

Can I still test and sideload?

Yes, for development
Google says developers are free to install apps without verification using ADB (Android developer verification FAQ)
For a handful of real testers outside Play, the free limited distribution account covers up to 20 devices (Android Developer Console Help)

Why so many developers are angry

Google frames this as anti malware, citing an analysis of apps from internet sideloaded sources
F-Droid says it has not seen that analysis and calls developer verification an existential threat to free software distribution platforms like F-Droid and to emerging Play Store competitors (F-Droid)

My take as someone shipping on Play: for Play only indies this is mostly paperwork
The real cost lands on people who distribute outside Play, and on anyone who lost a signing key years ago

Your checklist before 2027

  • Confirm Play Console developer verification is complete
  • Check every app shows as registered
  • Back up signing and upload keys in two places
  • Enroll old apps in Play App Signing where possible
  • Match your profile name and address to your ID and address proof
  • Decide your account type if you ship APKs outside Play
  • Start a D-U-N-S request early if you publish as a company

Ship without surprises

Verification is one more box between you and a live app
I keep a full launch guide with the store rules that trip up solo developers most in the docs

Related doc · freeDon't Get Rejected: App Store Launch GuideThe 5 reasons new apps get rejected, and the step-by-step way to ship yours.