Personal tools

Firefox/Roadmap

From MozillaWiki

< Firefox(Difference between revisions)
Jump to: navigation, search
(undo spam)
m (Q2: Fix typo)
(12 intermediate revisions by 8 users not shown)
Line 1: Line 1:
<small>[[Roadmaps|< Product Roadmaps]] | [[Firefox|< Firefox Portal]]</small>
 
 
 
<section begin=summary />{{RoadmapSummary
 
<section begin=summary />{{RoadmapSummary
 
|icon=Firefox-512-noshadow.png
 
|icon=Firefox-512-noshadow.png
 
|pagelocation=Firefox/Roadmap
 
|pagelocation=Firefox/Roadmap
|pagetitle=Firefox 2011 Roadmap
+
|pagetitle=Firefox 2012 Strategy & Roadmap
|owner=[mailto:beltzner@mozilla.com Mike Beltzner]
+
|owner=Asa Dotzler
|updated=Feb 7, 2011
+
|updated=Feb 12, 2012
|status=Draft
+
|description=Firefox is Mozilla's expression of our manifesto and mission; it represents our vision of a people-centric Web experience, as well as a platform that makes it possible to do amazing things with the Web.
|description=We succeeded in re-energizing the browser market, creating competition and innovation which benefits Web application developers and users alike. This newly competitive market has presented challenges for the continued success of Firefox, and in 2011 we must ensure that we can deliver a product that is compelling to users in order to continue to be able to demonstrate our vision for the Web. This roadmap outlines our planned strategy and direction for Firefox in 2011.
+
 
}}<section end=summary />
 
}}<section end=summary />
  
 
{{DoNotEdit}}
 
{{DoNotEdit}}
  
Thanks for reading this document! Here's a quick guide:
 
* '''[[#Product Priorities for 2011|Product Priorities for 2011]]''' is most important bit, and the framing/context/priorities from which all Firefox project plans for the next 12-18 months should flow.
 
* '''[[#So, what are we building?|So, what are we building?]]''' is a set of proposed projects for Firefox and Firefox-related ecosystems which would support the priorities set out in the previous section. My goal is for '''leaders in each of these areas to actually create and vet plans''' that would serve those priorities; this is just offered as examples / for reaction.
 
* '''[[#How will we know how we're doing?|How will we know how we're doing?]]''' begins to explore what metrics we'll use to track success throughout the development and delivery cycles. As with the previous section, we'll need area leaders to own the actual plans, here.
 
* '''[[#Product Roadmap|Product Roadmap]]''' is a proposed market delivery schedule based on the example project work laid out in previous sections.
 
* '''Feedback and Questions''' can be sent to [mailto:beltzner@mozilla.com beltzner@mozilla.com] or added to the [[Talk:Firefox/Roadmap|discussion page]].
 
 
== tl;dr ==
 
# Ship Firefox 4, 5, 6 and 7 in the 2011 calendar year
 
# Always respond to a user action within 50 ms
 
# Never lose user data or state
 
# Build Web Apps, Identity and Social into the Open Web Platform
 
# Support new operating systems and hardware
 
# Polish the user experience for common interaction tasks
 
# Plan and architect for a future of a common platform on which the desktop and mobile products will be built and run Web Apps
 
 
Curious to know why those are the priorities for this year? Read on!
 
 
== Context: Back to Mission ==
 
Firefox is Mozilla's expression of our [http://www.mozilla.org/about/manifesto.en.html manifesto] and [http://www.mozilla.org/about/mission.html mission]; it represents our vision of an Open Web Platform that is powerful, versatile, accessible, customizable, and interoperable. When we first shipped Firefox in 2004, our goal was to get the web moving again, and demonstrate the power of the technologies that made up the platform at that time.
 
 
We succeeded in re-energizing the browser market, creating competition and innovation which benefits Web application developers and users alike. This newly competitive market has presented challenges for the continued success of Firefox, and in 2011 we must ensure that we can deliver a product that is compelling to users in order to continue to be able to demonstrate our vision for the Web. To do this we must:
 
 
* provide a browser that is stable and responsive,
 
* build a product for modern desktop and mobile hardware,
 
* provide a simple set of features & experiences to help users get the most out of the web,
 
* support web technologies that are desired most by application developers and users,
 
* deliver those technology improvements quickly to our user base.
 
 
It is important to remember, however, that gaining browser market share is not the only goal of Mozilla's mission. Our mission is to promote an Open Web Platform which is the most compelling environment for modern applications. Increasingly this vision is being threatened by application development models which bypass the Web in favour of directly connecting with Internet based resources in closed, proprietary models such as:
 
 
* closed or single platform "App" SDKs (AIR, iOS, Android SDK, Chrome Web Store),
 
