For years, one of Android’s defining traits has been the freedom to sideload apps—installing them from outside the Play Store. That freedom isn’t disappearing, but Google is tightening the rules around how it works. A new developer policy adds mandatory verification for sideloaded apps in the name of security.
The change comes after pushback from open-source advocates, including F-Droid, who warned the rules could cripple alternative app stores. In a blog post, Google pushed back, saying sideloading is “absolutely not going away,” but admitted that the days of unverified APKs are ending.
Under the new system, every app distributed outside the Play Store will need a verified digital signature tied to a developer’s real identity. Google argues this brings Play Store-level accountability everywhere, pointing to data that shows malware in non-Play Store apps appears at 50 times the rate of its own marketplace. If a verified developer distributes something malicious, Google can revoke the certificate, instantly cutting off that app across devices.
For casual users, this means certified Android devices will no longer install unsigned APKs. Developers still have workarounds—local testing through Android Studio or ADB sideloading won’t be affected—but any app meant for public use will have to comply. That’s where concerns come in. F-Droid has suggested that as many as 30% of its 4,000+ apps could face problems if verification ends up being too rigid.
The bigger question is whether this undermines Android’s open identity. Supporters see a win for safety, while critics worry it edges closer to Apple’s walled garden.
Google says the policy strikes a balance between choice and protection. Whether developers and users agree will become clear once the rollout begins.
Don’t miss a thing! Join our Telegram community for instant updates and grab our free daily newsletter for the best tech stories!
For more daily updates, please visit our News Section.
(Source)
Comments