Android developer verification: how to prepare before the September 2026 deadline

Android developer verification is a mandatory identity verification program for Android app developers. Developers who distribute Android apps will need to verify their identity with Google, or their apps may be blocked from installing on supported Android devices as enforcement expands globally.

Why? Google is trying to crack down malware and fraudulent apps distributed through sideloading channels. Rather than banning sideloading, Google requires developers to verify their identity so that users can see who is behind an app before installing it.

Try it for free!

Enter any URL to build an Android app

Registration is already open, the Android Developer Verifier system launched in April 2026, and enforcement begins on September 30, 2026 in Brazil, Indonesia, Singapore, and Thailand.

What does this mean for developers? Developers must complete Android developer verification before enforcement reaches their target markets or risk additional installation restrictions for their apps.

What does this mean for end users? Users may see additional security warnings, more restrictive installation flows, or be unable to install apps from unverified developers on supported Android devices.

Android developer verification timeline: Key dates and deadlines

Google is rolling out Android developer verification in phases to give developers time to register their apps and adapt their distribution workflows:

• October 2025: Early access for developers begins.

• March 2026: Global developer registration opens through Play Console and Android Developer Console.

• April 2026: Android launches the on-device Android Developer Verifier system service.

• June 2026: Early access expands to limited-distribution apps, including student, hobbyist, and independent developer projects.

• August 2026: Limited-distribution accounts and Android's new advanced sideloading flow become available globally.

• September 30, 2026: Enforcement begins in Brazil, Indonesia, Singapore, and Thailand. Apps distributed by unverified developers will no longer install on supported Android devices in these regions.

• 2027 and beyond: Android developer verification expands to additional countries as part of a broader global rollout.

How to complete the Android developer verification process

To complete Android developer verification, developers must register and verify their identity through the Android Developer Console.

For most commercial apps, developers will need a standard Android developer account. The Android developer account fee is a one-time $25 registration charge.

• Individual developers: Complete Android developer account verification using a government-issued photo ID. Google uses this information to confirm the identity of the app publisher.

• Organizations and businesses: Complete a business verification process that includes identity checks, a verified website, and organizational verification requirements such as a D‑U‑N‑S number where applicable.

• Students, teachers, and hobbyists: Apply for the free limited distribution account. This account type allows developers to distribute Android apps to up to 20 explicitly authorized devices without paying the standard Android developer account fee.

• For app teams: Complete Android developer verification before enforcement begins in your target markets. Once enforcement is active, apps from unverified developers may face installation restrictions or additional user-facing security checks on supported Android devices.

Why is Google requiring Android developer verification?

Google is requiring Android developer verification to reduce malware, impersonation scams, and anonymous app distribution, particularly in sideloaded apps.

Android’s flexibility allows users to download and install apps from the Play Store, third-party app stores, or directly from a developer's website or bundle.

Google's own analysis puts a hard number on the problem: there is over 50 times more malware in apps sideloaded from the internet than in apps distributed through Google Play.

Malicious actors hide behind anonymity, impersonate legitimate developers, and ship convincing fake apps that steal data or deploy trojans and spyware.

That's what developer verification is built to stop, alongside existing device-level risks like jailbroken/rooted Android devices.

How does developer verification impact your Android app?

Meeting Google Play Store requirements for Android app development has always included a verified developer account, and this policy extends that accountability to channels outside of Google Play.

If your app lives exclusively on Google Play and your developer account is already in good standing, the practical impact is minimal.

Play Store developers will move through a simplified verification process that builds on existing account infrastructure, similar to Google's recent app testing updates.

The bigger question is for teams who distribute apps outside Google Play, whether that's a website to Android app build shared via MDM, or apps shipped through private distribution channels.

These pipelines will need to account for developer verification before September 2026 if you serve users in the initial enforcement regions.

Managed-device deployments may have specific handling under Android Enterprise, but Google is still finalizing the exact carve-outs. Don't assume your MDM pipeline is automatically covered.

There's also a subtler implication: install friction. Even without a visible "verified" badge, the gap between verified and unverified apps becomes very real at the moment of install.

An unverified app in an enforcement region may not install at all without the user navigating the advanced flow. For any team relying on sideloaded distribution, it’s important to get verified early.

How should Android developers prepare for verification?

If you distribute Android apps in any capacity, here's a practical checklist:

• Pick the right account tier. For most commercial developers, that's the full Android Developer Console account ($25 one-time fee, government ID or D‑U‑N‑S for orgs). For classroom projects, hobby apps, or internal tools sharing with up to 20 devices, the free limited distribution tier is purpose-built for you.

• Register early. Global developer registration opens in March 2026. Don't wait until enforcement starts, early verification gets you ahead of the queue and removes last-minute pressure.

• Audit your distribution channels. If your app reaches users outside the Play Store, map that flow and understand where verification fits in. This matters especially across Android fragmentation.

• Check your enterprise deployments. MDM-managed devices may have specific handling under Android Enterprise, but don't assume your setup is exempt. Validate it against your MDM vendor and Google's guidance before September 2026.

• Communicate with your users. Users in enforcement regions will hit the new advanced flow, including the 24-hour delay, when they install an unverified build. Get ahead of their questions now.

Key takeaway

If you distribute Android apps outside of Google Play, developer verification is quickly becoming a requirement rather than a recommendation.

September 2026 is approaching fast.

Companies that rely on private app distribution, employee apps, customer apps, direct APK downloads, MDM deployments, or alternative app stores should complete verification before enforcement reaches their target markets.

Talk to our team to make sure your distribution workflow is ready.

Frequently asked questions

What is Android developer verification?

Developer verification, announced in August 2025 on the Android Developers Blog, ties every Android app to a registered, identity-verified developer. To install an app on a certified Android device, the developer behind that app must be verified first.

Why is Google starting developer verification with Brazil, Indonesia, Singapore, and Thailand?

According to Google, these markets were selected for the first enforcement phase because they face elevated levels of sideloading-related fraud and malicious app distribution. By launching in regions with higher exposure to app scams, Google can reduce user risk while gathering real-world data before expanding Android developer verification globally.

What are Play Protect Certified devices?

"Play Protect certified" devices are those that ship with Google Mobile Services and meet Google's security and compatibility requirements, this includes nearly all mainstream Android phones and tablets from major brands like Samsung, Google Pixel, Motorola, and Xiaomi. Devices running AOSP-only builds or custom ROMs are not Play Protect certified. The rule applies to app installs from any source: Play Store, third-party stores, or direct downloads.

Is Google banning Android sideloading?

No, Google is not banning sideloading. What changes is that unverified installs move to an "advanced flow" with extra safeguards, including Developer Mode steps and a mandatory 24-hour delay before the first install completes.

What happens if I'm not verified by the September 2026 deadline?

In the initial enforcement regions, Brazil, Indonesia, Singapore, and Thailand, users on certified Android devices will be unable to install your app through the normal flow. They would need to navigate the multi-step "advanced sideloading flow," including a mandatory 24-hour delay, to get it installed. Outside those regions, enforcement follows later in 2027, but waiting is a risk.