1890613 - SUMO article about Android Toolbar Redesign Phase 1 [Android V135]

Status: RESOLVED WONTFIX

(support.mozilla.org :: Knowledge Base Content, task, P2)

Description

[[e-mail]]

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 Toolbar. This one is a big change so every article that shows the URL Bar and Navigation Bar should be updated. We are going with an Experiment on 127 (Population yet to be defined)

Release plan:
FX 127 - Beta Experiment (50% Control | 50% New Toolbar)
FX 127 - Release Experiment (Population % to be defined by DS)
FX 128 - Release 100% (If experiment doesn’t have negative impact)

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

It will depend on experiment results.

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 127 - Experiment
Firefox Android 128 - Full Release

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
Firefox Android 127 - Experiment - June 11
Firefox Android 128 - Full Release - July 9

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-1012

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/8fsCvtnweBkWGZ9NfL907l?type=design%27&node-id=5320:13971

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

It will be available in nightly 127 - Check with Android Team for experiment.

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

Comment 1

[Chris Peterson [:cpeterson]]

We're trying to standardize on this new toolbar terminology in our Android designs and code:

• Use the term address bar for the (existing) bar with the address input, share button, and refresh button. (Our notes and the current product have been calling this the "toolbar".)
• Use the term toolbar for the new bar with the buttons for back/forward, home, tab tray, and app menu. (Our notes had been calling this the "navigation bar".)

Comment 2

[Chris Peterson [:cpeterson]]

Moving this bug to our Release blockers meta bug because the SUMO article doesn't need to block our experiment.

Comment 3

[SUMO Mandy]

Confirming we can remove this bugzilla Chris?

Comment 4

[Chris Peterson [:cpeterson]]

Confirming we can remove this bugzilla Chris?

The Android toolbar project's schedule is delayed, but we will still need to new or revised SUMO articles about the new toolbar UX.

Since the first toolbar milestone won't ship until (roughly) Fx 131 in October, do you recommend:

• We close this bug for and file a new SUMO request when we get closer to Fx 131?
• Leave this bug open as a reminder to your team and revisit it when we get closer to Fx 131?

Comment 5

[Lucas Siebert]

Thanks for the reply, Chris. Let's keep this open. I'll move it to the V131 content release tracker in Asana.

Comment 6

[Chris Peterson [:cpeterson]]

To reduce schedule risk, the Android toolbar will ship in two phases:

• Toolbar phase 1: add the new "nav bar" toolbar (targeting Fx 132)
• Toolbar phase 2: update the existing address bar (targeting 2025 Q1, maybe Fx 136)

The iOS toolbar (SUMO request bug 1890616) will ship in one release with the nav bar and address bar together.

Timeline:
https://docs.google.com/document/d/1S-AN82C-T37jbZ_sgrcfToTSzgeDs5j30CgB7lIj7jc/edit

We can use this SUMO request for phase 1. I will file a follow-up SUMO request for phase 2.

Comment 7

[Chris Peterson [:cpeterson]]

The new Android toolbar is now targeting Fx 135, not 132.

Comment 8

[Lucas Siebert]

Task link in the Asana Content Roadmap: https://app.asana.com/0/1203460865189761/1208525315672111/f

Comment 9

[Joe M [:jmahon]]

Lucas, I know the target release has been moved a few times, but at this point we're getting closer to releasing the Toolbar changes (in 135) - just wanted to check in if you're still tracking it on your end, and/or if you need anything from the Toolbar crew.

Comment 10

[Lucas Siebert]

Hi! Thanks for checking in. Yep, we’re on track with the Toolbar changes — it’s in the content roadmap, and we should have a draft ready for review about a week before the V135 go-live date. My plan is to work on it as I go through the priority queue for release tasks, but let me know if you need it prioritized!

Comment 11

[Dayana]

Hi Mandy, could you help confirm if this request is still valid? I don't seem to have access to the Asana task linked above.

Comment 12

[SUMO Mandy]

I think this work is paused so I have asked Mobile PMs to submit a new ticket once new work on this resumes.