* plug-in balkanization (h.264, .swf, NaCl),
 
* user personalizations and customizations kept in "walled clouds"
 
 
[[File:Firefox2011RoadmapImage1.png]]
 
 
These types of challenges are not new to Mozilla, and once again our community must work to prove that open, interoperable technologies can exist on the same footing as closed, proprietary ones. To do this we must:
 
 
* work with the community to develop and support an open web "App" model,
 
* identify the key elements of an open and interoperable social network and develop an open standard for them within the Web.
 
 
== Our Product Vision: What the web looks like in 24-36 Months ==
 
 
<small>''(This vision should be revisited and updated regularly. As with all good technology, it should always be aspirational and representative of a future we want to realize)''</small>
 
 
Our mission implies a vision where the currently closed "App" ecosystem and walled social ecosystems are replaced with Open Web Platform based alternatives. While this may not be realizable within the next calendar year, a co-ordinated vision of what we're building towards will help keep our product plans on track and inform our technology choices:
 
 
[[File:Firefox2011RoadmapImage2.png]]
 
 
=== User scenario ===
 
This scenario illustrates the end-user experience of this sort of ecosystem:
 
 
[[File:Firefox2011RoadmapImage3.png|600px]]
 
 
# Friend Status App bleeps, Johnath has said he's started using Pic2It for pics [Social API]
 
# Open Browser on Phone, search for "Pic2It"
 
## Result 1: Pic2It Web App [WebApps]
 
## Result 2: Pic2It Wikipedia Entry [WebApps]
 
## Result 3: Blog post by someone about Pic2It
 
# Click Result 1:
 
## Browser asks if I want to install Pic2It [WebApps]
 
## Pic2It asks if it can know who my contacts are [Identity/Social]
 
## Pic2It connects me to contacts [Identity/Social]
 
## Pic2It is now an app on my desktop [WebApps]
 
## Pic2It runs as headless Gecko Process [Flexible Architecture]
 
## I start browsing pictures in Pic2It, decide I like one, tell my browser I "like" it [Social API]
 
## Other users informed that I like that thing
 
# Click Result 2:
 
## Wikipedia App launches as headless Gecko Process to handle [WebApps, Flexible Architecture]
 
# Click Result 3:
 
## Browser loads and displays blog post
 
# Unplug smartphone from dock removing keyboard / mouse / monitor
 
## Firefox UI replaced with Fennec UI
 
 
=== Developer Scenario (TBD) ===
 
* NEED TO WORK UP WITH BLIZZARD
 
* not just design-code-debug, include distribute app
 
* competitor: iOS4
 
 
== Product Priorities for 2011 ==
 
Our product priorities for 2011 are determined by our overall organizational context and the vision we're trying to achieve. They represent our understanding of what's required in order to produce a web browser that will be both successful in the market and representative of our vision of the web.
 
 
# '''Ship our new technology to users in smaller bundles, more frequently'''
 
## Four technology shipment vehicles in 2011, including Firefox 4
 
## Achieve a regular cadence for shipping
 
# '''Develop a product that is responsive from "click to render"'''
 
## No more than 50ms delay between user action and application reaction
 
## Provide optimizations to hide network latency
 
## Obtain metrics from users in addition to our test infrastructure
 
# '''Expand the Open Web Platform to include Apps, Social and Identity'''
 
## Design and implement open systems for Identity and social interactions
 
## Design and implement Web Application Framework
 
## Implement missing pieces of CSS/HTML required for compelling Web Applications
 
# '''Never lose the user's data or state'''
 
## Continue to improve stability
 
## Mitigate the cost of application failure
 
## Interact with cloud-based storage to allow users to "take it with them"
 
# '''Shine the primary UI until it gleams'''
 
## Determine and optimize top 5-10 user interaction flows (ie: search for restaurant)
 
## Improve tools for customization/restoration of old functionality so we can remove it from primary UI
 
## Improve user interface polish so that Firefox feels modern, graceful and elegant
 
# '''Support modern operating systems and platforms'''
 
## support Firefox Windows 64-bit builds
 
## OSX 10.7 system integration
 
## Android 3.0 tablet integration
 
## ensure JIT performs well on modern ARM CPU families
 
# '''Plan for a future where Desktop, Mobile and Web Apps run on a common platform'''
 
## Need to design and architect towards this eventual outcome
 
## Implementation of this is not a priority
 
 
== So, what are we building? ==
 
We are a community of builders, tinkerers and engineers. We rely on our various leaders (at the module, component and project level) to take ownership and responsibility for what we're building. While product drivers expect to work with these people to ensure that the result is well co-ordinated, the impetus and prioritized plans must come from our distributed community. The following proposals can be used to start the discussion of how best to serve the priorities set out in the previous section.
 
 
=== Firefox Front End ===
 
