1069035 - (menu-reorg) [meta] Reorganize Menu (and children)

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Settings and Preferences, defect)

Description

[Robin Andersen [:tecgirl]]

Attachment: Menu Proposal.001.jpg

Creating this to keep track of the overflow menu reorganization I am working on.

Will effect: the main menu, Tools, Customize, Settings

Comment 1

[Robin Andersen [:tecgirl]]

Attachment: Menu-Proposal.002.jpg

Updated Menu screens

Comment 2

[:Margaret Leibovic]

Some feedback on the mock-ups:

* I really like the "Page tools" menu idea, since the "Page" menu we currently have isn't very descriptive.

* I think it's an interesting idea to break "Customize" out of "Settings", but I wonder if users will be confused that it's not part of Settings anymore. I also think that something like "Display" would belong inside Settings, since it just includes a bunch of display preferences.

* I want to make sure we're on the same page that creating a native add-ons manager in settings (bug 891115) would require a lot of work, and I don't want this reorganization effort to depend on that, so tapping "Add-ons" would still open up the current add-ons manager (although I would like to start a separate effort to tackle some low-hanging fruit to improve what we currently have there).

* As a small style nit on the mock-ups, we currently use the ">" icon to indicate that the item leads to a sub-menu, so that would appear on "Page tools", not on "Customize" or "Settings".

Finally, we now have settings telemetry data all the way up to beta, so we should make sure we dig into that to see if it can help inform our decisions here:
https://people.mozilla.org/~mfinkle/uitelemetry/

(Navigating to the "Events" tab and searching for "settings" and "menu" will lead to the relevant data points.)

Comment 3

[Robin Andersen [:tecgirl]]

(In reply to :Margaret Leibovic from comment #2)
> Some feedback on the mock-ups:
> 
> * I really like the "Page tools" menu idea, since the "Page" menu we
> currently have isn't very descriptive.
> 
> * I think it's an interesting idea to break "Customize" out of "Settings",
> but I wonder if users will be confused that it's not part of Settings
> anymore. I also think that something like "Display" would belong inside
> Settings, since it just includes a bunch of display preferences.
> 

I'm hoping that by bringing it up a level, they might be encouraged to play with the customization settings more often (and especially since we're moving Add-ons there). I can go either way with Display, since it's both a customization and a setting—if you think it makes more sense to leave it in Settings let's do it. Currently telemetry shows little use so either they don't care or they can't find what they're looking for. I'm counting on the latter.

> * I want to make sure we're on the same page that creating a native add-ons
> manager in settings (bug 891115) would require a lot of work, and I don't
> want this reorganization effort to depend on that, so tapping "Add-ons"
> would still open up the current add-ons manager (although I would like to
> start a separate effort to tackle some low-hanging fruit to improve what we
> currently have there).
> 

Correct, we are absolutely *not* touching the Add-on manager at this time. While it would be amazing to give the native experience a whirl, and I plan on giving it a shot, it's definitely not in this round. So yes, tapping Add-ons will still take you to the current Add-on manager and subsequently AMO.

> * As a small style nit on the mock-ups, we currently use the ">" icon to
> indicate that the item leads to a sub-menu, so that would appear on "Page
> tools", not on "Customize" or "Settings".
> 

Thank you for that clarification! I researched patterns regarding carets on Android and couldn't find anything! It made sense to me to put the carets where another menu screen was rather than a sub-menu, but if this is the pattern then I will honor that and update my mock.

> Finally, we now have settings telemetry data all the way up to beta, so we
> should make sure we dig into that to see if it can help inform our decisions
> here:
> https://people.mozilla.org/~mfinkle/uitelemetry/
> 
> (Navigating to the "Events" tab and searching for "settings" and "menu" will
> lead to the relevant data points.)

Comment 4

[Robin Andersen [:tecgirl]]

Attachment: Menu-Proposal.002a.jpg

updated mock to reflect proper caret placement (on Page Tools and NOT on Customize/Settings).

Comment 6

[Kevin Brosnan [Ex-Mozilla]]

Moved over dependencies from 1156534. Please verify they are in scope.

Comment 7

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Attachment: pres_settings_V2.pdf

I'm going to pick this up again. But I'm going to try and scope this more so it's easier to get moving. 

Namely, I want to start by just reorganizing the "Settings" and updating the UI switches (having 1 checkbox option is kind of silly). 

Next will be adding Search, then thinking about other things like enhancements, maybe Tools, changing copy, etc.

Also talked to Robin about this as well to get her thoughts on what I'm attaching here as the "Step 1" (reorganizing). We think this is a good start, but we definitely need to follow up with "step 2" and "step 3" to complete the "revamp".

NI: mhaigh for attn :)

Comment 8

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Attachment: pres_settings_V2_pub2.pdf

Comment 9

[:Margaret Leibovic]

Anthony, are the outstanding bugs here still valid? Maybe we should close this bug and open a new one when we have a clear idea about what we want to do with the menu.

Comment 10

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Good call. I've closed the remaining bugs.