[UX] Design Spike: Create flow & mockups for different variations of the onboarding tour

RESOLVED FIXED

Status

()

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: phlsa, Assigned: verdi)

Tracking

(Blocks: 2 bugs)

36 Branch
x86
All
Points:
13
Dependency tree / graph
Bug Flags:
firefox-backlog +
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ux])

Attachments

(2 attachments, 1 obsolete attachment)

Following Michael Verdis analysis of onboarding flows, we need to spec out the most common onboarding flows for new installs of Firefox.

The cases we need to cover are:
- New user / never used Fx before
- Existing user installing on a new machine
- Pave-over installation
- Returning user (there's a profile but no Fx installed)
Flags: firefox-backlog+

Updated

4 years ago
Flags: qe-verify-

Updated

4 years ago
Assignee: nobody → mverdi
Status: NEW → ASSIGNED
Iteration: --- → 38.1 - 26 Jan
Points: --- → 13
(Assignee)

Comment 1

4 years ago
Created attachment 8554922 [details]
firstrun-flowchart.png

The first run user flows (download, install or update, and run Firefox) are are one of our biggest opportunities to help users be successful. Our goal is to build an experience that allows us to do this in a holistic and systematic way. Instead of having a new user onboarding tour as a distinct piece in a series of distinct pieces, we want to create one continuous onboarding experience that tells a story from download to browsing.

In addition, we’ll tailor experiences for other use cases:
* Current user paveover or automatic update
* Part-time user paveover or automatic update

For new users, we want to create a setup experience instead of a tour. The distinction being that in a setup, the user can skip steps but sees them all and in a tour, the use can completely dismiss it at any time. 

For updating users, we can continue to use a tour for major updates. For part-time users (those who use another browser as their default) we can use a hybrid setup/tour.

The attached flowchart outlines how this would work. I'll file a followup bug to create a specification and wireframes for each flow.
Attachment #8554922 - Flags: review?(philipp)
(Assignee)

Updated

4 years ago
Blocks: 1126319
(Assignee)

Updated

4 years ago
Blocks: 1126327
(Assignee)

Updated

4 years ago
Blocks: 1126329

Updated

4 years ago
Iteration: 38.1 - 26 Jan → 38.2 - 9 Feb
Comment on attachment 8554922 [details]
firstrun-flowchart.png

Looks very good Michael!

One thing that would be nice just for future reference would be a legend of what the various colors mean (current flow, desired flow etc.)

I am slightly nervous about un-skipable tours, but this works as a hypothesis that we can test :)
Attachment #8554922 - Flags: review?(philipp) → review+
(Assignee)

Comment 3

4 years ago
Created attachment 8556654 [details]
firstrun-flowchart.png

Thanks Philipp. I updated the flowchart with a legend.
Attachment #8554922 - Attachment is obsolete: true
(Assignee)

Updated

4 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Created attachment 8562978 [details]
Use correct terms

Several of the terms used are incorrect. Instead of typing them into a comment I made notes on the png.
You need to log in before you can comment on or make changes to this bug.