Material Design 3

Build a coherent product interface with Material 3 semantics, components, tokens, interaction states, and platform behavior. The target is not a screen that merely looks vaguely Material. It must behave like a good Android or web product and use expression only where it improves hierarchy or comprehension.

Resolve the Context First

Before changing UI, inspect enough of the project to answer:

• Which target is in scope: Android Compose, Android Views, Wear OS, or web?
• Which Material libraries and versions are already present?
• Is the requested API stable, experimental, or unavailable on that target?
• Which theme, components, navigation model, spacing conventions, and assets already exist?
• What is the screen's primary task, primary action, content hierarchy, and state model?
• Which compact, medium, expanded, desktop, foldable, and input scenarios matter?

Preserve established product identity and architecture. Prefer the existing theme and reusable components unless the task explicitly requests a redesign or migration. Never upgrade a dependency, opt into an alpha release, or migrate Views to Compose as an incidental styling change.

Read the Relevant Reference