Mozilla says Apple’s conditions for running independent browser engines on iPhones remain impractical, leaving users without a non-WebKit browser nearly three years after the company introduced an alternative-engine pathway in the European Union.
Browsers distributed on iOS have historically been required to use Apple’s WebKit engine, even when their desktop counterparts use different technology. Firefox uses Mozilla’s Gecko engine on other major operating systems, including macOS, but the iPhone version cannot deliver the full engine-level capabilities of desktop Firefox under the general iOS rules.
Apple began permitting alternative engines in the EU in response to the Digital Markets Act. Japan later adopted rules requiring similar access, and Apple established conditions there that Mozilla describes as closely resembling the European framework. According to Mozilla, no developer has yet launched a non-WebKit iOS browser through either opening.
The dispute is now centered less on whether Apple formally permits another engine and more on whether a browser maker can use that permission in a viable product. Mozilla says it cannot simply update the Firefox application already installed by users to replace WebKit with Gecko. Instead, it would have to distribute a separate application and ask existing users to download it, transfer bookmarks, passwords and history, then manually change browsers.
That migration process would impose substantial friction on people who have already chosen Firefox, Mozilla argues. It would also split development and distribution between two iOS applications, complicating the effort to bring engine-specific features to users. Mozilla says it has worked privately to test and improve Apple’s terms, but those discussions have not produced conditions under which it can launch Gecko on iOS.
The organization’s complaint arrives as Firefox usage on iPhone is increasing. Mozilla says daily iOS use in the EU has doubled since 2024 and that millions of users have selected Firefox, aided by rules requiring Apple to offer browser choice. Those figures show that a choice screen can influence which browser application people use, while the underlying engine restriction still determines much of what that browser can do.
Browser engines interpret web code and provide many of the security, performance and feature foundations exposed through a browser. Mozilla describes Gecko as the last major engine not developed by a large technology company, making engine access an issue of both product competition and technical diversity on the web.
Mozilla says it will continue pressing for revised conditions. Its position is that regulatory compliance should be measured by whether competitors can actually ship an alternative engine, rather than by the existence of a formal entitlement that no browser developer has successfully used. The absence of a launched non-WebKit browser, it argues, is the clearest evidence that the present framework has not delivered the intended result.



