Mozilla scraps Firefox's Windows Metro version, cites less than 1K active daily users for beta
Mozilla scraps Metro version of Firefox, citing low interest — After more than two years of work, Mozilla has scrapped its effort to build a Metro-specific version of Firefox for Windows 8 …
Context & Ripple Effects
Mozilla began building a Metro-specific Firefox in March 2012, once Microsoft agreed to let third-party browsers into Windows 8's touch-first shell, and shipped a first public preview that October. By February 2014 the build had reached touch-friendly beta status, so this week's cancellation closes out a two-year investment rather than an experiment.
The stated reason is stark: fewer than 1,000 active daily users on the beta. The pickup was unusually broad — TechCrunch, Ars Technica, The Register, The Next Web and others all carried the story on or about March 14 — reflecting how closely watchers read any sign of where Mozilla concentrates scarce resources. It lands in a week when Mozilla also confirmed handing its Persona authentication system to the community, even as it pushes Firefox OS outward through ZTE, Huawei and Alcatel handsets and a $25 Spreadtrum reference design.
First-order effects
- Windows 8 tablet and touchscreen users who want a non-Microsoft browser in the Metro environment are left with Internet Explorer there, since Mozilla will not ship a finished alternative.
- Mozilla's engineering effort shifts away from Metro toward Firefox OS, whose 2014 expansion plan — new partner devices, the low-cost reference design, and a planned interface overhaul — now competes for the same budget.
Second-order effects
- Microsoft gets its touch-first shell back as effectively an IE-only surface by default, weakening the 2012 concession that opened Metro to third-party browsers and lowering the incentive for Chrome or Opera to fund equivalent builds.
- Every browser vendor weighing a platform-specific variant now has a public data point — under 1,000 daily actives after two years — to justify declining similar porting work.
Third-order effects
- If the pattern holds, Mozilla consolidates around fewer fronts: side projects like Persona move to community maintenance while the organization bets on Firefox OS and core desktop, a portfolio-discipline model for nonprofit-funded software.
- Platform-specific browser forks look structurally fragile unless an ecosystem's user base justifies them early, pushing vendors toward adaptive single codebases rather than per-shell builds.
The trend: Browser makers are retreating from per-platform variants toward consolidated codebases, with Mozilla reallocating from Windows Metro to mobile via Firefox OS.