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

From MozillaWiki
Jump to navigation Jump to search
m (clearing in prep for migration to new feature page format (will be done momentarily))
Line 1: Line 1:
{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Extension_Manager:Projects:Improve_Add-on_Installation|Improve Add-on Installation]]
| {{StatusHealthy|status=Finalizing plan for initial improvements in Firefox 7, beginning to scope out further research for future Firefox.}}
| 2011-05-19
| Jennifer Boriss
<section end="status" />
|-
|}


== Summary  ==
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.
While general improvements in efficiently and consistency are the goal, several specific issues fall under this category.
'''Priority 1:'''
*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.<br>
<br>
<br>
<center>[[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]</center>
<br> <br>
*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<br>
<br>
<br>
<center>[[Image:Timerdelay.png|656x332px|Timerdelay.png]] </center>
<br> <br>
*Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by: <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1. Removing "author not verified" messaging for trusted authors<br>
<br>
<br>
<center>[[Image:Trusted messaging3242342342.png|648x84px|Trusted messaging3242342342.png]]<br> </center>
<br> <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2. Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users<br>
<br>
<center>[[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]] </center>
'''Priority 2''':<br>
*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.<br>
<br>
'''&nbsp;&nbsp;&nbsp; Download-then-ask-permission (current model)''':<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Image:Backwards addon installation case.png|54x72px|Backwards addon installation case.png]]<br> '''&nbsp;&nbsp;&nbsp;&nbsp; Ask-permission-then-download (goal)''':<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Image:Not backwards addon case.png|45x76px|Not backwards addon case.png]]
== Team  ==
Who's working on this?
*'''Feature Manager''': Jennifer Boriss
*'''Lead Developer''':
*'''Product Manager''':
*'''QA''': Henrik Skupin
*'''UX''': Jennifer Boriss
*'''Security''': Jesse Ruderman / Curtis Koenig
*'''L10n:''' TBD
*'''Accessibility:''' TBD
== Release Requirements  ==
Several user experience improvements detailed in {{bug|646602}}.
== Next Steps  ==
Review security issues involved in changes, find developers with free cycles for implementation<br>
== Open Issues  ==
- How can different trust levels of add-ons can be both determined and messaged to users appropriately?
== Related Bugs &amp; Dependencies  ==
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>
== Security Discussion Notes  ==
[https://wiki.mozilla.org/Security/Reviews/Firefox6/ReviewNotes/AddOns Security Discussions/Reviews]
== Designs  ==
=== '''Ask permission, then download installation (ideal order)'''<br>  ===
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.<br>
<br>
[[Image:Not backwards addon case.png|202x340px|Mockup]]
<br>
<br>
=== '''Download, then ask permission second installation (current but not ideal order)'''<br>  ===
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.<br>
<br>
[[Image:Backwards addon installation case.png|218x289px|Mockup]]
<br> (also see {{bug|646602}})
== 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)
== Test Plans  ==
None so far.
== Goals  ==
Make add-on installation a more efficient, more consistent, and more secure experience
== Non-Goals  ==
__NOTOC__
<br>
[[Category:Features]] [[Category:Firefox]]

Revision as of 23:07, 10 July 2011

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Extension_Manager:Projects:Improve_Add-on_Installation&oldid=327336"