Confirmed users
98
edits
Mobile/FennecVision: Difference between revisions
→Key themes
| Line 17: | Line 17: | ||
In priority order, here are the key themes of the first Fennec release: | In priority order, here are the key themes of the first Fennec release: | ||
1. Simple, fast navigation to Web content - | 1. Simple, fast navigation to Web content - We need to pay close attention to very basic operations that are still hard to accomplish on most mobile phones, like entering URLs, managing bookmarks, providing an equivalent to multiple windows/tabs, designing zooming and scrolling to achieve readability; we will need to question assumptions about how people use the Web when they're on the go, and not view the UI as a "port" of desktop Firefox. | ||
2. | 2. Compatibility with the Web - Fennec will provide access to the "full" Web, including rich internet applications developed using AJAX. Web content developers should be able to optimize to smaller screen sizes, etc., but not be required to adopt alternate technologies. | ||
3. Secure - Providing a powerful desktop browser engine with full implementation of JavaScript, AJAX, and other advanced web technologies could open a phone up to exploits which could be more costly and more invasive than PC exploits; security will need to be a key consideration from day one. | 3. Secure - Providing a powerful desktop browser engine with full implementation of JavaScript, AJAX, and other advanced web technologies could open a phone up to exploits which could be more costly and more invasive than PC exploits; security will need to be a key consideration from day one. | ||
4. A "whole product" for mobile - Subject to the security constraints above, Fennec should strive to integrate as much as possible with a phone's mapping application, have the ability to initiate phone calls from phone numbers in Web pages, have access to location information through, and integrate with contacts | 4. A "whole product" for mobile - Subject to the security constraints above, Fennec should strive to integrate as much as possible with a phone's mapping application, have the ability to initiate phone calls from phone numbers in Web pages, have access to location information through, and integrate with contacts, calendar items and camera. We should work to ensure that critical necessary plug-ins work out of the box. | ||
5. Support for add-ons - A key strength of Firefox is its support for third-party innovation through Add-ons. Fennec should support Add-ons as well to enable a whole new community of developers to have access to the mobile platform. | 5. Support for add-ons - A key strength of Firefox is its support for third-party innovation through Add-ons. Fennec should support Add-ons as well to enable a whole new community of developers to have access to the mobile platform. | ||
The rationale behind the prioritization is this: If we have addressed themes 1-3, and created a super easy-to-use browser that works on a majority of Web sites and is secure, a case could be made to ship without all of the phone hooks and Add-on support exemplified by items 4 and 5. | The rationale behind the prioritization is this: If we have addressed themes 1-3, and created a super easy-to-use browser that works on a majority of Web sites and is secure, a case could be made to ship without all of the phone hooks and Add-on support exemplified by items 4 and 5, and add those in a follow-on release. | ||
==Leveraging the strengths of Mozilla and Firefox== | ==Leveraging the strengths of Mozilla and Firefox== | ||