Material Design
Give it an Android-style look with layered cards and a ripple when people tap.
Scroll sideways to explore the full example
- Build from reusable components and tokens
- Use elevation only to explain layer relationships
- Give every interactive state visible feedback
- Let motion connect cause and result
- Adapt the system to the brand without breaking consistency
When to use it
- Android and cross-platform productRefer to Android’s component and interaction guidelines.
- Large interface needing a mature component systemEmail
you@example.comFloating labels can clarify field names and input states. - Team that benefits from documented patternsAB
- Rapid product work with accessibility requirements→
When NOT to use it
- Copy default components without matching the product's content
- Use elevation as decoration+✎ButtonLink
- Mix several design systems in one flow+✎★
- Customize each component independently until the system disappearsPurple buttonHot-pink button
Paper-like layers, ripple feedback, and the floating action button gave Android a shared system-wide design language.
Gmail, Calendar, Maps, and other services adopted the system as the component ecosystem matured across platforms.
Shape, color, and type became easier to customize in response to criticism that every Material app looked the same.
Android 12 introduced themes derived from a user's wallpaper, making the system more personal while keeping shared structure.
Material Design interface, indigo primary color with a restrained pink accent, consistent component tokens, elevation that explains layers, floating action button where appropriate, ripple feedback and clear states
Scroll sideways to explore the full example
Scroll sideways to explore the full example
Scroll sideways to explore the full example
Scroll sideways to explore the full example
