Feature Creep: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "{{FeatureStatus |Feature name=Feature Creep |Feature stage=Draft |Feature health=OK }} {{FeatureTeam |Feature product manager=Jeff Griffiths |Feature lead engineer=Shane Caraveo ...")
 
No edit summary
 
Line 22: Line 22:
}}
}}
{{FeatureTeamStatus}}
{{FeatureTeamStatus}}
Problem: people working on Firefox features have difficulty getting user feedback if they ride the train model. The Nightly and Aurora channels don't get the right set of users exposure.
Problem: people working on Firefox features have difficulty getting user feedback if they ride the train model. The Nightly and Aurora channels don't get the right set of users exposure.  


Solution: create a channel through which people can opt in to and try out new features that have been implemented as add-ons. Some examples:
Solution: create a channel through which people can opt in to and try out new features that have been implemented as add-ons. Some examples:  


* add-ons that implement proposed UX changes<br>* socialAPI prototypes<br>* Panorama 2
*add-ons that implement proposed UX changes<br>* socialAPI prototypes<br>* Panorama 2


The most sensible comparison I can think of would be Google's 'labs' capability for adding advanced or obscure capabilities to their websites.
The most sensible comparison I can think of would be Google's 'labs' capability for adding advanced or obscure capabilities to their websites.  


The particularly important distinctions between this concept and pointing people to Firefox Nightly are:
The particularly important distinctions between this concept and pointing people to Firefox Nightly are:  


* audience / exposure. Feature Creep would install into the current release of Firefox.<br>* features, not bug fixes.
*audience / exposure. Feature Creep would install into the current release of Firefox.<br>* features, not bug fixes.


Some sketchy implementation details:
Some sketchy implementation details:  


The feature would be implemented as an add-on that provides an about:addons-style listing of feature prototypes to try out.
The feature would be implemented as an add-on that provides an about:addons-style listing of feature prototypes to try out.  


The add-ons presented to the user would be a collection on AMO ( eg we would use existing infrastructure with few tweaks ) curated by Mozilla.
The add-ons presented to the user would be a collection on AMO ( eg we would use existing infrastructure with few tweaks ) curated by Mozilla.  


The 'Feature Creep' add-on could also be instrumented to provide additional metrics about user behaviour when using new / prototyped features. <br>
The 'Feature Creep' add-on could also be instrumented to provide additional metrics about user behaviour when using new / prototyped features. <br>
Confirmed users
1,100

edits

Navigation menu