Summary
Add Material Design 3 (M3) support to .NET MAUI Android as an opt-in feature, allowing developers to modernize their app's appearance while maintaining backward compatibility with existing Material 2 applications.
Problem
Direct migration to Material 3 would be a breaking change because visual appearance, color schemes, and component behaviors would change for all existing apps.
Solution
Provide M3 as an opt-in feature via MSBuild property:
<PropertyGroup>
<UseMaterial3>true</UseMaterial3>
</PropertyGroup>
Key Deliverables
Implementation Phases
| Phase |
Focus |
Scope |
| 1 |
Foundation |
Build property infrastructure, M3 resources, theme selection |
| 2 |
Controls |
Update handlers for M3 widgets (Switch, RadioButton, etc.) |
| 3 |
Documentation |
Migration guide, samples, PR template updates |
Breaking Change Analysis
None - M2 remains default, opt-in only, fully backward compatible.
Summary
Add Material Design 3 (M3) support to .NET MAUI Android as an opt-in feature, allowing developers to modernize their app's appearance while maintaining backward compatibility with existing Material 2 applications.
Problem
Direct migration to Material 3 would be a breaking change because visual appearance, color schemes, and component behaviors would change for all existing apps.
Solution
Provide M3 as an opt-in feature via MSBuild property:
Key Deliverables
UseMaterial3MSBuild property to enable M3 at build timestyles-material3.xmlandcolors-material3.xmlwith M3 tokensImplementation Phases
Breaking Change Analysis
None - M2 remains default, opt-in only, fully backward compatible.