|
|
|
|
|
|
by sascha_sl
1821 days ago
|
|
|
Okay, so. 1 and 3 require profiles to be installed (or, as with the case of testflight, have a limited blast radius), they are high friction and non-technical users are not likely to go through with them. Any party bypassing Apple on a large scale would see their signing cert revoked. Apple doesn't generally do that because enterprise certs that have been stolen would also disable business processes for weeks for that customer, but they still have the right to pull them. And I seem to recall that Facebook had their enterprise cert revoked indefinitely. 2 is, yet again, a policy issue. One that iOS 14 actually partially solved. The issue I have with (easily enabled) sideloading specifically is that some very desirable apps want to bypass the App Store to either circumvent the IAP tax (I'd say that's legitimate) or policies designed to prevent #2 from happening. Fortnite being the obvious example, since they already pulled out of Google Play. Facebook is a weird example to bring up, considering they've been in crisis mode ever since iOS 14 took away most of their tracking data. The issue is that Apple uses some of the side effects of their strict curation for their own benefit (once again IAP, but also special entitlements for their own ecosystem, e.g. how their HomePod third party API surface is very barebone and will never work properly with Spotify Connect). I'd be very happy if some better rules were put in place as a result of Apple v. Epic, but I don't think the model is broken to begin with. |
|
|
As for 1 and 3, the limited blast radius doesn't matter so much as long as you target the installs, which seems to be happening.
Also: sorry someone downvoted you, it wasn't me. I'm pretty much eternally logged out due to noprocrast so I rarely vote.