Firefox OS: Mozilla’s attempt to reinvent the mobile

Introduction

In the early years of the 2010s, Mozilla decided to bring its open-source philosophy and web standards to the world of smartphones. The result was Firefox OS, an operating system based entirely on HTML, CSS, and JavaScript technologies. Although the project never reached the market share of iOS or Android, it left an important mark on the conversation about what a mobile phone can be when built on the web.

What Was Firefox OS?

Firefox OS, initially known as Boot to Gecko (B2G), was a mobile platform that eliminated the traditional native application layer and replaced everything with web pages executed in the Gecko rendering engine. Each “app” was simply a website packaged with a manifest declaring permissions and capabilities. The system included a runtime called Gaia, which provided the user interface and basic services such as calls, messages, and contact management.

Main Features

  • Interface built entirely with HTML5, CSS3, and JavaScript.
  • Hardware access via standard WebAPI APIs (camera, GPS, sensors, etc.).
  • Security model based on granular permissions, similar to browser extensions.
  • OTA (over-the-air) updates managed directly from Mozilla’s servers.
  • Compatibility with any device capable of running the Gecko engine, allowing it to be tested on low‑cost hardware.

The Application Ecosystem

Instead of a traditional app store, Firefox OS featured Marketplace, a web catalog where developers could upload their packaged applications. Because apps were essentially web pages, the publishing process resembled uploading a site to a server: the code was packaged, a manifest added, and it was submitted for review. This lowered the barrier to entry for web developers and allowed the same applications to run, with few changes, in desktop browsers.

Reasons for Failure

  • Lack of significant support from hardware manufacturers, who preferred to invest in Android.
  • Inferior performance on low‑end devices, where the Gecko engine consumed more resources than optimized native solutions.
  • Fragmentation of WebAPIs, which were still being standardized and did not offer the same coverage as native SDKs.
  • Limited app ecosystem; many developers saw little incentive to create specific versions when they could target the standard mobile web.
  • Fierce competition from iOS and Android, which already had mature stores and large user bases.

Legacy and Lessons

Although Firefox OS was discontinued in 2016, its influence persists. The concepts of progressive web apps (PWAs) and the WebAPIs that Mozilla helped promote have found adoption in modern browsers. Moreover, the project demonstrated that it is possible to build a complete operating system using only open standards, an idea that continues to inspire initiatives like KaiOS and various experiments with web‑based systems.

This post is also available in ESPAÑOL.

Leave a Reply

Your email address will not be published. Required fields are marked *

Esta obra está bajo una Licencia Creative Commons Atribución 4.0 Internacional para Francesc Roig francesc@vivaldi.net .