Personal tools

Firefox/Features/InstallerUIRewrite

From MozillaWiki

Jump to: navigation, search
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 `

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 `

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

`


Feature details

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

Team status notes

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