Will Firefox OS change the face of smartphone operating systems?

by: Robert TriggsMay 7, 2013

Firefox OS fox phone logo

The jury is still out on whether Firefox OS poses a legitimate threat to the mobile OS status-quo; many are writing it off for simply being too late to the party and others are quietly rooting for their favorite browser developer. Whilst Android, or any other mobile OS for that matter, obviously isn’t going to be overtaken overnight, Firefox OS poses some interesting questions for the future of smartphone software.

As a big open-source fan I see bags of potential in the fledgling operating system, it’s something which I believe could be a big changer in the mobile OS space. So, let’s take an in-depth look at what Firefox OS brings to the table.

The Vision

Firefox OS isn’t aiming for top spot competition with the Galaxy S4, HTC One, Nexus 4, or the iPhone 5. Instead, Mozilla wants to replace the plethora of aging handsets which still populate emerging markets with cheap, Internet-connected smartphones. You have to admit that the memories of using the web on an old Sony Ericsson or flip-cover Motorola seem horribly clumsy by modern standards.

[quote qtext=”we bring web connectivity to people who cannot afford smartphones” qperson=”” qsource=”” qposition=”center”]

By making use of web standards such as CSS, HTML5, and Java, Firefox aims to put the web at your fingertips regardless of your means or budget. Mozilla has clearly taken some inspiration from Chrome OS, loading applications through web browser technologies rather than through the main OS. You could consider some something akin to a “compatibility layer,” where apps function independently of the operating system.

As always, open-source is at the core of what Firefox is aiming to do. Freeing developers from the restraints and demands placed on them by Apple and Microsoft, but without the fragmentation presented by Android.

[quote qtext=”We use completely open standards and there’s no proprietary software or technology involved.” qperson=”” qsource=”” qposition=”right”]

This opens the door for app developers to flock to the platform, and there are many already working in the HTML5 and Java space. This will no-doubt be a key factor in determining the success of Mozilla’s operating system.

For a complete view of what Firefox OS aims to achieve, Darcy LaCouvee’s first look at Firefox OS is worth a watch:

[embed, width=”645″]http://www.youtube.com/watch?feature=player_embedded&v=7QnIskIc3EY[/embed]


Firefox’s greatest strength as a fledgling platform lies in its low price point for consumers and, just like Android, an absence of licensing costs for manufacturers. You may have heard that Firefox OS runs perfectly fine on just 256MB RAM and cheap 1GHz single-core CPUs – unlike Android Jelly Bean which requires at least 320MB RAM – which keeps compatible handsets cheap to manufacture.

The cheapest developer preview handset, named Keno, comes with a 1GHz Qualcomm Snapdragon S1 processor, 512MB RAM, with a 3.5-inch screen and support for common 3G networks. The price point; a very reasonable $119, and that was for the developer preview, the final version will likely ship with a little less memory to keep production costs down.

Geeksphone FirefoxOS handsets

The Geeksphone Keno and Peak developer handsets sold out in record time, suggesting that their’s strong interest in FireFox’s OS.

What’s more, these technologies continue to be produced at lower and lower costs as manufacturing processes improve and yields increase. So the price is expected to come down even more over the next year or two.


There’s tremendous potential for Firefox OS to capture a significant share of the budget market, providing that the hardware price is right. Of course Android software doesn’t cost manufacturers anything either, but Firefox’s appeal could come from a few of the projects finer details.

Firstly, as the interview put so elegantly:

[quote qtext=”(we) don’t have the problem that a very low end phone doesn’t get newer versions of the operating system” qperson=”” qsource=”” qposition=”center”]

By using web standards, new features can be easily implemented in much the same way as a Chrome, Firefox, or Safari browser update. This puts an end to the dreaded hardware fragmentation which plagues budget devices.

Android fragmented versions

This is a sight which Firefox OS users shouldn’t have to deal with; no more outdated versions or missing out on new features.

Secondly, as already mentioned, Firefox OS will run apps built from web-based languages like HTML5 or Java, which is the key to this flexibility. Essentially the idea is that, as long as your phone is good enough to run these web APIs you won’t have to worry so much about changes to your operating system or hardware specifications. Apps and features can be created and updated to work with existing web technologies, which aren’t particularly hardware- or OS-dependent.

There will obviously be performance differences between individual hardware setups, but, with low-end hardware, gaming or 3D apps aren’t too important. Instead, consumers are more interested in Internet and social functionality, rather than 4k video output.

Whilst it might seem problematic to base a handset around the web, especially when coverage can be temperamental, Firefox OS allows for app installations too. Your favourite apps will still work offline, which is massively important when it comes to roaming, and will even work with Android handsets too.

Currently, consumers in emerging markets are stuck with older Android handsets, many of them still on Gingerbread – some are on even older versions like Froyo – and even more limited OSs like Nokia’s Symbian. Many of these platforms are out of date, and some are no longer supported by app developers. With Jelly Bean or iOS features and compatible software out of reach, there’s room and a real need for cheap, internet accessable handsets.

Web applications, the way of the future?

This is where I feel Firefox OS has the potential for the biggest impact. As we’ve already discussed, Mozilla has the potential to capture a massive installation base and with it comes software developers eager to peddle their wares to a growing platform.

