Firefox/Features/InstallerUIRewrite: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Stub Installer and UI update
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Development
| style="font-weight: bold; background: #DDD;" | Status
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | ETA
}}
| style="font-weight: bold; background: #DDD;" | Owner
{{FeatureTeam
|-
|Feature product manager=Asa Dotzler
<section begin="status" />
|Feature feature manager=Robert Strong
| [[Firefox/Features/InstallerUIRewrite|Installer UI Rewrite]]
|Feature lead engineer=Robert Strong
| Not started.
|Feature qa lead=Jason Smith
| TBD
}}
| Robert Strong
{{FeaturePageBody
<section end="status" />
|Feature overview=Building a stub installer offers numerous advantages over our current installation process.  It is necessary for us to understand our acquisition funnel and potentially get some early wins on improving download failures.
|-
|}
== Summary ==


To support Windows x64 we would like to have a stub installer that checks if the user is runnin Windows x64 and then downloads / installs the correct bits. To accomplish this, I propose we use the existing installer, have it check if it already has the files to install, and if it doesn't have it download an archive containing the correct files. To support this, a rewrite of the installer user interface will be necessary.
In addition, to support Windows x64 we would like to have a stub installer that checks if the user is running Windows x64 and then downloads / installs the correct bits. To accomplish this, I propose we use the existing installer, have it check if it already has the files to install, and if it doesn't have it download an archive containing the correct files. To support this, a rewrite of the installer user interface will be necessary.
|Feature users and use cases=Enable product (stub installer) downloads over SSL
|Feature requirements=See UX specs here: https://bug651965.bugzilla.mozilla.org/attachment.cgi?id=543348
|Feature ux design=Initial mockups can be found in {{bug|651965}}.


== Release Requirements ==
Most recent mockup: https://bug651965.bugzilla.mozilla.org/attachment.cgi?id=543348


* For clarity, the installer user interface rewrite can be done prior to implementing the stub installer.
Note that after the user clicks install on step 1, even if they walk away Firefox will eventually be installed.  This will likely improve conversion, since the stub installer is considerably smaller than the entire Firefox download (and they may lose interest at the download stage).


== Next Steps ==
Here's a [https://bug513414.bugzilla.mozilla.org/attachment.cgi?id=397421 high level view of our previous install process]
 
|Feature security review=A security review should not be necessary for the installer user interface rewrite though a security review will most assuredly be required for the stub installer ({{bug|322206}}).
* Final mockups - initial mockups were given to Alex Faaborg and Alexander Limi on 2/11/2011.
|Feature implementation notes=These are the bugs we are using the track this work...
* Decide if we want to contract out this work as we have done once before with the Windows x64 installer work.
 
== Related Bugs & Dependencies ==
 
These are the bugs we are using the track this work...


* {{bug|651965}} - Installer user interface rewrite
* {{bug|651965}} - Installer user interface rewrite
* {{bug|322206}} - Firefox net / stub installer (depends on {{bug|651965}})
* {{bug|322206}} - Firefox net / stub installer (depends on {{bug|651965}})
* {{bug|628869}} - [Win] update installer elements to read Mozilla Firefox (depends on {{bug|651965}})
* {{bug|628869}} - [Win] update installer elements to read Mozilla Firefox (depends on {{bug|651965}})
 
}}
== Use Cases ==
{{FeatureInfo
 
|Feature priority=P2
TBD
|Feature rank=15
 
|Feature theme=Product Hardening
== Team ==
|Feature roadmap=Firefox Desktop
 
|Feature secondary roadmap=Security
* Feature Manager: Robert Strong
|Feature list=Desktop
* Lead Developer: Robert Strong
|Feature engineering team=Platform Integration
* QA: ?
}}
* UX: Alex Faaborg
{{FeatureTeamStatus}}
* Security: ?
 
== Designs ==
 
Initial mockups can be found in {{bug|651965}}.
 
--[[User:Faaborg|Alex]] 17:58, 31 May 2011 (PDT):
I need to post updated mockups, but in terms of flow only having three steps is great:
 
#Welcome
#progress bar (download + install)
#Complete
 
(with a fourth page that contains options the user can configure).
 
