It’s not a “bullshit new term”, it’s three decades old and means transferring files locally from one device to another, instead of directly downloading or uploading from/to an external server.
The origin goes back to MP3.com and i-drive in late 90’s, but the most common sideloading people did was downloading music to their PC using services like iTunes, and transferring them to their mp3 players. As they did often with early PDA and smartphone apps, where the term for Android comes from - get the .apk on your computer, transfer it to your phone, and install it.
Sideloading.
Okay, but Google uses it in a way where directly going to the server they host F-Droid.apk, downloading and installing it counts as sideloading.
If anything, using Google Play is sideloading by that definition, since I can’t just download a release from the originators’ server, they need to first transfer it into a secondary location, Google’s servers, and I can only install it from there.
Fair, it’s not a new term. I was born in the 80’ies, I’m familiar with the concept.
However, it’s now being used with new bullshit meaning (i.e. going outside the Google/Apple app and their own offered selection), and media are normalizing this use.
It is still the same installation method, directly installing the .apk file, from way back when the term for Android usage was defined. So, kinda, but also kinda not.
Also, if you do use ADB to do the install from a PC, the command is “ADB sideload filename” which will do the transfer and installation to the memory directly. Then it truly is sideloading as defined.
Android doesn’t use ROMs (Read-only Memory) any more either, because the filesystems are now writable. But Lineage etc are still called custom ROMs, because the end result hasn’t changed.
It’s not a “bullshit new term”, it’s three decades old and means transferring files locally from one device to another, instead of directly downloading or uploading from/to an external server.
The origin goes back to MP3.com and i-drive in late 90’s, but the most common sideloading people did was downloading music to their PC using services like iTunes, and transferring them to their mp3 players. As they did often with early PDA and smartphone apps, where the term for Android comes from - get the .apk on your computer, transfer it to your phone, and install it.
Sideloading.
Okay, but Google uses it in a way where directly going to the server they host F-Droid.apk, downloading and installing it counts as sideloading.
If anything, using Google Play is sideloading by that definition, since I can’t just download a release from the originators’ server, they need to first transfer it into a secondary location, Google’s servers, and I can only install it from there.
Fair, it’s not a new term. I was born in the 80’ies, I’m familiar with the concept.
However, it’s now being used with new bullshit meaning (i.e. going outside the Google/Apple app and their own offered selection), and media are normalizing this use.
so you’re saying it is the wrong word, because most apks are downloaded from the internet on-device. That is not a local transfer
It is still the same installation method, directly installing the .apk file, from way back when the term for Android usage was defined. So, kinda, but also kinda not. Also, if you do use ADB to do the install from a PC, the command is “ADB sideload filename” which will do the transfer and installation to the memory directly. Then it truly is sideloading as defined.
Android doesn’t use ROMs (Read-only Memory) any more either, because the filesystems are now writable. But Lineage etc are still called custom ROMs, because the end result hasn’t changed.