[engeljohnb]

I can install on my Fedora laptop through dnf. I've never felt like I needed a new word to describe downloading and running an AppImage. Why would phones be different?

[opan]

`adb sideload` existed as a command for installing an apk from your PC on to your phone. Sideloading was not meant to refer to installing an apk on the phone from the phone.

[nzeid]

I knew if I read enough comments I'd finally arrive at my favorite take.

Installing an APK directly through your phone is in fact NOT sideloading.

[cbolton]

That actually sounds like a good idea, the situation is similar with an official channel of "trusted" software for which the distributor takes some responsibility, versus whatever file you downloaded yourself. It's certainly more risky on a Debian system to install a .deb from some random website, or an AppImage, compared to a .deb from the official repositories. I guess it's the same for Fedora.

[tonyhart7]

well because its not allowed to "install" from third party sources (atleast not yet)

google has control on their android ecosystem behave, same reason why its not allowed in playstation or xbox or ios

[engeljohnb]

The whole selling point of Android up until now was that it allowed you to install any app you want.

The point of the above comment is that Google intentionally introduced the word "sideload" to make "installing an app on your own device which Google did not curate" sound more risky and sinister than it is, and I'm inclined to agree.

I "make" coffee on my keurig. If Keurig decides that making any single-serve coffe pods that aren't owned by the Keurig brand is now called "off-brewing," I'd dismiss it as ridiculous and continue calling it "making coffee."

We should use the language that makes sense, not the language that happens be good PR for google.