Input Addon Developers

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


Input for Addons Developers
Stage Feature Inbox
Status In progress
Release target `
Health OK
Status note `


Product manager Asa Dotzler
Directly Responsible Individual Aakash Desai
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


Stage 1: Definition

1. Feature overview allows Firefox users to submit feedback for the browser, but not for the rest of their browsing experience (i.e. Add-ons). What we've seen over the past year on are the following:

1. Desktop Firefox users do submit feedback about add-on compatibility issues as they see them on any build of Firefox. 2. Desktop Firefox users do submit feedback about add-on functionality issues as they see them on any build of Firefox. 3. Desktop Firefox users do submit enhancement requests for add-ons.

Further, AMO does not offer an in-product feedback service for add-ons developers who do want feedback. Input's method of being tied into the product has already been implemented and tested. Its easy to use and has given the Firefox development teams much needed insight into the development of the product.

I believe integrating the Add-ons Manager and Input would increase participation from our user base in the development of add-ons as well as increase the amount of feature development and compatibility checking by add-ons authors.

2. Users & use cases

  • End-users will be able to submit feedback about enhancement requests, compatibility breakages and functionality issues of their installed add-ons.
  • Add-ons developers, who check that they want feedback enabled, will be able to receive anonymous praise, issues and ideas from their userbase straight into their developer hub.

3. Dependencies

  • AMO service call to check if feedback is wanted by a Desktop Firefox Add-on Developer
  • Firefox client developer resources to add the necessary AMO service call(s) and show the praise/issue/ideas buttons within the detail-view of an installed add-on.
  • Input's ElasticSearch node location and access information for AMO WebDev to add the data to the Developer Hub in a easy to view manner.

4. Requirements

Firefox Client

  • If an Add-on Developer has explicitly stated they want to received feedback, the praise/issue/idea buttons should show on their detail view on the add-ons manager.
  • On click of any of these buttons, the corresponding submission page should load with the add-on's name pre-loaded onto the comment field.

  • On submission, the comment should show within Input's main dashboard under the requisite product/version/language/feedback_type.

  • On submission, the comment should show within the add-on developer's developer hub on AMO.


  • Offer praise/issue/idea buttons for all add-ons without their knowledge.
  • Offer praise/issue/idea buttons for Mozilla projects past Firefox and Fennec (i.e. Seamonkey, Thunderbird, Camino, etc.)

Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan

8. Reviews

Security review


Privacy review


Localization review

Needs to be contacted



Quality Assurance review

Needs to be contacted

Operations review


Stage 4: Development

9. Implementation

Stage 5: Release

10. Landing criteria


Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap User Engagement
Secondary roadmap `
Feature list Desktop
Project `
Engineering team Desktop front-end

Team status notes

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