Changes

Jump to: navigation, search

B2G/FAQ

4 bytes added, 04:41, 8 August 2011
no edit summary
B2G is designed to build on the success of the web, and given the early stage of the project it could reach users in many forms. We're certainly interested in working with OEMs and others who share our vision of even greater success for web-based applications.<br>
'''- One of the aims of B2G is to create web APIs for access to core mobile device features - cameras, USB, etc. Given that on desktops we've been increasingly sandboxing the browser to ensure web apps don't compromise security, couldn't that raise security issues?'''
It absolutely raises security issues, and they're ones that we are taking very seriously. Installing applications on a mobile device right now (or on a desktop operating system for that matter) raises similar security issues, and we're looking at ways to improve on those existing models.<br>
'''- What would B2G offer mobile users that HTML5 doesn't?'''
B2G would offer mobile users all the power of HTML5, extended with device capabilities like Bluetooth and SMS, a richer capability model for interaction with the filesystem, and a way to tie these "native HTML5 apps" together. The intent is very much that B2G lead to improved capabilities for the web platform, not that it replace HTML5 or related tech in any way. Many of these new capabilities will also make sense in desktop browsers, and we look forward to seeing them there as well.<br>
36
edits

Navigation menu