Mozilla launched a new project last year called Boot2Gecko (B2G) with the aim of developing a mobile operating system. The platform's user interface and application stack will be built entirely with standards-based Web technologies and will run on top of Gecko, the HTML rendering engine used in the Firefox Web browser. The B2G project has advanced at a rapid pace this year and the platform is beginning to take shape.
The B2G team at Mozilla is preparing to give a demo of the platform's user experience at the upcoming Mobile World Congress (MWC) event. Mozilla's Brendan Eich told us via Twitter that the B2G project has already attracted partners, including one that is developing its own custom home screen. This suggests that multiple parties, possibly hardware vendors, are interested in adopting the platform.
According to a roadmap recently published by Mozilla, the B2G project could potentially reach the product stage by the second quarter of 2012. That's a highly ambitious target, but the project's impressive rate of development suggests that it can be done. The pervasive use of HTML and JavaScript to build the user interface and application stack is no doubt speeding the project along. Web technologies are very conducive to rapid development.
The B2G platform consists of three main layers. The bottom layer, which is called Gonk, includes the Linux kernel, the hardware abstraction layer, the telephony stack, and other low-level system components. The middle layer is the Gecko rendering engine, which has been improved with new APIs that expose device capabilities. The top layer is Gaia, the B2G user interface, which is built entirely with HTML and JavaScript.
The Linux kernel that is used in Gonk is said to be "reasonably close" to upstream Linux. According to Mozilla's documentation, Gonk uses some of the underlying bits of the Android open source project, including some minor kernel customizations, in order to make it easier for hardware vendors to get B2G running on Android hardware. B2G is not based on Android, however, and will not run Android applications. It's currently possible to replace the Android environment on a Samsung Galaxy S II with a B2G build.
Much of the interaction between the Gecko and Gonk layers will be mediated by a B2G process that runs with a high privilege level and acts as a sort of Gecko server. The B2G process will paint to the framebuffer and interact with hardware components like a built-in GPS antenna or camera.
The wireless modem functionality is implemented in a radio interface layer (RIL) daemon, which B2G will interact with through a simple proxy process. Actual Web content and multimedia playback will be handled by separate processes that communicate with the B2G process.
Mozilla aims to build the entire B2G user interface and application stack with native HTML and JavaScript. In order to accomplish that, Mozilla launched the WebAPI project, which exposes device functionality to Web content through JavaScript APIs. Mozilla has already previously introduced APIs for accessing certain device capabilities, such as the accelerometer and geolocation APIs that are supported in the mobile versions of Firefox.
The WebAPI project goes a step further and adds a great deal of additional functionality for tasks like taking pictures with the built-in camera, dialing the phone, accessing the device's battery level and status, sending and managing SMS messages, accessing the user's address book, and making a device vibrate. These capabilities are largely made accessible to Web content through a set of JavaScript APIs. This means that the B2G dialer interface, for example, is just a Web page that uses a JavaScript function to initiate a call.
Mozilla is working to standardize these APIs through the W3C Device APIs working group. In theory, the same underlying JavaScript APIs that are used to enable access to underlying platform features on B2G could eventually be supported natively in the default Web browsers that ship with other platforms.
The standardization effort around device APIs is especially significant. If the APIs gain widespread adoption, it would make it possible for large portions of the B2G user experience and application stack (which are, essentially, just Web content) to run in Web browsers on other platforms. At that heart of Mozilla's agenda for B2G is a vision of the future in which browser-based mobile applications, built with standards-based HTML and JavaScript, will be capable of doing everything that can be done today with the native mobile application development frameworks.
Because B2G's Gaia user interface layer is implemented in HTML and JavaScript, it can technically run in a regular desktop Web browser. Of course, the device-related capabilities will only work when the content is run in an environment that has WebAPI support.
We tested the Gaia home screen user interface and several of the platform's applications in a Firefox nightly build. All we had to do to get it running was download the code from the relevant GitHub repository and then open the homescreen.html file in Firefox.
When the page loads, the user will see the B2G lock screen, which displays the current date and time. The home screen interface can be accessed by dragging the lock screen up. The home screen displays a grid of application launchers and has a notification bar at the top. You can drag a notification slider down from the bar, much like the equivalent user interface element in Android.
If you look at the source code of the homescreen.html page, you will see that the contents of the interface, including the lock screen, are created with HTML div tags with some JavaScript code to handle interaction and populate the values. It's quite simple and predictable Web content.
Individual applications run inside of a frame in the homescreen interface. We tested several applications, including a dialer, a Web browser, and a map application. Like the home screen, these are all implemented in HTML and CSS. The Web browser is basically a Web page with an HTML input element for the URL bar and an embedded iframe element where the page content loads.
The current implementation of the Gaia environment is still simplistic and incomplete, but it offers a compelling demonstration of how conventional Web content can be used to create a smartphone user experience. It's possible to do anything in the B2G user interface that can be done with HTML and CSS, so the possibilities for styling and theming are prodigiously extensive. Such intrinsic flexibility could help make B2G appealing to hardware vendors because it would make it easier for them to create custom user interfaces that differentiate their products.
Mozilla hasn't created an HTML-based widget toolkit for application development. The applications currently included in Gaia are just straight markup with CSS for design. It's theoretically possible to use existing HTML widget toolkits in B2G, however, such as jQuery Mobile and Sencha Touch.
The B2G project is off to an impressive start. The underlying concept of bringing native application capabilities to the standards-based Web technology stack is also tremendously compelling. It hints at the possibility that the open Web could someday provide a unified application platform for mobile devices.
It's also worth noting that the project is entirely open. As Eich pointed out to us yesterday in response to our coverage of Open webOS, the B2G project has had open governance and public source code since its first day. B2G also benefits from Mozilla's engineering talent and potential partners. The B2G platform has an opportunity to bring positive disruption to the mobile landscape and be a serious contender.
Listing image by Photograph by Coralie Mercier
reader comments
31