Android developer verification: four countries first, global in 2027
If your Android app reaches people outside Google Play, the install path is changing for some of them. Enforcement began on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, and Google says the global rollout follows in 2027.
What Google's guide says
The developer verification guide was last updated on 18 August 2026. It says: "Starting September 30, 2026, these new developer verification protections go live for users in Brazil, Indonesia, Singapore, and Thailand." For the rest of the world, it says: "we will expand these protections globally for all apps on certified Android devices in 2027." It also says the verification capability "will soon be expanded to all third-party Android app stores."
The guide says the ADB workflow "stays the same," and it says: "Your apps can still be sideloaded. Your user's experience may be different depending on the path you choose." It describes an advanced flow for sideloading unregistered apps "with extra safeguards." The rules below are ours, and they are labelled as ours.
Who has to register
The guide gives two registration routes. Developers who distribute only outside Google Play sign up for an Android Developer Console account. Developers who also use Google Play use their existing Play Console account, which gets new functions for registering apps and keys outside Google Play. The guide says that if you distribute through Google Play, you are registered automatically.
Check which route you are on before the date that affects your users. Registration is a step you own, and the guide does not do it for you if your only channel is a direct download.
One codebase. iOS, Android, and web.
The Fitness Kit ships with auth, a database, and a backend already connected — no setup. Live demo at fitness-preview.otf-kit.dev.
What does not change
Read the guide's limits before you plan for worst-case users. The guide says the ADB workflow stays the same, so it describes developer testing with ADB as unchanged. It also says sideloading still works, and that the user experience depends on the path the developer picks.
The guide describes a limited distribution option, and it says: "Distribute to up to 20 devices." Our rule is to use that option only for testers, not for a public install.
Map your distribution
Our rule is to write down three facts before anything else: the countries you ship to, the channels you use (Google Play only, Google Play plus direct APK, or direct APK only), and whether each channel is already registered. Then sort each user group into one of those channels.
Users in the four countries named in the guide need the most attention, because enforcement has already started there. Users elsewhere have until the 2027 global date, so a plan for them can wait. Keep the list of countries in one place, so the plan is easy to update when Google adds detail.
What the guide does not say
The guide does not describe the install prompts a user sees in each path. It does not give a sideload success rate, and it does not give the cost of registration. If your plan depends on one of those details, check the current guide and your own test devices, and do not assume the answer.
Test on a real device in one of the four countries if you can reach one. Install your build through the path your users take, and record every prompt. A screenshot of each prompt is better than a description written from memory.
Our own Android build
The OTF download page offers a direct install of the latest Android build, and it says: "You may need to allow installs from unknown sources." The page does not say how that build fits developer verification. This article does not claim our build is registered or exempt, and it does not describe our build's status under the guide.
If you ship a direct APK, use the same three facts as above: countries, channels and registration status. Then add the install steps your users see, so the support path matches what the device shows.
Keep the support path ready
A user who meets a prompt they do not understand will contact you, not Google. Prepare one support article for each install path: what the prompt says, what to tap, and what happens next. Name each screen by its visible title, so the reader can match the page to the phone in front of them. Link the article from the download page and from any listing you control.
Date every revision of that article. When Google updates the guide, you will need to know which version your users read, and a dated page answers that without a debate.
Test before you ship
Run these checks on a real device, not only in your head:
- Install a build through a direct APK on a device with the setting for unknown sources turned off. Record every prompt.
- Install the same build through Google Play, if you use it. Record the path and any difference.
- Confirm that your support page explains the install steps for each path, in plain words.
- Check that a user who gets stuck on a prompt can find a way forward without a developer tool.
- Keep a record of each device and each country you tested, so the next test starts where this one ended.
Run the last check on a phone with a small screen. A long prompt can push its buttons below the fold, and a user who cannot see the way forward will leave.
Where OTF stands
If you want an Android app already prepared for this change, we cannot point you to one. We checked the SaaS Dashboard, Booking, Fitness and Arcade kit pages for developer verification, sideload, APK and Android install terms. The Expo-based kits say "One Expo codebase ships iOS, Android, and a web export," but none describes a sideload, APK or verification path. Our download page only offers a direct install without a store account.
The pricing page lists the Full-stack kits at $99 each and the Everything Bundle at $149, both as one-time payments, and it offers a live demo before you buy. Check each kit's repository and build settings before you rely on any of them. For the permission changes Google is also rolling out, see the Android notification permission guide. If you are choosing a starting point for a product, the pricing page is the place to compare kits side by side: OTF pricing.
Sources
- Android Developers, developer verification guide: https://developer.android.com/developer-verification/guides
- OTF download page: otf-kit.dev/download
- OTF pricing: otf-kit.dev/pricing
Stop wiring. Start shipping.
- Login, database, and backend already connected — nothing to set up
- iOS + Android + web from one codebase
- AI configs pre-tuned + 40+ tested prompts included