PeerPlay
If you only publish on Google Play, Android developer verification asks little of you: once you've completed Play Console's own verification, Google says it registers your eligible Play apps for you. The new work is for apps you distribute outside Google Play, which must be registered by a verified developer before they install on certified Android devices in the regions where the rules are live.
Those rules started on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, and Google says it will expand them globally in 2027. Sideloading isn't banned. Users can still install unregistered apps with ADB or a new advanced flow. Here's what it means for indie developers, testers and hobbyists.
What Android developer verification is
Google's goal is to tie every app installed on a certified Android device to a real, verified developer. In its March 2026 announcement, Google said its analysis found over 90 times more malware from sideloaded sources than on Google Play, and verification is its answer to that.
In practice it has two parts. The developer verifies their identity, and then registers the package names of their apps, proving they own each one by providing an APK signed with their private key. Devices then check whether an app comes from a registered developer before installing it.
For most users nothing changes. Google says it's only when someone tries to install an unregistered app that they need ADB or the advanced flow.
Do Google Play developers need to do anything?
Mostly no. Google's guide says developers who distribute through Google Play are registered automatically and should use their existing Play Console account to meet the requirements. If you've already completed Play Console's developer verification, your identity counts as verified.
Google also says that in rare cases it can't register an app automatically, and then you need to follow a manual app claim process. So it's worth a quick check. Google said Android Studio would show an app's registration status when you generate a signed App Bundle or APK.
If your Play Console account isn't verified yet, finish that first. It's required for publishing on Play anyway, and it now covers this too.
Apps outside Google Play: the Android Developer Console
If you distribute APKs yourself, through your website, another store or direct downloads, you sign up for an Android Developer Console account. Google's guide lists three steps: create the account, verify your identity, and register your package names.
Google offers two account types. Full distribution is for organizations and professional developers who share apps widely, and it requires identity verification. Organizations also need to verify their website with Google Search Console. Limited distribution is for students, hobbyists and personal use: no identity verification, an email account is enough, and the app can be shared with up to 20 devices whose owners accept an invitation from you.
Some third-party sites quote a registration fee for full accounts. We couldn't find the amount on Google's own pages, so check the sign-up screen before you count on a number. Google describes the limited distribution account as free.
Does this affect closed testing on Google Play?
Not directly. In a Google Play closed test, testers opt in and install your app from the Play Store, so it isn't a sideload. The app comes from your Play developer account, which Google registers for you once you're verified.
Where it can matter is if you send test builds to people outside Play, for example an APK in a chat message or a download link. In regions where the rules are live, those installs need a registered app, the limited distribution invitation, or the user going through ADB or the advanced flow. For the 12-tester, 14-day requirement, only testers on your Play closed test track count anyway, so keep testers on Play.
Sideloading for users: ADB and the advanced flow
Google says ADB installs work the same as before, which is good news for developers testing on their own devices.
For people who want to install unregistered apps without a computer, Google added an advanced flow with extra safeguards. According to reports from 9to5Google and Android Authority, it lives in Developer options under a setting to allow apps from unverified developers, includes warnings and a one-time 24-hour waiting period, and can then stay on for seven days or indefinitely. Those details come from news reports rather than Google's guide, so they may change.
What to do now
Play-only developer: make sure your Play Console account is verified and check that your apps show as registered. APK outside Play: create an Android Developer Console account and register your package names before 2027 brings the rules to every region. Student or hobbyist: the limited distribution account covers up to 20 devices for free.
And if you're still stuck before production at the closed testing step, PeerPlay is a free way to find testers who install from Google Play and open your app every day for 14 days.
FAQ
Is Google banning sideloading on Android?
No. Google says users can still install apps from any source using ADB or the new advanced flow. Unregistered apps just need one of those routes in regions where the rules are live.
When does Android developer verification apply?
Google started it on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand on certified Android devices, and plans to expand it globally in 2027.
Do I need a government ID?
For a full distribution account, yes, identity verification is required. Google's limited distribution account for students and hobbyists needs no government ID and allows sharing with up to 20 devices.
I only publish on Google Play. Do I need an Android Developer Console account?
Google says no. Use your existing Play Console account. Verified Play developers have eligible apps registered automatically, with a manual claim process in rare cases.