You also cannot work on this outside of Europe. Developers have to use VPN or special networks to make iOS think they are in Europe. Otherwise you cannot build and run with a custom engine.
It is completely bonkers.
Apple is smart enough to just allow this world wide AND still make huge profits.
> Apple is smart enough to just allow this world wide AND still make huge profits.
Well, no, empirically, it is not smart enough.
Not to be persnickety. :)
Just was a wake up call for me, over years, to realize when I was reflexively making claims* on behalf of Apple that they wouldn't back up.
* a less sad example: they're totally taking gaming seriously now and its gonna be so good. Among others, I thought for sure Apple TV was gonna be at least a minor console
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.
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.
What features on the browser are blocked that are preventing your app from being a PWA? Is it one of the many Google supported privacy breaking features no other vendors want to implement?
Effectively it is because getting accredited as an official App Store is made so ridiculously demanding by Apple that almost no one can afford it and then you still have to somehow get consumers to switch to your App Store.
Why do you have to set up your own App Store when others have already done that? There are alternative stores; publish there without any Apple oversight.
Apple is on the W3C comittee that gets to decide on which proposals will become standardized browser APIs. And they use their power there to block API proposals that could make browsers more capable, competing with native apps.
Apple is holding up quite a few useful API proposals, and they won't even suggest any changes to make to the proposals. They just do not want web browsers to be any more capable than they currently are. Apple is literally stifling innovation in favor of their own greed.
It’s exactly what I’m doing with my personal OS. It’s a web app that runs on my Mac and I access it on my phone using Tailscale and PWA. I haven’t missed not having a native app since web is that good now.
Apple only allows you to access the microphone if you use HTTPS so I had to use Tailscale serve to get a url and I use that.
Distribution is tricky since you’re asking a person to run a web app but fuck Apple’s walled garden.
That's an entirely separate thing. Allowing alternate web engines is wholly different from those web engines being able to add arbitrary icons to springboard.
Browser engines require JIT compilation to work with any sort of performance. The whole iOS security model is (at least partially) based on Apple being able to validate all app code in advance, so Apple doesn't want apps to be able to ship engines that can do their own code generation since they can't sign code generated at runtime.
True, but Google is very aggressive about promoting Chrome on its sites and Gmail. And if you have it installed as an alternative browser it will not stop asking you to make it the default.
Same here, and I refuse to use mobile apps for many experiences. No idea where people get the idea that Chrome is forced onto you if you don't want it.
Google literally paid companies with popular software downloads to hide a Chrome install inside their own product's installer.
If users didn't pay enough attention while clicking next through the installer, they ended up with Chrome as their default browser without understanding how that had happened.
This behavior is disallowed on the App Store, and nobody is asking for that policy to change, but of course Apple, Google, and the Android OEMs can use their privileged position to bundle apps with the OS.
Google goes out of its way to force me to use Chrome.
E.g. despite repeatedly getting "use safari/default browser" all Google apps will ask you again, and again, and again, and again, "Open in Chrome (default choice), Safari, System browser"
Users will install Chrome because they will run into a website which only works on Chrome.
You might not consider that magic, but I do: Look how it changes absolutely everything about what you said without you needing to change a single word.
Google (and others, for different reasons mostly amounting to being cheap or lazy) push people toward Chrome, either very-forcibly ("sorry, Chrome only, go away and come back with Chrome") or by making their sites suck on other browsers (Google likes to do this to desktop Safari and Firefox; my latest encounter is that it's, for weeks, been popping up a tiny and long-lived "unreliable stream?" interactive "toast" directly over the "play/pause" button on Youtube for me, for no reason [the streams are fine! My connection is great! My computer is fast!], but I'm sure being on the "wrong" browser is "accidentally" triggering something, yet again).
I recently had to install Chrome (Chromium wouldn't cut it) on my Mac laptop to do a Telehealth call. That and Edge (which is also Chrome, though that wasn't enough for Chromium to be allowed) were the only two browsers it'd permit, Safari, Firefox, and Chromium (I had all three already) were all refused. That horse-shit would be all over iOS too, if more browser engines could run on it.
On the one hand, they may have self-serving reasons for not permitting other browser engines on iOS. On the other hand, I'm very glad they do it for my own selfish reasons.
For all the hacker news users talking about apple's monopoly, please first talk about Google's monopoly controls of the web. After all apple is at least not monopoly on the entire smart phone market while Google is the web and half of the smart phone market
But hacker news users won't do that because they complain about Apple not because they are close or monopoly, but they make squeezing money from web users a little bit harder
I don't disagree with you, but that goes both ways here too.
Chrome isn't exclusive to one platform, and conversely Android doesn't force you to use it across the entire operating system.
If Chrome is forcing Web standards even in places where no one wants them, the equal and opposite problem is that Safari has a long history of holding back Web standards that are inconvenient to them, and making the entire industry bend around them because their users don't have the option to just install something else.
Part of the problem is actually that Apple also won't really compete here. They want the vertically-integrated everything, and so WebKit everywhere other than their devices is a second class citizen. The support for its underlying stack anywhere else -- from Linux-based browsers like GNOME Web to runtimes like Bun using JavaScriptCore -- has come pretty much entirely from third parties, and there doesn't really seem to be any sort of toolkit analogous to the CEF that could be used to embed it into other applications.
If anything, the only viable effort to make WebKit available across platforms was Chrome.
It's possible to be critical about more than one thing at a type. But to hand it to google, chrome won because it was better for users. Webkit only wins because of structural control. Same for android really, you can run a non google OS on most (all?) android phones, for now at least. the consumer still has choice. Being a hacker is about liberty, and a critical part of liberty is the freedom to make choices (even not the best ones, looking at chrome lol).
This isn't about Google, it's about Apple. And it's not just about browsers, it's about JIT too.
Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.
The site is objective, data-based, and open source, built in response to HN folks posting feelings-based claims. I created it assuming Safari would eat shit, as I was told it would.
> For others, here's the real truth of the matter:
Just look at this person's history and tell me they're objective. I have no skin in the game, other than being a fan of the web as a platform generally and PWAs specfically.
The biggest potential market (revenue wise) for PWA is mobile games. Safari mobile has no fullscreen, screen orientation lock, or vibration API.
PWA installation is also more hidden on iOS, it can't be initiated from a user interaction on the page. The user has to manually go through the share menu, a very non-intuitive location.
> This would be a credible argument if PWAs on Android had any impact.
How are you so sure they don't? Regardless there is less necessity on Android. Google Play store rules and fees are slightly more favorable, there's also third party app stores, and side loading.
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?
Safari is the last non-evergreen browser since it's tied to the OS and the slowest to update so I'm not sure the security argument goes in their favor.
> 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.
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.
I don't think you can dismiss the fact that they don't even allow their own JavaScript engine to use JIT in third party apps as absolutely nothing to do with it.
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.
> The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS.
I mean, that's the prevailing notion.
There's the question of battery life, but that isn't really well served by having e.g. poor touch sampling when a WebGL app can easily go through the entire battery of an iPhone in an hour.
Is there actually any overlap to talk about of web apps that are also one time payment? What apps are we talking about? I don't see many paid apps out in the wild which aren't exclusively native (as opposed to web). Subscription apps easily bypass Apple's app store cut.
I purchase native apps whenever I need to. I wouldn't mind purchasing a web app if that was the best option, but where are they for sale?
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.
Ok, I'll bite, how are you running uBlock Origin (or similar blocking that uses the fanboy/easylists) on iOS today? With dynamic JS blocking, like I have on desktop and Android, so that trackers and such are actually blocked, instead of just some weak DNS-level blocklist that does some superficial adblocking. And SponsorBlock, how are you running that?
If I can't replicate that on iOS then it's not "just fine," imo, and I presume that's the GP's point. If I can't do that, the "bullshit" is the claim that adblocking works on iOS.
I am guessing neither of them are relying on BrowserEngineKit nor following the safe programming guidelines Apple enforces for them to be distributable (and get JIT support on the store basically).
> One of the conditions requires us not to disclose non-public information related to the project
This is insane. Basically if you have a cool project you want to show progress and build hype around, you're not allowed to. Apple knows exactly how deadly this is
They just mean they can't update their existing app with the non-WebKit engine. They have to make a separate SKU, with the non-WebKit engine, and publish that on the App Store.
The sentence after that explains what they mean. They would have to migrate users from the Firefox WebKit SKU to the Firefox Gecko SKU in the EU and migrate all the data from one SKU to the other, essentially a full browser migration.
Isn't that because alternative browser engines are region-locked, so you'd need to have a WebKit version and a non-WebKit version for different regions?
Well I mean there is this port of Gecko to iOS, but you have to sideload it and it seems not as polished as Firefox: https://github.com/minh-ton/reynard-browser . But it's good to at least see somebody try!
There can't be many people that care enough to download an alternative browser. Building a wrapper browser is relatively easy. Porting and maintaining an engine is likely not worth the squeeze. If people actually wanted this, they wouldn't mind migrating their bookmarks to another app. That's not much of an effort really.
Not enough people care → the economics doesn't make sense → Mozilla doesn't care. This is "why there are still no non-WebKit browsers on iOS."
So, Mozilla's excuse is not the complexity of making a browser engine up to Apple's specs [1], but that the users will have to deal with 2 different Firefox browsers on the store.
They'll double their support load, because a good browser will only be available in Europe. And then it'll get randomly disabled for people travelling outside the EU.
Nothing beats not being able to access your stored data when you're away on a business trip!
Apple is/was being sued by the US DOJ in a class action lawsuit over many things relating to these issues: https://www.justice.gov/archives/opa/media/1344546/dl?inline - I say is/was beacuse "Tim Apple" gave a golden trophy to the current president who is easily distracted by shiny gold things.
Apple already lost in Europe and must now allow other browser engines to be installed on iOS by European users.
Why do people in here keep saying "web apps are a threat to the App Store" when Safari on iOS supports web apps and installing them to the Home Screen, just like it always has? Originally iOS was going to be web app only, it only added an App Store because developers figured out how to make apps without Apple's consent and Steve Jobs had to be convinced to create the App Store.
A recent project of mine is web app only, and works great on iOS and Android as an installed web app, exactly the same way. Whether Firefox is running WebKit or not, web apps are a thing on iOS already, so that's not even relevant to this discussion at all.
Safari and iOS support an extremely limited set of "app" APIs. You can't build a web app that works with bluetooth or any other radio. You can't build any kind of full featured camera app.
You can theoretically ship a new default browser that implements more Javascript APIs. There's no way to use that to render web sites added to the home screen though. And they routinely ban browsers that add more APIs for sites.
Because those web apps using WebKit have limited API access compared to other engines/browsers like Gecko/Firefox or Blink/Chromium. Apple doesn't implement those APIs for "security" reasons, but they even directly point at App Store "review" process, so they openly admit that on their platform, those capabilities need review and web apps would bypass that.
Because EU/Japan laws are not enforced, partially because the US president is a moron but also because US politicans are corrupt in general, so US won't help.
Once the admin in US changes in January, you can expect a sheer force of the backlogged EU fines, which they held back to avoid tariffs and other retaliation.
And hey, don't downvote me, I'm seriously just a messenger here.
I downvoted because I don't understand your comment, and I've been tracking the issue of other browser engines not being allowed on iOS for many years.
This includes a long list of strict requirements, some of which are hypocritical because Apple itself doesn't follow them, e.g., "Prioritize resolving reported vulnerabilities with expedience, over new feature development" and "Most vulnerabilities should be resolved in 30 days".
One requirement that Mozilla mentions in their blog post: "Not sync any state (including cookies) between the Alternative Web Browser Engine App (EU) and any other app, even another app of the same developer, unless the user has explicitly given permission for state to be synced, either by signing into both the Alternative Web Browser Engine App (EU) and the other app, or through another mechanism of providing explicit permission"
Some of these requirements are so vague that anything can be rejected. E.g.
> Use memory-safe programming languages, or features that improve memory safety within other languages, within the alternative web browser engine at a minimum for all code that processes web content;
This doesn't seem like a reasonable requirement. Webkit probably doesn't satisfy it.
1. The user already has WebKit Firefox installed on their iPhone, with bookmarks, passwords, history, etc.
2. Apple requires that the non-WebKit Firefox be a separate app, available only in the EU and Japan.
3. If the user wants to switch from WebKit Firefox to non-WebKit Firefox, the user loses their bookmarks, passwords, history, etc.
In contrast, when the WebKit Firefox simply releases an update in the App Store, the user data is retained. Thus, Apple is making it extremely difficult for Firefox to switch from WebKit to non-WebKit.
In general, Apple does allow iOS apps by the same developer to share data, so this restriction for non-WebKit browsers is totally arbitrary. "App groups allow multiple apps produced by a single development team to access shared containers and keychain access groups, and communicate using interprocess communication (IPC)." https://developer.apple.com/documentation/bundleresources/en...
The way you phrase it, you make it sound like Mozilla doesn't care about privacy or user control. That's not the situation here. Also, I notice that your HN account was created less than a hour ago seemingly for the sole purpose of making this comment, which is strange.
Hm, perhaps antimonopoly branches of governments should fine companies for monopolistic behavior in other countries. Because clearly that behavior harms customers in their jurisdictions.
Can't they provide a build through sideloading in an alternative app stores? I'm confused with what the technicals limitations of sideloading are and what Mozilla would preferably do.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations nor having to jump over arbitrary complicated hoops. I'd also add, it is a reason for why i still don't buy an iPad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
The limitations aren't technical. Apple does not want third party browsers on iOS so it is technically possible (in some regions, because they were forced to) but filled with hurdles to discourage anyone from trying.
I was under the impression you still need the entitlement from Apple for JIT, even when you publish to alternative app stores. The only way to get that entitlement is to go through Apple's process here for EU and Japan (or tethered workarounds that may be closed at any time)
Listen I don't understand the issue: You don't even want an iPad, so why the fuck do you care?
I do want an iPad. I like the fact that I can visit my hospital and my bank's websites on it.
I think if Chrome or Firefox were possible to be installed, then the bank and the hospital would eventually target chrome-only, thinking it would save them time or money.
Can you understand, for your mere preference, you might literally cause me and people like me harm?
No, I want an iPad, mostly for its hw, but i even could accomodate myself with iOS/iPadOS, but Safari is not my browser, i don't like it and i use Firefox since Firefox 1.0 and don't plan to change. What i don't like is having an artificial limitation over the most important apps on any modern device: the browser.
Ah, I see your reasoning, I could be sympathetic to it, an argument could be made that the current support for Safari (Firefox is i think largely irrelevant on both mobile and desktop at this point) is just because of its dominance on mobile iOS and that if Chrome were to become dominant it could lead to a single targetted engine. It's a real risk i guess, at least in the short term (given the current Google's enshitification i wouldnt bet against one day people with an appropriate alternative, leaving Chrome, although it wouldn't be Safari or Firefox i think, they already lost), but I still prefer a fair level playing field anyway.
You also cannot work on this outside of Europe. Developers have to use VPN or special networks to make iOS think they are in Europe. Otherwise you cannot build and run with a custom engine.
It is completely bonkers.
Apple is smart enough to just allow this world wide AND still make huge profits.
> Apple is smart enough to just allow this world wide AND still make huge profits.
Well, no, empirically, it is not smart enough.
Not to be persnickety. :)
Just was a wake up call for me, over years, to realize when I was reflexively making claims* on behalf of Apple that they wouldn't back up.
* a less sad example: they're totally taking gaming seriously now and its gonna be so good. Among others, I thought for sure Apple TV was gonna be at least a minor console
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.
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.
This is it. The only answer. 30% toll-booth/extortion racket
> XCode. > 30%.
What features on the browser are blocked that are preventing your app from being a PWA? Is it one of the many Google supported privacy breaking features no other vendors want to implement?
Regular apps have more access to de-identifying information than PWAs. JFYI.
There are all kinds of small issues. For example, we can't do HDR on iOS for photos in the browser because WebGPU doesn't support it.
transpile a copy of gecko/firefox to js that renders to canvas?
That does not add up. In the EU you can distribute apps on iOS outside of App Store. So, there's no monopoly.
Effectively it is because getting accredited as an official App Store is made so ridiculously demanding by Apple that almost no one can afford it and then you still have to somehow get consumers to switch to your App Store.
Why do you have to set up your own App Store when others have already done that? There are alternative stores; publish there without any Apple oversight.
There's plenty of oversight on the alternative app stores. Apple still retains the authority to block apps regardless of what store they come from.
It's so funny considering that at some point Jobs was pushing this version of webapps as future of iOS instead of native appstore apps.
PWAs were literally Steve Jobs' vision for the iPhone when he launched it https://www.youtube.com/watch?v=QvQ9JNm_qWc
It's all of that, and also worse than that.
Apple is on the W3C comittee that gets to decide on which proposals will become standardized browser APIs. And they use their power there to block API proposals that could make browsers more capable, competing with native apps.
Apple is holding up quite a few useful API proposals, and they won't even suggest any changes to make to the proposals. They just do not want web browsers to be any more capable than they currently are. Apple is literally stifling innovation in favor of their own greed.
It’s exactly what I’m doing with my personal OS. It’s a web app that runs on my Mac and I access it on my phone using Tailscale and PWA. I haven’t missed not having a native app since web is that good now.
Apple only allows you to access the microphone if you use HTTPS so I had to use Tailscale serve to get a url and I use that.
Distribution is tricky since you’re asking a person to run a web app but fuck Apple’s walled garden.
That's an entirely separate thing. Allowing alternate web engines is wholly different from those web engines being able to add arbitrary icons to springboard.
Browser engines require JIT compilation to work with any sort of performance. The whole iOS security model is (at least partially) based on Apple being able to validate all app code in advance, so Apple doesn't want apps to be able to ship engines that can do their own code generation since they can't sign code generated at runtime.
> 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.
I suspect that a $5 trillion company could do a reasonable job of competing in browsers if they had to.
Chrome wouldn't magically install itself or make itself the default browser. Users would only ignore Safari if they explicitly want to use Chrome.
True, but Google is very aggressive about promoting Chrome on its sites and Gmail. And if you have it installed as an alternative browser it will not stop asking you to make it the default.
Every Google app I have will first ask to open a link in Chrome, even though it’s not installed. They are very aggressive about it
I've used Firefox as my default browser on Android for years. I have not run into this issue.
Same here, and I refuse to use mobile apps for many experiences. No idea where people get the idea that Chrome is forced onto you if you don't want it.
Google literally paid companies with popular software downloads to hide a Chrome install inside their own product's installer.
If users didn't pay enough attention while clicking next through the installer, they ended up with Chrome as their default browser without understanding how that had happened.
Which iOS applications bundle Chrome in their own installer?
This story sounds a lot like Apple hiding a Safari install for people installing iTunes to use their iPods. https://www.theregister.com/off-prem/2008/03/24/mozilla-ceo-...
This behavior is disallowed on the App Store, and nobody is asking for that policy to change, but of course Apple, Google, and the Android OEMs can use their privileged position to bundle apps with the OS.
> of course Apple, Google, and the Android OEMs can use their privileged position to bundle apps with the OS.
https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
Google goes out of its way to force me to use Chrome.
E.g. despite repeatedly getting "use safari/default browser" all Google apps will ask you again, and again, and again, and again, "Open in Chrome (default choice), Safari, System browser"
Users will install Chrome because they will run into a website which only works on Chrome.
You might not consider that magic, but I do: Look how it changes absolutely everything about what you said without you needing to change a single word.
Chrome does not magically install itself or make itself the default browser on MacOS or Windows either.
Yet…
Google (and others, for different reasons mostly amounting to being cheap or lazy) push people toward Chrome, either very-forcibly ("sorry, Chrome only, go away and come back with Chrome") or by making their sites suck on other browsers (Google likes to do this to desktop Safari and Firefox; my latest encounter is that it's, for weeks, been popping up a tiny and long-lived "unreliable stream?" interactive "toast" directly over the "play/pause" button on Youtube for me, for no reason [the streams are fine! My connection is great! My computer is fast!], but I'm sure being on the "wrong" browser is "accidentally" triggering something, yet again).
I recently had to install Chrome (Chromium wouldn't cut it) on my Mac laptop to do a Telehealth call. That and Edge (which is also Chrome, though that wasn't enough for Chromium to be allowed) were the only two browsers it'd permit, Safari, Firefox, and Chromium (I had all three already) were all refused. That horse-shit would be all over iOS too, if more browser engines could run on it.
On the one hand, they may have self-serving reasons for not permitting other browser engines on iOS. On the other hand, I'm very glad they do it for my own selfish reasons.
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.
They don't want to allow JIT because it lessens the monopoly of the App Store.
For all the hacker news users talking about apple's monopoly, please first talk about Google's monopoly controls of the web. After all apple is at least not monopoly on the entire smart phone market while Google is the web and half of the smart phone market
But hacker news users won't do that because they complain about Apple not because they are close or monopoly, but they make squeezing money from web users a little bit harder
I don't disagree with you, but that goes both ways here too.
Chrome isn't exclusive to one platform, and conversely Android doesn't force you to use it across the entire operating system.
If Chrome is forcing Web standards even in places where no one wants them, the equal and opposite problem is that Safari has a long history of holding back Web standards that are inconvenient to them, and making the entire industry bend around them because their users don't have the option to just install something else.
Part of the problem is actually that Apple also won't really compete here. They want the vertically-integrated everything, and so WebKit everywhere other than their devices is a second class citizen. The support for its underlying stack anywhere else -- from Linux-based browsers like GNOME Web to runtimes like Bun using JavaScriptCore -- has come pretty much entirely from third parties, and there doesn't really seem to be any sort of toolkit analogous to the CEF that could be used to embed it into other applications.
If anything, the only viable effort to make WebKit available across platforms was Chrome.
> If Chrome is forcing Web standards even in places where no one wants them
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
It's possible to be critical about more than one thing at a type. But to hand it to google, chrome won because it was better for users. Webkit only wins because of structural control. Same for android really, you can run a non google OS on most (all?) android phones, for now at least. the consumer still has choice. Being a hacker is about liberty, and a critical part of liberty is the freedom to make choices (even not the best ones, looking at chrome lol).
This isn't about Google, it's about Apple. And it's not just about browsers, it's about JIT too.
Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.
Can we talk about the mating habits of spotted owls in Nebraska instead? I think it's more relevant to the topic at hand.
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.
I've seen reports of about 2 billion active iPhones, that would be $10 per device. It means that Google can extract a lot of money from that people.
A large part is to hinder PWA capabilities on iOS, having equivalent PWA support to Android would drastically impact App Store revenue.
The Safari team is doing a terrible job of hindering PWA capabilities on iOS: https://pwascore.com/
> …having equivalent PWA support to Android would drastically impact App Store revenue.
This would be a credible argument if PWAs on Android had any impact.
Every time this topic comes up, you and your terrible site pop up to spread absolute nonsense about this topic. Are you a paid Apple shill?
For others, here's the real truth of the matter: https://infrequently.org/series/browser-choice-must-matter/
https://open-web-advocacy.org
The site is objective, data-based, and open source, built in response to HN folks posting feelings-based claims. I created it assuming Safari would eat shit, as I was told it would.
> For others, here's the real truth of the matter:
Just look at this person's history and tell me they're objective. I have no skin in the game, other than being a fan of the web as a platform generally and PWAs specfically.
I compared your site to https://wpt.fyi/. Your site seems to track fewer features.
If you were a fan of the web and PWAs, you would be as vocal as I am in denouncing Apple's nonsense. Instead you just add to it.
Here's our most recent exchange https://news.ycombinator.com/item?id=49727868
The biggest potential market (revenue wise) for PWA is mobile games. Safari mobile has no fullscreen, screen orientation lock, or vibration API.
PWA installation is also more hidden on iOS, it can't be initiated from a user interaction on the page. The user has to manually go through the share menu, a very non-intuitive location.
> This would be a credible argument if PWAs on Android had any impact.
How are you so sure they don't? Regardless there is less necessity on Android. Google Play store rules and fees are slightly more favorable, there's also third party app stores, and side loading.
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.
Safari is the last non-evergreen browser since it's tied to the OS and the slowest to update so I'm not sure the security argument goes in their favor.
At the time of the DMA, this wasn't a problem. What's your next excuse?
> 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.
This is not even slightly why they prevent alternative browser engines.
I don't think you can dismiss the fact that they don't even allow their own JavaScript engine to use JIT in third party apps as absolutely nothing to do with it.
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.
> The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS.
Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/
> The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS.
I mean, that's the prevailing notion.
There's the question of battery life, but that isn't really well served by having e.g. poor touch sampling when a WebGL app can easily go through the entire battery of an iPhone in an hour.
Is there actually any overlap to talk about of web apps that are also one time payment? What apps are we talking about? I don't see many paid apps out in the wild which aren't exclusively native (as opposed to web). Subscription apps easily bypass Apple's app store cut.
I purchase native apps whenever I need to. I wouldn't mind purchasing a web app if that was the best option, but where are they for sale?
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.
I run ad blockers etc just fine on iOS.
You need to be up-to-date if you're going to spew bullshit. Ask the AI first.
Ok, I'll bite, how are you running uBlock Origin (or similar blocking that uses the fanboy/easylists) on iOS today? With dynamic JS blocking, like I have on desktop and Android, so that trackers and such are actually blocked, instead of just some weak DNS-level blocklist that does some superficial adblocking. And SponsorBlock, how are you running that?
If I can't replicate that on iOS then it's not "just fine," imo, and I presume that's the GP's point. If I can't do that, the "bullshit" is the claim that adblocking works on iOS.
Ya'll still watching youtube ads though?
Haven’t seen a YouTube ad in years on iOS, or do you mean the lack of sponsor block?
There are non-WebKit browsers on iOS but they don't qualify for notarization:
- Reynard: Gecko-based, iOS 13+, extension support https://github.com/minh-ton/reynard-browser
- Blinker-Fluid: Chromium-based, iOS 12+, content blocker https://github.com/Nodesclock/Blinker-fluid
I am guessing neither of them are relying on BrowserEngineKit nor following the safe programming guidelines Apple enforces for them to be distributable (and get JIT support on the store basically).
> One of the conditions requires us not to disclose non-public information related to the project
This is insane. Basically if you have a cool project you want to show progress and build hype around, you're not allowed to. Apple knows exactly how deadly this is
> One of the conditions requires us not to disclose non-public information related to the project
What does that mean? Doesn’t anything they disclose become public the moment they do that?
iOS is the last bastion before Chromium has the monopoly. Gecko is at 5%, WebKit has 15%.
If keeping a monopoly alive in a small part of the technological world prevents a monopoly for everything, it's worth doing so.
Safari can remain a preinstalled default without preventing me from using my preferred Firefox browser. There is no excuse whatsoever.
I just want to be able to use a custom search engine on Safari without having to use a hacky workaround that only half works..
> we can’t simply update the Firefox app
I'm confused about this part. Is there some sort of code signing requirement that wouldn't be available to the "original" Firefox iOS app?
They just mean they can't update their existing app with the non-WebKit engine. They have to make a separate SKU, with the non-WebKit engine, and publish that on the App Store.
The sentence after that explains what they mean. They would have to migrate users from the Firefox WebKit SKU to the Firefox Gecko SKU in the EU and migrate all the data from one SKU to the other, essentially a full browser migration.
Apple require app with non-WebKit engine target Japan OR EU only. So they can't just update exists app.
Isn't that because alternative browser engines are region-locked, so you'd need to have a WebKit version and a non-WebKit version for different regions?
every update goes through an app review. how do you think that's going to go if you don't adhere to this?
Well I mean there is this port of Gecko to iOS, but you have to sideload it and it seems not as polished as Firefox: https://github.com/minh-ton/reynard-browser . But it's good to at least see somebody try!
There can't be many people that care enough to download an alternative browser. Building a wrapper browser is relatively easy. Porting and maintaining an engine is likely not worth the squeeze. If people actually wanted this, they wouldn't mind migrating their bookmarks to another app. That's not much of an effort really.
Not enough people care → the economics doesn't make sense → Mozilla doesn't care. This is "why there are still no non-WebKit browsers on iOS."
if iOS had:
- something similar to ADB
- profiles like graphine OS
- ability to remove the bloatware apps (music, books, etc..)
- real firefox with real adblock extension
I think a lot of google users would jump ship.
Tech companies are typically the ‘bad guys’ to put it simplistically, and I suspect that is the case here.
But, is there a genuine ‘non-asshole’ reason for these continued Apple restrictions post the EU regulations?
No. Its all about money - web apps are a threat to their App Store extortion racket
So, Mozilla's excuse is not the complexity of making a browser engine up to Apple's specs [1], but that the users will have to deal with 2 different Firefox browsers on the store.
I find it hard to believe.
[1]: https://developer.apple.com/support/alternative-browser-engi...
They'll double their support load, because a good browser will only be available in Europe. And then it'll get randomly disabled for people travelling outside the EU.
Nothing beats not being able to access your stored data when you're away on a business trip!
Is anybody bringing a lawsuit against Apple over this? If this is indeed subverting the purpose of the law, this should be a fight worth taking.
Apple is/was being sued by the US DOJ in a class action lawsuit over many things relating to these issues: https://www.justice.gov/archives/opa/media/1344546/dl?inline - I say is/was beacuse "Tim Apple" gave a golden trophy to the current president who is easily distracted by shiny gold things.
Apple already lost in Europe and must now allow other browser engines to be installed on iOS by European users.
Controlled opposition is no competition.
Why do people in here keep saying "web apps are a threat to the App Store" when Safari on iOS supports web apps and installing them to the Home Screen, just like it always has? Originally iOS was going to be web app only, it only added an App Store because developers figured out how to make apps without Apple's consent and Steve Jobs had to be convinced to create the App Store.
A recent project of mine is web app only, and works great on iOS and Android as an installed web app, exactly the same way. Whether Firefox is running WebKit or not, web apps are a thing on iOS already, so that's not even relevant to this discussion at all.
Safari and iOS support an extremely limited set of "app" APIs. You can't build a web app that works with bluetooth or any other radio. You can't build any kind of full featured camera app.
You can theoretically ship a new default browser that implements more Javascript APIs. There's no way to use that to render web sites added to the home screen though. And they routinely ban browsers that add more APIs for sites.
Because those web apps using WebKit have limited API access compared to other engines/browsers like Gecko/Firefox or Blink/Chromium. Apple doesn't implement those APIs for "security" reasons, but they even directly point at App Store "review" process, so they openly admit that on their platform, those capabilities need review and web apps would bypass that.
But why not at least try? Apple has no incentive to improve some of these things of no one is releasing alternative browsers.
Because Apple fraudulently claims to sell hardware, and still maintain indefinite control over their devices.
Because they maintain true ownership, they can and do dictate all terms of usage of their devices. And that means 'no unapproved browsers'.
They are better classified as indefinite rentals, and not 'sales'
Because EU/Japan laws are not enforced, partially because the US president is a moron but also because US politicans are corrupt in general, so US won't help.
Once the admin in US changes in January, you can expect a sheer force of the backlogged EU fines, which they held back to avoid tariffs and other retaliation.
And hey, don't downvote me, I'm seriously just a messenger here.
I downvoted because I don't understand your comment, and I've been tracking the issue of other browser engines not being allowed on iOS for many years.
"Using alternative browser engines in the European Union" https://developer.apple.com/support/alternative-browser-engi...
This includes a long list of strict requirements, some of which are hypocritical because Apple itself doesn't follow them, e.g., "Prioritize resolving reported vulnerabilities with expedience, over new feature development" and "Most vulnerabilities should be resolved in 30 days".
One requirement that Mozilla mentions in their blog post: "Not sync any state (including cookies) between the Alternative Web Browser Engine App (EU) and any other app, even another app of the same developer, unless the user has explicitly given permission for state to be synced, either by signing into both the Alternative Web Browser Engine App (EU) and the other app, or through another mechanism of providing explicit permission"
Some of these requirements are so vague that anything can be rejected. E.g.
> Use memory-safe programming languages, or features that improve memory safety within other languages, within the alternative web browser engine at a minimum for all code that processes web content;
This doesn't seem like a reasonable requirement. Webkit probably doesn't satisfy it.
If giving users control of whether they want things synced or not is one of the reasons Mozilla cites as a hurdle, then we’re better off as we are.
If privacy and user control are hurdles for you, then your software will not make its way onto my hardware.
I think you misunderstand the problem here:
1. The user already has WebKit Firefox installed on their iPhone, with bookmarks, passwords, history, etc.
2. Apple requires that the non-WebKit Firefox be a separate app, available only in the EU and Japan.
3. If the user wants to switch from WebKit Firefox to non-WebKit Firefox, the user loses their bookmarks, passwords, history, etc.
In contrast, when the WebKit Firefox simply releases an update in the App Store, the user data is retained. Thus, Apple is making it extremely difficult for Firefox to switch from WebKit to non-WebKit.
In general, Apple does allow iOS apps by the same developer to share data, so this restriction for non-WebKit browsers is totally arbitrary. "App groups allow multiple apps produced by a single development team to access shared containers and keychain access groups, and communicate using interprocess communication (IPC)." https://developer.apple.com/documentation/bundleresources/en...
The way you phrase it, you make it sound like Mozilla doesn't care about privacy or user control. That's not the situation here. Also, I notice that your HN account was created less than a hour ago seemingly for the sole purpose of making this comment, which is strange.
Hm, perhaps antimonopoly branches of governments should fine companies for monopolistic behavior in other countries. Because clearly that behavior harms customers in their jurisdictions.
Can't they provide a build through sideloading in an alternative app stores? I'm confused with what the technicals limitations of sideloading are and what Mozilla would preferably do.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations nor having to jump over arbitrary complicated hoops. I'd also add, it is a reason for why i still don't buy an iPad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
The limitations aren't technical. Apple does not want third party browsers on iOS so it is technically possible (in some regions, because they were forced to) but filled with hurdles to discourage anyone from trying.
I was under the impression you still need the entitlement from Apple for JIT, even when you publish to alternative app stores. The only way to get that entitlement is to go through Apple's process here for EU and Japan (or tethered workarounds that may be closed at any time)
You can already install a Gecko-based browser with AltStore or another side-loading technique: https://github.com/minh-ton/reynard-browser
This isn't really meaningful for Mozilla, though.
Listen I don't understand the issue: You don't even want an iPad, so why the fuck do you care?
I do want an iPad. I like the fact that I can visit my hospital and my bank's websites on it.
I think if Chrome or Firefox were possible to be installed, then the bank and the hospital would eventually target chrome-only, thinking it would save them time or money.
Can you understand, for your mere preference, you might literally cause me and people like me harm?
It would be your bank or hospital causing you harm in this case. Not another user that wants to use a different browser.
No, I want an iPad, mostly for its hw, but i even could accomodate myself with iOS/iPadOS, but Safari is not my browser, i don't like it and i use Firefox since Firefox 1.0 and don't plan to change. What i don't like is having an artificial limitation over the most important apps on any modern device: the browser.
That's not what I asked you though. I asked you if you could understand why other people want you to have what you call an artificial limitation?
Ah, I see your reasoning, I could be sympathetic to it, an argument could be made that the current support for Safari (Firefox is i think largely irrelevant on both mobile and desktop at this point) is just because of its dominance on mobile iOS and that if Chrome were to become dominant it could lead to a single targetted engine. It's a real risk i guess, at least in the short term (given the current Google's enshitification i wouldnt bet against one day people with an appropriate alternative, leaving Chrome, although it wouldn't be Safari or Firefox i think, they already lost), but I still prefer a fair level playing field anyway.