Google partially reverses its plan to block the installation of apps from unverified developers. The company is developing a new advanced procedure that will allow experienced users to accept the risks and continue installing software outside of official channels. It is an intermediate solution that seeks maintain security without considering sideloading dead.
Until now, the only way that Google mentioned to install apps from unverified authors was to use ADB (Android Debug Bridge): It works, but it is tedious and not designed for everyone. With the new process, the system will display clear warnings and additional steps designed so that no user can be forced to ignore them. It is not perfect or as open as before, but it better adjusts to the use that a part of the community gives to Android.
What exactly changes
1/6 Keeping users safe on Android is our top priority. Today, we're sharing an update on our new developer verification requirements – why they are critical to fighting modern scams, and how we're adjusting our approach based on community feedback. 👇
— Sameer Samat (@ssamat) November 13, 2025
Google will continue with the requirement of identity verification for any developer whose apps can be installed on certified Android devices, either from the Play Store or through sideloading, third party stores or APK files (Android Package). The novelty is that, if you choose to install an app from a unverified developerthis will appear advanced flow within Android itself to allow that installation assuming the risk. The interface is not yet finalized, but the idea is to avoid non-transparent practices and centralize everything in the system.
In addition, Google prepares a light account type for students and fanswith fewer requirements and designed to share test apps with a limited number of devices. It is a limited way of keeping the door open to development, although insufficient for projects that aspire to reach a larger audience.
Calendar and how it affects you
Developer verification does not come suddenly to everyone. In March 2026 will be opened to all developers and, starting September 2026will be mandatory in Brazil, Indonesia, Singapore and Thailand. From 2027 It will be progressively deployed to the rest of the regions. Meanwhile, Google is already inviting a early access program to polish the experience and collect feedback.
For Android users in Spain, the most tangible change will be the appearance of that advanced flow when you try to install an app outside of the Play Store that does not come from a verified developer. If you're an advanced user who relies on alternative sources (for example, an open source project not in the Play Store), you'll be able to proceed without using ADB, albeit with more deliberate steps and warnings to help you make informed decisions.
Greater opening, with conditions
In short, Google is trying to balance opening and scam protection. Sideloading does not disappear, but it is channeled into a lane with strong warnings and more responsibility. Not everyone will agree with this approach, of course, and there will be debate about where to set the bar. How do you see it? Are you convinced by this balance or would you prefer fewer obstacles to install what you want?
