Google now requires a verified developer identity behind every app installed on a certified Android device — including apps that never pass through Google Play. Its developer verification guide states, “Android requires all apps to be registered by verified developers for users to install them on certified Android devices,” and that the requirement applies “regardless of your app’s download source.” Enforcement began on Sept. 30, 2026, for users in Brazil, Indonesia, Singapore and Thailand, and Google says the program expands globally in 2027; no U.S. or European date has been announced, so developers should plan as if it arrives early next year.
Sideloading and which apps are affected
Many business-to-business Android apps that skip Play are caught by the rule: point-of-sale apps loaded during reseller staging and warehouse apps that update by fetching new files both count. Because the requirement follows the device rather than the store, each install depends on the app package name being registered once enforcement reaches a customer’s certified devices. Google’s FAQ warns that unregistered apps “won’t be available for new installation on certified devices” in covered countries.
Google said in a July 15 update to its June announcement that about 99% of Play apps had already been registered automatically, so exposure is greatest for apps distributed outside Play. Device certification matters: the requirement applies to devices built to Google’s compatibility program and covers mobile and tablet form factors starting in September 2026. That means the same app running on consumer tablets or purpose-built terminals may be affected — check which customer devices are certified before assuming an exemption.
White-label builds increase the work: each package name needs its own registration, and registration is tied to the signing key. If a customer-branded build was signed with a key only a former contractor can access, resolving that key ownership is urgent.
What registration requires
The paperwork is modest. Developers who distribute only outside Play open an Android Developer Console account; Play developers work in Play Console. You verify your identity as an individual or an organization, then register each package name by uploading an Android application package (APK) signed with your private key. Organizations must also verify a website through Google Search Console.
Google’s verification FAQ says organizations need a Data Universal Numbering System (D-U-N-S) number. Dun & Bradstreet issues the number free but it can take up to 28 days to deliver. A full distribution account costs $25.
Exemptions, device certification and the developer-mode back door
Some installs are exempt: apps distributed through an organization’s store on managed devices “won’t need to complete the verification requirements,” because the customer’s IT admin has already vetted them. A retailer pushing your app to company-owned scanners via its mobile device management (MDM) platform fits that description; a technician installing the app on a personal phone does not. Google still recommends registering managed apps that might reach unmanaged devices, so most independent software vendors will register them anyway.
Google left a limited back door. Android Debug Bridge (ADB) installs still work, and an advanced flow permits installing apps from unverified developers. That flow requires turning on developer mode, restarting the device, and waiting out a one-time, one-day waiting period. A free limited distribution account covers up to 20 devices without a government-issued ID but is aimed at students, hobbyists and personal use — not merchant deployments. An install guide telling resellers to enable developer mode and wait a day is likely to generate support tickets and security questions from customers’ IT teams.
How to prepare before 2027
Map every route your Android apps take to devices — Play, your website, reseller staging, MDM pushes and any self-updater. Inventory package names and signing keys across every build, including white-label versions, and confirm who controls each key. If your company lacks one, request a D-U-N-S number now, since that step has the longest lead time. Set up an Android Developer Console account or claim your apps in Play Console, then register every package name and test a clean install on a certified device. Once packages are registered, Google says users should see no change.
Register before Google announces U.S. or European dates so resellers staging hundreds of handhelds don’t have to rely on the one-day advanced flow for each device — and so your existing install scripts continue to run as they always have.

