Policy & Community

Mozilla reports failure of alternative browser engines on iOS despite EU and Japan regulations

Key Takeaway

Apple's compliance conditions for the Digital Markets Act have prevented any developer from successfully launching a non-WebKit browser engine on iOS.

Summary

Mozilla has released a detailed critique explaining why alternative browser engines have failed to appear on iOS despite regulatory mandates in the EU and Japan. While the Digital Markets Act (DMA) theoretically allows developers to bypass Apple's WebKit requirement, the specific conditions imposed by Apple have proven unworkable for independent projects.

Mozilla highlights that these restrictions prevent the deployment of the Gecko engine on mobile devices. Currently, Firefox on iOS remains a WebKit-based wrapper rather than a full Gecko implementation. The company argues that the current regulatory environment creates a 'trap door' rather than a level playing field for independent software developers.

Technical and regulatory barriers to Gecko on iOS

  • Engine Restriction: Apple currently mandates that all iOS browsers use the WebKit engine, preventing the use of independent engines like Gecko or Blink.
  • Implementation Obstacles: Compliance rules prevent developers from simply updating existing apps; instead, they would be forced to release entirely separate applications to host a new engine.
  • Data Migration Friction: The current regulatory framework would require users to manually migrate bookmarks, passwords, and history between different app installations, creating significant user friction.
  • Information Constraints: Apple's conditions include restrictions on disclosing non-public project information, which complicates the development and testing of alternative engine implementations.

Why it matters

This situation limits the diversity of the mobile web ecosystem and prevents users from accessing the full feature sets of independent browsers. For open-source developers, it demonstrates that legislative wins like the DMA may be neutralized by platform-specific technical and administrative compliance requirements.

Original reference: blog.mozilla.org →