为什么 iOS 上仍然没有非 WebKit 浏览器
Why there are still no non-WebKit browsers on iOS

原始链接: https://blog.mozilla.org/en/mozilla/internet-policy/apple-ios-browser-engine-rules/

Firefox 正在吸引更多 iPhone 用户,尤其是在欧盟,因为 DMA 允许人们选择默认浏览器。但 Apple 仍然强制所有 iOS 浏览器使用其自有引擎,阻止 Mozilla 将基于 Gecko 的 Firefox 完整地引入 iPhone。尽管欧盟和日本现在要求支持替代浏览器引擎,但 Apple 的条件不可行:没有任何开发者推出过非 WebKit 的 iOS 浏览器。Mozilla 表示无法简单更新现有 Firefox,必须创建独立应用并让用户手动迁移数据,造成巨大摩擦。Apple 对其施加的障碍比对其自有应用更为严格。Mozilla 继续推动公平竞争环境,以便 iPhone 用户能访问 Gecko——最后一个主要的独立浏览器引擎。

该帖讨论了 Mozilla 的博客文章,解释 iOS 为何仍缺乏非 WebKit 浏览器。Apple 仅在有限地区(欧盟/日本)允许替代浏览器引擎,且附带严格而沉重的规则:单独的应用构建、不同版本间无法同步数据/状态、非披露限制,以及地区资格检查。这使得全球版 Firefox 引擎不切实际,并可能导致用户数据碎片化。评论者争论 Apple 的动机——保护 App Store 收入、限制 PWA、维持控制,以及安全/JIT 担忧——与限制具有反竞争性、扼杀网络标准的主张。一些人指出 Safari 对 PWA 支持薄弱且更新缓慢;另一些人则为 Apple 的封闭模式辩护。用户提到像 Orion 或侧载 Gecko 浏览器这样的变通方法,以及 iOS 广告屏蔽限制。总体而言,监管压力尚未实现实用的第三方引擎,WebKit 在 iOS 上仍占主导。
相关文章

原文

Firefox on iPhone is growing fast across the world. This is especially true in the EU since 2024, when the EU Digital Markets Act (DMA) started requiring Apple to let people choose their default browser; millions have picked Firefox, and daily use on iOS has doubled. People want to choose the browser on their phone.

But there remains an important limitation to what is available on iPhones: Apple forces all browsers on iOS to be built on Apple’s own browser engine. 

This has meant that companies like Mozilla cannot easily bring the full range of Firefox features and functionality to iPhone users because many of these are built within our browser engine, Gecko. iPhones and iPads are unique in having this restriction. On all other major operating systems, including Apple’s macOS, people can access the Gecko-powered version of Firefox.

As a result of the DMA, Apple began allowing alternative browser engines on iOS in the EU. It published a set of conditions that companies like Mozilla must comply with to bring their own browser engine. At the time we said Apple’s rules made it “as painful as possible” for alternatives like Gecko. In the meantime, Japan also introduced new rules requiring alternative browser engines on iOS. Apple applied very similar conditions in Japan to those in the EU.    

Nearly three years since Apple introduced these conditions in the EU and almost a year since Japan, not one developer has been able to launch a non-WebKit browser on iOS. The reason is simple: Apple’s conditions remain unworkable. The real test of any rule is whether it delivers the change it was meant to achieve in practice. Compliance on paper alone falls short of that test.

Since the DMA came into effect we’ve been working behind the scenes to test and improve Apple’s conditions so that we can bring Gecko to iOS users. Those efforts have so far largely failed. 

One of the conditions requires us not to disclose non-public information related to the project, but here’s an example of what we are up against: to use Gecko, we can’t simply update the Firefox app people already use and love. We’d have to build a whole separate app, a second Firefox. Then we’d have to ask every Firefox user to download it, move their bookmarks, passwords and history across, and manually switch over, step by confusing step.

That’s a lot to ask of people who already made their choice. A significant proportion of people would understandably give up, including many who picked Firefox from the EU’s choice screen.  

The conditions Apple imposes, including a level of user friction Apple would never accept for its own apps, mean that the open door feels more like a trap door. 

Firefox users on iPhone chose an independent browser. They should get everything that comes with it, including Gecko, the last major browser engine not developed by a big tech company. We’ll keep pushing for a real level playing field, not an opening that drops independent browsers through the floor.

联系我们 contact @ memedata.com