1890620 - [Menu Redesign] SUMO article about Android Menu Redesign [Android V140]

Reporter

Description

•

2 years ago

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **
YES

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

Note: If yes, ensure 'Advanced Fields' are visible by selecting 'Show Advanced Field' at the top right, then scroll to 'Security' and check 'Confidential Mozilla Employee Bug (non-security)'.'
NO

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]
Firefox for Android

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
KB content update/ new content

Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

We are redesigning the Android Menu (hamburger button). We will do an experiment on 130.

Release plan:
FX 130 - Experiment (population to be defined)
FX 131 - Full Release

Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

It should

Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

Firefox Android 130 - Experiment Release
Firefox Android 131 - Full Release

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
Firefox iOS 130 - Experiment Release - Sept 3
Firefox iOS 131 - Full Release - Oct 1

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

Note: If you don’t let us know if this date changes, it will be published on this date
No

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Note: A minimum of 10 days is required for translation requests.
Same languages as we have today

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

JIRA -> https://mozilla-hub.atlassian.net/browse/FXDROID-1732

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'

FIGMA -> https://www.figma.com/file/RFz9fYtotQCQuinwcZujZt/Menu-Redesign?type=design&node-id=0-1&mode=design&t=9mWkmDDT75QtJ3GV-0

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

The experiment will be available on nightly and beta 128. (Lucas can use the preview mode as you did with the other experiments)

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
Channing