Mozilla to introduce new API for Firefox to make it easier to port extensions from other browsers, to deprecate certain classes of add-ons 12-18 months from now
The Future of Developing Firefox Add-ons — Today we are announcing some major upcoming changes to Firefox add-ons.
Context & Ripple Effects
This announcement lands six weeks after Mozilla laid out its broader Firefox plans around partnerships, better add-ons, and faster updates — and the add-on piece is now concrete: a new API designed so extensions port easily from other browsers, plus a 12-18 month clock on deprecating certain classes of existing add-ons.
It is also part of a wider teardown of Firefox's legacy extension surface: weeks later Mozilla confirmed it would drop NPAPI plugin support by end of 2016, keeping only Flash, and by 2017 it was pruning channels too (retiring Aurora). The through-line is fewer bespoke Firefox-only technologies, more web-standard ones.
First-order effects
- Developers of the affected legacy add-on classes face a hard deadline: rebuild on the new API within 12-18 months or their products stop working in Firefox.
- Porting gets materially cheaper for developers whose extensions already target other browsers, lowering the cost of bringing those add-ons to Firefox.
Second-order effects
- Chrome-style extensions become easier to run on Firefox, which pressures Google's ecosystem: Firefox can absorb extensions built elsewhere, while Firefox-only add-on authors must compete against a larger incoming catalog.
- Add-on maintainers who skip the rewrite cede their user base, consolidating the Firefox extension market toward developers able to sustain cross-browser codebases.
Third-order effects
- If the pattern holds, browser extension platforms converge on one shared API model rather than per-browser ones — a convergence Mozilla itself later stress-tested when it chose to diverge from Google on Manifest v3 changes affecting ad blockers, showing that a common API still leaves room for implementation politics.
- Control over the extension API becomes the real gatekeeping layer: whoever shapes the spec decides what classes of add-ons (and business models) survive on the platform, echoing the same dynamic as the NPAPI phase-out.
The trend: Browsers are dismantling proprietary extension and plugin architectures in favor of standardized APIs, trading ecosystem uniqueness for cross-browser portability — and turning the API spec itself into the battleground.