20 Nov 2026

feedPlanet Mozilla

Mozilla Addons Blog: Unveiling the All-New Firefox Add-on Developer Hub

Sixteen years ago, Mozilla launched the add-ons developer hub to be a one-stop shop for Firefox extension and theme creators. While it served our community well for a long time, we knew it was time for a modern upgrade. Today, we're thrilled to announce a completely reimagined Firefox add-ons developer hub, rolling out this December.

At the start of 2026, we surveyed over a hundred Firefox add-on developers to learn about your biggest pain points. Your feedback was crystal clear: you wanted faster reviews, clearer guidelines, deeper insights into submission workflows, and better overall communication from Mozilla.

We took that feedback to heart when building the new developer hub, putting transparency, clarity, and communication at its core. With every submission, you'll see exactly where your version stands in the review process, what step comes next, and actionable advice if policy issues arise. Best of all, we will be integrating all communications right into the dashboard - no more digging through email threads! (Don't worry, you'll still get the emails)

Beyond workflow enhancements, we've streamlined navigation, unified messaging, and even added native dark mode support.

The preview release supports everything needed to submit and manage extensions in your default locale. We're actively building out additional features over the coming weeks, and you can seamlessly switch back to the classic hub at any point if you need legacy functionality.

Invitations to the preview release are rolling out gradually. When your account is invited, you'll see a "Try the new Developer Hub" link in the top navigation menu in the Developer Hub. Give it a spin and let us know what you think via the feedback link.

Happy developing!

The post Unveiling the All-New Firefox Add-on Developer Hub appeared first on Mozilla Add-ons Community Blog.

20 Nov 2026 5:21pm GMT

The Mozilla Blog: Why there are still no non-WebKit browsers on iOS

Firefox on iPhone is growing fast across the world. This is especially true in the EU since 2024, when the EU Digital Markets Act (DMA) started requiring Apple to let people choose their default browser; millions have picked Firefox, and daily use on iOS has doubled. People want to choose the browser on their phone.

But there remains an important limitation to what is available on iPhones: Apple forces all browsers on iOS to be built on Apple's own browser engine.

This has meant that companies like Mozilla cannot easily bring the full range of Firefox features and functionality to iPhone users because many of these are built within our browser engine, Gecko. iPhones and iPads are unique in having this restriction. On all other major operating systems, including Apple's macOS, people can access the Gecko-powered version of Firefox.

As a result of the DMA, Apple began allowing alternative browser engines on iOS in the EU. It published a set of conditions that companies like Mozilla must comply with to bring their own browser engine. At the time we said Apple's rules made it "as painful as possible" for alternatives like Gecko. In the meantime, Japan also introduced new rules requiring alternative browser engines on iOS. Apple applied very similar conditions in Japan to those in the EU.

Nearly three years since Apple introduced these conditions in the EU and almost a year since Japan, not one developer has been able to launch a non-WebKit browser on iOS. The reason is simple: Apple's conditions remain unworkable. The real test of any rule is whether it delivers the change it was meant to achieve in practice. Compliance on paper alone falls short of that test.

Since the DMA came into effect we've been working behind the scenes to test and improve Apple's conditions so that we can bring Gecko to iOS users. Those efforts have so far largely failed.

One of the conditions requires us not to disclose non-public information related to the project, but here's an example of what we are up against: to use Gecko, we can't simply update the Firefox app people already use and love. We'd have to build a whole separate app, a second Firefox. Then we'd have to ask every Firefox user to download it, move their bookmarks, passwords and history across, and manually switch over, step by confusing step.

That's a lot to ask of people who already made their choice. A significant proportion of people would understandably give up, including many who picked Firefox from the EU's choice screen.

The conditions Apple imposes, including a level of user friction Apple would never accept for its own apps, mean that the open door feels more like a trap door.

Firefox users on iPhone chose an independent browser. They should get everything that comes with it, including Gecko, the last major browser engine not developed by a big tech company. We'll keep pushing for a real level playing field, not an opening that drops independent browsers through the floor.

The post Why there are still no non-WebKit browsers on iOS appeared first on The Mozilla Blog.

20 Nov 2026 2:03pm GMT

19 Nov 2026

feedPlanet Mozilla

Firefox Tooling Announcements: Firefox MCP v0.11.0 released

New release of Firefox MCP. Available on npm at https://www.npmjs.com/package/@mozilla/firefox-mcp

Firefox DevTools MCP is now called Firefox MCP.
The npm package is now @mozilla/firefox-mcp, and the repository is now GitHub - mozilla/firefox-mcp: Model Context Protocol (MCP) server that lets AI agents browse the web and debug web pages with Firefox · GitHub. Existing setups keep working: the same build is still published as @mozilla/firefox-devtools-mcp.

External contributors authored half of the PRs released today, huge thanks to:

Added

Fixed

Changed

Full changelog: Release v0.11.0 · mozilla/firefox-mcp · GitHub
Repository and issues: GitHub - mozilla/firefox-mcp: Model Context Protocol (MCP) server that lets AI agents browse the web and debug web pages with Firefox · GitHub
Public chatroom: https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org

1 post - 1 participant

Read full topic

19 Nov 2026 10:57am GMT