Backers Tout Firefox OS as Open Mobile Option
For all the excitement around mobile apps, they seem a step backward in one respect: they tie users to a particular operating system and devices that support it. The Web, by contrast, evolved so that content is experienced much the same way on any hardware.
Context & Ripple Effects
This is the moment Mozilla's mobile bet gets its public framing. The project began as Boot to Gecko, Mozilla's plan for a ChromeOS-style rival on phones announced in July 2011, and by July 2012 testers could run B2G nightly builds on desktop hardware. What is new in this piece is the argument rather than the code: backers position Firefox OS as the answer to a step backward they see in native apps, which tie users to one operating system and its supported devices, while the Web renders much the same experience on any hardware.
The pickup list — NYT Bits, AllThingsD, Phone Arena, Softpedia and others all running the story on or about September 8, 2012 — signals that the open-versus-native framing, not just another OS announcement, is what traveled.
First-order effects
- Developers gain a third targeting option: write to Web standards once and reach any Firefox OS handset, instead of maintaining separate builds per operating system and app-store gatekeeper.
- Hardware makers and carriers evaluating platforms get an OS whose differentiation rests on openness rather than on a proprietary ecosystem controlled by Apple or Google.
Second-order effects
- If hardware-agnostic Web apps prove good enough for everyday tasks, the app-store lock-in that anchors iOS and Android economics comes under direct argument — distribution could shift from curated stores to the open Web, where no single player collects the toll.
- Google faces a rhetorical problem: Android sells itself as open, so a genuinely open competitor forces the openness claim to be tested against nominal-versus-usable distinctions rather than taken on faith.
Third-order effects
- If the pattern holds, the operating system itself commoditizes: value migrates up the stack to whoever controls the runtime and discovery layer, echoing how the desktop Web eroded client-software moats in earlier cycles.
- Whether HTML5-class apps can match native performance and API access is the unresolved variable — the entire structural case rests on that gap closing, and nothing in the coverage at this date shows it has.
The trend: Mobile platform competition is shifting from device-and-appstore ecosystems toward a fight over whether the open Web can serve as the application layer itself.