* Simple Sharing
 
* Animations in the user interface
 
* 50 high priority polish issues for common taskflows
 
* Asynchronous Places
 
* Account Manager
 
* Remove Smart Search functionality from Bookmark Manager
 
* Electrolysis
 
* Web Application Install/Uninstall Support
 
* Process-per-tab to mitigate effects of crashes
 
 
=== Web Platform ===
 
* Hardware Accelerate <canvas>
 
* CSS 3D Transforms
 
* Seamless switch to fullscreen video
 
* Websockets
 
* input type=camera, video
 
* Low Power mode
 
* IndexedDB
 
 
=== Gecko Platform Development ===
 
* Gather performance metrics from users
 
* Support Windows 64-bit builds
 
* Document how to design a common platform to be used for interchangably running desktop, mobile or chromeless web apps
 
* Integrate with new OSX 10.7 user interface
 
* Integrate with new Android 3.0 user interface
 
* Ensure JIT performs well on modern ARM CPU families
 
  
=== JavaScript Engine ===
+
== Firefox Desktop Strategy ==
* tbd
+
  
=== Add-Ons, Plugins, Customizations ===
+
In 2012, Firefox will deliver incredible user and developer experiences in four areas.
* Easier UI customization that links to Add-on discovery
+
** Primary path/UI to support: JetPack and Personas
+
** Secondary path: add-ons, themes
+
* Add support for Greasemonkey like scripts via JetPack?
+
* Addons story that doesn't suck / good metrics / disable-as-soon-as-it crashes
+
* Fix PFS
+
** simple update path for plugins
+
** simple discovery & install path for plugins
+
* need better policy around expectations
+
* need better support and enforcement for versioning expectations
+
* not a lot of vendors come to MDC
+
* improving IPC / sandboxing
+
* NaCl? some vendor push, here, mostly from Adobe
+
  
=== Developer Tools ===
+
First, Firefox will continue shipping innovative new features that ensure users stay in control of their online lives. As a non-profit organization, Mozilla is uniquely positioned for putting users first, and in 2012 Firefox will do just that with features to help users manage how they're tracked on the Web, make sharing across multiple social networks quick and easy, bring privacy and control to the site sign-in process, and much more.
* Console & Inspector
+
* Providing Diffs
+
* Integration with GitHub
+
* How it meshes with open web app ecosystem
+
  
=== Distribution Support ===
+
Second, Firefox will deliver the highest quality browsing experience with top notch performance, memory usage, and stability. In 2012, all browsers do more, stay open longer, and display more and richer content; but as the capabilities of the browsers increase so do the opportunities for the experience to become heavy or unstable. Mozilla understands the value of a responsive user experience and a highly stable and performant platform for Web developers. In 2012 strengthened and dedicated teams will wipe out any and all Firefox responsiveness issues users face and guarantee the rock solid stability at low memory costs that developers demand for their apps.
* direct download
+
* stub downloader
+
* ability to create custom bundles of add-ons and product and customizations
+
* BYOB
+
* MSI
+
  
=== Build to Brand ===
+
Third, while our mission compels us to deliver innovative new features and the highest quality experiences, the Web is more than just the desktop browser and so in 2012 Mozilla will be broadening its product offerings to include a web-wide people-centric identity system, a complete web apps ecosystem, and a no-compromises mobile browser. Integrating these products into the Firefox experience will give users a much richer Firefox and will help launch these new products to a broad user and developer audience.
Firefox has a strong brand based on the Mozilla mission, which must be enforced through our product's design ethos:

+
* Put the user in control
+
** Fully customizable
+
** Full control over private information
+
** Can always take their data with them
+
* Freedom for hackers
+
** Open source (duh)
+
** Tools for hacking and exploring
+
  
== How will we know how we're doing? ==
+
Finally, Firefox in 2012 will bring major advances in HTML, CSS, and JavaScript as well as a powerful and beautiful set of Web developer tools. These capabilities will enable app-quality experiences and developer productivity that rivals native platforms.
In order to measure the effect of this plan, we will employ the new capabilities provided by the Metrics and Engagement groups to obtain metrics on:
+
* Usage and market share
+
* Customer satisfaction amongst end users and web developers
+
* Brand impressions amongst end users, web developers, and technology influencers
+
  
The Market Research team will also be employed to provide competitive analyses and validation of prioritization decisions.
 
  
== Product Roadmap ==
+
== What is this document!? ==
Changing the way we ship products will require the re-evaluation of many assumptions (see below) and a large shift in the way we think about the size of a "major" release. The criteria for inclusion should be no regressions, well understood effects for users, and completion in time for a planned release vehicle. Again, these serve as proposals and should not be taken as prescriptive:
+
  
