canmove, Confirmed users
1,584
edits
Line 33: | Line 33: | ||
==Is it built with Gecko? Why not use WebKit?== | ==Is it built with Gecko? Why not use WebKit?== | ||
Gecko provides many things that WebKit does not. First and foremost is the backing of the Firefox development project and the Mozilla community. We also believe that the web should be open and there should be number of different browsers and rendering engines to help drive the open web forward, and we are willing to invest to make that happen. | |||
In addition, the main backers of WebKit today, | In addition, the main backers of WebKit today (including Apple, Google, and RIM) are also operating system vendors and have a vested interest in making their own platforms supported. Mozilla doesn't make devices and we're more interested in making sure the open web succeeds. We know based on conversations with other device manufacturers that they are interested in an option that comes from a neutral third party that also has a commitment to an open source solution. | ||
Finally, to have the kind of user base required to move the web forward, we need users who care about us, care about our brand, and use our product every day. We do on the desktop that by having direct relationships with users through the Firefox product and brand. We will use that same strategy in the mobile space. WebKit is not a brand and it's not something that is directly consumable by non-developers. It's a mechanism to extend certain vendors' brands. We believe that a world in which these vendors are the only brands associated with the mobile web is a sad one indeed. The Web and the Internet have to be much more interesting and diverse than only two or three players. Hence we are investing here and will make our work available to mobile users and device manufacturers. | |||
== I'm a device manufacturer, what are my options to build a browser with Mozilla? == | == I'm a device manufacturer, what are my options to build a browser with Mozilla? == |