Google’s recent moves to tighten Android’s sideloading capabilities have sparked quite the debate among users and developers. While browsing through the aftermath of this controversy, I stumbled upon an X thread from Sameer Samat, Google’s President for Android, that caught my attention.

Samat was doing damage control, trying to clarify Google’s position on the new developer identity requirements. “Sideloading is fundamental to Android, and it’s not going anywhere,” he insisted. The restrictions, he explained, only apply to unverified developers and are meant to protect users from bad actors rather than limit choice.

sameer-samat-android-sideloading-clarification

This isn’t exactly breaking news since it’s exactly what I mentioned in my rant earlier this week, and dozens of media outlets said the same thing.

But what caught my eye was a response from Sameer to a suggestion that’s actually interesting and might put an end to all the backlash.

A user going by @Le_happy_can proposed something elegant in its simplicity: “I would suggest making a pop-up at installation if it’s from a non verified dev, saying something like ‘This app is from a developer who is not verified. Are you sure you want to install?’ If you guys want to be extra secure, require user authentication (screen lock) on yes”.

Rather than flat-out dismissing the idea, Sameer said, “Thank you for the suggestion — we are still designing how the user side of all that will work.” He also added that they announced this change a full year in advance to give developers time to complete the identity verification process.

google-sideloading-discussion

This could genuinely be the middle ground everyone’s looking for. Android already prompts users about installing apps from unknown sources, but that’s mainly for granting permission to allow APK installations through browsers or other apps. This new suggestion would specifically warn users about unverified developers while still preserving the core sideloading functionality.

The beauty of this pop-up solution lies in its transparency. Instead of blocking unverified apps outright, it puts the choice back in users’ hands while clearly communicating the risks. Google gets to protect novice users from potential threats, while experienced users can still access the apps they need.

Samat also hinted at special accommodations for developers and hobbyists, suggesting Google recognizes the legitimate use cases for unverified apps. But it’s still not clear how this would work because the site clearly mentions verification is required. One Redditor suggested, “Maybe it’ll use your Google account as the signature so you would be able to sign apps for yourself only. Still not a fan of that but better than taking away sideloading altogether.” This makes sense, but we’ll have to wait and see what Google says.

google-apk-developers-hobbyists-testing-sideloading

Whether this becomes a developer setting toggle or something more sophisticated remains to be seen. The implementation details will make or break this approach, but it’s refreshing to see a potential solution that doesn’t completely abandon Android’s open roots.

TechIssuesToday primarily focuses on publishing 'breaking' or 'exclusive' tech news. This means, we are usually the first news website on the whole Internet to highlight the topics we cover daily. So far, our stories have been picked up by many mainstream technology publications like The Verge, Macrumors, Forbes, etc. To know more, head here.

Dwayne Cubbins
1314 Posts

For nearly a decade, I've been deciphering the complexities of the tech world, with a particular passion for helping users navigate the ever-changing tech landscape. From crafting in-depth guides that unlock your phone's hidden potential to uncovering and explaining the latest bugs and glitches, I make sure you get the most out of your devices. And yes, you might occasionally find me ranting about some truly frustrating tech mishaps.

Comments

Follow Us