iOS has allowed side loading for half a decade now. Companies that find $100 prohibitive have a free path that’s nearly identical to Android side loading.
It’s completely reasonable that side loaded applications should not be entitled to use regulated payment services.
Edit: Even Android will not entitle side loaded apps for Google payment processing. Android and iOS are literally identical in this regard.
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?
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.
Anything that can run LLVM can side load.
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.
I've never heard of this being possible.
You can install any app you compiled with your own key and it lasts for 7 days before requiring it to be recompiled.
This seven day lie/conspiracy/flat-earth is disappointing.
A far bigger limitation for me is the three-app provisioning limit. There isn't any way to work around it[1], and if you do want to do serious sideloading you almost certainly will need to upgrade to a paid developer account.
[0] Specifically iOS only allows app provisioning over USB or Wi-Fi, not locally. Locally installed software cannot actually communicate with the remote debugging daemon. You can work around this with network extensions, but you don't get to use them in dev-signed apps unless you have a paid dev account that's been approved by Apple to use them.
For the record, that isn't to make sideloading harder; that's because Facebook went and shipped a spyware VPN with their enterprise cert.
[1] Personal experience time: Even when jailbroken, and with AltDaemon and Immortal installed, AltStore still bumps up against the three-app limit.