Sideloading on iOS is nothing like sideloading on Android, you have to compile the app from source with your personal key and even then it's only valid on the device for 7 days.
There is tooling to manage self-signed certs beyond the seven day window. Unrelated but I find it weird that “you have to compile the app” is a bad thing now.
There are ways to go past 7 days but all come with even more downsides to both the end user and company trying to get users to sideload. "You have to compile the app" is extremely related if you're a company wanting users to install your app, especially since that requires more than just knowledge to be able to do.
To ask you the inverse question, in what way is any of this "nearly identical" to Android sideloading which allows indefinite sideloading via any delivery method, including installation of 3rd party stores, with no more than a click on an approval prompt from the user?
Optimizing for people who want to side load ~and~ cannot click the build button in Xcode seems wild to me. (No disrespect!)
It’s identical though in that <when one side loads> one is <completely disconnect from the ecosystem of the device manufacturer>.
Re: side loading binaries/APKs on my actual phone that’s logged into my actual bank account? Hard pass. There’s a time and place for lax security. This is what air gapping is for.
> Optimizing for people who want to side load ~and~ cannot click the build button in Xcode seems wild to me. (No disrespec
When you personally limit sideloading to be "I compile the app and manage a personal security chain to keep it active" it may seem wild, that's not what the vast majority of Android sideloading/3rd party stores is though. Xcode, beyond requiring installation, requires a macOS install to run it on. There are other ways to compile iOS apps, each even less accessible to users or distribution by companies. And again: the obvious statement that the vast majority of revenue generating apps on the App Store are not open source.
Even amongst the Android tech nerds 3rd party stores like F-Droid are popular because users don't want to compile their open source apps constantly... and there are even less requirements around compiling Android apps than iOS apps!
> It’s identical though in that <when one side loads> one is <completely disconnect from the ecosystem of the device manufacturer>.
Not true, sideloading apps on Android means loading them from a different source not disconnecting them from Google services or the Android ecosystem as a whole. It of course allows for that if it's what you're after but it's not limited in such a scope.
> Re: side loading binaries/APKs on my actual phone that’s logged into my actual bank account? Hard pass. There’s a time and place for lax security. This is what air gapping is for.
On Android sideloading is being able to pick which app sources you trust, even if that means "not Google". That could mean "I compiled it myself on an air gapped computer" to you, "I loaded it from a 3rd party store" to another, and "I downloaded it from the developers site" to a third. Which you personally choose is irrelevant as each user gets to pick their allowed sources so it can fit any user's need.
