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 tacke tracked in Jira
Bug 1953629 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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