MozillaWiki

Extension Manager:Projects:Improve Add-on Installation: Difference between revisions

Page Discussion

Extension Manager:Projects:Improve Add-on Installation (view source)

Revision as of 19:29, 1 February 2012

3,316 bytes added ,  1 February 2012
no edit summary
No edit summary
No edit summary
 
(37 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Improve Add-on Installation
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Design
| style="font-weight: bold; background: #DDD;" | Status
|Feature status=In progress
| style="font-weight: bold; background: #DDD;" | ETA
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | Owner
|Feature status note=Finalizing plan for initial improvements in Firefox 7, beginning to scope out further research for future Firefox.
|-
}}
<section begin="status" />
{{FeatureTeam
| Extension Manager:Projects:Improve Add-on Installation
|Feature product manager=Asa Dotzler
| {{StatusHealthy|status=Finalizing plan for initial improvements in Firefox 6, beginning to scope out further research for future Firefox.}}
|Feature feature manager=Jennifer Boriss
| 2011-05-19
|Feature security lead=Jesse Ruderman, Curtis Koenig
| Jennifer Boriss  
|Feature qa lead=Henrik Skupin
<section end="status" />
|Feature ux lead=Jennifer Boriss
|-
}}
|}
{{FeaturePageBody
|Feature open issues and risks=* How can different trust levels of add-ons can be both determined and messaged to users appropriately?
|Feature overview=The process of installing Firefox add-ons is currently fraught with user experience issues. The process involves differently-styled windows, unnecessary amounts of user interaction, and delays which users find confusing and annoying.


== Summary ==
Our goal is to make the process of installing add-ons more efficient and smoother while (at the least) not effecting and (at the best) improving security.  
The process of installing Firefox add-ons is currently fraught with user experience issues.  The process involves differently-styled windows, unnecessary amounts of user interaction, and delays which users find confusing and annoying.


Our goal is to make the process of installing add-ons more efficient and smoother while (at the least) not effecting and (at the best) improving security.
This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.)  


While general improvements in efficienty and consistency are the goal, several specific issues fall under this category:
While general improvements in efficiently and consistency are the goal, several specific issues fall under this category.


* Not switching windows styles during installation, and removing all modal dialogs.  Currently, the verified add-on information confirmation notification is modal, while the download notification window at the beginning of the process and confirmation/restart notification at the end of the process are in the arrow panel notification style
'''Priority 1:'''  
* Reducing the timer wait time from 3 seconds to 1, and giving more understandable messaging about the delay
* Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by:
** Removing "author not verified" messaging for verified authors
** Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users
** Not requiring permission for AMO to install add-ons


== Team ==
*Not switching windows styles during installation, and removing all modal dialogs. Currently, the verified add-on information confirmation notification is modal, while the download notification window at the beginning of the process and confirmation/restart notification at the end of the process are in the arrow panel notification style.&nbsp; All notifications should be moved into the arrow-panel notification style, with subtle animated resizes where needed.
Who's working on this?


* '''Feature Manager''': Jennifer Boriss
[[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]
* '''Lead Developer''':
* '''Product Manager''':
* '''QA''':
* '''UX''': Jennifer Boriss
* '''Security''': Jesse Ruderman


== Release Requirements ==
*Reducing the timer wait time from 3 seconds to 1, and subtly fading the install button from disabled to active state rather than displaying a countdown
Several user experience improvements detailed in {{bug|646602}}.


== Next Steps ==
[[Image:Timerdelay.png|656x332px|Timerdelay.png]]
Outline specific UI flow changes to implement and any related security changes


== Open Issues ==
*Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by:
How different trust levels of add-ons can be both determined and messaged to users appropriately


== Related Bugs & Dependencies ==
1) Removing "author not verified" messaging for trusted authors
{{Bug|646602}}


note that mossop already has some related work in progress here: {{bug|643020}} - Implement the new install UI in the content area
[[Image:Trusted messaging3242342342.png|648x84px|Trusted messaging3242342342.png]]


== Designs ==
2) Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users
Interaction is described in {{bug|646602}}.


