Material Design 3 Guide: Color, Type, Components
Material Design 3 explained for app makers: color roles and dynamic color, type scale, shapes, elevation, layout sizes, key components and Compose theming.

Material Design 3 (M3) is Google's current design system for Android and the foundation of Jetpack Compose's Material components. This guide is for founders, developers and designers who need to design or build Android screens that feel at home on the platform. It covers the color system, typography, shape, elevation, layout, the components you will actually use and how to set up a theme, with the real numbers.
TL;DR: M3 builds an entire color scheme from one source color, assigns colors by role (primary, container, surface) rather than by hex value, and can adapt to the user's wallpaper with dynamic color. It uses a 15-style type scale, a corner-radius scale from 4 to 28 dp, tonal surfaces instead of heavy shadows, and window size classes for adaptive layout. Use the standard components, theme them through tokens, and test light, dark and dynamic color.
What Material Design 3 is
Google introduced Material Design 3, also known as Material You, alongside Android 12. It replaced Material Design 2's fixed brand palettes with a personal, adaptive approach: colors can come from the user's wallpaper, shapes are rounder, and components were redesigned with larger touch areas and tonal color.
In 2025 Google extended it with M3 Expressive, which adds more emphasis tools: new components such as button groups, split buttons, FAB menus and toolbars, a wider shape library, and spring-based motion. Expressive builds on M3's foundations rather than replacing them, so everything in this guide still applies. For applying Expressive specifically, read our guide on Material Design 3 Expressive on real Android screens.
M3 is organized around design tokens: named values such as md.sys.color.primary or md.sys.typescale.body-large that both designers and code reference. Change a token and every component using it updates.
The color system
M3's color system is the part most worth understanding, because it drives almost every component.
From one source color to a full scheme
- •Source color: you pick one brand color, or Android takes one from the user's wallpaper.
- •Key colors: M3 derives five: primary, secondary, tertiary, neutral and neutral variant.
- •Tonal palettes: each key color becomes a palette of tones from 0 (black) to 100 (white), such as 10, 20, 30 through 90, 95, 99 and 100, generated in Google's HCT color space so tones are perceptually even.
- •Color roles: specific tones are assigned to named roles for the light and dark schemes.
Color roles you will use
| Role | Used for | Light scheme tone | Dark scheme tone |
|---|---|---|---|
| primary | Key actions, filled buttons, active states | 40 | 80 |
| onPrimary | Text and icons on primary | 100 | 20 |
| primaryContainer | Less prominent filled elements, FAB | 90 | 30 |
| onPrimaryContainer | Content on primaryContainer | 10 | 90 |
| secondary / secondaryContainer | Less prominent components, filter chips | 40 / 90 | 80 / 30 |
| tertiary / tertiaryContainer | Contrasting accents, highlights | 40 / 90 | 80 / 30 |
| error / errorContainer | Errors and destructive states | 40 / 90 | 80 / 30 |
| surface | Default background for screens | Neutral, near white | Neutral, near black |
| onSurface / onSurfaceVariant | Primary and secondary text and icons | Dark neutrals | Light neutrals |
| outline / outlineVariant | Borders and dividers | Neutral variant | Neutral variant |
Every "on" role is paired with its container so text contrast is built in. That pairing is the main rule: always place onX content on X. Mixing roles, such as primary text on a tertiaryContainer, breaks the contrast guarantees.
Surface containers
Instead of tinting surfaces by elevation alone, current M3 defines five surface container roles for layering: surfaceContainerLowest, surfaceContainerLow, surfaceContainer, surfaceContainerHigh and surfaceContainerHighest. Use them to separate areas: a navigation bar on surfaceContainer, a card on surfaceContainerLow, a dialog on surfaceContainerHigh.
Dynamic color
On Android 12 and later, dynamic color generates the scheme from the user's wallpaper, so your app matches their phone. Your options:
| Approach | When to use |
|---|---|
| Full dynamic color | Utility and productivity apps where personalization fits |
| Brand scheme only | Apps where brand color is core to recognition, such as fintech or retail |
| Dynamic with brand accents | Dynamic surfaces and containers, fixed brand color for the logo and key moments |
Whatever you choose, provide a fallback brand scheme for devices without dynamic color. If you are still choosing brand colors, our mobile app color palette guide shows how to build one that maps cleanly to roles.
Typography
M3's type scale has five roles, each in three sizes, for 15 styles. Defaults use Roboto, though you can substitute brand fonts.
| Style | Size / line height (sp) | Typical use |
|---|---|---|
| Display Large | 57 / 64 | Hero numbers, rare large moments |
| Display Medium | 45 / 52 | |
| Display Small | 36 / 44 | |
| Headline Large | 32 / 40 | Screen headlines on large layouts |
| Headline Medium | 28 / 36 | |
| Headline Small | 24 / 32 | Dialog titles, section headers |
| Title Large | 22 / 28 | Top app bar titles |
| Title Medium | 16 / 24 | List item titles, card titles |
| Title Small | 14 / 20 | Small headers |
| Body Large | 16 / 24 | Main reading text |
| Body Medium | 14 / 20 | Secondary text, list supporting text |
| Body Small | 12 / 16 | Captions |
| Label Large | 14 / 20 | Button text |
| Label Medium | 12 / 16 | Chips, navigation labels |
| Label Small | 11 / 16 | Badges, timestamps |
Rules worth following:
- •Use sp for text so it scales with the user's font size setting, and test at the largest setting.
- •Stick to the scale; one-off sizes break consistency across components.
- •If you swap Roboto for a brand font, check its x-height; you may need to adjust sizes slightly to keep legibility.
Generate a custom scale with the type scale generator.
Shape
M3 uses a corner-radius scale. Components reference a shape level rather than a fixed radius:
| Shape level | Default radius | Typical components |
|---|---|---|
| None | 0 dp | Full-bleed images, some app bars |
| Extra small | 4 dp | Text field corners, snackbars, menus |
| Small | 8 dp | Chips |
| Medium | 12 dp | Cards, small FABs |
| Large | 16 dp | FABs, navigation drawers, side sheets |
| Extra large | 28 dp | Dialogs, bottom sheets (top corners), large FABs |
| Full | Fully rounded | Buttons, search bars, sliders, badges |
Change the scale once in your theme to shift the whole app's personality, from softer to sharper. Preview values with the border radius generator.
Elevation
M3 expresses elevation primarily through tonal color and secondarily through shadow. There are six levels:
| Level | Elevation | Example |
|---|---|---|
| 0 | 0 dp | Flat surfaces, filled cards |
| 1 | 1 dp | Elevated cards, modal bottom sheets |
| 2 | 3 dp | Navigation bar, menus, scrolled top app bar |
| 3 | 6 dp | FAB, dialogs, search bar |
| 4 | 8 dp | Hover or focus states on level 3 |
| 5 | 12 dp | Pressed or dragged states |
In practice: use surface container roles to separate layers, add shadow only where something floats (FABs, menus), and avoid stacking many elevations on one screen.
Layout and adaptive design
M3 uses window size classes based on the available width, not the device:
| Window class | Width | Typical navigation | Margins |
|---|---|---|---|
| Compact | Under 600 dp | Navigation bar (bottom) | 16 dp |
| Medium | 600 to 839 dp | Navigation rail | 24 dp |
| Expanded | 840 to 1199 dp | Navigation rail or drawer, two panes | 24 dp |
| Large and extra-large | 1200 dp and up | Persistent drawer, multiple panes | 24 dp or more |
Most phones in portrait are compact; foldables open to medium or expanded; tablets in landscape are expanded or larger. Canonical layouts help: list-detail for email or messaging, supporting pane for a main view plus context, and feed for grids of cards.
Other layout rules:
- •Spacing: work in 4 dp increments, with 8 dp as the common step.
- •Touch targets: at least 48 × 48 dp, even when the visible icon is 24 dp.
- •Edge-to-edge: apps targeting Android 15 and later draw behind system bars by default; handle window insets so content is not hidden.
The components you will use most
M3 ships a full set of components in Jetpack Compose and Material Components for Android. These are the ones nearly every app needs.
Buttons
| Type | Emphasis | Use for |
|---|---|---|
| Filled | Highest | The single main action, e.g. "Save," "Checkout" |
| Filled tonal | High, softer | Important secondary actions |
| Elevated | Medium | Actions that need separation from patterned backgrounds |
| Outlined | Medium | Secondary actions next to a filled button |
| Text | Lowest | Dialog actions, inline links |
Use one filled button per area. Button height is 40 dp by default, with the 48 dp touch target maintained around it.
Floating action buttons
The FAB holds the screen's primary constructive action, such as compose or create. Sizes: small (40 dp), standard (56 dp) and large (96 dp), plus the extended FAB with a text label. Use at most one per screen, and skip it if there is no clear primary action. M3 Expressive adds a FAB menu for revealing a few related actions.
Navigation
| Component | Use when | Spec notes |
|---|---|---|
| Navigation bar | 3 to 5 top destinations on compact windows | 80 dp tall, active indicator pill behind the icon |
| Navigation rail | Medium and expanded windows | Vertical, on the leading edge |
| Navigation drawer | 5 or more destinations, or large screens | Modal on phones, persistent on large screens |
| Top app bar | Every screen title and actions | Small 64 dp; medium and large variants collapse on scroll |
| Tabs | Switching between related content in one area | Primary tabs under the app bar, secondary within content |
Selection and input
- •Chips: assist (smart actions), filter (toggle filters), input (entered items like contacts) and suggestion (dynamic suggestions).
- •Segmented buttons: choose between two to five related options.
- •Text fields: filled or outlined; pick one style per app. Always show a label, not just a placeholder, and use supporting text for errors.
- •Switches, checkboxes and radio buttons: switches for instant on/off, checkboxes for multiple selections, radios for one choice.
- •Sliders and date/time pickers for ranges and dates.
Containment and feedback
- •Cards: elevated, filled or outlined. Keep each card about one subject with a clear primary action.
- •Lists: one, two or three lines with leading icons, avatars or images.
- •Bottom sheets: standard (coexist with content) or modal (block it). Include a drag handle.
- •Dialogs: basic for short decisions, full-screen for complex tasks on compact windows.
- •Snackbars: brief messages at the bottom with an optional single action like "Undo."
- •Progress indicators: linear or circular, determinate when progress is known.
Theming in practice
1. Generate a scheme
Use Google's Material Theme Builder, available on the web and as a Figma plugin. Enter a source color (or several custom colors), preview light and dark schemes, and export tokens for Compose, Android XML views, the web or Figma styles.
2. Apply it in Jetpack Compose
@Composable
fun AppTheme(
darkTheme: Boolean = isSystemInDarkTheme(),
dynamicColor: Boolean = true,
content: @Composable () -> Unit
) {
val context = LocalContext.current
val colors = when {
dynamicColor && Build.VERSION.SDK_INT >= Build.VERSION_CODES.S ->
if (darkTheme) dynamicDarkColorScheme(context)
else dynamicLightColorScheme(context)
darkTheme -> DarkBrandColors
else -> LightBrandColors
}
MaterialTheme(
colorScheme = colors,
typography = AppTypography,
shapes = AppShapes,
content = content
)
}
This falls back to your brand schemes on devices older than Android 12 and when you choose to disable dynamic color.
3. Mirror it in your design file
Google publishes a Material 3 Design Kit in the Figma Community with components and variables matching the tokens. Keep design and code in sync by naming colors with M3 roles rather than "Blue 500."
Material Design 3 vs Apple's HIG
If you ship on both platforms, keep brand and content consistent and let platform conventions differ. The biggest differences:
| Topic | Material 3 | iOS HIG |
|---|---|---|
| Units | dp and sp | pt |
| Touch target | 48 × 48 dp | 44 × 44 pt |
| Body text | 16 sp Body Large | 17 pt Body |
| Primary action | Often a FAB | Prominent button in content or toolbar |
| Back | System back gesture | Back button and edge swipe |
| Color | Roles and dynamic color | System and semantic colors |
Our iOS Human Interface Guidelines summary covers Apple's side in the same format.
Common Material 3 mistakes
- •Using hex values directly instead of color roles, which breaks dark mode and dynamic color.
- •Putting onPrimary text on a container color, or any mismatched role pair.
- •Several filled buttons competing on one screen.
- •A FAB for a non-primary action like "Filter."
- •Bottom navigation with more than five items, or used on tablets instead of a rail.
- •Fixed text sizes in dp instead of sp.
- •Content hidden behind the status or gesture bar after enabling edge-to-edge.
- •Placeholder-only text fields with no visible label.
Material Design 3 checklist
- • Color scheme generated from a source color, with light and dark variants
- • All colors referenced by role; every onX sits on X
- • Dynamic color decision made, with a brand fallback
- • Type uses the 15-style scale in sp, tested at the largest font size
- • Shape scale set once in the theme
- • Surfaces layered with surface container roles; shadows only on floating elements
- • Touch targets at least 48 × 48 dp
- • Navigation bar on compact, rail on medium and wider
- • Edge-to-edge with correct window insets
- • One filled button and at most one FAB per screen
- • Text fields have visible labels and error text
- • Theme mirrored in the design file with M3 token names
If you want to see these rules applied quickly, you can generate a first draft of Material 3 Android screens in floow and check them against this list. For the build and publishing side, follow our guide on how to make an Android app.
FAQ
What is the difference between Material Design 2 and Material Design 3?
Material Design 3 introduced dynamic color from the user's wallpaper, tonal palettes and color roles, rounder shapes, updated components such as the navigation bar with a pill indicator, and tonal elevation instead of relying mainly on shadows. Material Design 2 was built around fixed primary and secondary brand colors.
Is Material You the same as Material Design 3?
Largely, yes. Material You was the name Google used when launching the personal, wallpaper-based design language with Android 12, and Material Design 3 is the design system that implements it. Today they are used almost interchangeably.
What is M3 Expressive?
M3 Expressive is a 2025 update to Material Design 3 that adds more expressive tools, including new components such as button groups and FAB menus, a larger shape library and spring-based motion. It builds on M3's color, type and token foundations.
Do I have to use dynamic color?
No. Dynamic color is optional. Many brands keep a fixed scheme, or use dynamic color for surfaces while keeping brand color for key moments. Always supply a fallback scheme either way.
Can I use Material Design 3 on iOS?
You can, since Flutter and the web support Material 3 components, but iPhone users expect iOS conventions. For cross-platform apps, share brand and content and adapt navigation and controls per platform.
Design it with floow
Want Android screens that follow Material Design 3 from the start? Describe your app in floow, refine the screens in chat and export to Jetpack Compose or Figma. Try:
Design a 4-screen Android podcast app in Material Design 3: a home screen with a large top app bar, filter chips and tonal episode cards; a show detail with a filled "Follow" button; a now-playing screen with a large FAB-style play button; and a library with a navigation bar. Use a teal source color with full light and dark schemes.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Guides22 November 2026Mobile App Accessibility: Designer and Founder ChecklistMobile app accessibility made practical: contrast, touch targets, Dynamic Type, VoiceOver and TalkBack labels, motion and a full pre-launch checklist.By floow.design
Roundups22 November 2026ScreensDesign Alternatives: 9 Places for Real App ScreensScreensDesign alternatives compared: Mobbin, Page Flows, Refero and more, with what each library is best for and how to turn references into your own screens.By floow.design
Insights21 November 2026Music App Design: Player, Library and DiscoveryMusic app design guide: home and discovery, search, library, mini player, now playing, queue and offline, plus lock screen, car and widget surfaces, with.By floow.design