Confirmed users
954
edits
Extension Manager:Projects:Improve Add-on Installation: Difference between revisions
Jump to navigation
Jump to search
Extension Manager:Projects:Improve Add-on Installation (view source)
Revision as of 19:40, 25 May 2011
, 25 May 2011changing some wording
No edit summary |
(changing some wording) |
||
| Line 8: | Line 8: | ||
| style="font-weight: bold; background: #DDD;" | Owner | | style="font-weight: bold; background: #DDD;" | Owner | ||
|- | |- | ||
| [[ | | [[Extension Manager:Projects:Improve Add-on Installation]] | ||
| {{StatusHealthy|status=Finalizing plan for initial improvements in Firefox 6, beginning to scope out further research for future Firefox.}} | | {{StatusHealthy|status=Finalizing plan for initial improvements in Firefox 6, beginning to scope out further research for future Firefox.}} | ||
| 2011-05-19 | | 2011-05-19 | ||
| Line 22: | Line 22: | ||
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. | 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 | While general improvements in efficiently and consistency are the goal, several specific issues fall under this category. | ||
'''Priority 1:''' | '''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. All notifications should be moved into the arrow-panel notification style, with subtle animated resizes where needed. | *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> | |||
<center>[[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]</center> | |||
<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> | |||
<center>[[Image:Timerdelay.png|656x332px|Timerdelay.png]] </center> | |||
<br> | |||
*Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by: <br> | |||
<br> | |||
1. Removing "author not verified" messaging for trusted authors<br> | |||
<br> | |||
<center>[[Image:Trusted messaging3242342342.png|648x84px|Trusted messaging3242342342.png]]<br> </center> | |||
<br> | |||
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> | '''Priority 2''':<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. | *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> | ||
''' Download-then-ask-permission (current model)''':<br> | |||
<center>[[Image:Backwards addon installation case.png|54x72px|Backwards addon installation case.png]]<br></center> | |||
''' Ask-permission-then-download (goal)''':<br> | |||
<center>[[Image:Not backwards addon case.png|45x76px|Not backwards addon case.png]] </center> | |||
== Team == | == Team == | ||
| Line 65: | Line 91: | ||
== Next Steps == | == Next Steps == | ||
Review security issues involved in changes, find developers with free cycles for implementation<br> | |||
== Open Issues == | == Open Issues == | ||
How different trust levels of add-ons can be both determined and messaged to users appropriately | - How can different trust levels of add-ons can be both determined and messaged to users appropriately? | ||
== Related Bugs & Dependencies == | == Related Bugs & Dependencies == | ||