`abd install` will still work as per[0] so to me sideloading is still possible, so the statement 'Google’s message that “Sideloading is Not Going Away” is clear, concise, and false' is not correct.

I think users should be able to install whatever software they want, without any charge or other external permissions, but at the same time device and OS makers should be able to make it difficult to do so, within reason. Apparently scam apps are more common in some countries than others and is actually a problem in some countries, although I'm not sure.[1] Google did cite that as the reason for the change.[2] However, combined with the way Google has been locking down Android APIs more and more, (eg. the file system, but other APIs as well) it is concerning. At the same time those changes were also about security. I think every phone should be able to have full root permissions if you go through enough hoops without having to install another ROM. That seems to solve most of the issues here.

[0] https://android-developers.googleblog.com/2025/09/lets-talk-...

[1] see eg. https://techcrunch.com/2024/02/07/google-starts-blocking-use... at the end of the article for some examples

[2] https://android-developers.googleblog.com/2025/08/elevating-...

▲

pmontra 9 days ago | parent | next [-]

So are we going to download APKs from fDroid to our computers and then adb install them to our phones? For every update? I see a lot of people, even developers, giving up.

▲

bpye 9 days ago | parent | next [-]

This actually seems worse from a security perspective to me than allowing installing apps on device.

Your email client from F-Droid has an RCE? Too bad - better hope you update manually!

▲

fngjdflmdflg 9 days ago | parent | prev | next [-]

You can run adb from the phone itself via wireless debugging. From what I understand, you can do this via Shizuku or Termux, and there are apps that can give you a user interface for this. What changes is that users have to enable developer mode to get this, which adds another warning label. Although admittedly they may remove this feature or add more hoops to jump through to use it.

▲

celsoazevedo 9 days ago | parent [-]

Wireless debugging not only requires an initial setup, but it also requires being connected to a Wi-Fi network to work. Considering the number of Android users in countries where many don't have Wi-Fi, it's not an option for many.

There's also the problem of some banking apps refusing to work if developer tools are enabled.

	▲	9 days ago \| parent [-]
		[deleted]

▲

MattTheRealOne 8 days ago | parent | prev [-]

This is what people defending this are overlooking. While it may still be technically possible to sideload apps, the additional barriers to entry will be enough to push at least some app developers away from Android development. So while it is possible for some users to avoid direct impacts of this change, the overall fallout will be unavoidable.

▲

floppyd 9 days ago | parent | prev | next [-]

"adb install" is such a far cry from a normal install that it's laughable to call it an alternative or jumping though hoops "within reason". I imagine it won't allow to update an app without another adb install, for one thing. And controlling adb is even easier for google, so how long till you can "adb install" only from within Android Development Studio and only if you have a verified account? Because otherwise all the spooky skammers would be installing stuff on people's phones willy-nilly!

▲

9 days ago | parent | prev [-]

[deleted]