Skip to content
Material Design 2
Main Navigation
v3
v2
v1

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

Appearance

Sidebar Navigation

Material System

Introduction

Material studies

About our Material studies

Basil

Crane

Fortnightly

Owl

Rally

Reply

Shrine

Material Foundation

Environment

Surfaces

Elevation

Light and shadows

Layout

Understanding layout

Pixel density

Responsive layout grid

Spacing methods

Component behavior

Applying density

Navigation

Understanding navigation

Navigation transitions

Search

Color

The color system

Applying color to UI

Color usage

Text legibility

Dark theme

Typography

The type system

Understanding typography

Language support

Sound

About sound

Applying sound to UI

Sound attributes

Sound choreography

Iconography

Product icons

System icons

Animated icons

Shape

About shape

Shape and hierarchy

Shape as expression

Shape and motion

Applying shape to UI

Motion

Understanding motion

The motion system

Speed

Choreography

Customization

Interaction

Gestures

Selection

States

Communication

Confirmation & acknowledgement

Data formats

Data visualization

Empty states

Help & feedback

Imagery

Launch screen

Onboarding

Offline states

Writing

Machine learning

Machine learning patterns

Object detection: live camera

Object detection: static image

Barcode Scanning

Material Guidelines

Material Theming

Overview

Implementing your theme

Usability

Accessibility

Bidirectionality

Platform guidance

Android bars

Android fingerprint

Android haptics

Android icons

Android navigating between apps

Android notifications

Android permissions

Android slices

Android split-screen

Android swipe-to-refresh

Android text selection toolbar

Android widget

Cross-platform adaptation

Components

App bars: bottom

App bars: top

Backdrop

Banners

Bottom navigation

Buttons

Buttons: floating action button

Cards

Checkboxes

Chips

Data tables

Date pickers

Dialogs

Dividers

Image lists

Lists

Menus

Navigation drawer

Navigation rail

Progress indicators

Radio buttons

Sheets: bottom

Sheets: side

Sliders

Snackbars

Switches

Tabs

Text fields

Time pickers

Tooltips

On this page

Component behavior ​

This page describes how components behave in a layout, both in relationship to the grid as well as breakpoints.

Position terminology ​

UI elements behave in different ways at each breakpoint range. The position of UI elements, components, and surfaces in the grid are described with the terms below.

Position termDefinition
Above; belowThe y position of an element
In front of; behindThe z position of an element
Left; right;
center
The x position of an element
Top; bottomThe y position of an element relative to a container or screen edge
Vertically
centered
The x and y position of an element centered relative to a container or the screen edges
StickyAn element that scrolls with the UI and locks at a certain point in the scroll range
FloatingA fixed element positioned in front of scrolling content
Leading edgeThe edge of a screen or layout that written content begins from. For example, in LTR languages such as English, this is usually the left edge of a screen
Trailing edgeThe edge of a screen or layout where written content ends

Component adaptation ​

Component adaptation describes changes in visual presentation (padding, size, layout, or alignment), or switching out one component for another that is better suited to the device size and use case.

Visual presentation ​

Visual presentation is the most common method of adaptation. This type of adaptation affects the scale and placement of content and objects on screen, as well as their relationships to each other. For example, a text list on a mobile device can adjust margins, vertical spacing, or density to better fit larger screens like tablets.

Size constraints ​

Material Components have minimum and maximum values for container dimensions, margins, and padding. For size constraints of each component, visit the Components section.

For example, snackbars have a maximum width of 600dp for large screens. These minimum and maximum values allow for continuous change to the component’s visual presentation as a layout expands from mobile to large screens.

When scaling a layout, components can have fixed or responsive widths within the range of size constraints.

Elements with fixed widths remain the same width regardless of a screen’s size.

The button component remains fixed in position and size along the right margin
The button component remains fixed in position and size along the right margin.

Elements with responsive widths expand and contract as a screen size changes.

The button scales in response to the two columns on the right side
The button scales in response to the two columns on the right side.

Don’t use a container on responsive components if the screen is too narrow to display elements and padding at smaller

Don't

Don’t use a container on responsive components if the screen is too narrow to display elements and padding at smaller widths.

Caution: use caution when enlarging a responsive component across several columns in a wide screen

Caution

