A (Very) Early Look at Mozilla’s Boot2Gecko Mobile OS

When I got the news that Mozilla was planning to enter the Mobile OS battlefield, I have to admit that I was shocked. Mozilla does not seem like the organization that would be interested in the mobile space that Apple and Google have so spectacularly dominated. However, what really turned my head was when Mozilla boasted that its new mobile OS, coined Boot2Gecko, would be built entirely from Web technologies.

The Preview

A few days ago, being the curious developer I am, I checked out the Boot2Gecko repository on GitHub, where all the work is being done on Mozilla’s newest endeavor.  I was interested to see what it had gotten done so far, and was even more intrigued when I read on the Boot2Gecko MozillaWiki page that the OS would not be based on Android:

B2G uses some of the same low-level building blocks used in Android (Linux kernel, libusb, etc.) in order to reduce the burden on ODMs/OEMs to bring up B2G on new hardware. However, B2G is not based on Android, and will not be compatible with the Android stack (in particular B2G will not run Android applications).

With that statement in mind, I combed through the top layer of the code repository. I had cloned the repository locally so that I might be able to give the OS a trial run in an emulator. When I went to build, however, things seemed eerily familiar.

A little background: I’ve done a tiny bit of work with custom Android ROMs in the past, contributing a few things to the CyanogenMod project. Suffice it to say, I know my way around Android and its build system.

With that said, when I went to build Boot2Gecko, I learned that what Mozilla had done was literally this: clone the Gingerbread branch of the AOSP code repositories and proceeded to begin stripping it of its Android-specific layers. I was a bit thrown off by this, since the wiki page had said that Boot2Gecko wouldn’t be based on Android, but then understood what it meant: Android has already established a stable build environment as well as a stable mobile Linux environment from which Boot2Gecko can be bootstrapped. Boot2Gecko uses the close-to-the-hardware system components Android is built on. But rather than boot into a Dalvik runtime (Google’s implementation of the Java VM for mobile devices) and the rest of the Android platform, Boot2Gecko instead replaces Dalvik in favor of Gecko, Mozilla’s layout engine that powers its browser, Firefox. From there, Boot2Gecko loads Gaia, Mozilla’s mobile user experience built entirely from Web technologies powered by Gecko.

A (Very) Early Look at Mozilla's Boot2Gecko Mobile OSA (Very) Early Look at Mozilla's Boot2Gecko Mobile OS

After this, I went ahead and built an emulator image as I was eager to take Boot2Gecko for a spin (or what is ready to be spun, that is). The emulator image boots via Android’s QEMU port — no surprises there. I was greeted with a familiar lock screen, which (after a bit of bumbling with my fingers) I figured out had to be swiped upwards in order to unlock. The pull-down notification area from Android seems to still be intact, and there is no telling whether Mozilla will keep this scheme or not. I was then presented with the home screen application, full of icons that reminded me somewhat of Chrome’s new tab page. I tried my best to maneuver around the incredible amount of lag present (most likely due to the fact that it was being run on an emulator; you’d better blame me for being too lazy to port it over to my phone).

A (Very) Early Look at Mozilla's Boot2Gecko Mobile OSA (Very) Early Look at Mozilla's Boot2Gecko Mobile OS

All the basic applications are there, so Mozilla seems to be ready for prime time (at least as far as Gaia goes). All that appears to be left is some polish to the UI, implementing the rest of the system backend, and getting OEMs to build devices that run it.

I have to admit, what Mozilla has done so far is pretty nice. Even nicer when you remember that the slick UI you are seeing is done entirely in HTML, CSS, and JavaScript. I think it is pretty clear that I was eager to see where Mozilla is planning to take this going forward.

The Outlook

Okay, so Mozilla has begun developing its own mobile OS. I hate to say it, but I think that is the easy part for the company. What lies ahead is the tough stuff: getting the OS onto devices and into consumers’ hands. Mozilla seems to be doing all right on this front so far; it has got Boot2Gecko successfully running on the Samsung Galaxy S II, and there are strong rumors suggesting that a Boot2Gecko-flavored phone is in the works over at LG.

So, if Mozilla manages to get its foot in the door with Boot2Gecko (which it seems likely), the next issue is getting developers interested in the platform to create applications. The amusing part is this: Both Apple and Google worked hard to convince developers to learn their platforms filled to the brim with gigantic APIs and design patterns. Meanwhile, all Mozilla has to do is get Web developers to ensure that their existing Web apps can scale down to a mobile level. Plus, getting new developers to sign on with the platform should be simple, as I think it is safe to say Web development is one of the first things people learn when they begin a development career. Getting developers who know the platform (HTML, CSS, and JavaScript) and are able to build awesome applications should be a piece of cake.

