Add-ons/Roadmap
Note: you might be looking for the newer roadmap, this is from 2012.
Add-ons Roadmap 2012
Top Priorities
The appearance pane needs to allow users to see larger previews of what themes and personas will look like as well as allowing selection of both theme and persona individually.
2) In-content install experience
The process of installing Firefox add-ons is currently fraught with user experience issues. The process involves differently-styled windows, unnecessary amounts of user interaction, and delays which users find confusing and annoying. Our goal is to make the process of installing add-ons more efficient and smoother while (at the least) not effecting and (at the best) improving security.
Unknown, slow or insecure plugins shouldn't be allowed to run without user interaction.
Meant to help with multiple scenarios:
- Accidental/malicious install: "Hey, we suddenly found a new SketchyWare.dll plugin on your system. Did you actually want to use it?"
- Performance: The "Java makes my system asplode when a page loads, but sometimes I want to use it" problem.
- Security: Users who don't trust Flash, as well as giving us a way to soft-block a plugin that a user needs to use on legit sites (YouTube, intranet, whatever).
4) In-content UI Visual unification
Do preparation work for having new in-content UI have a consistent and unified visual appearance.
5) Default-to-compatible followups.
Only small lower-priority items are left.
Secondary Priorities
1) Telemetry for add-ons.
2) Exposing add-on performance information
Users should be informed when an add-on they are about to install or have installed causes Firefox performance and or memory problems. This information should be presented at AMO and in the Firefox Add-ons Manager.
3) Moving search engines to the Add-ons Manager
Search engines should be included in the add-ons manager and the existing search engines UI removed.
Security and usability concerns associated with letting content area widgets modify the surrounding browser -will help integrate the Add-ons Manager and add-ons settings.
Tertiary Priorities
Improve the user experience of dealing with blocklisted add-ons/plugins.
2) Add-ons Manager side of signing reviewed add-ons.
No wiki page or bug yet, I want to develop a plan for this soonish.
3) Application self-tests/detecting broken add-ons
This is a followup project for default-to-compatible. Anyone can work on this - it's not specific to any knowledge I have.
There's a few other Add-ons related things on the Firefox Features wiki page that may or may not push out other lower-priority things:
