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

hacky indentations
m (indentation)
(hacky indentations)
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.
*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.


   [[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]  
          [[Image:Modalvsnot123412.png|665x243px|Modalvsnot123412.png]]  
 
<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>


&nbsp;&nbsp;&nbsp; [[Image:Timerdelay.png|656x332px|Timerdelay.png]]  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;[[Image:Timerdelay.png|656x332px|Timerdelay.png]]  


*Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by:  
*Not giving the implication that AMO and AMO's reviewed code are untrusted, specifically by:  
**Removing "author not verified" messaging for trusted authors [[Image:Trusted messaging3242342342.png|648x84px|Trusted messaging3242342342.png]]<br>  
**Removing "author not verified" messaging for trusted authors  
***Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users [[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]]
&nbsp;&nbsp;&nbsp;&nbsp;[[Image:Trusted messaging3242342342.png|648x84px|Trusted messaging3242342342.png]]<br>  
**Messaging reviewed add-ons differently to unreviewed add-ons and relaying the different meaningfully to users  
&nbsp;&nbsp;&nbsp;&nbsp;[[Image:Authornotverifiedfail234444.png|639x81px|Authornotverifiedfail234444.png]]


'''Priority 2''':<br>  
'''Priority 2''':<br>  
Line 44: Line 44:
*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 instllation.&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.weafwe<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 instllation.&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.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]]  
&nbsp;&nbsp;&nbsp;&nbsp;[[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]]
&nbsp;&nbsp;&nbsp;&nbsp;[[Image:Not backwards addon case.png|100x170px|Not backwards addon case.png]]


== Team  ==
== Team  ==
Confirmed users
954

edits