=== Firefox 5 ===
+
This strategy and roadmap is being developed with the direct inputs of key Firefox stakeholders, including engineering teams and technical leads; user experience, user research, and user support teams; marketing, market insights, and engagement teams; product management; and the entire Mozilla community.
* Account Manager
+
* Simple Sharing UI
+
* UI Animation
+
* 64 Bit on Windows
+
* ...anything that improves responsiveness and is ready
+
* ...anything that improves stability and is ready
+
* ...anything that polishes the user interface and is ready
+
* ...anything else serving product priorities and is ready
+
  
=== Firefox 6 ===
+
The features covered here are primarily Firefox front-end work. For the specific strategy and feature lists covering [https://wiki.mozilla.org/Platform/Roadmap Platform], [https://wiki.mozilla.org/DevTools/RoadmapDec2011 Developer Tools], [https://wiki.mozilla.org/Apps/Roadmap Apps], [https://wiki.mozilla.org/Fennec/NativeUI Mobile], and [https://wiki.mozilla.org/Identity Identity], [https://wiki.mozilla.org/Performance/Snappy Performance/Responsiveness], and [https://wiki.mozilla.org/CrashKill Stability], visit their respective roadmaps and other documentation.
* Web Applications
+
* FasterCache
+
* OSX 10.7
+
* JS Optimizations
+
* ...anything that improves responsiveness and is ready
+
* ...anything that improves stability and is ready
+
* ...anything that polishes the user interface and is ready
+
* ...anything else serving product priorities and is ready
+
  
=== Firefox 7 ===
+
== Firefox Desktop Feature Roadmap ==
* e10s? deXBLification?
+
* ...anything that improves responsiveness and is ready
+
* ...anything that improves stability and is ready
+
* ...anything that polishes the user interface and is ready
+
* ...anything else serving product priorities and is ready
+
  
== How to ship faster ==
+
=== Q1 ===
There's no such thing as a free lunch. To ship smaller bundles of technology more quickly will require us to take a hard look at our existing systems and re-evaluate some of the assumptions we take as immutable, such as:
+
* [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible Add-on Compatibility]: Our experience has given us confidence that the overwhelming majority of add-ons are not broken by new Firefox releases, so we are changing Firefox behavior from assuming add-ons are broken with each new release and managing exceptions with an allow list to assuming add-ons are compatible with each new release and managing exceptions with a disallow list.
* we must provide binary compatibility for Add-ons
+
* [https://wiki.mozilla.org/Firefox/Features/Chrome_migration Chrome Migration]: Firefox already supports migrating from other popular browsers. Users moving from Chrome to Firefox should be able to bring their data with them. We are building this capability into Firefox.
* we must support older branches with maintenance fixes
+
* [https://wiki.mozilla.org/Firefox/Features/Media_Controls_Refresh Refreshed Media Controls]: HTML5 media is increasing on the Web. The default media controls are being refined for usability and to include controls for new HTML5 features like full-screen viewing.
* intermittent oranges are unavoidable
+
* [https://wiki.mozilla.org/Services/Sync/Features/Addon_Sync Add-ons Sync]: Firefox Sync makes it easy to move between computers and devices.  In addition to syncing passwords, bookmarks, and history between Firefox installs, users are going to be able to sync add-ons.
* scaling localization
+
* [https://wiki.mozilla.org/Features/Desktop/Add-on_hotfix Firefox Hotfix]: There are small issues that can occasionally affect Firefox users after a release. Correcting those small issues should not require a full Firefox update. With a new hotfix system, Mozilla can patch minor issues in Firefox without requiring a browser restart.
* we cannot predict the effect of our changes without large scale beta testing
+
* Developer Tools advancements: See the [https://wiki.mozilla.org/DevTools/RoadmapDec2011 Developer Tools roadmap].
* all code needs formal code review
+
* Web Platform advancements: See the [https://wiki.mozilla.org/Platform/Roadmap Web Platform roadmap].
* every contributor knows how to obtain code review expediently
+
* every contributor gets equal say on issues of user interface design and technology prioritization
+
  
'''TODO''': Process change suggestions (w/Shaver)
+
=== Q2 ===
 +
* [https://wiki.mozilla.org/Windows8 Proof of concept for Firefox in Windows 8 Metro]: In order to deliver a compelling Firefox for Windows 8 Metro experience, we need to understand what's possible. A technology proof of concept is the first step. This is not a Alpha or a Beta, but should demonstrate the feasibility of Firefox in Windows 8 Metro. (Timing here is dependent on when Microsoft releases their Windows 8 consumer preview and developer documentation.)
 +
* [https://wiki.mozilla.org/Features/Desktop/Firefox_Home_Tab Firefox Home Tab additions]: Firefox's start page, AKA Firefox Home Tab, is where users start their browsing session and where they land when they've closed their last tab. In addition to easy search, Firefox Home will become a launch point for managing all of your Firefox data.
 +
* [https://wiki.mozilla.org/Firefox/Features/New_Tab_Page A New Tab page powered by the Awesomebar]: For keyboard users, opening a new tab and visiting a top site is super-easy thanks to the Awesomebar. For mouse users, Firefox's new tab page will include a "speed dial" like feature that provides Awesomebar-powered shortcut tiles for super-fast navigation.
 +
* [https://wiki.mozilla.org/Silent_Update Silent Update]: The Firefox update process will be moved to the background and Windows admin passwords and/or UAC prompts will be removed. Also, users with the rare incompatible extension will have a gentler upgrade process.
 +
* [https://wiki.mozilla.org/Web_Apps_integration Web Apps Marketplace integration]: Firefox Home will offer a launcher for the Web Apps Marketplace and promotion for personalized app recommendations.
 +
* [https://wiki.mozilla.org/Support/Firefox_Features/Clean_up_user_profile Restore Firefox]: For various reasons, a Firefox profile can become damaged causing performance and stability problems. Users will be able to quickly and easily restore Firefox without losing their passwords, history, and bookmarks.
 +
* [https://wiki.mozilla.org/Firefox/Features/URL_Autocomplete Awesomebar In-Line URL auto-complete]: In addition to the amazing Awesomebar pop-up list, users will have easy in-line address completion for even faster navigation.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=710372 Smooth scrolling]: Scrolling pages is one of the most common user interactions on the web. With a new scrolling implementation, users will find web page scrolling to be consistently silky smooth.
 +
* [https://wiki.mozilla.org/User:P.A./Panel-based_Download_Manager Panel-based Download Manager]: Firefox was one of the first browsers with an integrated download manager. With the new panel-based manager, users will be able to easily monitor and managing Web downloads without leaving the main browser window.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=692255 Start-up Performance Improvements]: Using the Firefox Windows maintenance service to work around Microsoft's pre-fetch "de-optimization", Firefox start-up speed will be improved dramatically.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=698919 New Cycle Collector] + [https://wiki.mozilla.org/Platform/Features/Incremental_GC Garbage Collector]: With the proliferation of games and other real-time content on the Web, even brief browser pauses are no longer acceptable. Thanks to major improvements to Firefox's cycle and garbage collectors, Firefox pauses and hangs will be a thing of the past.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=669034 Speedy Session Restore]: Session restore makes restarting the browser a frictionless experience. Firefox's session restore is being re-architected for major performance improvements.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=711193 Automatic Session Restore with Tabs on Demand]: Most users prefer starting the browser right where they left off. Firefox is moving to a model that restores all tabs when a user starts up the browser but delays the loading of background tabs until they are needed. This will improve the performance and usability of Firefox just after launch.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=712109 Hang Detector and Reporter]: Similar to how Mozilla collects crash data, this new capability will allow Mozilla to collect, analyze, and fix browser hangs.
  
[[Category:Roadmaps]]
+
=== 2H ===
 +
* Seamless Plug-in [[Improved_missing_plugin_experience|install]] and update experience: Plug-ins like Flash are still a common experience on the Web. Firefox will make acquiring and updating the most popular plug-ins a simple and easy process.
 +
* Tracking Map and 3rd party cookie management: People are increasingly concerned about how they're tracked on the web. With Firefox's tracking map feature, people will be able to visualize how they are tracked as they move around the web and be empowered to easily block that tracking.
 +
* [https://wiki.mozilla.org/Labs/F1/Feature_Blocks/F1 Firefox Share]: The web is a social experience. But few of us live exclusively inside of any one social network. With Firefox Share, Firefox users will be able to easily share links and status updates across a variety of social networks.
 +
* [https://wiki.mozilla.org/Identity/Features/Sign_into_the_browser Log in to Firefox]: Many users carry around dozens of account logins and passwords but that's way too difficult. Based on the Verified Email standard, Firefox users will be able to log in to Firefox to enable Sync and user-centric site logins. Users will finally be able to say goodbye to remembering countless passwords.
 +
* [https://wiki.mozilla.org/Firefox/Features/Theme_Refinement_and_Evolution Firefox theme refresh]: Firefox is a modern browser that feels like you. With the new [http://people.mozilla.com/~shorlander/firefox-ui-design/firefox-visual-design-across-platforms.html Australis] look and feel, Firefox will be a more inviting and confident experience for users.
 +
* [https://wiki.mozilla.org/Windows8 Alpha and Beta of Firefox for Windows 8 Metro]: The Alpha will prove the installation path and basic browsing features. The Beta will be feature complete for a 1.0-capability product.
 +
* [https://wiki.mozilla.org/Features/Firefox/Network_Installer Network Installer]: Firefox's installer is the first experience of Firefox for most users. A new lightweight installer will strengthen security and help improve download performance.
 +
* [https://wiki.mozilla.org/Browser_translation Integrated translation service]: Firefox users, especially outside of the the U.S., encounter a lot of content that's not written in their native tongue. Firefox will offer an easy to use translating feature that makes reading foreign language content a piece of cake.
 +
* [https://wiki.mozilla.org/Firefox/Features/Expose_Add-on_Performance Add-on performance indicators]: Some add-ons cause Firefox users to experience performance and memory problems. Firefox will give users the information they need to decide whether or not a problematic add-on is worth the performance cost.
 +
* Site-based permissions manager: Currently users manage their permissions on a per-feature basis: cookies, passwords, history, etc. This is confusing. A site-based permission manager will empower people to edit all of the permissions associated with any particular site.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=712731 Multiple] [https://bugzilla.mozilla.org/show_bug.cgi?id=715376 Tab] [https://bugzilla.mozilla.org/show_bug.cgi?id=715378 Performance] Improvements: Most Firefox users have several tabs open in a session and background tabs can consume computer resources in ways that slow down the focused tab. There are several upcoming changes to Firefox that will better balance resources to improve performance for the focused tab.
 +
* [https://wiki.mozilla.org/Program_Management/Projects/SearchHijacking Search hijack prevention]: Because search is such a lucrative Web feature, some add-ons and plug-ins are switching user search settings without user consent. We can alert the user when a third party tries to change their search service settings.
 +
* [http://msujaws.wordpress.com/2012/01/09/in-content-preferences-for-firefox-may-be-here-in-16-weeks/ In-line Preferences Manager]: People appreciate Firefox's customizability, but some changes are too difficult for most users. Firefox Preferences will be moved from a pop-up window into the content area of the browser in order to improve ease of customization.
 +
* [https://bugzilla.mozilla.org/show_bug.cgi?id=711552 Plug-in Click to Start]: In order to protect our users from drive-by plug-in exploits and to provide users with more control over plug-ins in the browser, Firefox will have a new "click to play" feature.
 +
* [https://wiki.mozilla.org/Focus_mode Firefox Focus/Reader Mode]: Despite the rise of multi-media on the Web, reading is still the most common web activity. We will make reading long-form content a wonderful experience with a user-activated re-formatting and re-styling of the page that puts focus on the content rather than ads and navigation.
 +
* [https://wiki.mozilla.org/Platform/Features/IonMonkey IonMonkey]: The next generation of the Firefox JavaScript engine, code-named IonMonkey, will bring dramatic improvements to JavaScript performance making Web applications even faster.
 +
* [https://groups.google.com/forum/#!topic/mozilla.dev.tech.network/cUqRe8ZZjbA/discussion New Cache]: Firefox's network cache will be overhauled to improve page loading performance.
 +
* New DOM bindings: DOM manipulations are one of the performance bottlenecks in browsers today. To dramatically improve DOM performance for rich web applications, Mozilla will deliver a revamped for performance set of DOM bindings.
 +
* [https://wiki.mozilla.org/JavaScript:GenerationalGC Generational GC]: Moving to a generational collector will increase cache locality and make collections less expensive, increasing performance for apps and benchmarks that create a lot of short-lived objects.
 +
* [https://wiki.mozilla.org/Show_PDF_inline Inline PDF View]: Most users encountering PDFs on the Web do not need the full capabilities of a dedicated PDF editor application. A built-in PDF viewer will make viewing and previewing PDFs faster and safer for all users.

Revision as of 13:13, 15 February 2012

Firefox-512-noshadow.png Firefox 2012 Strategy & Roadmap
Owner: Asa Dotzler Updated: Feb 12, 2012
Firefox is Mozilla's expression of our manifesto and mission; it represents our vision of a people-centric Web experience, as well as a platform that makes it possible to do amazing things with the Web.
Please do not edit this page without permission.
Thank you!


Contents

Firefox Desktop Strategy

In 2012, Firefox will deliver incredible user and developer experiences in four areas.

First, Firefox will continue shipping innovative new features that ensure users stay in control of their online lives. As a non-profit organization, Mozilla is uniquely positioned for putting users first, and in 2012 Firefox will do just that with features to help users manage how they're tracked on the Web, make sharing across multiple social networks quick and easy, bring privacy and control to the site sign-in process, and much more.

Second, Firefox will deliver the highest quality browsing experience with top notch performance, memory usage, and stability. In 2012, all browsers do more, stay open longer, and display more and richer content; but as the capabilities of the browsers increase so do the opportunities for the experience to become heavy or unstable. Mozilla understands the value of a responsive user experience and a highly stable and performant platform for Web developers. In 2012 strengthened and dedicated teams will wipe out any and all Firefox responsiveness issues users face and guarantee the rock solid stability at low memory costs that developers demand for their apps.

Third, while our mission compels us to deliver innovative new features and the highest quality experiences, the Web is more than just the desktop browser and so in 2012 Mozilla will be broadening its product offerings to include a web-wide people-centric identity system, a complete web apps ecosystem, and a no-compromises mobile browser. Integrating these products into the Firefox experience will give users a much richer Firefox and will help launch these new products to a broad user and developer audience.

Finally, Firefox in 2012 will bring major advances in HTML, CSS, and JavaScript as well as a powerful and beautiful set of Web developer tools. These capabilities will enable app-quality experiences and developer productivity that rivals native platforms.


What is this document!?

This strategy and roadmap is being developed with the direct inputs of key Firefox stakeholders, including engineering teams and technical leads; user experience, user research, and user support teams; marketing, market insights, and engagement teams; product management; and the entire Mozilla community.

The features covered here are primarily Firefox front-end work. For the specific strategy and feature lists covering Platform, Developer Tools, Apps, Mobile, and Identity, Performance/Responsiveness, and Stability, visit their respective roadmaps and other documentation.

Firefox Desktop Feature Roadmap

Q1

  • Add-on Compatibility: Our experience has given us confidence that the overwhelming majority of add-ons are not broken by new Firefox releases, so we are changing Firefox behavior from assuming add-ons are broken with each new release and managing exceptions with an allow list to assuming add-ons are compatible with each new release and managing exceptions with a disallow list.
  • Chrome Migration: Firefox already supports migrating from other popular browsers. Users moving from Chrome to Firefox should be able to bring their data with them. We are building this capability into Firefox.
  • Refreshed Media Controls: HTML5 media is increasing on the Web. The default media controls are being refined for usability and to include controls for new HTML5 features like full-screen viewing.
  • Add-ons Sync: Firefox Sync makes it easy to move between computers and devices. In addition to syncing passwords, bookmarks, and history between Firefox installs, users are going to be able to sync add-ons.
  • Firefox Hotfix: There are small issues that can occasionally affect Firefox users after a release. Correcting those small issues should not require a full Firefox update. With a new hotfix system, Mozilla can patch minor issues in Firefox without requiring a browser restart.
  • Developer Tools advancements: See the Developer Tools roadmap.
  • Web Platform advancements: See the Web Platform roadmap.

Q2

  • Proof of concept for Firefox in Windows 8 Metro: In order to deliver a compelling Firefox for Windows 8 Metro experience, we need to understand what's possible. A technology proof of concept is the first step. This is not a Alpha or a Beta, but should demonstrate the feasibility of Firefox in Windows 8 Metro. (Timing here is dependent on when Microsoft releases their Windows 8 consumer preview and developer documentation.)
  • Firefox Home Tab additions: Firefox's start page, AKA Firefox Home Tab, is where users start their browsing session and where they land when they've closed their last tab. In addition to easy search, Firefox Home will become a launch point for managing all of your Firefox data.
  • A New Tab page powered by the Awesomebar: For keyboard users, opening a new tab and visiting a top site is super-easy thanks to the Awesomebar. For mouse users, Firefox's new tab page will include a "speed dial" like feature that provides Awesomebar-powered shortcut tiles for super-fast navigation.
  • Silent Update: The Firefox update process will be moved to the background and Windows admin passwords and/or UAC prompts will be removed. Also, users with the rare incompatible extension will have a gentler upgrade process.
  • Web Apps Marketplace integration: Firefox Home will offer a launcher for the Web Apps Marketplace and promotion for personalized app recommendations.
  • Restore Firefox: For various reasons, a Firefox profile can become damaged causing performance and stability problems. Users will be able to quickly and easily restore Firefox without losing their passwords, history, and bookmarks.
  • Awesomebar In-Line URL auto-complete: In addition to the amazing Awesomebar pop-up list, users will have easy in-line address completion for even faster navigation.
  • Smooth scrolling: Scrolling pages is one of the most common user interactions on the web. With a new scrolling implementation, users will find web page scrolling to be consistently silky smooth.
  • Panel-based Download Manager: Firefox was one of the first browsers with an integrated download manager. With the new panel-based manager, users will be able to easily monitor and managing Web downloads without leaving the main browser window.
  • Start-up Performance Improvements: Using the Firefox Windows maintenance service to work around Microsoft's pre-fetch "de-optimization", Firefox start-up speed will be improved dramatically.
  • New Cycle Collector + Garbage Collector: With the proliferation of games and other real-time content on the Web, even brief browser pauses are no longer acceptable. Thanks to major improvements to Firefox's cycle and garbage collectors, Firefox pauses and hangs will be a thing of the past.
  • Speedy Session Restore: Session restore makes restarting the browser a frictionless experience. Firefox's session restore is being re-architected for major performance improvements.
  • Automatic Session Restore with Tabs on Demand: Most users prefer starting the browser right where they left off. Firefox is moving to a model that restores all tabs when a user starts up the browser but delays the loading of background tabs until they are needed. This will improve the performance and usability of Firefox just after launch.
  • Hang Detector and Reporter: Similar to how Mozilla collects crash data, this new capability will allow Mozilla to collect, analyze, and fix browser hangs.

2H

  • Seamless Plug-in install and update experience: Plug-ins like Flash are still a common experience on the Web. Firefox will make acquiring and updating the most popular plug-ins a simple and easy process.
  • Tracking Map and 3rd party cookie management: People are increasingly concerned about how they're tracked on the web. With Firefox's tracking map feature, people will be able to visualize how they are tracked as they move around the web and be empowered to easily block that tracking.
  • Firefox Share: The web is a social experience. But few of us live exclusively inside of any one social network. With Firefox Share, Firefox users will be able to easily share links and status updates across a variety of social networks.
  • Log in to Firefox: Many users carry around dozens of account logins and passwords but that's way too difficult. Based on the Verified Email standard, Firefox users will be able to log in to Firefox to enable Sync and user-centric site logins. Users will finally be able to say goodbye to remembering countless passwords.
  • Firefox theme refresh: Firefox is a modern browser that feels like you. With the new Australis look and feel, Firefox will be a more inviting and confident experience for users.
  • Alpha and Beta of Firefox for Windows 8 Metro: The Alpha will prove the installation path and basic browsing features. The Beta will be feature complete for a 1.0-capability product.
  • Network Installer: Firefox's installer is the first experience of Firefox for most users. A new lightweight installer will strengthen security and help improve download performance.
  • Integrated translation service: Firefox users, especially outside of the the U.S., encounter a lot of content that's not written in their native tongue. Firefox will offer an easy to use translating feature that makes reading foreign language content a piece of cake.
  • Add-on performance indicators: Some add-ons cause Firefox users to experience performance and memory problems. Firefox will give users the information they need to decide whether or not a problematic add-on is worth the performance cost.
  • Site-based permissions manager: Currently users manage their permissions on a per-feature basis: cookies, passwords, history, etc. This is confusing. A site-based permission manager will empower people to edit all of the permissions associated with any particular site.
  • Multiple Tab Performance Improvements: Most Firefox users have several tabs open in a session and background tabs can consume computer resources in ways that slow down the focused tab. There are several upcoming changes to Firefox that will better balance resources to improve performance for the focused tab.
  • Search hijack prevention: Because search is such a lucrative Web feature, some add-ons and plug-ins are switching user search settings without user consent. We can alert the user when a third party tries to change their search service settings.
  • In-line Preferences Manager: People appreciate Firefox's customizability, but some changes are too difficult for most users. Firefox Preferences will be moved from a pop-up window into the content area of the browser in order to improve ease of customization.
  • Plug-in Click to Start: In order to protect our users from drive-by plug-in exploits and to provide users with more control over plug-ins in the browser, Firefox will have a new "click to play" feature.
  • Firefox Focus/Reader Mode: Despite the rise of multi-media on the Web, reading is still the most common web activity. We will make reading long-form content a wonderful experience with a user-activated re-formatting and re-styling of the page that puts focus on the content rather than ads and navigation.
  • IonMonkey: The next generation of the Firefox JavaScript engine, code-named IonMonkey, will bring dramatic improvements to JavaScript performance making Web applications even faster.
  • New Cache: Firefox's network cache will be overhauled to improve page loading performance.
  • New DOM bindings: DOM manipulations are one of the performance bottlenecks in browsers today. To dramatically improve DOM performance for rich web applications, Mozilla will deliver a revamped for performance set of DOM bindings.
  • Generational GC: Moving to a generational collector will increase cache locality and make collections less expensive, increasing performance for apps and benchmarks that create a lot of short-lived objects.
  • Inline PDF View: Most users encountering PDFs on the Web do not need the full capabilities of a dedicated PDF editor application. A built-in PDF viewer will make viewing and previewing PDFs faster and safer for all users.