Why is Apple so hell bent on preventing alternate browser engines in iOS? Is there a financial benefit for Apple in forcing their own engine on every user? At the surface level this just seems silly so I must be missing something.
> Why is Apple so hell bent on preventing alternate browser engines in iOS?
To keep Safari relevant.
> At the surface level this just seems silly so I must be missing something.
I worry a lot about the day Chrome becoming possible on iPhones, because at that point, people will be able to ignore Safari.
Yes. Apple gets more money if they don't open up, according to this UK government investigation. 2022.
https://www.gov.uk/government/publications/mobile-ecosystems...
This exceptional series of blog posts explains everything: https://infrequently.org/series/browser-choice-must-matter/
and this org is doing the most and best work to force Apple to change. Please support them: https://open-web-advocacy.org
There are some browsers but nothing with JIT, Apple doesn't want to allow JIT because it makes it easy to bypass the operating system restrictions.
Google pays Apple roughly $20B a year to keep Google the default search engine in Safari. It only does this because of Safari's market share.
A large part is to hinder PWA capabilities on iOS, having equivalent PWA support to Android would drastically impact App Store revenue.
They obviously don’t want to allow alternate browser engines but the only objection the alternate browser vendors have is that they’d had to release a new app (since they allow only alternate browser engines in certain markets)
That sucks, for sure, but I don’t see why that stops the browser vendors. Like… why wouldn’t just release a second app and see how it performs?
> Why is Apple so hell bent on preventing alternate browser engines in iOS?
They don't trust third parties to keep up with exploits on such a large attack surface.
The sheer quantity of old school Flash's exploits were a recent memory when the policy was set.
> The deal between Apple and Google makes Google the default search engine in Apple's Safari browser, with Google paying Apple roughly $20 billion annually (including a 36% share of search advertising revenue generated through Safari).
So.. Yes. More hoops to jump over, less competition, bigger market share, profit.
They would have to expose parts of the OS that they like to keep close.
A simple technical reason (and no, I’m not saying there aren’t anti-competitive reasons they do it too) is the locked down OS.
Safari has JIT. The webview you use inside apps runs in its own process, and has JIT. If you run JavaScriptCore in your own process, it doesn’t have JIT. So they’re clearly concerned about the possibility of JIT breaking some kind of security concern.
The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS. Poor web apps leads to requirement for good native app, Apple retains strong control over what gets run on their devices and maintains their very juicy cut of in app purchases.
Because with browser with an alternative engine (like Firefox) you can run extensions, and with extension you can (for example) block ads reliably on every site, bypass paywalls, access piracy sites, and do all sort of stuff that Apple prohibits you to do.
I wouldn't be surprised if Google will start attaching Firefox even on Android in favor of Chrome... the sole reason they probably didn't already do so is that they fear sanctions from the EU and other countries that have antitrust in place.
The web poses a threat to their monopoly on iOS app distribution. If web apps could easily install PWAs with a home screen icon, with 64-bit wasm and access to a bunch of OS APIs not currently exposed to installed PWAs, then a lot fewer people would find it necessary to jump through Apple's App Store review hoops for the privilege of giving 30% of their revenue to Apple, on top of paying for the developer program subscription and buying Macs to run XCode.