Input Addon Developers: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 12: Line 12:
|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:
|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. Users do submit feedback about add-on compatibility issues as they see them on any build of Firefox.
1. Desktop Firefox users do submit feedback about add-on compatibility issues as they see them on any build of Firefox.
2. Users do submit feedback about add-on functionality 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. For a feature like Input that is already in product and easy to use, a fit between the two makes sense.
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.
|Feature users and use cases=* End-users will be able to submit feedback about compatibility and functionality of their add-on.
 
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.
|Feature users and 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.
* 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.
|Feature dependencies=* AMO service calls if feedback is wanted by add-on developer
|Feature 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 calls and show the praise/issue/ideas buttons
* 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 pretty way.
* 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.
 
|Feature requirements=Firefox Client
|Feature 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.
* 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.
Line 30: Line 34:
addons.mozilla.org
addons.mozilla.org
* On submission, the comment should show within the add-on developer's developer hub on AMO.
* On submission, the comment should show within the add-on developer's developer hub on AMO.
|Feature non-goals=* Offer praise/issues/ideas for all add-ons without their knowledge.
|Feature non-goals=* Offer praise/issue/idea buttons for all add-ons without their knowledge.
|Feature implementation plan=
* Offer praise/issue/idea buttons for Mozilla projects past Firefox and Fennec (i.e. Seamonkey, Thunderbird, Camino, etc.)
* Extend upon the add-on already created: https://addons.mozilla.org/en-US/firefox/addon/alert-the-developer/  
|Feature 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)
* Add an AMO service call to only show the buttons when the feature is specifically enabled by developers (bug forthcoming)
|Feature localization review=Needs to be contacted
|Feature localization review=Needs to be contacted
Confirmed users
6,300

edits

Navigation menu