Mozilla says Apple’s conditions for alternative browser engines on iOS remain unworkable, despite rules in the EU and Japan intended to open the platform. The practical obstacle, Mozilla argues, is that bringing Firefox’s Gecko engine to iPhone users would require a separate app and a manual move of their bookmarks, passwords and history.
Mozilla Watch analysis
What happened
In a post published on 20 November, Mozilla says no developer has launched a non-WebKit browser on iOS under the alternative-engine arrangements in the EU and Japan. The company says it has spent years trying to meet Apple’s conditions, with little success.
Mozilla’s example is the user migration it says would be required: Firefox could not simply add Gecko to its existing iPhone app. Users would have to download a second Firefox and transfer their data themselves. Mozilla argues that the friction could cause many to give up, including people who chose Firefox through the EU’s browser-choice screen. These are Mozilla’s account and assessment of the rules.
Why it matters
Allowing a rival browser engine on paper does not necessarily make it practical to use one. If users face a separate app and a manual migration, the policy may offer less meaningful choice than its headline promise suggests.
Mozilla’s post is also an interested party’s case. It explains why the company says it has not shipped Gecko on iOS, but the supplied account does not include Apple’s response or establish how Apple would answer Mozilla’s criticism.
Our read
The sharpest point is not the familiar argument over who gets to set the rules. It is the gap between permission and a usable alternative. A choice that asks people to rebuild their browser life by hand is a choice with rather a lot of fine print.
Mozilla’s argument deserves scrutiny, but the useful test is practical: can a developer launch a competing engine without imposing a migration burden users will reject?
What to watch
- Whether Apple changes the conditions for alternative engines in the EU or Japan.
- Whether Mozilla or another developer ships a non-WebKit browser for iOS.
- How Apple responds to Mozilla’s account of the technical and user-migration requirements. Activity teaser Mozilla says Apple’s rules have not yet produced a non-WebKit browser on iOS in the EU or Japan. The company says it would need to launch a separate Firefox app and ask users to move their data by hand. That is a substantial hurdle for a policy meant to make room for alternatives. Is a platform genuinely open if the alternative is allowed but awkward to adopt?
Discussion spark: Should rules for alternative browser engines require a smooth path for existing users, or is it fair to leave migration friction to the competing browser maker?
Sources and evidence
- Why there are still no non-WebKit browsers on iOS (20 November 2026, 14:03 UTC)
Independent WittyWires tracker for public updates about Mozilla. Not affiliated with or endorsed by Mozilla; this is not an official account.