Confirmed users
954
edits
Extension Manager:Projects:Improve Add-on Installation: Difference between revisions
Extension Manager:Projects:Improve Add-on Installation (view source)
Revision as of 19:43, 25 May 2011
, 25 May 2011uncentering
(changing some wording) |
m (uncentering) |
||
| Line 28: | Line 28: | ||
*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. All notifications should be moved into the arrow-panel notification style, with subtle animated resizes where needed.<br> | *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. All notifications should be moved into the arrow-panel notification style, with subtle animated resizes where needed.<br> | ||
<br> | <br> | ||
<br> | |||
<center>[[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]</center> | <center>[[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]</center> | ||
<br> <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> | *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> | ||
<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> | *Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by: <br> | ||
<br> | <br> | ||
1. Removing "author not verified" messaging for trusted authors<br> | 1. Removing "author not verified" messaging for trusted authors<br> | ||
<br> | <br> | ||
<br> | |||
<center>[[Image:Trusted messaging3242342342.png|648x84px|Trusted messaging3242342342.png]]<br> </center> | |||
<br> <br> | |||
2. Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users<br> | |||
<br> | |||
<br> | |||
<center>[[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]] </center> | <center>[[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]] </center> | ||
'''Priority 2''':<br> | '''Priority 2''':<br> | ||
| Line 68: | Line 62: | ||
*Changing the installation flow order from download-then-ask-permission to ask-permission-then-download. We currently download an add-on's .xpi file before the user is asked permission to install it. 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. 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> | *Changing the installation flow order from download-then-ask-permission to ask-permission-then-download. We currently download an add-on's .xpi file before the user is asked permission to install it. 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. 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> | <br> | ||
''' Download-then-ask-permission (current model)''':<br> | |||
[[Image:Backwards addon installation case.png|54x72px|Backwards addon installation case.png]]<br> | |||
''' Ask-permission-then-download (goal)''':<br> | |||
[[Image:Not backwards addon case.png|45x76px|Not backwards addon case.png]] | |||
== Team == | == Team == | ||