Static

Why there are still no non-WebKit browsers on iOS

First reported by Blog.mozilla ·

The signal ●○○○ Compiled by AI from Blog.mozilla and Hacker News
Why you might care

You cannot use Firefox's own browser engine, Gecko, on your iPhone, even if you choose Firefox as your default browser.

What happened

Despite regulatory changes in the EU and Japan designed to allow alternative browser engines on iOS, no third-party browser engine has been successfully launched on Apple's platform. Apple's Digital Markets Act (DMA) and similar Japanese regulations mandated that Apple allow users to choose default browsers and permit alternative engines. However, companies like Mozilla, which develops the Gecko engine used in Firefox, report that Apple's conditions for implementing these engines are unworkable. Mozilla highlights that Apple requires a separate app download and a complex manual migration process for users to switch to a non-WebKit browser, creating significant friction. These hurdles have prevented any developer from releasing a non-WebKit browser on iOS, nearly three years after the EU rules took effect and almost a year after Japan's similar legislation.

What it means

Apple's stringent conditions for implementing alternative browser engines on iOS, despite regulatory mandates, effectively block competition and maintain a de facto monopoly for its WebKit engine. This strategy undermines the intent of regulations like the DMA by creating user friction so high that adoption of alternative engines is practically impossible. The requirement for a completely separate app and a cumbersome manual switch for users to migrate data, passwords, and history presents an insurmountable barrier for most. Apple's approach ensures that users remain on its native engine, limiting choice and innovation within the iOS browser ecosystem.

The continued dominance of WebKit on iOS, enforced by Apple's restrictive implementation of regulatory requirements, signals a significant challenge for browser developers seeking to offer a differentiated experience. This situation impacts users by limiting access to features and performance enhancements unique to non-WebKit engines like Gecko. It also affects the broader browser market, as the iOS platform remains a critical distribution channel where true engine choice is absent. Future efforts to comply with such regulations will likely require direct intervention to address the specific user-experience hurdles imposed by platform owners.

AI-written summary. May contain errors.

Tech