Sideloading For iOS Or Why You (Don’t) Want It On iPhones
Let’s take a look at the disadvantages and advantages it can bring
In recent years, the issue of so-called sideloading has been frequently discussed among Apple users. Apple is often criticised for not allowing the installation of apps from unofficial sources on the iOS platform.
On the contrary — the only option is the official App Store, which is completely under Apple’s control. The best way to explain this is with an example. If you create your app and want to get it out there, you have no choice but to try to upload it to the App Store.
The important word here is “try”. Because every app goes through a review and approval process. If there’s anything wrong with the software, the relevant Apple team will return it to you, and you’ll have to fix the specific flaws or bugs. Without that, you won’t get your app out to the public because, as we mentioned above, there’s no other option.
The solution would be to enable sideloading. This would be found on virtually every platform, from Android to Windows, to Apple’s macOS. Sideloading specifically means you can install new software from unofficial sources — for example, download an installer from anywhere on the internet, and you’re done. Something like that is missing from iOS, though. At least for now.
Sideloading in iOS
As we mentioned above, we can forget about sideloading on iOS. Although Apple is often criticized for monopolistic behaviour and abuse of its position, the giant is moving in this direction for a simple reason. Most often, it argues for security.
But the truth is that sideloading has both positive and negative sides. So let’s shine a light on it together. Let’s start with the cons because, as I learned in the course from Jakub, it’s always better to start with negative information and continue with positive than the other way around.
Cons of sideloading
It’s not for nothing that they say that not all gold glitters. Sideloading does come with some negatives. As we mentioned above, Apple often argues for security in this regard, and we have to give it the benefit of the doubt. The fact that all apps are currently available through the App Store, which not only mediates them but also controls them, means that we have much more security.
On the other hand, when we download free software from the Internet, we may need to be completely sure of its trustworthiness. In the worst-case scenario, an app can be used to hack a specific device, steal sensitive data or for long-term tracking. This goes hand in hand with another shortcoming. If sideloading were allowed, there would be virtually nothing keeping developers within the App Store.
Some apps could be pulled from it entirely and handle distribution independently. But there is another security risk in this regard. Users who need the software would have to find it before downloading it. This could be exploited by attackers who could impersonate the developer and send infected software to users’ devices instead.
This risk mainly affects inexperienced users, the elderly, etc., who are not that experienced, which unfortunately makes them easy targets. Disabled sideloading thus acts as an effective prevention in this case. A simple rule of thumb applies — every app has to pass a check as part of its introduction to the App Store.
Benefits of sideloading
First of all, let’s focus on the benefits of sideloading itself. First, we can’t mention anything other than a form of a certain freedom. Apple users would finally not have to look solely to the App Store and its rules but could install anything they want on their device.
Unfortunately, we can talk about a rather freer approach, which is unavailable now. This also goes hand in hand with potential financial savings. It’s no secret that Apple usually takes a hefty fee of 30% of each payment made through the App Store. This, of course, must impact the final price, which must be slightly higher.
By making sideloading available, this rule could be waived. Developers would no longer be forced to use Apple's payment method if they distributed the app in their way. They could thus avoid the aforementioned fees altogether.
In the end, sideloading doesn’t seem like a bad thing. Quite the contrary. It gives users the freedom mentioned above and the choice of whether and which apps to install on their devices.
What does sideloading look like from the perspective of an iOS app developer?
Unless you are a big developer with a turnover of more than $1M, you are looking at a 15% commission to Apple instead of the 30% it takes above $1M. As such, the commission will be on virtually every platform since it has to pay for operations and maintenance, and of course, the platform wants to make some money.
With Apple at this price, you can count on a working system that you don’t have to worry about any further. Suppose you would consider sideloading itself because you fall into the category of, for example, with a turnover of over $1M. In that case, you must also count on the fact that modifying the application for another store may not be trivial, it will cost you time, and it is known to be money.
In addition, you will lose the payment system offered by Apple, so if you use the integrations offered by Apple, you will have to redo everything, for example, against another payment gateway or store where you will have the application exposed.
Then there’s another problem, moving the app itself will also mean what to do with the users who bought your app through the App Store. At the same time, that imaginary tithe for Apple also means that developers don’t have to deal with pirated copies of their apps.
They have the option of using test flights. Yes, there would probably be a $99/year savings in developer fees, but I wouldn’t be sure it would be cheaper to run your app elsewhere.
Will iOS see sideloading?
The question is whether Apple users will ever see sideloading on their iPhones. According to the latest reports, its enablement is getting closer by the day; according to some, it’s also inevitable.
Indeed, Apple has been targeted by institutions like the European Union and others for meaningful regulation in this regard. Only time will tell if it will be for the better. Would you welcome sideloading in iOS, similar to macOS, or is it too much of a security risk?
Final thought
If Apple were to approach this, how would it work at all? For example, we have two stores for Samsung or Huawei products. One is official, and the other has the manufacturer directly.
Users want easily accessible apps that will be secure and won’t have to worry that the app contains, for example, some trojan ci malware that will abuse their data.
It would also be worth it because many end users have virtually yet to learn what any sideloading is, so even just installing a third-party store will go over their heads.
So, in the end, while it may be a nice thing for the big players in the market like Epic, where they get to take a commission on every transaction thanks to their store and not Apple, it’s not an advantage for smaller developers.
Thank you for taking the time to read this article! If you enjoyed it, I appreciate your support through likes 👏🏻 and comments 💬. And if you want more content like this, don’t forget to follow me! Cheers 😊👌👋
Please consider direct support of my work: https://ko-fi.com/jakubjirak
Challenge
I have no choice but to ask my fellow tech life writers what they think about this issue.
- Jakub could tell us something about security.
- Jessica could tell us how she sees it from a user’s perspective. Would you use the option to download third-party apps and be willing to pay for them?
- Ondrej could tell us about sideloading from the perspective of a long-time android user. Do you use it, or is it not for you? Thank you in advance if you join this challenge.
