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:27, 25 May 2011
, 25 May 2011indentation
No edit summary |
m (indentation) |
||
| Line 40: | Line 40: | ||
***Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users [[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]] | ***Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users [[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]] | ||
'''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.weafwe<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.weafwe<br> | ||
*Download-then-ask-permission (current model): | **'''Download-then-ask-permission (current model):''' | ||
[[Image:Backwards addon installation case.png|106x140px|Backwards addon installation case.png]] | |||
*Ask-permission-then-download (goal): | **'''Ask-permission-then-download (goal):''' | ||
[[Image:Not backwards addon case.png|100x170px|Not backwards addon case.png]] | |||
== Team == | == Team == | ||
| Line 168: | Line 168: | ||
__NOTOC__ | __NOTOC__ | ||
<br> | |||
[[Category:Features]] [[Category:Firefox]] | [[Category:Features]] [[Category:Firefox]] | ||