1953629 - [spike] Discovery and sizing estimate of work for migrating to Material 3

Status: RESOLVED FIXED

(Firefox for Android :: Design System and Theming, task, P1)

Description

[Noah Bond [:007]]

In order to better estimate the size/scope of the migration from Material 2 to Material 3, let's conduct an investigation spike to provide answers for the following questions:

• How much effort would it take to upgrade our overall app look to Material 3?
• Can we roll it out gradually, or does it need to be done all at once?
  • What is the size & capacity needed to the initial migration?
• What are the net differences with our design components?
  • Are they API and mostly cosmetic (padding etc.), or will any require significant refactors?
• Are there any game breaking changes that would require significant standalone effort to resolve?
• Would Focus be impacted by this?

Deliverable

Aggregate all of the relevant information in a google doc to provide to the team and the associated meta & intake ticket tracked in Jira

Comment 1

[Noah Bond [:007]]

Attachment: WIP: Bug 1953629 - M3 spike investigation

Comment 2

[Noah Bond [:007]]

Please check the Jira ticket for the full summary.

The TLDR of the document’s TLDR is that we are not blocked by any substantive M3 migration work in order to begin working on the redesigns. The migration work itself is tedious but small in scope overall and we should prioritize it in the immediate term to avoid any long term design tech debt/bugs.