Introduction
In the early years of the 2010's, Mozilla decided to bring his open source philosophy and web standards to the world of smartphones. The result was Firefox OS, a fully based operating system based on HTML, CSS and JavaScript technologies. Although the project never reached the market share of iOS or Android, it left an important footprint in the conversation about what a mobile can be when it is built on the web.
What was Firefox OS?
Firefox OS, initially known as Boot to Gecko (B2G), was a mobile platform that removed the traditional layer of native applications and replaced everything with web pages executed on a Gecko rendering engine. Each «app» was simply a website packed with a manifesto that declared permissions and capabilities. The system included an execution environment called Gaia, which provided the user interface and basic services such as calls, messages and contact management.
Main characteristics
- Interface built entirely with HTML5, CSS3 and JavaScript.
- Access to hardware using standard APIs WebAPI (camera, GPS, sensors, etc.).
- Security model based on granular permissions, similar to browser extensions.
- OTA (over-the-air) updates managed directly from Mozilla servers.
- Compatibility with any device that could run the Gecko engine, which allowed to test it on low-cost hardware.
The application ecosystem
Instead of a traditional application store, Firefox OS had Marketplace, a web catalog where developers could upload their packaged applications. Because the apps were essentially web pages, the publishing process was similar to that of uploading a site to a server: the code was packed, a manifesto was added and sent for review. This reduced the entry barrier for web developers and allowed the same applications to work, with few changes, on desktop browsers.
Reasons for failure
- Lack of significant support from hardware manufacturers, who preferred to invest in Android.
- Lower performance on low-end devices, where the Gecko engine consumed more resources than the native optimized solutions.
- Fragmentation of APIs WebAPI, which were still in the standardization phase and did not offer the same coverage as native SDK.
- Limited application ecosystem; many developers saw little incentive to create specific versions when they could target the standard mobile web.
- IOS and Android fierce competition, which already had mature shops and large user bases.
Legacy and lessons
Although Firefox OS was discontinued in 2016, its influence persists. The concepts of progressive web applications (PWAs) and the APIs WebAPI that Mozilla helped to boost have found adoption in modern browsers. In addition, the project demonstrated that it is possible to build a complete operating system using only open standards, an idea that continues to inspire initiatives such as KaiOS and various web-based system experiments.
