> 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
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.
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 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"
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.
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.
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).
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?
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.
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.
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!
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?
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.
Hm, perhaps antimonopoly branches of governments should fine companies for monopolistic behavior in other countries. Because clearly that behavior harms customers in their jurisdictions.
Can't they provide a build through sideloading in an alternative app stores? I'm confused with what the technicals limitations of sideloading are and what Mozilla would preferably do.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations nor having to jump over arbitrary complicated hoops. I'd also add, it is a reason for why i still don't buy an iPad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
The limitations aren't technical. Apple does not want third party browsers on iOS so it is technically possible (in some regions, because they were forced to) but filled with hurdles to discourage anyone from trying.
I was under the impression you still need the entitlement from Apple for JIT, even when you publish to alternative app stores. The only way to get that entitlement is to go through Apple's process here for EU and Japan (or tethered workarounds that may be closed at any time)
Listen I don't understand the issue: You don't even want an iPad, so why the fuck do you care?
I do want an iPad. I like the fact that I can visit my hospital and my bank's websites on it.
I think if Chrome or Firefox were possible to be installed, then the bank and the hospital would eventually target chrome-only, thinking it would save them time or money.
Can you understand, for your mere preference, you might literally cause me and people like me harm?
No, I want an iPad, mostly for its hw, but i even could accomodate myself with iOS/iPadOS, but Safari is not my browser, i don't like it and i use Firefox since Firefox 1.0 and don't plan to change. What i don't like is having an artificial limitation over the most important apps on any modern device: the browser.
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
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.
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"
Yet…
But hacker news users won't do that because they complain about Apple not because they are close or monopoly, but they make squeezing money from web users a little bit harder
Chrome isn't exclusive to one platform, and conversely Android doesn't force you to use it across the entire operating system.
If Chrome is forcing Web standards even in places where no one wants them, the equal and opposite problem is that Safari has a long history of holding back Web standards that are inconvenient to them, and making the entire industry bend around them because their users don't have the option to just install something else.
Part of the problem is actually that Apple also won't really compete here. They want the vertically-integrated everything, and so WebKit everywhere other than their devices is a second class citizen. The support for its underlying stack anywhere else -- from Linux-based browsers like GNOME Web to runtimes like Bun using JavaScriptCore -- has come pretty much entirely from third parties, and there doesn't really seem to be any sort of toolkit analogous to the CEF that could be used to embed it into other applications.
If anything, the only viable effort to make WebKit available across platforms was Chrome.
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.
The sheer quantity of old school Flash's exploits were a recent memory when the policy was set.
> …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.
https://www.gov.uk/government/publications/mobile-ecosystems...
That sucks, for sure, but I don’t see why that stops the browser vendors. Like… why wouldn’t just release a second app and see how it performs?
Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/
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.
I wouldn't be surprised if Google will start attaching Firefox even on Android in favor of Chrome... the sole reason they probably didn't already do so is that they fear sanctions from the EU and other countries that have antitrust in place.
You need to be up-to-date if you're going to spew bullshit. Ask the AI first.
I'm confused about this part. Is there some sort of code signing requirement that wouldn't be available to the "original" Firefox iOS app?
The sentence after that explains what they mean. They would have to migrate users from the Firefox WebKit SKU to the Firefox Gecko SKU in the EU and migrate all the data from one SKU to the other, essentially a full browser migration.
But, is there a genuine ‘non-asshole’ reason for these continued Apple restrictions post the EU regulations?
This includes a long list of strict requirements, some of which are hypocritical because Apple itself doesn't follow them, e.g., "Prioritize resolving reported vulnerabilities with expedience, over new feature development" and "Most vulnerabilities should be resolved in 30 days".
One requirement that Mozilla mentions in their blog post: "Not sync any state (including cookies) between the Alternative Web Browser Engine App (EU) and any other app, even another app of the same developer, unless the user has explicitly given permission for state to be synced, either by signing into both the Alternative Web Browser Engine App (EU) and the other app, or through another mechanism of providing explicit permission"
> Use memory-safe programming languages, or features that improve memory safety within other languages, within the alternative web browser engine at a minimum for all code that processes web content;
This doesn't seem like a reasonable requirement. Webkit probably doesn't satisfy it.
If privacy and user control are hurdles for you, then your software will not make its way onto my hardware.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations nor having to jump over arbitrary complicated hoops. I'd also add, it is a reason for why i still don't buy an iPad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
I do want an iPad. I like the fact that I can visit my hospital and my bank's websites on it.
I think if Chrome or Firefox were possible to be installed, then the bank and the hospital would eventually target chrome-only, thinking it would save them time or money.
Can you understand, for your mere preference, you might literally cause me and people like me harm?
This isn't really meaningful for Mozilla, though.