Sideloading your Android app? Register it before 2027.


Featured image courtesy of Flickr, Rob Bulmahn

Google now wants a verified name behind every app installed on a certified Android device, including apps that never pass through Google Play. Its developer verification guide says “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.”

Plenty of business software reaches devices without Play. A point of sale (POS) app gets loaded during a reseller’s staging process, and a warehouse app updates itself by fetching a new file. Both count. Enforcement began Sept. 30, 2026, for users in Brazil, Indonesia, Singapore, and Thailand, and Google’s developer verification page says the program expands globally in 2027. No date has been named for the U.S. or Europe, so plan as if it lands early next year.

What registration takes, and which apps it catches

The paperwork is modest. Developers who distribute only outside Play open an Android Developer Console account, and 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 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, which Dun & Bradstreet issues free but can take up to 28 days to deliver. A full distribution account costs $25.

Software developers who sell only through Play can mostly relax. Google said in a July 15 update to its June announcement that about 99% of Play apps had already been registered automatically.

The exposure sits with apps that skip Play, and plenty of business-to-business (B2B) software developers ship Android apps that way, especially for mobile POS, a market we covered in why merchants are going all in on mobile POS (mPOS). A field service app downloaded from a vendor portal is in the same position. Because the rule follows the device rather than the store, each of those installs depends on your package names being registered once enforcement reaches your customers. If they aren’t, Google’s FAQ says the app won’t be available for new installation on certified devices in those countries. Put registration on the same list as the mobile app security myths to forget in 2026 we covered in March.

Device certification matters here. The requirement applies to devices built to Google’s compatibility program, and the FAQ says it covers mobile and tablet form factors starting in September 2026. Customers often run the same app on consumer tablets and on purpose-built terminals, so find out which of their devices are certified before you decide you’re covered or exempt.

White-label builds add work. Each package name needs its own registration, and registration ties to your signing key. If a customer-branded build was signed with a key that only a former contractor can reach, that’s a problem to solve this quarter.

Some installs will be exempt. Google’s FAQ says 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 vetted them. A retailer pushing your app to company-owned scanners through its mobile device management (MDM) platform fits that description. A technician installing it on a personal phone doesn’t. Google still recommends registering managed apps that might reach unmanaged devices, and for most independent software vendors (ISVs) that means registering them anyway. For more on planning enterprise deployments, see our list of factors to consider when building a mobile app for enterprise.

Google did leave a back door. Android Debug Bridge (ADB) installs still work, and an advanced flow lets people install apps from unverified developers. As Google described it in March, 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 Google aims it at students, hobbyists, and personal use. None of that belongs in a merchant’s Saturday morning store opening. An install guide that tells customers to enable developer mode and wait a day will generate support tickets and an awkward security conversation with their IT team.

Get registered before 2027

Start by mapping every route your Android apps take to a device, including Play, your website, reseller staging, MDM pushes, and any self-updater. Next, inventory package names and signing keys across every build, white-label versions included, and confirm who controls each key. Then request a D-U-N-S number if your company doesn’t have one, since that’s the step with the longest wait, and set up an Android Developer Console account or claim your apps in Play Console. Finally, register every package name, rewrite your reseller and customer install guides, and test a clean install on a certified device. Once you’re registered, Google says users see no change.

A reseller staging 200 handhelds for a new customer won’t wait out a one-day advanced flow on each device. Register before Google names the U.S. date, and the reseller’s install script keeps running the way it always has.

Leave a Reply

Your email address will not be published. Required fields are marked *