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
Kev Needham / Mozilla Add-ons Blog :
Context & Ripple Effects
This announcement opens the most consequential restructuring of Firefox's add-on platform in its history: Kev Needham's post commits Mozilla to a new API designed for easy ports from other browsers, and sets a 12-18 month clock on deprecating the classes of add-ons that depended on deep, privileged hooks into the browser. It lands amid a broader Mozilla campaign to shed legacy surface area — weeks later came the plan to drop NPAPI plugins by end of 2016 (keeping Flash alone), and by 2017 the Aurora release channel was phased out entirely.
What makes the move matter is where it leads: the new API becomes the foundation for Mozilla's WebExtensions work, which by 2019 Mozilla would steer independently of Google's implementation rather than follow it on ad-blocker-affecting changes — and eventually carries into opening Firefox extensions on Android with hundreds at launch.
First-order effects
- Developers of the deprecated classes of Firefox add-ons face a hard deadline: rebuild on the new API or lose their users when support ends 12-18 months out.
- Developers targeting multiple browsers get a materially cheaper path — an extension written against the new API ports to Firefox without maintaining a separate codebase.
Second-order effects
- Chrome's extension ecosystem effectively gains a second distribution target, since Firefox now accepts near-drop-in ports; Mozilla trades ecosystem lock-in for catalog depth.
- Add-on authors who built businesses or workflows on Firefox's uniquely powerful legacy APIs become the constituency pushing back hardest during the transition window.
Third-order effects
- If the pattern holds, browser extension platforms converge on one shared API shape — which hands whoever defines that shape (Google, in practice) outsized influence over what all browsers' add-ons can do, forcing Mozilla into a permanent posture of diverging where its values demand it, as it later did on Manifest v3.
The trend: Browsers are converging on a single cross-vendor extension model, with Mozilla swapping its bespoke add-on stack for interoperability while reserving the right to diverge from Chromium's implementation.