Yes, but not everywhere and not all at once. Android developer verification means certified Android phones only install apps through the normal path if a verified developer registered them. Since September 30, 2026 that applies to apps from participating stores in Brazil, Indonesia, Singapore and Thailand, and Google plans to extend it to all apps worldwide in 2027. Power users can still install unregistered apps through an “advanced flow” or ADB.
What Android developer verification is
Developer verification is Google’s rule that apps must be tied to a known developer before a phone installs them. Google’s verification guide applies it to all apps on certified Android devices.
“Certified” matters: the verification FAQ says the rule applies to certified devices running Android 7 or higher.
When Android starts blocking unverified apps
Blocking started on September 30, 2026, in four countries and only for certain stores. The verification landing page lists the timeline:
| Date | What happens |
|---|---|
| August 2026 | Developer APIs, limited distribution accounts and the advanced flow launch |
| September 30, 2026 | Protections begin for users installing apps from participating stores in Brazil, Indonesia, Singapore and Thailand |
| 2027 | Google expands the protections globally for all apps on certified devices |
The participating stores, per the guide, are Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps. So a user in Jakarta who downloads an unregistered app from Galaxy Store hits the new check. A user in Jakarta who downloads your APK from your website does not, yet.
Google hasn’t published a single worldwide enforcement date for 2027. Watch the Android Developers Blog post from June 2026 and the landing page for it.
Is sideloading blocked?
Sideloading is not blocked, but it gets harder for apps from unregistered developers. The FAQ says users can still install them through an advanced flow, a one-time setup for power users:
- Turn on developer mode in system settings.
- Confirm nobody is coaching you through it.
- Restart the phone and sign in again.
- Wait out a one-time, one-day waiting period, then confirm with fingerprint, face or PIN.
- Choose to allow unverified installs for 7 days or indefinitely.
After that, installing an unregistered app shows a warning that it’s from an unverified developer, and the user taps Install Anyway. ADB is untouched: the FAQ says developers can still install apps without verification over ADB.
The catch is updates. The FAQ says unregistered apps can only be installed or updated while the advanced flow is on or through ADB, so if a user turns it off, updates fail. For a small app that people update from your website, that’s the part that will cost you users.
What it means for your app, by channel
How the change affects you depends on where people get your app. For a typical WebView app from a small business or indie developer:
| Where users get the app | Today (November 2026) | After the 2027 global rollout |
|---|---|---|
| Google Play | Play registers almost every app for you | Same |
| Another participating store | Must be registered in the four countries | Must be registered everywhere |
| Your own website as an APK | No new check yet | Unregistered apps need the advanced flow |
| A few test phones | No new check yet | Use limited distribution or ADB |
Google Play is the easy case. The landing page says Play automatically registers 99% of apps. The FAQ adds that apps using Play App Signing are part of that automatic registration. If you’re new to that, Play App Signing explained covers how Google holds your key.
Your own website is where 2027 bites. My take: if you share an APK publicly today, verify now rather than wait. Asking customers to enable developer mode and wait a day kills sales, and the switch lands on a date you don’t control. My older guide on sharing an APK on your website shows the install steps your users see today.
Account types and cost
Developers who distribute only outside Google Play use the new Android Developer Console, while Play developers keep using their existing Play Console, per the guide.
- Full distribution is for organisations and professional developers. It includes identity verification and lets you ship from any store or channel. The FAQ lists a $25 fee for this account in the Developer Console.
- Limited distribution is for students, hobbyists and personal use. The limited distribution page says it’s free and needs no government ID. You still need a Google Account with 2-Step Verification, a Google payments profile and a contact email.
One limitation of the current docs: Google’s own pages disagree on the device cap for limited distribution. The limited distribution page says up to 50 devices, while the guide and the June 2026 blog post say 20. Plan around 20 until the console shows you otherwise.
Play is a different cost line. If you’re weighing it, what it costs to publish on Google Play breaks down the one-time registration.
What to do if you build WebView apps
The safest move is to register the package names you already ship, before 2027 forces the question.
- Keep your package name and signing key stable. You register the apps you ship, and Android won’t update an installed app with one signed by a different key.
- Pick your channel. If you’re heading to Play, the Google Play publishing guide for WebView apps walks through the account, listing and review.
- Tell sideloading users about the advanced flow early, if you stay unregistered. Otherwise they’ll report a failed update as a broken app, much like the errors in APK “App not installed”.
WebToAPK Free builds and signs your APK and AAB in the browser with your own key, and it needs no account. It doesn’t register you with Google, though. A generated AAB isn’t Play approval, and developer verification is a separate step you do in Google’s console.
FAQ
Can I still sideload apps from unverified developers?
Yes. Google’s FAQ says power users can turn on an advanced flow: enable developer mode, restart, wait a one-time 24 hours, then confirm. After that, installs show a warning with an Install Anyway button. ADB installs are unchanged.
Does Android developer verification apply to APKs on my own website?
Not yet. Google’s FAQ says that if users sideload your app directly, the new requirements won’t apply to your app yet. Google plans to expand the protections to all apps on certified devices in 2027.
Which countries are affected first?
Brazil, Indonesia, Singapore and Thailand, from September 30, 2026, for apps installed from participating stores on certified devices running Android 7 or higher.
How much does developer verification cost?
A Full Distribution account in the Android Developer Console has a $25 fee. A Limited Distribution account for students and hobbyists is free and needs no government ID. Play developers use their existing Play Console account.
Will my Google Play app be blocked?
Unlikely. Google says Play automatically registers 99% of apps, and apps that use Play App Signing are part of that automatic registration.