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

Cross-platform adaptation ​

Material Design supports design and usability best practices across platforms to help create beautiful user experiences.

When to adapt ​

Material Design is built on a foundation of best practices in the fields of both traditional and web design, and is informed by user experience research and cognitive science. The design guidelines that developed from research findings are intended to be applied universally across all platforms and devices.

Design conventions differ from platform to platform. These differences in convention can affect the user's ability to understand the UI or complete certain tasks. In such cases, it’s recommended to adapt to platform-specific conventions. In areas where design differences are minimally disruptive, adapting to the platform is optional.

The following guidelines indicate when to adapt to native platform conventions and adaptation is optional. Be aware that platform considerations constantly evolve, and adaptations may need to be updated.

Cross-platform guidelines ​

Toolbars ​

Toolbars are commonly used to frame the context of a screen. On iOS, toolbars are called navigation bars and their height is shorter than the Android version. On Android, toolbars are called top app bars.

It’s recommended to use a platform’s default text alignment for toolbar titles, unless multiple action buttons are present.

Titles are left-aligned by default in top app bars
Android
Titles are left-aligned by default in top app bars.
Titles are center-aligned by default in navigation bars
iOS
Titles are center-aligned by default in navigation bars.

When multiple actions, or even no actions, appear on the right side, top app bar titles are always left-aligned
Android
When multiple actions, or even no actions, appear on the right side, top app bar titles are always left-aligned.
When multiple action buttons are on the right side, or on the home screen of an application, titles may be left-aligned
iOS
When multiple action buttons are on the right side, or on the home screen of an application, titles may be left-aligned.

Translucency ​

Material Design uses shadows to express elevation in app bars. In iOS, products can use translucency to differentiate app bars from content.

Use shadow to express elevation
Android
Use shadow to express elevation.
Products have the option to use translucency to express elevation in iOS
iOS
Products have the option to use translucency to express elevation in iOS. Use a hairline as a bottom border of the app bar to ensure differentiation between the top app bar and scrolling content.

Iconography ​

System icons are used to represent many universally available actions for the platform.

The up button contains a thin arrow with a stem
Android
The up button contains a thin arrow with a stem.

On iOS, the back arrow is thicker and doesn’t have a stem
iOS
On iOS, the back arrow is thicker and doesn’t have a stem.
On iOS, the back arrow may also include a label for the associated destination
iOS
On iOS, the back arrow may also include a label for the associated destination.

The action overflow menu icon (indicated by the “More…” symbol) contains three vertical dots
Android
The action overflow menu icon (indicated by the “More…” symbol) contains three vertical dots.
The action overflow menu icon (indicated by the “More…” symbol) contains three horizontal dots
iOS
The action overflow menu icon (indicated by the “More…” symbol) contains three horizontal dots.

Controls ​

Controls should clearly indicate how users should interact with them.

Use Material switches, checkboxes, and radio buttons
Android
Use Material switches, checkboxes, and radio buttons.
Native platform switches should be used as they have matching functionality and presentation as Material switches
iOS
Native platform switches should be used as they have matching functionality and presentation as Material switches.

Use switches instead of checkboxes and check mark lists instead of radio buttons as these are the graphics expected on iOS.

Communication ​

Dialogs ​

Dialogs inform users about critical tasks that require a decision and they can contain multiple actions. On iOS there are components that perform similar functions to dialogs on Android, such as alerts and action sheets. Look at the number of actions and their text length to decide which component (Alert or Action Sheet) to use when adapting a dialog component to iOS.

Use Alerts when there are two actions with short text labels that fit horizontally.

Use a simple dialog when displaying two actions
Android
Use a simple dialog when displaying two actions.
You have the option to use an alert when displaying two actions
iOS
You have the option to use an alert when displaying two actions.

When there are three or more actions with long text labels in a Material dialog, products may use iOS action sheets or bottom sheets.

Stack actions if a text label is long
Android
Stack actions if a text label is long.

Gestures ​

Edge swipe ​

An edge swipe starts from the outer edge of the screen to reveal off-screen content.

Edge swipes can conflict with other swipe gestures, such as horizontal swipes through pages or table rows. To avoid conflicts, an edge swipe should perform the same behavior as any other swipe that exists over a content area.

Android
When conflicting gestures are not present, performing an edge swipe from the left reveals off-screen content, such as a navigation drawer.
iOS
When conflicting gestures are not present, performing an edge swipe from the left navigates the user back in an app’s hierarchy.

Transitions ​

Transitions use motion to help users navigate an app by illustrating the relationship between UI elements. It is recommended to use the platform defaults as a starting point for implementing motion for transitions.

Android
The default transition on Android uses scale to indicate moving forward and backward in a navigation flow.
iOS
The default transition on iOs uses horizontal translation to indicate moving forward and backward in a navigation flow.

Typography ​

Typography communicates both text content and branding. In both cases, text must be accessible and resizable.

If your app already uses a brand specific typeface for branding, it’s recommended to use it in moderation throughout the app.

The default typeface on Android is Roboto
Android
The default typeface on Android is Roboto. On Android text size should be specified in scalable pixels to allow type to be resized using accessibility features.
The default typeface on iOS is San Francisco
iOS
The default typeface on iOS is San Francisco. Using this typeface is the easiest way to implement accessibility features like Dynamic Type. Using other typefaces may require adjustments to get the same accessibility features.

Pixel density

Material Design layout encourages consistency across platforms, environments, and screen sizes by repeating visual elements and using consistent spacing.

Related article

Type scale

Use typography to present your design and content as clearly and efficiently as possible.

Related article

Google Fonts

Making the web more beautiful, fast, and open through great typography.

Related link

Pager
Previous pageAndroid widget
Next pageApp bars: bottom

Released under the Apache-2.0

Copyright © 2018-Present Google

https://m2.material.io/design/platform-guidance/cross-platform-adaptation.html

Released under the Apache-2.0

Copyright © 2018-Present Google