Use caution when enlarging a responsive component across several columns in a wide screen. Certain components such as buttons can become overly emphasized at larger screen widths.

Internal Composition ​

When scaling a component, define the position and alignment of its internal elements in relationship to the container.

For example, the icon and text label within an icon button remain anchored to each other and remain centered while the button expands horizontally.

A button's internal elements maintain a consistent relationship as the component scales
A button's internal elements maintain a consistent relationship as the component scales

For more complex components, like app bars, internal elements can be grouped and anchored to multiple points within the container.

For example, a menu icon and logo can be grouped and anchored to the leading edge, while a search bar is anchored to the center, and action icons are anchored to the trailing edge.

Logo and menu icon anchored to the leading edge of Fortnightly's app bar
1. Logo and menu icon anchored to the leading edge of Fortnightly's app bar
2. Account picker anchored to the trailing edge of Fortnightly's app bar

A component’s internal composition should accommodate the ergonomic needs of the device on which it’s displayed. For example, a horizontally-oriented card on a mobile device can shift to a more square-shaped card on larger screens. This adaptation gives more prominence to imagery and allows for larger type styles to enhance readability.

Cards can change orientation on larger screens
Cards can change orientation on larger screens.

Component swapping ​

As a layout changes across screen sizes, components with similar functions can also be exchanged. This makes it possible to adjust a layout for large-scale changes to the ergonomic and functional qualities of an interface.

For example, a bottom navigation bar can swap with a navigation rail on tablets, and a navigation drawer on larger screens.


Components can switch types as well. For example, a full-screen dialog on mobile can be exchanged with a simple dialog on larger screens. This component change maintains the function of the dialog, while also making use of screen space in a way that preserves a user’s context by revealing underlying content.

A full screen dialog can adapt to a simple dialog on larger screens
A full screen dialog can adapt to a simple dialog on larger screens.

Some functionally-equivalent component groups are defined below.

Component typeMobile optionTablet optionLaptop option
NavigationBottom navigationNavigation railNavigation drawer
NavigationModal navigation drawerModal navigation drawerPermanent navigation drawer
CommunicationFull-screen dialogSimple dialogSimple dialog
ActionBottom sheetMenuMenu

Use caution when swapping components by ensuring that the interchangeable components are functionally equivalent. Do not, for example, swap a button for a chip. Use caution when changing between list items and cards. The component swap should always serve a functional and ergonomic purpose for the user.

Responsive patterns ​

The arrangement of components in a layout can also adjust with changes in screen sizes. This adaptation occurs either by repositioning the component or concealing/revealing information based on available screen space.


Compatibility

An article on making apps accessible by ensuring compatibility with different devices.

Related link

Reveal ​

Parts of the UI that are hidden by smaller screens can be revealed when additional space becomes available at larger breakpoints.

Elements, such as side navigation, can become visible when the screen size increases
Elements, such as side navigation, can become visible when the screen size increases.

A UI can reveal more robust or complex options, such as additional editing features in a doc
A UI can reveal more robust or complex options, such as additional editing features in a doc.

Content that only appears after tapping on a small screen (1) can be revealed by default when more space is available
Content that only appears after tapping on a small screen (1) can be revealed by default when more space is available (2).

Menu items (1) can transform into icons in a toolbar on a larger screen (2)
Menu items (1) can transform into icons in a toolbar on a larger screen (2).

Reposition ​

An interface, and the components that comprise it, can reflow or reposition to take advantage of additional screen space. Repositioning is also a way to address changing ergonomics and input methods on different screen sizes.

Elements in a single-column format can reflow to fill the content area on a larger screen
Elements in a single-column format can reflow to fill the content area on a larger screen.

Horizontal tabs can reflow into a vertical list on a larger screen
Horizontal tabs can reflow into a vertical list on a larger screen.

A bottom sheet with menu items on a small screen be swapped for a menu on a larger screen
A bottom sheet with menu items on a small screen be swapped for a menu on a larger screen.

The Floating Action Button can be repositioned to account for the ergonomics of a larger screen
The Floating Action Button can be repositioned to account for the ergonomics of a larger screen.
Pager
Previous pageSpacing methods
Next pageApplying density

Released under the Apache-2.0

Copyright © 2018-Present Google

https://m2.material.io/design/layout/component-behavior.html

Released under the Apache-2.0

Copyright © 2018-Present Google