Google has begun the phased rollout of a new 'extended' mode for installing apps from third-party sources in Android. The key innovation concerns apps from developers that have not passed official verification: after a user allows the installation of such software, they must observe a mandatory 24-hour waiting period before the installation becomes possible. The mechanism is already being rolled out to devices gradually, and its launch is tied to a broader initiative on mandatory identification of Android app developers.
How the 24-hour waiting period works
To allow the installation of apps from unverified developers, the user must now open the developer options and enable the 'Allow apps from unverified developers' item. After that, Android displays several warnings about possible risks and offers to start a one-time 24-hour waiting period. Once it is over, the user will have to return to the same settings section and reconfirm the permission. Access to installing unverified apps can be enabled temporarily — for seven days — or left active for an indefinite period.
Exceptions and working with ADB
The new restrictions do not apply to installing apps via ADB — this mechanism continues to work as before. In addition, after activating the new mode, the developer options can be turned off again without canceling the choice made earlier. Thus, Google does not ban sideloading entirely, but deliberately complicates the procedure specifically for those APKs whose authors have not passed verification.
The role of Android Developer Verifier and the timeline
The new system is handled by the Android Developer Verifier app, which Google announced in March of this year. At the time of publication of this article, the corresponding update is being rolled out to devices gradually, which explains why some users already see the new scenario while others do not yet. The company emphasizes that the introduced warnings and delay are intended to protect users from malware and social engineering tactics.
Connection to mandatory developer identification
Changes to APK installation are directly linked to the introduction of mandatory identification of Android app developers. From September 30, Google will begin applying the new rules in Brazil, Indonesia, Singapore, and Thailand, and in 2027 it plans to extend the system to other markets. This means that in the coming months and years the barrier to entry for authors of apps from third-party sources will be systematically raised, and 'gray' APKs without a verified developer will fall under enhanced control.
Assessment of the impact on the ecosystem
For a typical user who installs apps from Google Play, the changes are practically unnoticeable. However, for an audience accustomed to sideloading modified versions of software, custom ROM apps, and unregistered utilities, the procedure becomes noticeably more burdensome: now a multi-day barrier is inserted between the intention to install a file and the actual installation. Experts note that the combination of the 24-hour wait, multiple warnings, and mandatory developer identification forms one of the strictest anti-sideloading regimes in Android's history, while still not blocking legitimate debugging scenarios via ADB.