Note that after the user clicks install on step 1, even if they walk away Firefox will eventually be installed.  This will likely improve conversion, since the stub installer is considerably smaller than the entire Firefox download (and they may lose interest at the download stage).
 
Here's a [https://bug513414.bugzilla.mozilla.org/attachment.cgi?id=397421 high level view of our previous install process]
 
== Testing ==
 
TBD
 
== Security Review ==
 
A security review should not be necessary for the installer user interface rewrite though a security review will most assuredly be required for the stub installer ({{bug|322206}}).

Latest revision as of 18:16, 13 August 2012

Please use "Edit with form" above to edit this page.

Status

Stub Installer and UI update
Stage Development
Status `
Release target `
Health OK
Status note `

{{#set:Feature name=Stub Installer and UI update

|Feature stage=Development |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}

Team

Product manager Asa Dotzler
Directly Responsible Individual Robert Strong
Lead engineer Robert Strong
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Jason Smith
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Asa Dotzler

|Feature feature manager=Robert Strong |Feature lead engineer=Robert Strong |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Jason Smith |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Building a stub installer offers numerous advantages over our current installation process. It is necessary for us to understand our acquisition funnel and potentially get some early wins on improving download failures.

In addition, to support Windows x64 we would like to have a stub installer that checks if the user is running Windows x64 and then downloads / installs the correct bits. To accomplish this, I propose we use the existing installer, have it check if it already has the files to install, and if it doesn't have it download an archive containing the correct files. To support this, a rewrite of the installer user interface will be necessary.

2. Users & use cases

Enable product (stub installer) downloads over SSL

3. Dependencies

`

4. Requirements

See UX specs here: https://bug651965.bugzilla.mozilla.org/attachment.cgi?id=543348

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

Initial mockups can be found in bug 651965.

Most recent mockup: https://bug651965.bugzilla.mozilla.org/attachment.cgi?id=543348

Note that after the user clicks install on step 1, even if they walk away Firefox will eventually be installed. This will likely improve conversion, since the stub installer is considerably smaller than the entire Firefox download (and they may lose interest at the download stage).

Here's a high level view of our previous install process

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

A security review should not be necessary for the installer user interface rewrite though a security review will most assuredly be required for the stub installer (bug 322206).

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

These are the bugs we are using the track this work...

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=Building a stub installer offers numerous advantages over our current installation process. It is necessary for us to understand our acquisition funnel and potentially get some early wins on improving download failures.

In addition, to support Windows x64 we would like to have a stub installer that checks if the user is running Windows x64 and then downloads / installs the correct bits. To accomplish this, I propose we use the existing installer, have it check if it already has the files to install, and if it doesn't have it download an archive containing the correct files. To support this, a rewrite of the installer user interface will be necessary. |Feature users and use cases=Enable product (stub installer) downloads over SSL |Feature dependencies=` |Feature requirements=See UX specs here: https://bug651965.bugzilla.mozilla.org/attachment.cgi?id=543348 |Feature non-goals=` |Feature functional spec=` |Feature ux design=Initial mockups can be found in bug 651965.

Most recent mockup: https://bug651965.bugzilla.mozilla.org/attachment.cgi?id=543348

Note that after the user clicks install on step 1, even if they walk away Firefox will eventually be installed. This will likely improve conversion, since the stub installer is considerably smaller than the entire Firefox download (and they may lose interest at the download stage).

Here's a high level view of our previous install process |Feature implementation plan=` |Feature security review=A security review should not be necessary for the installer user interface rewrite though a security review will most assuredly be required for the stub installer (bug 322206). |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=These are the bugs we are using the track this work...

|Feature landing criteria=` }}

Feature details

Priority P2
Rank 15
Theme / Goal Product Hardening
Roadmap Firefox Desktop
Secondary roadmap Security
Feature list Desktop
Project `
Engineering team Platform Integration

{{#set:Feature priority=P2

|Feature rank=15 |Feature theme=Product Hardening |Feature roadmap=Firefox Desktop |Feature secondary roadmap=Security |Feature list=Desktop |Feature project=` |Feature engineering team=Platform Integration }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}