[UX] Design Spike: Theme previewing during Firefox tour

RESOLVED FIXED

Status

()

Firefox
General
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: sevaan, Assigned: sevaan)

Tracking

unspecified
x86
All
Points:
3
Bug Flags:
firefox-backlog +
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ux] [fxgrowth])

Attachments

(1 attachment, 2 obsolete attachments)

(Assignee)

Description

4 years ago
We would like to concept a way for users to preview and install themes during the UI Tour in Firefox.
Flags: firefox-backlog+

Updated

4 years ago
Flags: qe-verify-
Whiteboard: [fxgrowth] → [ux] [fxgrowth]
(Assignee)

Updated

4 years ago
Assignee: nobody → sfranks

Updated

4 years ago
Status: NEW → ASSIGNED
Iteration: --- → 35.3
(Assignee)

Comment 1

4 years ago
Created attachment 8499131 [details]
Theme Previewing during Firefox Tour
Attachment #8499131 - Flags: ui-review?(philipp)
I think it could be helpful if the tour itself automatically cycled through the list to demonstrate what they look like (eh, apply them and highlight which one is active). Or in general somehow make it more obvious to the user that they can hover/select the thumbnails to make something happen. Otherwise I'd be afraid that a lot of people wouldn't realize what they can do here.
(Assignee)

Comment 3

4 years ago
One quick cycle through is a cool idea, with the highlight moving between the themes.
(Assignee)

Comment 4

4 years ago
Created attachment 8499618 [details]
Theme Previewing during Firefox Tour (Updated)
Attachment #8499131 - Attachment is obsolete: true
Attachment #8499131 - Flags: ui-review?(philipp)
Attachment #8499618 - Flags: ui-review?(philipp)
Looks great!
What's the thinking behind opening all themes in a background tab (instead of a new focused tab) when the user clicks on the »view more« link?
(Assignee)

Comment 6

4 years ago
(In reply to Philipp Sackl [:phlsa] from comment #5)
> Looks great!
> What's the thinking behind opening all themes in a background tab (instead
> of a new focused tab) when the user clicks on the »view more« link?

I didn't want to take users out of the tour as this shows up on step 2...so by opening the "View more themes"in a background tab, the user can check them out at their leisure after they've learned about all we have to offer.
(In reply to Sevaan Franks [:sevaan] from comment #6)
> (In reply to Philipp Sackl [:phlsa] from comment #5)
> > Looks great!
> > What's the thinking behind opening all themes in a background tab (instead
> > of a new focused tab) when the user clicks on the »view more« link?
> 
> I didn't want to take users out of the tour as this shows up on step 2...so
> by opening the "View more themes"in a background tab, the user can check
> them out at their leisure after they've learned about all we have to offer.

But wouldn't I assume that clicking on a link takes me somewhere? I already expressed my intention to go somewhere else by clicking. I don't think we (or websites) use this kind of behavior anywhere else.

If you're concerned about tour drop-off, would it make more sense to move this panel to a later step in the tour?
(Assignee)

Comment 8

4 years ago
It's the step about customization though.

What if it just opens a new tab and makes it the active one. Then when you are done, the tour will always be there for you to come back to.
(In reply to Sevaan Franks [:sevaan] from comment #8)
> It's the step about customization though.
> 
> What if it just opens a new tab and makes it the active one. Then when you
> are done, the tour will always be there for you to come back to.

Sounds good!
(Assignee)

Comment 10

4 years ago
Created attachment 8504723 [details]
Theme Previewing during Firefox Tour (Update #2)

Doc updated to reflect active tab discussion above.
Attachment #8499618 - Attachment is obsolete: true
Attachment #8499618 - Flags: ui-review?(philipp)
(Assignee)

Updated

4 years ago
Blocks: 1082559

Updated

4 years ago
Iteration: 35.3 → 36.1
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.