AI
Mozilla Says Apple’s Conditions Still Prevent Non-WebKit Browsers on iOS
Mozilla writes that although Apple has allowed alternative browser engines on iOS after the EU DMA and Japan has made similar demands, no developer has launched a non-WebKit browser in nearly three years. Mozilla says Apple’s conditions are impractical, especially the requirement to build a separate standalone Firefox and have users manually migrate data, creating unacceptable friction.
The article says Firefox for iPhone is growing rapidly worldwide. Since 2024, the EU has required Apple under the Digital Markets Act to let users choose a default browser, and millions have chosen Firefox, with daily usage on iOS doubling. But Apple still requires all browsers on iOS to be built on its own browser engine.
Mozilla says this prevents many Firefox features that depend on the Gecko engine from being fully brought to iPhone. iPhone and iPad are the only major platforms with this restriction; on other major operating systems, including macOS, users can use the Gecko version of Firefox.
After the DMA took effect, Apple began allowing alternative engines in the EU but imposed a series of conditions; after Japan’s new rules, Apple also adopted similar conditions. Mozilla says nearly three years after the EU conditions were introduced and nearly one year after Japan’s, no developer has been able to release a non-WebKit iOS browser because the conditions are impractical in reality.
The article gives the example that Mozilla cannot directly update the Firefox users have installed, but must build a second, standalone Firefox app and then ask users to download it, manually migrate bookmarks, passwords, and history, and switch. Mozilla argues that Apple’s own apps would not accept this kind of friction, and that formal openness is more like trapping independent browsers. It says it will continue pushing for a genuinely fair competitive environment.