If you install apps from outside the Google Play Store, your Android phone is about to work differently. Google has confirmed that its Android developer verification programme will start rolling out worldwide in January 2027, and once it reaches your phone, apps from developers who have not registered with Google will no longer install the normal way.
The good news is that sideloading is not being banned. There is a built-in escape route for experienced users, and most people will notice nothing at all. But if you install APKs from a developer’s website, an open-source store like F-Droid, or a friend’s test build, there is real homework to do before January. Here is everything that changes, who it affects, and exactly how to keep installing the apps you want.

What Google announced
Google confirmed the worldwide rollout in an update on 19 November 2026. Android developer verification will begin expanding to every country in January 2027, starting with seven app distributors — Google Play, Samsung Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo — and then widening over several months to every installation source on certified Android devices. That last part is the important one: once the rollout reaches your region, the check will apply not just to app stores but to sideloaded APKs and open-source registries too.
This is not a brand-new policy appearing out of nowhere. Google first announced developer verification in August 2025, opened registration to all developers in March 2026, and switched the protections on in four countries — Brazil, Indonesia, Singapore and Thailand — on 30 September 2026. Those four countries were the pilot. January 2027 is when the rest of the world joins them.
Google says millions of apps have already been registered since March, and that registered apps now account for over 99 percent of all Android app installs worldwide. The unregistered remainder is under 1 percent of installs — a small number overall, but a big deal if the app you rely on is in that 1 percent.
What is Android developer verification?
Android developer verification is an identity check, not a malware scan. Before an app can install normally on a certified Android device, its developer has to verify their identity with Google and register the app, linking a real identity to the app’s signing key and package name. Google says registration takes less than ten minutes, and standard registration involves a $25 fee and a government-issued ID.
That is separate from Play Protect, which already scans app binaries for malware regardless of who signed them. Verification adds an identity layer on top: the idea is to make it harder for anonymous bad actors to keep spreading harmful apps under new names after being caught. Matthew Forsythe, Google’s director of product management for Android app safety, said Google worked with distributors and Android communities for more than a year before the September launch.
There is also a free route for small developers. Limited distribution accounts, launched in August 2026, let students and hobbyists skip the registration fee and the government ID check. Google has raised the sharing cap on those accounts from 20 to 50 authorised devices, so a hobbyist can share a test build with a small group without paying. Teams shipping many apps can automate registration through two APIs Google provides: the Android Developer ID Status API and the Android Developer Console API.
One detail catches a lot of developers out: even apps that are already on Google Play must be registered separately if they are also distributed outside Play. And for open-source registries, Google has published a separate guide for registering existing and new apps.
What changes for you
If you only install apps from Google Play or your phone maker’s store, almost certainly nothing. Those apps come from developers who are already registered, and Google says the install experience for registered apps stays exactly the same. Your phone will keep working as it does today.
If you sideload apps, it depends on the developer. If the developer has registered their app with Google, nothing changes for you either — the app installs normally. The friction only appears when you try to install an app whose developer has not registered. In that case the normal install path is blocked, you get a notification explaining why, and your options are the advanced flow described below, or installing over ADB from a computer.
The timing matters too. January 2027 is when the global rollout begins, not when it lands on every phone at once. Google says the protections will expand over several months, and the check is delivered through Google Play services rather than a full OS update. That means it can reach your phone quietly, without an Android version upgrade — and, by the same token, Google can adjust it without shipping new system software. Reports based on Google’s developer guides suggest the rollout could be fully online by March 2027, but Google has not published a single worldwide enforcement date, so treat that as an expectation rather than a promise.
How to keep installing apps from unverified developers
Google has built a deliberate side door for power users, called the advanced flow. It is a one-time setup, and it is intentionally awkward — the friction is the point. Google designed it so that a scammer on the phone cannot talk someone through installing a malicious app in the moment. Here are the steps, as described in Google’s own FAQ and help documentation:
- Turn on Developer options. Go to Settings, then About phone, and tap Build number seven times until Developer options is unlocked.
- Open Developer options and find the unverified apps setting. Look for the option covering apps from unverified developers and turn it on.
- Confirm that nobody is pressuring you. Android will ask you to confirm that you are making this change freely and that nobody is coaching you through it. This is the anti-scam check.
- Restart your phone and unlock it again.
- Wait 24 hours. This is a mandatory one-day waiting period. There is no way to skip it, and it is the single most important guardrail: if someone is pressuring you to install an app right now, the delay gives you time to step back and think.
- Come back and confirm with your PIN, fingerprint or face unlock. After the wait, return to the setting and confirm your identity.
- Choose how long to allow unverified installs — for seven days, or indefinitely.
After that, installing an app from an unverified developer still shows a warning, and you tap “Install anyway” to proceed. If you turn the setting off again, you will not be able to install or update unregistered apps until you turn it back on — so updates to those apps depend on keeping the flow enabled.
There is one more route that skips the wait entirely: ADB. Installing an app from a computer over USB with Android Debug Bridge is not affected by the verification check, and the 24-hour wait does not apply. That keeps life normal for developers and testers, though it is not a practical everyday method for most users. And the whole programme only applies to Google-certified devices — phones running custom ROMs without Google certification are not covered.
Why Google is doing this — and why people are unhappy
Google’s argument is straightforward: most malware on Android comes from apps whose makers are anonymous, and tying every app to a verified identity makes it harder for bad actors to reappear under a new name. With over 99 percent of installs already covered by registered apps, Google presents this as a change that protects the vast majority while inconveniencing a small minority.
Critics see it differently. Developers and open-source advocates argue that the requirement hands Google a gatekeeper role over software it never distributed, that the $25 fee and ID check are a real barrier for hobbyists in some countries, and that the advanced flow is deliberately buried deep enough that ordinary users will never find it. The campaign against the change has pointed out that the fallback flow runs through Google Play services — a proprietary component Google can change without an OS update — and that the policy applies retroactively to phones people already own. Google’s answer to the hobbyist concern is the free limited distribution account, but that caps sharing at 50 devices, which does not work for a popular open-source app with thousands of users.
Both sides agree on one thing: this is the biggest change to how Android apps are installed since the Play Store itself. Whether you see it as security or control probably depends on how you get your apps.
What to do before January
Do not panic, and do not rush into the advanced flow today — the check is not live in most countries yet, and turning it on early gains you nothing. Instead, do three practical things now:
First, check where your apps come from. Open your app list and think about which apps you installed from outside the Play Store. If the answer is none, you can stop reading — this change will not touch you. If you do sideload, note which apps they are and who makes them.
Second, check whether those developers have registered. Most established developers — the makers of popular sideloaded apps, alternative stores and open-source projects — are registering now, and many already have. If a developer has not said anything about verification, ask them or check their website and release notes before January.
Third, if you do need the advanced flow, set it up calmly and on your own time. The 24-hour wait means you cannot do it in a hurry, so do not leave it until the day you need to install an urgent update. And never enable it because someone on a call, in a message or on a remote-support session tells you to — that is exactly the scam the waiting period is designed to stop.
Google has been rolling out a wave of Android changes this November — from the November Pixel Drop, which brought Pixel Search to every Pixel since 2021, to Gemini’s arrival in the car with Android Auto — and developer verification is the one with the longest tail. It will not change your phone overnight in January, but it will change how Android works for everyone who installs apps outside the Play Store. Knowing the steps now means you will not be locked out of your own apps later.
FAQs
Is sideloading banned on Android in 2027?
No. Sideloading is not banned. From January 2027, Google is extending Android developer verification worldwide, which means apps from developers who have not registered with Google will not install through the normal path on certified Android devices. You can still install those apps through the advanced flow for experienced users — a one-time setup in Developer options with a 24-hour waiting period — or over ADB from a computer. Apps from registered developers, which Google says already account for over 99 percent of Android installs, will install exactly as they do today.
What is the advanced flow for installing unverified apps?
The advanced flow is Google’s built-in route for experienced users who want to install apps from unverified developers. You turn on Developer options, enable the unverified apps setting, confirm that nobody is pressuring you into the change, restart your phone, wait a mandatory 24 hours, then confirm with your PIN, fingerprint or face unlock and choose to allow unverified installs for seven days or indefinitely. After that, installing an unverified app shows a warning and you tap “Install anyway” to proceed.
Will Google Play apps be affected by developer verification?
No, not in any way you will notice. Apps installed from Google Play come from developers who are already registered, and Google says the install experience for registered apps stays the same. The change only creates friction for apps whose developers have not registered with Google. One exception for developers: an app that is on Google Play but is also distributed outside Play must be registered for that outside distribution too.
Do I need to do anything before January 2027?
For most people, no. If you only install apps from Google Play or your phone maker’s store, nothing changes. If you sideload apps, check whether the developers of those apps have registered with Google — most established developers are doing so now. If you rely on an app from an unregistered developer, set up the advanced flow calmly before you need it, because the 24-hour waiting period means you cannot enable it in a hurry. Never enable it because someone on a call or in a message tells you to.
Does developer verification apply to all Android phones?
No. It applies to Google-certified Android devices, and the check is delivered through Google Play services. Phones running custom ROMs without Google certification are not covered by the programme. ADB installs from a computer are also exempt, so developers and testers can keep installing unpublished apps without the 24-hour wait. Google’s FAQ describes the requirement as applying to certified devices running Android 8 or later, although some of Google’s own documentation mentions Android 7 — the exact minimum version is one detail Google has not stated consistently.
Sources: Help Net Security — https://www.helpnetsecurity.com/2026/11/20/android-developer-verification-power-users/ ; Digital Trends — https://www.digitaltrends.com/phones/google-to-make-sideloading-harder-android-developer-checks-january/

