Why there are still no non-WebKit browsers on iOS
Source Entity
Hacker News

Mozilla reports significant growth for Firefox on iOS in the EU following the Digital Markets Act. However, Apple's requirement that all iOS browsers use its WebKit engine continues to limit Firefox's full functionality.
The Browser Engine Standoff: iOS and the WebKit Mandate
The Shift in the European Market
Since the implementation of the European Union’s Digital Markets Act (DMA) in 2024, the landscape for mobile browsing has undergone a significant shift. By mandating that Apple allow users to select their preferred default browser, the EU has empowered consumers to move away from Safari. Mozilla has reported that Firefox usage on iOS has doubled in this region, signaling a clear consumer appetite for choice and alternative browsing experiences that were previously stifled by platform gatekeeping.
The Technical Bottleneck of WebKit
Despite these gains in user adoption, a critical technical hurdle remains: Apple’s long-standing policy requiring all browsers on iOS to utilize the WebKit engine. While this restriction is ostensibly framed around security and performance consistency, it effectively creates a 'walled garden' where third-party browsers like Firefox are essentially just skins over Apple’s proprietary technology. This prevents developers from deploying their own unique engines—such as Mozilla’s Gecko—which are essential for delivering a consistent cross-platform experience.
Feature Parity and Platform Constraints
For developers at Mozilla, the WebKit mandate is more than a policy grievance; it is a direct impediment to functionality. Because many of Firefox’s advanced features, security protocols, and privacy-focused tools are deeply integrated into the Gecko engine, they cannot be easily ported to the WebKit framework. Consequently, iPhone users are currently unable to access the full suite of capabilities that Firefox provides on other operating systems, including macOS, where Apple does not impose such engine-level restrictions.
Historical Context and OS Parity
It is important to note that Apple’s restriction on browser engines is a unique anomaly in the modern computing landscape. On almost every other major operating system—including Windows, Android, Linux, and even Apple’s own macOS—browser developers are free to innovate using their preferred engines. This historical divergence on iOS highlights a deliberate choice by Apple to maintain control over the rendering layer of the mobile web, effectively limiting the scope of competition in a space where browser engines serve as the foundation for the internet experience.
Implications for Future Competition
As the EU continues to monitor the compliance of 'gatekeeper' companies under the DMA, the debate over browser engines is likely to intensify. If Apple is forced to relax its WebKit mandate, it would represent a monumental change for mobile web development, allowing browsers to offer genuine performance and feature differentiation. Conversely, if the status quo holds, the gap between the 'open' web on desktop and the 'controlled' web on iOS will continue to frustrate both developers and users who prioritize platform-independent browsing tools.