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.
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.
It would be helpful if Apple actually used their control to create a pleasant browsing experience. Safari is diametrically unpleasant, and is the first thing that I disable and purge on an iOS device.
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.
> Apple still has a lot of bad habits and controlling users to a pointless degree is still part of that.
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.
It's actually a lot more complex than that, the EligibilityD deamon pulls in a ton of signals from your mobile provider, other devices, gps location, which version of the appstore and the decides your eligibility based on combo of those. I think it would be very hard to circumvent.
> 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
The Steam Machine is relatively weak compared to proper PC gaming setups but it is still far more capable than even the latest Apple TV. Less than half as much RAM (8GB vs. 16+8GB) and apps can only use 2GB. Good enough for basic games, like what you listed, but not for anything serious.
It's possible to get Ocarina of Time Remake working within the 2GB limit of the latest Apple TV - https://www.reddit.com/r/decomps/comments/1xwnadj which is a modern Switch 2 game. If Apple allowed games to take up the full 8GB, you would definitely be able to play significantly more games as well.
With all due respect, lists like this really highlight why Apple's walled garden approach to gaming crashed and burned compared to devices like the Steam Deck.
It's even sadder to think that software is the only thing stopping them. Proton has been AArch64 native for almost a year now.
Enjoy it while it lasts. You only rent those games, you don't own them. The second the game studio takes their game out of Arcade, your copy of it stops working. Having downloaded the game does not mean you can use it beyond that point.
I get what you're saying, totally, and respect it, upboated you. Hell I'd probably enjoy it more than a console at this point.
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."
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?
> 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.
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.
If it doesn't work on iOS it doesn't matter how standard it is or many other browsers implement it, because as a developer you can't rely on it. That's a big reason why Apple wants to keep their browser engine monopoly on iOS, to have veto power over standards.
Firefox follows Apple on most things Apple wants to block. But again, instead of providing any feedback or proposing any changes, they just let these proposals die in committee. I would not doubt that someday we find out Apple has been somehow forcing Firefox to do this. There is simply no good reason to block WebBluetooth, WebSerial, or any of the many other APIs that would benefit developers and users. And no, it isn't a security issue, and no it isn't a privacy issue, as these APIs work the same way existing APIs work with regards to security and privacy - they are strictly opt-in per-website, just like the microphone and camera APIs are done now.
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.
Perfectly fine for you to think that. However, you could simply not allow websites to access WebBluetooth and WebSerial instead of supporting browser vendors that refuse to support the features entirely. Both already require you to allow access.
>WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth
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.
WebSerial sounds like a really neat feature. I could see consumer 3d printing companies like Bambu using that to make 3-D printing from their model libraries dead simple, no need for the end user to even have a slicer. And for the hobbyist it makes all sort of cool web apps possible. There's all sorts of devices that I could see a much better story for if that was possible. Both for the less and more technical user.
WebUSB is even more interesting. There's been several projects that "rescue" old hardware where the drivers are no longer viable on modern OS, and instead the browser can now support the older hardware.
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.
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.
That may be what he said at the time. It was easier for Apple and differentiated from competitors. Yet that changed so quickly I find it hard to believe they weren't already working on native apps behind the scenes.
The web is filled with garbage. Purpose built programs are always going to be better than web solutions which will never be trusted nor be as good particularly in the era of AI. And it’s also funny about this new theory that you are a monopoly of yourself.
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.
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.
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.
What's important is that you can publish without Apple's review. I doubt that unless you publish something extremely criminal Apple would care to revoke the certificate.
Apple can’t lead a horse to water. Most people still to this day don’t buy most of the apps that are on the App Stores and mostly it is a trust issue and in most cases quality issue even at this late date.
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.
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.
Nearly twenty years, the same thread dozens of times each year, filled with the same tired argument: simple-minded, juvenile “greed” dictates the policy and procedures of Apple’s corporate business strategy. As if.
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
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.
Google Maps loves to randomly decide to forget your chosen default option and bring up their picker with Chrome up top and system default below the fold. (And no, I rarely update maps and I only have one account that’s always signed in. There’s nothing I’m doing that would make me think that I “reset” maps somehow.)
That's a problem with iOS not allowing setting default apps for a long time (2020 for browser, 2025(!) for maps). If these prompts remain, it's because iOS users have gotten used to it, so Google thinks it can get away with it. This was never a problem on Android.
Google is less aggressive on mobile browsers, as well as on Firefox in general (I still see it there occasionally). But try going to google.com in any Chromium-based browsers on a desktop PC and you'll see this: https://ibb.co/xt3V26mQ
(the nag likely varies by region, time of day, your browser extensions, operating system, and moon alignement so ymmv)
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.
Right. If anything, they would push you to the mobile app for the service instead of Chrome, and they actually do this the first time you access Gmail or Google Maps in a mobile browser, but this happens even if I use Chrome.
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.
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.
> As long as this is the current state of things with WebKit
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.
The poor adoption of PWAs is part of that disease.
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)
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).
> you can run a non google OS on most (all?) android phones, for now at least
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.
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.
Apple makes hardware and software. And in comparison to the competition, they do both fairly well. Google only cares about one thing: collecting information. so that they can sell to their real customers.
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.
>For all the hacker news users talking about apple's monopoly, please first talk about Google's monopoly controls of the web.
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.
Google does control most of the web as an app platform and that's how most hackernews users use web to make money. Safari is one of the last reason google does not control all.
and no matter how abusive apple is, they are not monopoly on a critical part of human being's daily life. People can just buy an android (or even linux) phone and call it a day. Hence a person can avoid the whole apple ecosystem easily. That's not true for google. If you cannot see that then there's not point to continue the discussion.
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.
> and no matter how abusive apple is, they are not monopoly on a critical part of human being's daily life.
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.
You say that like we can't walk and chew gum at the same time.
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.
I'm not sure why JIT is okay on desktop, but not okay on mobile. Is the desktop any less important than mobile? Does Apple not care if JIT is used to exploit desktop computers? My mobile phone is way more likely to get lost or stolen than any other device I own, so I don't keep anything of value on it. I simply don't worry about JIT exploiting it as much as I do someone at a coffee shop walking away with it.
They do it because Apple has the highest paid group of people online within their ecosystems and it’s interesting that Google was only able to get a measly $1 billion refund on that $20 billion they probably thought they had leverage just like OpenAI who also thought they had leverage and they walked away with even less they got nothing.
Why not make a open source + open foundation browser exemption - like for Firefox ? The all time vulnerability count for Safari is also pretty high so your position doesn't quite make sense. And AFAIK, Apple has never stated your position knowing that basic math would invalidate it.
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 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.
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.
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".
Control and the fact that no one cared before they got big, like the birth of the M1 or Apple Pay which only exist because the other pay systems couldn’t be bothered at the time to support Apple devices.
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.
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?
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 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 were always extreme in market manipulation anti-competitive and lock-in behavior like that, as long as they thought they could get away with it, damaging the competition with impunity.
Browsers in iOS is just one of the most infamous examples, but they do it all over the place.
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.
Just FYI, Orion supports extensions. Both Orion and Brave also have native adblocking supporting arbitrary filter-lists that perform dynamic JS blocking.
> SponsorBlock, how are you running that?
This is literally available in the app store, if you choose not to use Brave / Orion.
You can run uBO with Orion browser (Apple doesn't allow swapping browser engines, but they do allow network filtering and editing webpages/running scripts)
SponsorBlock has an officially supported iOS app (or you can use Orion browser)
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
My interpretation was more like: One of the conditions requires us not to disclose [information Apple hasn't publicly disclosed] related to the project -- so essentially the Firefox team is having difficulties beyond what they mention here, but they can't mention them here because Apple hasn't mentioned them publicly. Presumably, it's something about the root cause of the prohibition on an engine swap in the existing app. I assume it's not merely the region-targeting (since TFA says "Apple began allowing alternative browser engines on iOS in the EU") but perhaps the PWA/WASM stuff as discussed in other comments here.
If anti-monopoly regulators were serious, they would require OS vendors to provide a toggle for "let me install software from anywhere I damn well please with zero interference".
The fact that they have not suggests that these regulations are performative.
>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.
Perhaps this view is much less popular than you may think? For example, despite being a technie, I would campaign against that with all my might, write letters, and shout from the highest rooftops I could find. When I buy a locked down device, I buy it precisely for that. And no "just don't toggle the toggle" does not work, just like "just don't download viruses" did not work in the 2000s. I need a device that my grandmother CANNOT misuse, not even when a very patient scammer on the phone walking her through it.
The solution to this problem looks something like Windows S mode combined with an account managed by a family member. Once enrolled, the account manager has to approve an exit from the restricted mode.
Apple could choose to selectively allow Gecko as an alternative while rejecting Chrome's rendering engine.
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]
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."
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.
> Safari and iOS support an extremely limited set of "app" APIs.
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.
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.
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.
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!
I don't like Apple, and maybe you were just using the slippery slope argument. But let's be clear: your apps don't get disabled when you travel in a country where they're not available.
Yes, they do. Apple will disable EU-related features after you're 30 days outside the EU, including app updates. You also will not be able to restore them, if you break your phone on a trip and buy a replacement.
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.
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.
Why do people who ask such questions keep on spending money on the fruit factory in the full knowledge that they'll do their best to extract as much extra money from them as feasible? Just... stop giving them money? There's plenty of alternatives, some almost as restricted and getting even more so - Google, looking at your future plans - and some doing their best to keep a balance between 'security' and the freedom to tinker. Get one of those, new or used, do with it what you want - from just using it as it comes to writing your own OS and anything in between - and leave the fruit to ferment on the vine.
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.
Hm, perhaps antimonopoly branches of governments should fine companies for monopolistic behavior in other countries. Because clearly that behavior harms customers in their jurisdictions.
There should be a better competition law enforcement so Apple couldn't get away with these shenanigans. They should be very heavily fined until they comply.
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.
Your fear is completely irrational, no bank or hospital is going to target Chrome only on iOS because 99% of the user base will stick to the default of Safari. Or you will use their app. Or (oh no!) you might have to install Chrome for a few sites.
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.
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.
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.
The control is there to increase profits, so doesn't make sense to contrast them
Its to stop Google using it's control over Chrome.
It would be helpful if Apple actually used their control to create a pleasant browsing experience. Safari is diametrically unpleasant, and is the first thing that I disable and purge on an iOS device.
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.
How do you manage to ‘disable and purge’ it from an iPhone? As far as I am aware it can only be hidden
> Apple still has a lot of bad habits and controlling users to a pointless degree is still part of that.
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.
I was under the impression that developers can run whatever they want on their device, including enabling JIT support.
No, JIT requires Apple reviewed entitlements.
How can sidestores companion enable JIT then for Qemu?
What mechanism are they enforcing that? Xcode stops you from building it or something?
GPS, actually.
It's actually a lot more complex than that, the EligibilityD deamon pulls in a ton of signals from your mobile provider, other devices, gps location, which version of the appstore and the decides your eligibility based on combo of those. I think it would be very hard to circumvent.
GPS simulators are a thing though :)
By now, Apple management is just a bunch of standard idiots, driven by greed, same as in any other monster corporation.
As opposed to when?
> 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
> Apple TV was gonna be at least a minor console
I mean, it is? Its sort of a poor mans steam machine.
Off topic but I just wanted to say hello from another James Swift :)
It’s not a super common name.
Tell me more? (my steelman: "there's games on the App Store" / "I can stream games from my PC" :)
Have you tried apple arcade? Its a pretty good service. And gamepad support is really good in my experience.
Some games my kids have enjoyed:
The Steam Machine is relatively weak compared to proper PC gaming setups but it is still far more capable than even the latest Apple TV. Less than half as much RAM (8GB vs. 16+8GB) and apps can only use 2GB. Good enough for basic games, like what you listed, but not for anything serious.
It's possible to get Ocarina of Time Remake working within the 2GB limit of the latest Apple TV - https://www.reddit.com/r/decomps/comments/1xwnadj which is a modern Switch 2 game. If Apple allowed games to take up the full 8GB, you would definitely be able to play significantly more games as well.
With all due respect, lists like this really highlight why Apple's walled garden approach to gaming crashed and burned compared to devices like the Steam Deck.
It's even sadder to think that software is the only thing stopping them. Proton has been AArch64 native for almost a year now.
Enjoy it while it lasts. You only rent those games, you don't own them. The second the game studio takes their game out of Arcade, your copy of it stops working. Having downloaded the game does not mean you can use it beyond that point.
This is no different than other subscription schemes like. PlayStation Plus or Xbox Game Pass. You can also buy apps like normal.
I get what you're saying, totally, and respect it, upboated you. Hell I'd probably enjoy it more than a console at this point.
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."
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.
Personally I have two issues with PWA for iOS:
- 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
> 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.
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.
Must W3C proposals be unanimously accepted?
It seems odd the world is letting one company hold our hand behind our backs.
If it doesn't work on iOS it doesn't matter how standard it is or many other browsers implement it, because as a developer you can't rely on it. That's a big reason why Apple wants to keep their browser engine monopoly on iOS, to have veto power over standards.
Firefox follows Apple on most things Apple wants to block. But again, instead of providing any feedback or proposing any changes, they just let these proposals die in committee. I would not doubt that someday we find out Apple has been somehow forcing Firefox to do this. There is simply no good reason to block WebBluetooth, WebSerial, or any of the many other APIs that would benefit developers and users. And no, it isn't a security issue, and no it isn't a privacy issue, as these APIs work the same way existing APIs work with regards to security and privacy - they are strictly opt-in per-website, just like the microphone and camera APIs are done now.
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.
WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth
Perfectly fine for you to think that. However, you could simply not allow websites to access WebBluetooth and WebSerial instead of supporting browser vendors that refuse to support the features entirely. Both already require you to allow access.
>WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth
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.
WebSerial sounds like a really neat feature. I could see consumer 3d printing companies like Bambu using that to make 3-D printing from their model libraries dead simple, no need for the end user to even have a slicer. And for the hobbyist it makes all sort of cool web apps possible. There's all sorts of devices that I could see a much better story for if that was possible. Both for the less and more technical user.
WebUSB is even more interesting. There's been several projects that "rescue" old hardware where the drivers are no longer viable on modern OS, and instead the browser can now support the older hardware.
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.
Of course not: Google adds web features without W3C consensus all the time. And then Hacker News bitches about that too.
transpile a copy of gecko/firefox to js that renders to canvas?
Sounds wildly inefficient
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.
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
That may be what he said at the time. It was easier for Apple and differentiated from competitors. Yet that changed so quickly I find it hard to believe they weren't already working on native apps behind the scenes.
There was some movement that way, but it was a skunkworks project and not part of the official plan, as I recall.
The web is filled with garbage. Purpose built programs are always going to be better than web solutions which will never be trusted nor be as good particularly in the era of AI. And it’s also funny about this new theory that you are a monopoly of yourself.
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.
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 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.
What's important is that you can publish without Apple's review. I doubt that unless you publish something extremely criminal Apple would care to revoke the certificate.
Except for the time they did it to UTM in alternate stores: https://sixcolors.com/link/2024/06/apple-refuses-to-notarize...
Apple can’t lead a horse to water. Most people still to this day don’t buy most of the apps that are on the App Stores and mostly it is a trust issue and in most cases quality issue even at this late date.
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.
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.
Nearly twenty years, the same thread dozens of times each year, filled with the same tired argument: simple-minded, juvenile “greed” dictates the policy and procedures of Apple’s corporate business strategy. As if.
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
> 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.
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
Google Maps loves to randomly decide to forget your chosen default option and bring up their picker with Chrome up top and system default below the fold. (And no, I rarely update maps and I only have one account that’s always signed in. There’s nothing I’m doing that would make me think that I “reset” maps somehow.)
That's a problem with iOS not allowing setting default apps for a long time (2020 for browser, 2025(!) for maps). If these prompts remain, it's because iOS users have gotten used to it, so Google thinks it can get away with it. This was never a problem on Android.
I've used Firefox as my default browser on Android for years. I have not run into this issue.
Google is less aggressive on mobile browsers, as well as on Firefox in general (I still see it there occasionally). But try going to google.com in any Chromium-based browsers on a desktop PC and you'll see this: https://ibb.co/xt3V26mQ
(the nag likely varies by region, time of day, your browser extensions, operating system, and moon alignement so ymmv)
If you use a Chromium-based browser, you search from the omnibox and would ~never see that.
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.
Right. If anything, they would push you to the mobile app for the service instead of Chrome, and they actually do this the first time you access Gmail or Google Maps in a mobile browser, but this happens even if I use Chrome.
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?
Dude is talking about Windows. This used to be super common
The article is about web browsers on iOS.
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.
I suspect that a $5 trillion company could do a reasonable job of competing in browsers if they had to.
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...
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
You're not wrong, but think of it this way:
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 does agree on
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.
> The only reason Google pretends to care about "standards"
Honestly, they are already past caring. web.dev often posts celebratory articles about "standards" already enabled in Chrome as fait accompli.
> As long as this is the current state of things with WebKit
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"
The poor adoption of PWAs is part of that disease.
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)
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).
> you can run a non google OS on most (all?) android phones, for now at least
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.
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.
Apple makes hardware and software. And in comparison to the competition, they do both fairly well. Google only cares about one thing: collecting information. so that they can sell to their real customers.
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.
>For all the hacker news users talking about apple's monopoly, please first talk about Google's monopoly controls of the web.
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.
Google does control most of the web as an app platform and that's how most hackernews users use web to make money. Safari is one of the last reason google does not control all. and no matter how abusive apple is, they are not monopoly on a critical part of human being's daily life. People can just buy an android (or even linux) phone and call it a day. Hence a person can avoid the whole apple ecosystem easily. That's not true for google. If you cannot see that then there's not point to continue the discussion.
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.
> and no matter how abusive apple is, they are not monopoly on a critical part of human being's daily life.
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.
Can we talk about the mating habits of spotted owls in Nebraska instead? I think it's more relevant to the topic at hand.
You say that like we can't walk and chew gum at the same time.
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.
No, we can't. Talking about apple's monopoly without goolge's is hypocrisy.
I'm not sure why JIT is okay on desktop, but not okay on mobile. Is the desktop any less important than mobile? Does Apple not care if JIT is used to exploit desktop computers? My mobile phone is way more likely to get lost or stolen than any other device I own, so I don't keep anything of value on it. I simply don't worry about JIT exploiting it as much as I do someone at a coffee shop walking away with it.
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.
Somewhat more money per device - per legal filings, only about 60% of searches go through access points governed by that agreement.
They do it because Apple has the highest paid group of people online within their ecosystems and it’s interesting that Google was only able to get a measly $1 billion refund on that $20 billion they probably thought they had leverage just like OpenAI who also thought they had leverage and they walked away with even less they got nothing.
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
> 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.
Why not make a open source + open foundation browser exemption - like for Firefox ? The all time vulnerability count for Safari is also pretty high so your position doesn't quite make sense. And AFAIK, Apple has never stated your position knowing that basic math would invalidate it.
Control, Why would they want to have clone Mac’s that was tried by a bean counter, CEO. It failed spectacularly.
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.
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?
A large part is to hinder PWA capabilities on iOS, having equivalent PWA support to Android would drastically impact App Store revenue.
M6 and M7 processors don’t come cheap. nor do paying for five ecosystems.
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.
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.
Meanwhile mozilla cancelled their PWA support for desktop. :( I was hoping PWA would help end electron bloat.
Safari desktop, however, even lets me wrap web apps like Slack that weren't coded to support PWA.
Firefox dropping desktop PWA was a catalyst for my switch to Brave across desktop and mobile.
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.
Those failures don't account for what exactly they are failing on.
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
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
> For others, here's the real truth of the matter: https://infrequently.org/series/browser-choice-must-matter/
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".
Control and the fact that no one cared before they got big, like the birth of the M1 or Apple Pay which only exist because the other pay systems couldn’t be bothered at the time to support Apple devices.
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.
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?
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 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.
It’s not the default, it just has a position along with several others that you can choose from.
They would have to expose parts of the OS that they like to keep close.
They were always extreme in market manipulation anti-competitive and lock-in behavior like that, as long as they thought they could get away with it, damaging the competition with impunity.
Browsers in iOS is just one of the most infamous examples, but they do it all over the place.
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.
You need to look at wBlock. Free and it works on macOS and iOS. Also includes SponsorBlock so can watch youtube videos on Safari too.
Just FYI, Orion supports extensions. Both Orion and Brave also have native adblocking supporting arbitrary filter-lists that perform dynamic JS blocking.
> SponsorBlock, how are you running that?
This is literally available in the app store, if you choose not to use Brave / Orion.
You can run uBO with Orion browser (Apple doesn't allow swapping browser engines, but they do allow network filtering and editing webpages/running scripts)
SponsorBlock has an officially supported iOS app (or you can use Orion browser)
Just installed Orion and uBO + SponsorBlock seem to work. Thanks.
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!
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?
My interpretation was more like: One of the conditions requires us not to disclose [information Apple hasn't publicly disclosed] related to the project -- so essentially the Firefox team is having difficulties beyond what they mention here, but they can't mention them here because Apple hasn't mentioned them publicly. Presumably, it's something about the root cause of the prohibition on an engine swap in the existing app. I assume it's not merely the region-targeting (since TFA says "Apple began allowing alternative browser engines on iOS in the EU") but perhaps the PWA/WASM stuff as discussed in other comments here.
If anti-monopoly regulators were serious, they would require OS vendors to provide a toggle for "let me install software from anywhere I damn well please with zero interference".
The fact that they have not suggests that these regulations are performative.
>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.
Perhaps this view is much less popular than you may think? For example, despite being a technie, I would campaign against that with all my might, write letters, and shout from the highest rooftops I could find. When I buy a locked down device, I buy it precisely for that. And no "just don't toggle the toggle" does not work, just like "just don't download viruses" did not work in the 2000s. I need a device that my grandmother CANNOT misuse, not even when a very patient scammer on the phone walking her through it.
The solution to this problem looks something like Windows S mode combined with an account managed by a family member. Once enrolled, the account manager has to approve an exit from the restricted mode.
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.
> Gecko is at 5%
Apple doesn't let you use it on iOS, so that cuts out a slice.
Gecko would get just 5% of those 15% at most, but Chrome would get up to 95%. So basically Safari is just protecting us from further Chrome monopoly.
Apple could choose to selectively allow Gecko as an alternative while rejecting Chrome's rendering engine.
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/#:~...
Safari can remain a preinstalled default without preventing me from using my preferred Firefox browser. There is no excuse whatsoever.
the greater the wealth the bigger the crime
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..
I’ve been quite happy with Kagi and their extension works really well (ie it’s invisible)
I definitely notice the redirects from duckduckgo every so often.
> 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!
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
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."
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.
> Safari and iOS support an extremely limited set of "app" APIs.
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.
https://pwascore.com/ chrome 97, firefox and(!) safari 89
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.
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.
What would the grounds for the lawsuit be? Are they breaking any specific laws?
If using a non-Webkit browser is so important to you, there are alternative devices.
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.
The whole article is about how they are practically still not letting any other browser engines, despite the law.
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!
I don't like Apple, and maybe you were just using the slippery slope argument. But let's be clear: your apps don't get disabled when you travel in a country where they're not available.
Yes, they do. Apple will disable EU-related features after you're 30 days outside the EU, including app updates. You also will not be able to restore them, if you break your phone on a trip and buy a replacement.
If Apple were a country it would be an authoritarian state, that's for sure.
And border Google.
It always surprises me that Apple is so popular on HN, considering HN's widespread hatred for close ecosystems.
But I suppose I'm just committing the Goomba Fallacy.
https://en.wiktionary.org/wiki/Goomba_fallacy
Controlled opposition is no competition.
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.
You can remove most iOS default apps.
And Orion browser has built-in adblock, AND supports firefox extensions, on all Apple OSes.
Orion is WebKit and doesn't really support extensions, only a small subset of them (case in adblock point - no ublock origin)
I think you can hide, but not remove apps like music, so bloat is not gone
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.
"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.
Why do people who ask such questions keep on spending money on the fruit factory in the full knowledge that they'll do their best to extract as much extra money from them as feasible? Just... stop giving them money? There's plenty of alternatives, some almost as restricted and getting even more so - Google, looking at your future plans - and some doing their best to keep a balance between 'security' and the freedom to tinker. Get one of those, new or used, do with it what you want - from just using it as it comes to writing your own OS and anything in between - and leave the fruit to ferment on the vine.
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.
EU already held back some fines. Not just Apple fingers, other big tech as well, especially social media corps. And not just EU.
Sounds like a poor reason to downvote.
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'
Hm, perhaps antimonopoly branches of governments should fine companies for monopolistic behavior in other countries. Because clearly that behavior harms customers in their jurisdictions.
There should be a better competition law enforcement so Apple couldn't get away with these shenanigans. They should be very heavily fined until they comply.
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?
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.
Most Apple haters online do not have or want to use Apple products. They just hate that the products exist and people use them willingly.
It would be your bank or hospital causing you harm in this case. Not another user that wants to use a different browser.
Your fear is completely irrational, no bank or hospital is going to target Chrome only on iOS because 99% of the user base will stick to the default of Safari. Or you will use their app. Or (oh no!) you might have to install Chrome for a few sites.
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.
Blaming fellow users for 1) the reality of network effects and 2) the laziness of the third parties that you patronize, is a strange approach.