Picture, for a moment, your day to day smartphone uses. Chances are that your work needs consist of email checking, maybe an Office suite, and web access. Home use probably isn’t that different, Internet access for streaming video, email, social networking, you get the picture. Most of these activities take place, or could be done, using your browser, we only use dedicated apps because they are faster and usually a bit easier to use than mobile web pages.

Having said that, quite a few of us probably already use plenty of web pages which operate in the same way as a traditional application too, and have been gradually moving away from dedicated applications over the past few years. I’m currently typing this using Google Docs rather than Office, I’ve used web-based email clients for years, and I’m happily using Spotify for Chrome for music.

Chrome apps

Virtually everything you need can be accessed online these days.

We’ve already seen some more advanced uses of this sort of HTML5 development with Google’s Chrome OS, which now has large range of apps developed for its browser based platform. Firefox OS should be able to achieve a similar result, once multiple platforms begin using similar development standards it could start a change reaction which could attract even more developers.

The real benefit of a move towards an HTML5 or Java standard is that apps will be compatible across various operating systems, in the same way that websites work regardless of whether you’re viewing them on Android, iOS, or Windows. A change in focus like that would mark a pretty dramatic shift in software development, and would be a great benefit to developers and consumers alike.

  • Alex

    There one thing I would like to see here, is the way Mozilla is calling ISP/Operators attention. They will get full access to the OS, and we all know where to normally goes.. And I hear something about Stores blocked for each ISP.

  • ChromeDroid

    Seriously Chrome and Android need too merge. customers and developers will have the choice to pick from natively written apps and html5 apps, thus creating a platform thats the best of both worlds

  • Mike Bastable

    Roberts articles continue tot be the best on this site, comprehensive land not pandering to Android fanboys…explains the black of comments.
    Keep up the good work man

  • gargamel

    Actually, Symbian is more advanced and feature-rich as an OS than JB… true multitasking anyone?

    • Arsenal™

      symbian whaaaaat? :)

      • URNumber6

        gargamel is right. The S60 ui layer on Symbian was stale and fusty but underneath was a hugely powerful, functional OS.

    • Yeah, that’s why Nokia lost its handset sales lead. And not to mention, it keeps dropping :D.

      • URNumber6

        NOKIA only lost its smartphone sales lead after the CEO publicly deprecated Symbian.

        It keeps dropping now because they’re exclusively offering Windows Phone handsets which no manufacturer has succeeded with.

        • Bridget Arnelle

          The funny thing about the WP8 exclusive thing. There’s some budget phones they have planned that don’t have WP8 at all… So, I think Mr. Elop needs to get his head out of MS’ arse and figure out how to manage a business without Ballmer’s dis/approval. >:C

          Note: I do own a WP8 phone, but I think there’s more to a phone than it’s OS, it needs to be well built all around and affordable and I don’t see that with a WP8-only approach IMO.

  • chrisnof

    Nice article, thanks.
    However, it’s HTML, CSS and Javascript, not Java…

  • Arthur Vincent Simon

    This has potential since developers will have to worry less(or not at all) about fragmentation, making it easier to develops. Not to mention that almost every developer is already familiar with HTML5

    I also would like to see it available more in emerging markets earlier. I just wonder how they will market it though. Through a carrier? A distributor? dedicated store?

  • Anirudh

    Ohh So they Say “we bring web connectivity to people who cannot afford smartphones”

    So Firefox users might not have money to spend on smartphones but can pay for extra carrier data charges for using those web apps”

    • URNumber6

      You misunderstand web apps, they are built using web technologies (HTML/JS/CSS) but are cached (installed) locally. They will not incurr any more data charges than native apps doing the same job.

    • Bridget Arnelle

      Not exactly. It’ll be using the HTML 5 specs for local storage, which makes most web apps effectively local apps. What qualifies the ‘web’ part of web app here is the fact they’re written to run in a browser using HTML, CSS, JS (or NaCL and Rust), which makes the browser more or less an app engine at its heart.

      This is not to say this is a problem free approach. IMO it’s going to be a nasty experience when some web app developers begin to realize their apps are poorly designed to handle a wide variety of cases in hardware and network connectivity (bandwidth and latency). It’s sort of like how the early console games had to use hacks to work within very limited memory capacities like Metroid. It’ll be fun to see these Ruby and other web language kiddies learn how to manage memory without pointers. >:3

  • Marc Diethelm

    Seriously. It’s JavaScript, not Java. You’re talking about web frontend technologies here.

  • This is like chrome OS but on a phone. If i understand it.

  • dgarra

    I’ve never been a fan of Firefox so I’m cautiously optimistic on this one. Seems like it’d make more sense for Chromium to come to phones.

  • nishantsirohi123

    this is a good idea.

    why not have chrome os ported to a tablet

    with detachable keyboard

  • shadow

    The guy in the video is perfect for a firefox ambassador! :p

  • Bridget Arnelle

    Yeah, it’s JS, not Java. But the idea is that we’re looking for a way to get around kludges like AJAX to actually produce code that runs at approximately native compiled speeds which is what ASM.js (and NaCL in Chrome) aims to do. It’s meant to get rid of plugin architecture entirely (yay!) and focus on providing a seamless experience between a ‘web’ app running from a local storage location and a website which can update that app with new features, data, and etc. So, you don’t have to be tied to Google, Microsoft, or Amazon. You get to control your data once again. Open garden vs Walled Garden is what this is all about.