Google has set a mandatory enforcement deadline of September 30, 2026 for its Android developer verification program, applying to app installs distributed via seven certified third-party stores in four initial launch markets, per Google’s official June 2026 Android Developers Blog announcement.
The first phase of the mandate covers only certified Android devices in Brazil, Indonesia, Singapore, and Thailand, with Google planning to collect feedback from device partners, end users, and the global developer community before expanding the requirement to all certified Android devices worldwide in 2027.
The rule applies exclusively to apps distributed through the participating partner stores in the four regions for this initial rollout, with no immediate enforcement planned for other markets outside that scope.
The program is designed to close a longstanding security gap that allowed unverified, anonymous developer accounts to publish harmful, deceptive, or malware-laden apps to millions of users without confirming their identity.
As of the June 2026 announcement, more than 99% of apps distributed via Google Play had already completed the required verification registration process, leaving only a small fraction of unregistered apps at risk of default blocking on certified devices in the four launch markets after the deadline passes, per the same official announcement.
Unverified apps will remain installable via Android Debug Bridge (adb) or an optional advanced sideloading flow for users who explicitly opt in, but will be blocked by default when sourced from the seven participating partner stores on certified devices in the covered regions.
Mandate Covers 7 Certified Third-Party App Stores Across Launch Regions
The verification requirement applies to installs from seven certified partner stores: Google Play, Honor’s HONOR App Market, OPPO’s OPlus App Market, Samsung’s Galaxy Store, Transsion’s Palm Store, vivo’s V-Appstore, and Xiaomi’s GetApps, as detailed in Google’s official program documentation. The rule covers all apps distributed through these storefronts to users in the four initial launch markets, regardless of the app’s target audience or category. Google designed the program specifically to prevent bad actors from using anonymous developer accounts to distribute fraudulent or malicious content to end users in the rollout regions.
New July 2026 APIs Streamline Bulk Verification for Non-Google Play Developers
To reduce administrative overhead for developers distributing apps outside Google Play, Google is launching two dedicated APIs in July 2026 ahead of the enforcement deadline. The Android Developer ID Status API lets developers instantly check if a specific app package name has already been registered for verification, eliminating duplicate registration work for teams that manage multiple app titles.
The Android Developer Console API supports bulk package name registration and native integration with continuous integration and deployment (CI/CD) pipelines, and includes OAuth delegation functionality that lets third-party app stores manage verification registrations on behalf of developers without requiring developers to share their private account credentials. These tools are targeted at smaller development teams and third-party store operators that manage large app catalogs and would face significant administrative burden registering apps individually.
Limited Distribution Accounts Lower Barriers for Student and Hobbyist Developers
For students, hobbyists, and non-commercial learners who do not wish to complete full developer verification, Google is introducing limited distribution accounts that allow app sharing to up to 20 devices without requiring a government-issued ID or payment of a registration fee. Early access for these accounts launches in July 2026, ahead of the full public global launch scheduled for August 2026, which will roll out alongside the full public release of the Android Developer Console API.
The feature is explicitly designed to lower barriers for non-commercial developers testing apps on small, personal device pools, rather than distributing to the general public, per the official announcement’s limited distribution account program details.
Advanced Sideloading Flow Preserves Access for Intentional Non-Store Installs
Google will also launch an advanced sideloading flow for unverified developers in August 2026, built to resist coercion scams where users are tricked into installing unvetted apps, while preserving intentional sideloading access for power users who deliberately install apps from outside the seven participating stores.
After the September 30, 2026 enforcement deadline takes effect, unregistered apps will remain installable via Android Debug Bridge (adb) or the optional advanced flow for users who explicitly opt in to maintain sideloading functionality. Default settings on certified Android devices in Brazil, Indonesia, Singapore and Thailand will automatically block unverified app installs sourced from the seven participating stores once the deadline passes, meaning users will have to actively choose to enable the advanced flow to install unregistered apps from those storefronts.
Compliance Steps for Developers Targeting the Initial Four Markets
For developers with apps distributed in the four initial markets, the September 30, 2026 verification deadline is the immediate top compliance priority. Google Play developers can check their app’s current verification status directly on their Play Console home page, and can register any unregistered apps they wish to continue distributing to users in Brazil, Indonesia, Singapore and Thailand after the deadline passes.
Developers who distribute exclusively outside of Google Play can sign up for the Android Developer Console to begin the bulk registration process starting in July 2026 when the new APIs launch. Students and hobbyists can apply for early access to limited distribution accounts via the sign-up link published in the official Android Developers Blog announcement to test the feature before its August 2026 global launch.
