B2G/FAQ: Difference between revisions

: Boot to Gecko (B2G) is a 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.  

: 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. Boot To Gecko is intended to identify those missing device capabilities and other application needs, and design standardized solutions for app developers to use.<br>  

: We are working towards a developer phone based on B2G, which we showed in February 2012 at Mobile World Congress. See [http://hacks.mozilla.org/2012/02/mozillas-boot-to-gecko-the-web-is-the-platform/] and much other coverage.

: We are leaning heavily on the existing Gecko and Firefox mobile work and the team of hundreds of engineers building those products. 95% of the code in B2G is shared with Firefox. As of the time this page was last updated, more than 20 engineers were working full-time on B2G-specific parts of the system (telephony, messaging, system-level phone integration). In addition to Mozilla contributors, engineers from carrier partners are working jointly with us on the project as well.

: We don't expect that it will affect our relationships with other organizations.  

: 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.  

: 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.  

: 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.  

: Currently B2G is still a project without a firm product schedule. We are working on Qualcomm chipset based hardware platform for our development and discussing with OEMs /carriers on B2G deployment plans. We will announce a product schedule and launch partners once we reach that stage.

: We are currently using off-the shelf developer hardware (Samsung Galaxy S II), because the device is commercially available to Mozilla employees and community members. We are working on Qualcomm chipset based hardware platform right now and optimizing B2G to this reference platform. As we mentioned above, we are in process of finalization of lead OEM partners for shipping commercial B2G devices.  That reference platform will likely be very different from the Samsung Galaxy S II.

: We don’t have any plans to build or distribute a custom device.

: You don't. By default, your web app will be accessible from the phone just like any other website. If you want to make it ''installable'' to the homescreen, you may consider adding a [https://developer.mozilla.org/en/Apps/Getting_Started open web app manifest] to your app. However, the install API is not complete yet on the B2G platform as of Jan 2012.