Why there are still no non-WebKit browsers on iOS
blog.mozilla.orgI'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, 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.
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?
Your minor inconvenience is nothing compared to people who literally -cannot- use a decent ad blocker, can't customise their browser UX, cannot use WebUSB or Web MIDI or any of the other technologies that Apple refuses to implement because they want to protect App Store revenue.
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"
> 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 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 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.
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
No, you can't, at least on most phones. Recently bought a new Android phone and it was sad to see how many vendors don't allow unlocking the bootloader anymore.
I've been running LineageOs without gApps for many years now and it is perfectly clear, that all big actors are actively working against that choice:
- Google forbidding installation of apps outside the play store - Apps refusing to run without Play services, e.g. some banking apps - Vendors forbidding to unlock the bootloader, e.g. Xiaomi in recent years.
It is getting worse on all fronts.
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.
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
I mean, Web Workers is something only Google could love. They could have provided an API that would let you give commands to the cache layer of the browser and it would have the speed and reliability of native code behind it and if the system wants to evict one piece of data from the cache to deal with storage pressure... it can. Instead they invented a Rube Goldberg machine which doesn't really do anything and you have to write another Rube Goldberg machine inside the first Rube Goldberg to get "offline operation as a service." And you've got to deal with all the async programming difficulties and unreliability and I know for years all the storage operations you could back it with are awful.
Like I'm the guy who signs off on the ticket being done and I've been the guy who answers the pager when it goes off in 2 in the morning and even when I'm getting a stage demo ready for somebody who has the improv acting and stage magic skills to make a 20% done app look like... magic I have to get that 20% functionality working 100% in some certain sense and the Web Workers API screams "you're going to mess around with this forever and it's never really going to work right" whether the product is under or over baked or just right.
So the discussion about PWAs is another one of those discussions that SV has with itself without involving the other 99% of software developers and web users. Google might have had a lot more luck pushing it had they involved a focus group of people in Minnesota or Dublin somewhere.
And of course that 1/3-baked notifications API just raises my hackles, like the first thing I am going to do with a new web browser is turn it off. I mean, every web site is already trying to spam me every way it can possibly spam me, the last things I need are another pop-up menu that covers content, another dialogue of any kind to close, and the possibility that I'll click the wrong button and get spammed.
(And in the "iOS sucks" department, notifications are a big part. I've found that if I have any kind of filtering or groupings I lose important notifications, I will find out i got a text message from my son a week after I get it, etc. To have a decent experience I have to turn filtering/grouping off and give notifications permissions to the few apps that I need notifications from)
As long as this is the current state of things with WebKit, the counterweight to that is that Apple ultimately gets veto power over any standard the rest of the industry does agree on, and random HTML and CSS features will sit functionally unusable for years because a single OS vendor doesn't see them as a priority.
The problem that we're both ultimately getting at here is that one vendor shouldn't get to have a chokehold on the spec. With Safari it just happens to be closer to what was wrong with IE.
The "rest of the industry" is functionality just Google. The only reason Google pretends to care about "standards" is because of the large amount of iOS users on WebKit. That evaporates when Google, via Chromium has complete control of the web platform.
Honestly, they are already past caring. web.dev often posts celebratory articles about "standards" already enabled in Chrome as fait accompli.
Firefox also rejects the Chrome-only non-standards
> ultimately gets veto power over any standard the rest of the industry does agree on
Where "rest of industry" is invariably "we build from Chromium source code with very little changes".
Apple very rarely vetoes standards that non-Chromium browsers (aka Firefox) also agrees on.
Edit:
> and random HTML and CSS features will sit functionally unusable
HTML and CSS features Apple is usually very much behind (as in: support them fully), and ships them very much on time with everyone else. They are often held back by Apple's own inane "release yearly" schedule.
See interop 2025 vs 2026: https://wpt.fyi/interop-2025?stable vs https://wpt.fyi/interop-2026?stable and then click to "experimental"
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.
If Apple did not make their own hardware, well, obviously they wouldn’t be in the position they’re in. if someone out there starts making their own hardware to go with their own operating system, they also can be in the same position. Its very simple, if you are a vertical computer company, you get to call the shots.
Apple would not be here today. If they had not made the decision to design their own hardware, just that simple, and it will be simple for someone else in the future who does the same thing because it will be the only way you can carve out a market and survive there used to be many vertical computer companies in the 1980s and Wintel put an end to them.
I wish SGI, Sun, Next, Digital, Acorn and Commodore Amiga, were still around some of them, because I can now afford to buy them.
No, Google does not control "the web". You're trying to divert the conversation to Google instead of the topic of Apple's abusive business practices.
Apple doesn't even make Safari for any other platform anymore. They used to but they decided to stop. They could compete with Google's web browser, but they don't. They prefer to stay in their closed ecosystem, not even trying to compete and forcing other browser makers to use their browser engine.
Maybe we should talk about why Apple doesn't make Safari for other platforms and their abusive business tactics, instead of whatever Google does.
edit: let me rephrase: apple is easy to avoid, google is not. Hackernews users disproportionately discuss about apple's "monopoly" and closeness not because they think it's morally wrong, but because it reduce the easiness to squeeze money from users.
I can't think of a single way that Google has made life harder or worse for me.
And Google is very easy to avoid. It hardly takes any effort at all. You just have to buy an iPhone where Apple is the monopoly, forcing you to use their browser engine whether you want to or not. Apple also stifles innovation in the W3C, actively making people's lives worse just for their own greed.
>If you cannot see that then there's not point to continue the discussion.
This pointless internet interaction is over.
This article is about Apple, so we'll yeah talk Apple. Other articles are about Google so we yeah talk Google. It's not some conspiracy, it's just how topics work.
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.
(the nag likely varies by region, time of day, your browser extensions, operating system, and moon alignement so ymmv)
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.
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.
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.
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.
SponsorBlock has an officially supported iOS app (or you can use Orion browser)
I had it in my head that that somehow wouldn't be possible without Apple allowing other browser engines. Happy to learn I was wrong!
> SponsorBlock, how are you running that?
This is literally available in the app store, if you choose not to use Brave / Orion.
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/
> 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.
Here's our most recent exchange https://news.ycombinator.com/item?id=49727868
E.g. it shows Safari failing on accelerometer tests. Same as Firefox. As both are against giving browsers unrestricted info about users' devices.
That's why Interop and Baseline are never about Chrome-only non-standards
Saying that Alex Russel has truth on the matter is quite rich. He has a very, let's say, interesting approach to truth.
> https://open-web-advocacy.org
Ah yes. The people who say that "Edge for all intents and purposes is a different browser" and lists Chrome-only APIs (those that even Firefox is against) "essential web standards".
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.
Safari desktop, however, even lets me wrap web apps like Slack that weren't coded to support PWA.
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.
My one suggestion is to create a style guide for Claude so that the homepage doesn't have Claudeisms.
For example, Claude loves the word hold, which is v annoying. The word "with" is right there.
E.g. "anyone holding its invite link"
For my personal OS, the main app is one where I can control terminals on my Mac on a web page and I built that into the personal app. The other is a calendar that’s not connected to Google or Apple calendar. It has an MCP so Claude can schedule tasks for me, workout session, LinkedIn posts, etc. It has a nice timeline so I can see my day.
Another big app is curator where I started finding and collecting nice things I find on the internet and good websites. Overall it’s a great playground to get ideas off the ground before turning them into fully fleshed products.
I also made a lot of mini apps in personal OS for websites I don’t like or push ads so I use their unofficial API. It also has a built in web browser in the web app itself so I can look at the website changes and dictate to the AI at once. Overall it’s helping me build an open-source Shopify for every vertical.
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 seems odd the world is letting one company hold our hand behind our backs.
The only reasons I see Firefox blocking it is 1) Apple is paying them, 2) Firefox just doesn't have the resources to implement them. I'm leaning towards option 1, because Firefox shouldn't care what other browser makers have the resources to implement as long as the API proposals are sound (and they are sound).
Edit: If you're going to downvote, at least provide a comment as to why I'm wrong about any of this. Provide some evidence that counter my statements. I admit I stated opinions, not facts.
What kind of thought process did you use to arrive at this conclusion? It's really not very well reasoned, honestly.
There have already been several great projects that use these APIs. You thinking they don't matter is nonsense, because many people know that web browsers do benefit from these APIs, and I have many uses for them myself.
These APIs allow me to avoid Apple's App Store, and being forced to buy Apple desktop and mobile devices just to develop an iOS app where they can then extract even more money from me through the app. So Apple users will just have to suffer instead, because I refuse to give Apple that kind of money.
I need Web Bluetooth to communicate with my hardware device product. I don't want to have to pay Apple for the privilege to use bluetooth when it works perfectly fine in a web browser that isn't intentionally crippled.
https://medium.com/@larsgk/web-enabling-legacy-devices-dc3ec...
https://news.e-ink.me/en/archive/2026-04-07/article/rescuing...
https://yes-we-scan.app/details
Not that iOS needs this, but Apple is just holding back innovation. They won't even make recommendations for any changes to get their approval for these browser APIs.
So it is totally useful, I can experiment with and deploy applications and not have to pay to get into the platform and deal with App Store bullshit, I just post my files to the web when I want to update.
I’d argue overall it would be difficult to make applications with a better UI outside web technology, everything else looks like Motif in comparison. There is a reason why there are so many Electron crapplets.
Epic had a chance with their own store in Android. It turns out no one trusted them and no one bought from them, but that didn’t stop them from crying. Google is unfair and what’s interesting is that they still have the same problem on iOS. No one trusts them and the government ultimately can’t help with that.
And no surprise, Epic is having the same problem within the iOS world. No one trusts them.
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.
- Install discoverability is awful and there's not a single install button API like Chrome
- Safari often break core web features like localStorage or indexDB and since it's the slowest browser to update, you are playing russian roulette
Because only updating the browser during a full OS upgrade was a stupid move. There's absolutely no reason it can't be upgraded via the app store like Google does with Chrome and other system apps, even ones that can't be removed.
What a concept if you build something well, people actually will pay if a product is good I mean, I don’t understand the problem. Isn’t Android out there? How are developers doing in the Android world when it comes to people actually paying when it comes to apps. I understand that it’s three times less, despite the market being three times bigger worldwide.
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.
Having other browsers while you’re the one making the operating system and the hardware would leave you with all the blame and no profit.
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 deep in the recesses of the mid-level sub-threads you finally spot it: standing there indiscriminately is the Where’s Waldo you’ve been searching for. The one guy that always gets it.
“You can’t map memory to execute on App Store binaries. Makes a lot sense actually…” he begins, but it’s already too late. You reach out back him up, but the comment is already fading. “and you could always sideload whatever you want on an iPhone, and that tiny fee has other benefits..”.
And then it’s gone. You pause, a moment of gratitude for witnessing it’s sad, brief existence, and continue scrolling onward. God bless you, Mr. Guy-That-Gets-It
Apps can ship engines that can run arbitrary code, it just needs to be so slow that it can't compete with WebKit.
Browsers in iOS is just one of the most infamous examples, but they do it all over the place.
The gaming industry couldn’t be bothered either. But in one or two generations they will when the Apple GPU hardware gets in the neighborhood of Nvidia GPU’s and they appear to be just two generations away at most and that’s when crying will start.
Nothing is stopping anyone from doing anything. They just can’t be bothered, or they want a free ride. Which has been the case over the years Autodesk and Adobe are indifferent as is SolidWorks so still are many others, the pattern is indifference until Apple goes something successful that becomes popular and then the crying starts about unfair competition, wash, rinse, and repeat.
It’s amazing that a little company in Australia blackmagic can support all three platforms and stay up to date. when so many big companies, well, can’t be bothered.
Apple didn't have the API until like 2024. "https://www.apple.com/newsroom/2024/08/developers-can-soon-o..."
They want to remain independent from chromium but if your browser has no user, no one even check if it works.
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
What does that mean? Doesn’t anything they disclose become public the moment they do that?
- 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).
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."
Apple already lost in Europe and must now allow other browser engines to be installed on iOS by European users.
If using a non-Webkit browser is so important to you, there are alternative devices.
There are significantly fewer browser companies and their interest in pushing for compliance is a lot less though, so we'll see if it ever comes around. It seems Mozilla might be starting to get frustrated enough to compile a complaint at least.
And hey, don't downvote me, I'm seriously just a messenger here.
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.
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.
Yup. That "very limited set of app APIs" is always shifting and changing, according to whatever definition of "limited" suits the speaker. Every time Chrome releases another (standard or non-standard, doesn't mater) distantly PWA-related API, HN is all aflame with "look, Safari is limited".
And yet we're yet to see a plethora of great amazing PWAs on Android that doesn't have these perceived limitations.
And yet we're yet to see a plethora of great amazing PWAs on Android. An OS that doesn't have these perceived limitations.
I.e. it's only on iOS where there is a forced position to use PWAs for distribution of anything not vendor approved (in most regions) and therefore only on iOS where there is a desire to more heavily use them yet, not coincidentally, only iOS where they are always less powerful anyways. Solve the ask for one and you largely solve the ask for the other.
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!
It is completely bonkers.
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. I thought for sure Apple TV was gonna be, at least, a minor console a la Wii
I mean, it is? Its sort of a poor mans steam machine.
Some games my kids have enjoyed:
- Sneaky Sasquatch
- Crossy Road
- TMNT Splintered Fate
- What the Golf
- Bloons
- BalatroIt's even sadder to think that software is the only thing stopping them. Proton has been AArch64 native for almost a year now.
The me that was thinking this was young and dumb, more akin to "Ah, given the stuff Apple built here and what they're saying, _of course_ GTA 6 will be launching on Apple TV alongside other consoles in 2026."
It’s not a super common name.
I would posit that Apple isn't doing this for profit, but for control. Apple still has a lot of bad habits and controlling users to a pointless degree is still part of that.
Safari encourages the retention of multiple browser background windows, so grievously that I can find dozens or even hundreds of active webpages on an average user's device.
Private browsing also requires several steps to engage, unlike Android Chrome and peers, that allow a long click on the Chrome icon to drag a private browsing link onto the desktop.
My normal and immediate replacement for Safari is Firefox Focus. I don't usually want browsers on iOS retaining any state, so anyone who complains about Safari behavior to me is advised to vivisect it thus.
One could argue that's not a bad habit, that's a core value, and a feature not a bug.
decades ago there was was some "chicken crosses the road" jokes around computing, C++ chicken, dos chicken, windows 95 chicken. the joke for Apple was "No reasonable chicken owner would want their chicken to cross the road so there's no way to tell it to do so"
Apple has long been about a refined and controlled experience. Excessive choice and freedom are antithesis of what Apple is all about.
apple tolerates an app called StikDebug which fakes a debugging connection from Xcode, under that condition JIT is enabled (along with other entitlements).
to distribute an app that uses JIT normally you must get the entitlement expressly reviewed from Apple. many do, including other emulators.
- 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.
And Orion browser has built-in adblock, AND supports firefox extensions, on all Apple OSes.
I think you can hide, but not remove apps like music, so bloat is not gone
You can pretty much delete anything. Even the clock.
If keeping a monopoly alive in a small part of the technological world prevents a monopoly for everything, it's worth doing so.
* Google has already convinced a huge number of people to install the Chrome app (which is currently a Webkit skin until Google ships an update).
* Google apps (e.g. Gmail) and Google Search will be even more aggressive in pushing you to Chrome rather than the system default. iOS users will be familiar with the dark patterns Google employs to trick you into clicking an App Store link for Chrome when you just wanted to see your web search results.
* Perennially lazy web developers will have an excuse to slap a "works best in Chrome" banner on their websites and force end users to install a browser they didn't want. So much for browser "choice".
When web developers stop caring about Webkit, browser choice dies.
Apple doesn't let you use it on iOS, so that cuts out a slice.
For what it's worth, concerns of Google "beating" WebKit may be overstated: Only 19% of iOS users choose Google Chrome's app right now, while 79% choose Safari[0]
[0]: Per CloudFlare Radar, https://sqmagazine.co.uk/mobile-browser-usage-statistics/#:~...
But I suppose I'm just committing the Goomba Fallacy.
The fact that they have not suggests that these regulations are performative.
Of course they are because the governments themselves don't want this. They want everyone to use these app stores with "certified" devices to push their mass-surveillance agenda and make it as painfully as possible to use your device like you want.