Input Addon Developers
|Input for Addons Developers|
|Product manager||Asa Dotzler|
|Directly Responsible Individual||Aakash Desai|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
input.mozilla.com 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 input.mozilla.com 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.
- 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.
- 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 input.mozilla.com/feedback 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
- Extend upon the add-on already created: https://addons.mozilla.org/en-US/firefox/addon/alert-the-developer/
- Add an AMO service call to only show the buttons when the feature is specifically enabled by developers (bug forthcoming)
Needs to be contacted
Quality Assurance review
Needs to be contacted
Stage 4: Development
- Feedback buttons in Add-ons Manager: https://bugzilla.mozilla.org/show_bug.cgi?id=681794
- AMO bug link needed
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
|Engineering team||Desktop front-end|
Team status notes