Google has confirmed that Android will introduce a more demanding path for installing apps from developers who have not been verified, while maintaining that advanced users will still be able to proceed after acknowledging the risks.
The confirmation followed an Android Authority report about text found in recent versions of Google Play. Those strings pointed to new warnings around developer verification, connectivity requirements and potential dangers associated with software obtained outside verified channels.
Matthew Forsyth, Google’s director of product management for Google Play developer experience, responded publicly that the change should be understood as an “Accountability Layer” rather than a prohibition on sideloading. According to Android Authority’s account of his statement, users will retain an option labeled “Install without verifying.” Reaching and using that option, however, will require extra steps intended to make the decision deliberate and ensure that risks are understood.
The distinction matters because sideloading—the ability to install software without obtaining it from Google Play—has long been part of Android’s identity as a comparatively open mobile platform. Independent developers, alternative app stores and advanced users depend on that route when an app is unavailable through Google’s marketplace or when they prefer a different distribution channel.
Google’s framing puts developer identity and informed choice at the center of the planned flow. A warning can help users distinguish a known developer from an unknown one and may interrupt impulsive installation of harmful software. At the same time, every added screen or requirement makes the alternative route less convenient, so the design details will determine whether the feature acts mainly as risk education or as a practical deterrent.
Several details were not settled in the supplied report. Google had not indicated that installation would require a personal computer or external tools, and Android Authority said the precise degree of friction remained unclear. The evidence also does not provide a rollout date, supported Android versions, a complete sequence of screens or rules for how developers become verified.
That leaves the policy’s effect dependent on implementation. A clearly marked override that remains available on the device would preserve user choice, albeit with more warnings. A long or confusing sequence could make sideloading substantially harder even without formally blocking it.
For now, the confirmed point is narrower than either outcome: Android is preparing additional steps for unverified installations, and Google says those steps are designed to establish awareness and accountability. Evaluation of the change will require the final user interface and verification policy, not just labels found in development builds. Users and developers will need the released flow to judge the balance.
