Features/Desktop/Make Add-ons Awesome

From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Make Add-ons Awesome
Stage Draft
Status `
Release target `
Health OK
Status note `


Product manager Asa Dotzler
Directly Responsible Individual Jorge Villalobos
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead
Product marketing lead `
Operations lead `
Additional members Matt Grimes, Tyler Downer, Michael Verdi

Open issues/risks


Stage 1: Definition

1. Feature overview

Add-ons have become one of the top reasons behind complaints we receive from our users, ranging from unwanted installs to poor performance and malware. This is the tracking feature for all work that we'll be doing to address these add-on problems.

The major features are ordered by importance, the first being the most important, and low-hanging fruit features are identified with [LHF].

1. Enhanced customization APIs (feature page):

  • Vetted APIs for changing the homepage, default search, keyword URL and new tab page.

2. Firefox reset option on reinstall (feature page):

  • [LHF] Add the reset feature to the common repair path for Windows users so that it's discoverable.

3. Improve add-on monitoring (feature page):

  • Track more of all existing add-ons.
  • Quicker response to malware.

4. Enhanced Blocklisting (feature page):

  • [LHF] Double refresh rate.
  • [LHF] Blocklist entries should support reverting a set of preferences.
  • [LHF] Check for unblocked versions before blocking.
  • Blocklist entries should support more block types, like performance and security warnings.

5. Clearer Add-on Installation (feature page):

  • [LHF] Global add-on uninstall, instead of just disable.
  • Simpler install from trusted sources.
  • New opt-in install screen.
  • Installed add-ons reminder.

2. Users & use cases

End users are the primary target here, specially less knowledgeable users who are more likely to install malicious or unwanted add-ons unknowingly.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan


8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation


Stage 5: Release

10. Landing criteria


Feature details

Priority Unprioritized
Rank 999
Theme / Goal Experience
Roadmap `
Secondary roadmap `
Feature list `
Project `
Engineering team `

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `