What Android developer verification is
In practice, Google wants to know who is behind every app installed on certified Android devices. To do that, the developer verifies their identity and registers the app's package name, which is its unique identifier. According to Google, verification confirms who is publishing the app, not what the app does.
Installing outside the stores is still possible. Users can use the ADB command-line tool or an advanced flow, more laborious, that Google launched in August 2026 for apps from unverified developers.
The measure is controversial. There is a public campaign against it, arguing that Google gains too much control over what runs on devices. That debate is legitimate, but anyone running a business needs something else: to know the timeline and what changes for their own users.
Who is affected now and who will be in 2027
The rule took effect on September 30, 2026, for installs made through Google Play and other participating stores, such as those run by some phone manufacturers. It applies to certified devices in the four countries of the first wave. According to Google's FAQ, people who download the app directly from a website or from a store outside that list are not affected yet.
In 2027 the requirement expands globally to all apps on certified devices. Google has not published an exact date per country in the sources we consulted, so any promise of a specific day and month should be viewed with suspicion.
For apps on Google Play, Google says Play Console automatically registers 99% of apps. Even so, we prefer to check each app's registration rather than trust the statistic, because yours could be in the remaining 1%.
The case that worries us most: internal apps distributed by APK
Many companies have an Android app that never went through the store: the app for the field sales team, the driver, the field technician, the inspector. It arrives by link, by USB drive, or through a device management tool. It has worked for years, and that is why nobody looks at it.
When the global requirement arrives, these installs fall into the path of apps without a registered developer, with more steps to install and update. For an app running on dozens of employee devices, that turns into a flood of support tickets.
How managed corporate devices behave in each scenario is something we do not assume: check Google's official documentation and test on a real device. The usual ways out are to register the app in the Android developer console, or to publish it on Play with access restricted to the company, if that makes sense for your case.
Checklist: what to do in the coming months
Nothing here requires a big project. It requires someone with a name and a deadline for each item.
- List all of the company's Android apps and how each one reaches the user: Google Play, another store, APK by link, or a device management tool.
- Find out who owns the developer account for each app. An account in the name of a former employee or of an agency that disappeared is the most common problem.
- In Play Console, check that each app appears as registered and whether there are warnings in the policy status area.
- For apps distributed outside Play, plan registration in the Android developer console before the global expansion in 2027.
- Note the target API level (targetSdk) of each app and compare it with Google Play's current requirement.
- Test installation and updates on real devices used in your operation, including the oldest ones.
- Define who is responsible for maintaining each app and how often it will be updated.
The sister rule: target API level and the app that can no longer be updated
There is another Google Play requirement that catches the same kind of forgotten app. Since August 31, 2026, new apps and updates for phones and tablets must target Android 16 (API 36). Apps already published must target at least API 35 to remain visible to new users on devices running newer versions of Android.
The extension offered by Google ran until November 1, 2026, and that date has already passed. Anyone who has not updated cannot publish a new version, including an urgent bug fix.
The underlying point is that this floor rises every year, in August. A team that has to ask for an extension every year does not have a console problem; it has a maintenance problem.
Common mistakes we see in this kind of situation
The first is discovering the problem on the day the update is rejected. With a bug in production and the app blocked, any fix becomes an expensive emergency.
The second is treating the developer account as an administrative detail. Anyone who cannot prove the account belongs to the company is held hostage by a person or a vendor when registering or transferring the app.
The third is trying to skip several API levels at once on an old app. Each level changes behavior in permissions, notifications, background services, and libraries. Skipping four levels and testing everything at the end is a recipe for breaking what used to work.
How much work this takes and what it depends on
The registration itself is a small, bureaucratic task. What weighs more is updating the app to the required API level, and that depends on how many versions the app has been stalled, the state of the libraries it uses, whether or not the source code is well organized, and whether or not there are automated tests.
A regularly maintained app usually requires one small adjustment per year. An abandoned app may require updating dependencies and redoing old parts, and then the cost rises unevenly. That is why we do not quote a price without looking at the code.
Our approach at SKAD is incremental: update in stages, with the app working and the team using it, instead of stopping everything for a rewrite. When the app is very old, AI helps map out what depends on what, but a person decides the order and validates the result.
From our experience
In practice, what we see most is an Android app that works well for years with nobody touching it, until a store requirement blocks the next update.
The most common mistake we see in these cases is the developer account being in the name of a person or an old vendor, rather than the company that owns the app.
Frequently asked questions
Is Google banning app installs from outside the Play Store?
No. According to Google, installing outside the stores is still possible, but apps from unverified developers require extra steps, through the advanced flow or ADB, once the rule reaches the device.
Is my country in the first wave of developer verification?
The first wave, on September 30, 2026, covers Brazil, Indonesia, Singapore, and Thailand. For all other countries, Google plans to expand the requirement in 2027.
My app is only on Google Play. Do I need to do anything?
Probably very little: Google says it automatically registers the vast majority of Play apps. Even so, check the registration in Play Console and see who owns the account.
What happens if my app does not reach API 36?
You cannot publish updates on Google Play, not even urgent fixes, once the requirement or the extension ends. Apps published below API 35 also stop appearing for new users on newer devices.
Do internal apps, used only by employees, need to worry too?
Yes, especially if they are installed by APK. When the global requirement arrives, installing this kind of app may involve extra steps; the ideal is to register or republish the app before then and test on real devices.
Conclusion
This week, make a spreadsheet with three columns: each of the company's Android apps, how it reaches the user, and who owns the developer account. That alone shows where the risk is. Then pick the oldest app and ask whoever maintains it for a written estimate to bring it up to the required API level, separating what is registration, what is updating, and what is technical debt. If nobody in the company can say who maintains the app, that is the first urgent matter.