zlacker

[return to "Google restricts Android sideloading"]
1. tdeck+o9[view] [source] 2025-06-05 17:26:21
>>fsflov+(OP)
I've got to say, some of the comments here are pretty funny.

> "The sideloading restriction is easily solved by installing GrapheneOS"

> "Unless they block ADB, I wouldn't say it's accurate to claim they're "blocking sideloading"".

Not to pick on these folks but it's like we on HN have forgotten that ordinary people use phones too. For some of us, it's not a limitation as long as we can solder a JTAG debugger to some test pads on the PCB and flash our own firmware, but for most users that's just about as possible as replacing the OS.

◧◩
2. Aurorn+Xx[view] [source] 2025-06-05 20:06:02
>>tdeck+o9
Making it difficult for ordinary people to sideload apps that access their SMS or accessibility features (e.g. screen recording, controlling the phone) is the point.

I think what people on HN really forget is that the average person isn’t equipped to tell the difference between a legit source sideloaded app or a Trojan horse app that some TikTok video instructed them to install.

◧◩◪
3. palmot+wy[view] [source] 2025-06-05 20:11:08
>>Aurorn+Xx
> Making it difficult for ordinary people to sideload apps that access their SMS or accessibility features (e.g. screen recording, controlling the phone) is the point.

I wonder if they could solve that with delays. E.g. you can sideload, but the process is deliberately delayed to take two full days and require carefully reading warning screens and correctly answering questions about the warnings, then getting time to think, multiple times.

[go to top]