The two issues I see Mozilla having a difficult time with are as such: patents and the end-user. First off, we all know that the mobile OS landscape is on fire at the moment, what with all the mud-slinging and name-calling back and forth between the big players, whining about each other breaking patents and such. While we can hope that this silliness comes to an end, I don’t think Mozilla, a non-profit organization, would stand a very good chance against a corporation like Apple that has billions upon billions of dollars in the bank. Second, Mozilla must, in the end, win over the consumer if Boot2Gecko is to succeed. It did well in that aspect with Firefox, but that was really only because the only alternative was Internet Explorer (’nuff said there). So how Mozilla will differentiate Boot2Gecko from Android or iOS in the user’s mind, I don’t know, but I wholeheartedly hope for the best.

The UI is slick, it’s built on the Web, and it even has a dedicated device already in the works. Boot2Gecko seems to be off to a smashing start, but can it take this excitement all the way to the big leagues and go toe to toe with Google and Apple? We can only wait and see as Boot2Gecko evolves, matures, and steals our hearts.

In the meantime, keep a close eye on Mozilla’s official product page for Boot2Gecko.

Article Written by

  • Matthew Cheung

    Looks pretty cool :)

  • MatthewSabia

    This actually looks pretty nice. I hope it’s more complete and simple than Android. But, the name has to go lol

    • http://twitter.com/lhamil64 Lee

      I agree, especially about the name. If I were to get a Boot2Gecko phone and someone asks what kind of phone I have, I wouldn’t want to say “Oh, it’s a Boot2Gecko phone!” I could see a lot of people calling it a Mozilla phone (they already call Firefox Mozilla which annoys me so much).

      • Pizik Spaeth

         I would expect it will just be known as a Gecko.

        • http://twitter.com/x_rus_x Vitaliy Anonymous

           It’ll confuse people, or the search engine. Basically it will just be a whole mess. Name vs browser engine.

    • RaterKey

      It is a totally different concept to Android, it is the Chromebook of the phone world.If anything it is less complete. For now! Much like the Chrome OS Boot2Gecko is a OS whose UI is a Web browser.I suspect the world isn’t quite ready for a “cloud phone” yet. Eventually it may be fantastic! But for now I suspect you are better off with an Android or iOS device.

       

  • LewiHussey

    I hope they make their own handsets.. id hate to see it being opensource =/

    • bob

       It is made by mozilla so it will be opensource.

    • RaterKey

      The rumour is that LG is working on a phone. And there’s no question about it, it will be open source!
      It isn’t a bad thing you know…

      • One

         Not “will be”, it is open-source. Didn’t you read the article?

    • swattz101

      What is wrong with opensource? It doesn’t keep them from creating their own base modle and alliwsthe community to contribute. The only problem I see is the possible fragmentation we see with Android. But it allows for multiple devices at multiple price points.

      Besides, as already pointed out, B2G is already opensource, so it’s a moot point.

  • Eli Jones

    This is exactly the kind of thing I’m talking about when I say that there’s so much evidence that OEMs really don’t like Android vis-a-vis dealing with Google about it. Customers only like cheap and useful smartphones, a very small % of them care if it’s made by Google.

  • http://it-it.facebook.com/people/Enrico-Casini/657033234 Enrico Casini

    It’s gonna fail miserably.

    • http://twitter.com/x_rus_x Vitaliy Anonymous

       Ah, quit trollin. People like you are the reason it fails. If every single person here in America relies on other people to have a mobile OS be popular, it will never be.

  • John_Westra

    #OpenSource OS + Open (Unlocked) HW  + Legislation prohibiting carriers from refusing to activate compatible HW on their networks = HUGE #Mobile #Mozilla Win.  Remove any part of this equation and you get #EpicFail

  • http://twitter.com/corporatethief corporatethief

    congrats you got your first visitor from ireland on your analytics page ! its not None anymore for Ireland

  • http://www.about.me/AngeloGopaul Eingoluq

    Firefox’s Mobile UI looks awesome.. but shows some signs of #Microsoft’s #Metro
    Its like what #Modernism is to #Post-Modernism.

  • Abel Luna

    I saw Boot2Gecko in action on the Galaxy S II, and unfortunately I saw that infamous Android lag when flipping screens. I hope they get rid of that and focus processor priority to the GUI.

    • http://eddieringle.com Eddie Ringle

      Like I said before, B2G was initiated from a clone of the Gingerbread (2.3) branch of the AOSP repositories. This “infamous Android lag” was present then, but I can assure you it’s barely ever present on ICS (or even Honeycomb), as full hardware-acceleration is pushed now.

      • http://chris.pirillo.com/ Chris Pirillo

        They still haven’t addressed it at the root level. “Fixing it” with faster hardware is a bad solution. ;)

        • http://www.cerebrux.net/ Salih Emin

           True, they just know that hardware will eventually will fix this problem because mobile HW is getting faster and more powerful every other quarter of year ;)

        • http://eddieringle.com Eddie Ringle

          No, they “fixed it” by enabling full hardware-acceleration. ;)

          For example, on Gingerbread I notice a bit of lag on my G2, but after upgrading to ICS I can definitely tell there have been massive changes occurring under the surface.

  • http://twitter.com/ashipod13 ashley isbitt

    this has the feel of wp7 (by the looks of it) 
    it has the intuitiveness of ios

    this might just beat all other os’s