Mozilla recently announced the Boot to Gecko (B2G) Project which is a project towards the goal of building a complete, standalone operating system for the open web.
The aim of B2G
The idea is that open web technologies can supersede single vendor control over application environments, and instead use something that will be open for all and consistent across the board. The first main aim is mobile/tablet devices and to be able in such an environment to give access through web technologies to all the capabilities native applications have.
The project is in a very early stage right now, but we believe in communicating this early and getting as much valuable input, help and suggestions as possible to make this out to be all it can be.
Areas of work
The main areas we see right now that will need a lot of work and input are:
- New web APIs
- Build prototype APIs for exposing device and OS capabilities to content (Telephony, SMS, Camera, USB, Bluetooth, NFC, etc.)
- Privilege model
- Making sure that these new capabilities are safely exposed to pages and applications
- Prototype a low-level substrate for an Android-compatible device
- Choose and port or build apps to prove out and prioritize the power of the system.
Helping out with B2G
Let me re-emphasize that the work with B2G has just begun. As you understand, the possibilities, work and collaboration being needed here is huge, and being open about the whole process, we would love to get your thoughts, suggestions, ideas, practical help or anything else you can think of to make this happen!
FAQ about B2G
To cover some common ground and questions, here are the Frequently Asked Questions for B2G:
What is Boot to Gecko?
Boot to Gecko (B2G) is an early-stage, exploratory project with the goal of building a complete, standalone operating system for the open web. It is not a product offering, but if successful, could form the basis for one.
When can we expect to see something?
We’re very early in the project, soliciting suggestions and contributions from a lot of people. As we have more specific estimates for different pieces of functionality, they’ll be shared widely.
What is the size of the team working on this project?
It’s very small right now: just 3 people working part time, but we’re looking to ramp up and as an open project we are actively inviting participation of developers, designers, and others from across the Web. We’re seeing lots of excitement and offers of help already, and we’re also obviously leaning heavily on the existing Gecko and Firefox mobile work.
Why are you doing this now?
We believe that the next frontier for Web applications is full device integration, so that Web developers have the same capabilities as those building for OS-specific stacks.
What does it mean for your relationships with Apple, Google, Microsoft?
We don’t expect that it will affect our relationships with other organizations.
Does this replace work that’s already being done on Web APIs for desktop and mobile?
We are already pushing hard on new Web APIs, and have been for some time. We’ll continue to implement and standardize new APIs for Web content while the B2G project ramps up.
How is this different than the Webian Shell project?
The Webian shell is an impressive project even in its early stages. Where Webian is focused on a Web-centric desktop experience, we’re focused on extending the Web to include more of what is traditionally the domain of OS-specific code. We think we can work together on a bunch of things, and we’re looking forward to it.
How is this different from Chrome OS?
We’re aiming at mobile/tablet devices rather than a notebook form factor. This is an early-stage project to expose all device capabilities such that infrastructure like phone dialers can be built with Web APIs, and not only “high level” apps like word processors and presentation software. We will of course be happy to work with the Chrome OS team on standards activities, and indeed to share source code where appropriate.
Are OEMs interested in B2G?
This is an early-stage project. We just got started, so we haven’t had any of those discussions yet. If an OEM shares our vision of a standard and open platform from top to bottom, we’d be happy to work together to get such a platform into the hands of users.
Whose hardware will you support?
We’ll be selecting initial hardware for hackability and general availability, but we haven’t settled on that yet. A Tegra 2 device is likely to be selected, due to its support for VP8 hardware acceleration. Over time we expect that B2G will work on the majority of devices that support modern Android versions.
Will this mean a Firefox Phone?
We don’t have any plans to build or distribute a custom device.
View full post on Mozilla Hacks – the Web developer blog