Re:Why there are still no non-WebKit browsers on iOS
by Hamuko on Friday November 20, 2026 @10:30AM
(#50576170)
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?
Re:Why there are still no non-WebKit browsers on iOS
by george_perez on Friday November 20, 2026 @11:32AM
(#50577326)
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.
Re:Why there are still no non-WebKit browsers on iOS
by doe88 on Friday November 20, 2026 @10:30AM
(#50576159)
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, on the official app stores, uncumbered by any artificial limitations, i'd even say it is a reason 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.
Re:Why there are still no non-WebKit browsers on iOS
by Rohansi on Friday November 20, 2026 @10:52AM
(#50576567)
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.
Re:Why there are still no non-WebKit browsers on iOS
by geocar on Friday November 20, 2026 @11:19AM
(#50577074)
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?
Re:Why there are still no non-WebKit browsers on iOS
by doe88 on Friday November 20, 2026 @11:24AM
(#50577170)
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.
Re:Why there are still no non-WebKit browsers on iOS
by doe88 on Friday November 20, 2026 @12:30PM
(#50578552)
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) is its domination on mobile iOS and that if Chrome were to become dominant it could lead to a single targetted engine. It's a risk i guess, but I still prefer a fair level playing field.
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"
Re:Why there are still no non-WebKit browsers on iOS
by spogbiper on Friday November 20, 2026 @10:59AM
(#50576718)
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.
Re:Why there are still no non-WebKit browsers on iOS
by larme on Friday November 20, 2026 @11:23AM
(#50577141)
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
Re:Why there are still no non-WebKit browsers on iOS
by ozlikethewizard on Friday November 20, 2026 @11:30AM
(#50577293)
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).
Re:Why there are still no non-WebKit browsers on iOS
by chaosharmonic on Friday November 20, 2026 @11:36AM
(#50577412)
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.
Re:Why there are still no non-WebKit browsers on iOS
by spankalee on Friday November 20, 2026 @11:47AM
(#50577648)
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.
Re:Why there are still no non-WebKit browsers on iOS
by Tagbert on Friday November 20, 2026 @11:32AM
(#50577341)
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.
Re:Why there are still no non-WebKit browsers on iOS
by bigyabai on Friday November 20, 2026 @12:44PM
(#50578819)
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.
Re:Why there are still no non-WebKit browsers on iOS
by troupo on Friday November 20, 2026 @11:43AM
(#50577563)
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"
Re:Why there are still no non-WebKit browsers on iOS
by GeekyBear on Friday November 20, 2026 @11:52AM
(#50577750)
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.
Re:Why there are still no non-WebKit browsers on iOS
by geocar on Friday November 20, 2026 @11:55AM
(#50577801)
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.
Re:Why there are still no non-WebKit browsers on iOS
by fearthemachine on Friday November 20, 2026 @01:04PM
(#50579126)
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.
Re:Why there are still no non-WebKit browsers on iOS
by alerighi on Friday November 20, 2026 @11:22AM
(#50577121)
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.
Re:Why there are still no non-WebKit browsers on iOS
by ozlikethewizard on Friday November 20, 2026 @11:26AM
(#50577213)
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.
Re:Why there are still no non-WebKit browsers on iOS
by Tade0 on Friday November 20, 2026 @11:30AM
(#50577307)
> 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.
Re:Why there are still no non-WebKit browsers on iOS
by carlosjobim on Friday November 20, 2026 @12:46PM
(#50578843)
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?
Re:Why there are still no non-WebKit browsers on iOS
by CharlesW on Friday November 20, 2026 @12:01PM
(#50577938)
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.
Re:Why there are still no non-WebKit browsers on iOS
by notnullorvoid on Friday November 20, 2026 @01:02PM
(#50579082)
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.
Re:Why there are still no non-WebKit browsers on iOS
by monocularvision on Friday November 20, 2026 @11:34AM
(#50577383)
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?
Re:Why there are still no non-WebKit browsers on iOS
by modeless on Friday November 20, 2026 @11:36AM
(#50577430)
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.
Re:Why there are still no non-WebKit browsers on iOS
by theturtletalks on Friday November 20, 2026 @11:52AM
(#50577761)
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.
Re:Why there are still no non-WebKit browsers on iOS
by dimitricole on Friday November 20, 2026 @12:16PM
(#50578294)
This is the best pattern I found as well. Tailscale makes the networking easy, but the configuration and getting it to less techie friends is still tricky. I made Ovenlight (https://ovenlight.app) to try to simplify this setup and make it easier to share with others (non-strangers) as well. It basically automates this pattern and gives you an ios/android client app to easily and securely access and share these web apps.
Re:Why there are still no non-WebKit browsers on iOS
by theturtletalks on Friday November 20, 2026 @12:44PM
(#50578810)
This is actually really cool! I can make apps for friends and family and I guess their own personal OS? And it’s open-source. You should put a link to the GitHub on the website:
Re:Why there are still no non-WebKit browsers on iOS
by dimitricole on Friday November 20, 2026 @01:05PM
(#50579142)
Thanks! And yes exactly, friends and family is who it's for and also just fyi mic access does work inside Ovenlight. And great feedback, I wanted to make it open source so that people felt comfortable trusting it to serve their private apps, so I'll make sure that's front and center on the site. Curious what does your personal OS do?
Re:Why there are still no non-WebKit browsers on iOS
by boxed on Friday November 20, 2026 @11:55AM
(#50577817)
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.
Re:Why there are still no non-WebKit browsers on iOS
by leptons on Friday November 20, 2026 @12:34PM
(#50578623)
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.
Re:Why there are still no non-WebKit browsers on iOS
by nchmy on Friday November 20, 2026 @12:39PM
(#50578719)
Not to be a pedant, because I completely agree with you, but everything you've mentioned (and more) is downstream of them wanting to hobble the web because it threatens their App Store extortion racket
Re:Why there are still no non-WebKit browsers on iOS
by mentalgear on Friday November 20, 2026 @01:06PM
(#50579159)
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.
Re:Why there are still no non-WebKit browsers on iOS
by viktorcode on Friday November 20, 2026 @01:12PM
(#50579248)
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.
Re:Why there are still no non-WebKit browsers on iOS
by hn-acct on Friday November 20, 2026 @01:21PM
(#50579390)
> 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?
Re:Why there are still no non-WebKit browsers on iOS
by realusername on Friday November 20, 2026 @12:11PM
(#50578161)
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.
Re:Why there are still no non-WebKit browsers on iOS
by k9294 on Friday November 20, 2026 @12:08PM
(#50578099)
> 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.
Re:Why there are still no non-WebKit browsers on iOS
by afavour on Friday November 20, 2026 @12:37PM
(#50578682)
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.
Re:Why there are still no non-WebKit browsers on iOS
by afavour on Friday November 20, 2026 @12:58PM
(#50579025)
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.
Re:Why there are still no non-WebKit browsers on iOS
by captainmuon on Friday November 20, 2026 @11:14AM
(#50577007)
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!
Re:Why there are still no non-WebKit browsers on iOS
by OsrsNeedsf2P on Friday November 20, 2026 @11:35AM
(#50577395)
> 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
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).
Re:Why there are still no non-WebKit browsers on iOS
by leptons on Friday November 20, 2026 @12:51PM
(#50578917)
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.
Re:Why there are still no non-WebKit browsers on iOS
by cromka on Friday November 20, 2026 @12:36PM
(#50578649)
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.
Re:Why there are still no non-WebKit browsers on iOS
by leptons on Friday November 20, 2026 @12:56PM
(#50579001)
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.
Re:Why there are still no non-WebKit browsers on iOS
by amiantos on Friday November 20, 2026 @12:44PM
(#50578799)
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? A recent project of mine is web app only, and works great on iOS and Android 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.
Re:Why there are still no non-WebKit browsers on iOS
by zb3 on Friday November 20, 2026 @12:58PM
(#50579020)
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.
Re:Why there are still no non-WebKit browsers on iOS
by mrkurt on Friday November 20, 2026 @01:07PM
(#50579169)
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.
Re:Why there are still no non-WebKit browsers on iOS
by zb3 on Friday November 20, 2026 @01:00PM
(#50579059)
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.
Re:Why there are still no non-WebKit browsers on iOS
by viktorcode on Friday November 20, 2026 @01:04PM
(#50579131)
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.
Re:Why there are still no non-WebKit browsers on iOS
by cyberax on Friday November 20, 2026 @01:33PM
(#50579575)
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!
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?
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.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, on the official app stores, uncumbered by any artificial limitations, i'd even say it is a reason 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.
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?
This isn't really meaningful for Mozilla, though.
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"
If privacy and user control are hurdles for you, then your software will not make its way onto my hardware.
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 in Japan.
3. If the user wants to switch from WebKit Firefox to non-WebKit Firefox, the user loses their bookmarks, passwords, history, etc.
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
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.
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
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.
https://www.gov.uk/government/publications/mobile-ecosystems...
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.
Yet…
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"
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.
https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
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.
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.
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.
You need to be up-to-date if you're going to spew bullshit. Ask the AI first.
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.
Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/
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?
> …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.
For others, here's the real truth of the matter: https://infrequently.org/series/browser-choice-must-matter/
https://open-web-advocacy.org
> 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.
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.
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?
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.
https://github.com/snowy-ghost/ovenlight
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.
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?
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.
The sheer quantity of old school Flash's exploits were a recent memory when the policy was set.
and this org is doing the most and best work to force Apple to change. Please support them: https://open-web-advocacy.org
So.. Yes. More hoops to jump over, less competition, bigger market share, profit.
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.
But, is there a genuine ‘non-asshole’ reason for these continued Apple restrictions post the EU regulations?
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
- 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).
Apple already lost in Europe and must now allow other browser engines to be installed on iOS by European users.
And hey, don't downvote me, I'm seriously just a messenger here.
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 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'
I find it hard to believe.
[1]: https://developer.apple.com/support/alternative-browser-engi...
Nothing beats not being able to access your stored data when you're away on a business trip!