== Use Cases ==
[[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]]
* Installing human-reviewed add-ons from AMO
* Installing automated security review sandbox add-ons from AMO
* Installing add-ons not from AMO (default buyer beware)
* (possibly) Installing trusted add-ons not on AMO (e.g. AdblockPlus)


== Test Plans ==
'''Priority 2''':
None so far.


== Goals ==
*Changing the installation flow order from download-then-ask-permission to ask-permission-then-download.&nbsp; We currently download an add-on's .xpi file before the user is asked permission to install it.&nbsp; While it's roughly understandable enough for users to navigate through, the order is backwards compared to the vast majority of similar installation flows. Installing a file before asking both flies in the face of user expectation, and gives the impression at first that we will be installing an add-on without asking permission at all. This may cause users to prematurely cancel an insatllation.&nbsp; If we can ask the user's permission first - even with imperfect add-on data - and then download the file, we'll be following a very well expected and utilized model.
Make add-on installation a more efficient, more consistent, and more secure experience


== Non-Goals ==
'''Download-then-ask-permission (current model)''':


[[Image:Backwards addon installation case.png|54x72px|Backwards addon installation case.png]]


'''Ask-permission-then-download (goal)''':


__NOTOC__
[[Image:Not backwards addon case.png|45x76px|Not backwards addon case.png]]
|Feature users and use cases=*Installing human-reviewed add-ons from AMO
*Installing automated security review sandbox add-ons from AMO
*Installing add-ons not from AMO (default buyer beware)
*(possibly) Installing trusted add-ons not on AMO (e.g. AdblockPlus)
|Feature requirements=Several user experience improvements detailed in {{bug|646602}}.
|Feature ux design===== Ask permission, then download installation (ideal order)  ====


The diagram below shows how the add-on installation would feel if we were able to ask the user's permission, with whatever add-on information was available, before downloading the .xpi file. This is far more consistent with user's expectations of giving permission before the action that they gave permission for. Obviously the information we have at the beginning of a download may be imperfect, but we should show the best information we have available and only throw a flag if there is a problem. At least on AMO, the information we display should be correct.


[[Category:Features]]
[[Image:Not backwards addon case.png|202x340px|Mockup]]  
[[Category:Firefox]]
 
==== Download, then ask permission second installation (current but not ideal order) ====
 
This is the order of our current add-on download installation. While it's roughly understandable enough for users to navigate through, the order is backwards compared to the vast majority of similar installation flows. Installing a file before asking both flies in the face of user expectation, and gives the impression at first that we will be installing an add-on without asking permission at all. This may cause users to prematurely cancel an instllation.
 
[[Image:Backwards addon installation case.png|218x289px|Mockup]]
 
(also see {{bug|646602}})
|Feature security review=* [https://wiki.mozilla.org/Security/Reviews/Firefox6/ReviewNotes/AddOns Security Discussions/Reviews]
|Feature implementation notes=Likely:
 
*{{bug|416605}} - Reduce security dialog delay from 2 seconds
*{{bug|643020}} - Implement the new install UI in the content area
*{{bug|652896}} - Allow AMO to show extension install dialog before downloading XPI
 
Possible:
 
*{{bug|646602}} - Installing add-ons from AMO should not invoke the security prompt
 
Wontfix:  
 
*{{bug|561177}} - <strike>Remove countdown from add-on install dialog</strike>''(wontfix - we're reducing, not removing, the delay)''
*{{bug|588266}} - <strike>Firefox add-on installation dialog should use doorhanger notification </strike>
*{{bug|616100}} - <strike>Remove redundant install delay (undo fix for Bug 162020) [for non-AMO sites] </strike>
}}
{{FeatureInfo
|Feature priority=P2
|Feature roadmap=Add-ons
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus
|Feature security health=OK
|Feature security notes=[[Security/Reviews/Firefox6/ReviewNotes/AddOns|Notes]]
}}
Curtisk
canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/302727...393071"