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

Confirmation & acknowledgement ​

Confirmation and acknowledgement communications ask for confirmation before taking an action and acknowledge successful actions.

Usage ​

Confirming and acknowledging user actions can reduce uncertainty about an action that a user has taken, or is about to take. They also prevent users from making mistakes.

Types of actions ​

  • Confirming actions ask the user to verify that they want to proceed with an action.
  • Acknowledging actions provide text to let the user know whether an action they chose has been completed.

Not all actions warrant a confirmation or an acknowledgement.

Confirmation ​

Usage ​

When a UI requests confirmation from a user, it asks if they want to proceed with the action they just took. It may be paired with a warning or critical information related to that action.

Confirmation isn't necessary when the consequences of an action are reversible or negligible. For example, if a check mark shows an image has been selected, further confirmation is unnecessary.


Alert dialogs

Dialogs inform users about a task and can contain critical information, require decisions, or involve multiple tasks.

Related article

Alert dialog ​

Confirmation is best delivered using an alert dialog.

An alert dialog confirming deletion and two actions a user can take to leave the dialog
An alert dialog confirming deletion and two actions a user can take to leave the dialog.
An alert dialog confirms the user action and informs the user of what will happen as a result
An alert dialog confirms the user action and informs the user of what will happen as a result.

Acknowledgement ​

Usage ​

An acknowledgement notifies the user about system actions occurring in the background. It appears for a short amount of time and may include an option to undo the action.

An acknowledgement in the form of a snackbar appears, then fades after a few seconds
An acknowledgement in the form of a snackbar appears, then fades after a few seconds.
An acknowledgement appears with an undo option
An acknowledgement appears with an undo option. It remains until the user takes an unrelated action, such as scrolling through a list.

Acknowledgement components ​

Acknowledgements can be delivered by a variety of components. Criteria for choosing the right acknowledgement component includes:

  • Urgency level
  • Inclusion of an action to correct a problem
  • Duration on screen (transient, dismissable, or both)

Acknowledgements that are transient mean the component will exit on its own within a few seconds of appearing. Dismissable acknowledgements can be dismissed by selecting an action to dismiss the component.

ComponentUrgencyContentBehaviorNumber of actions to dismiss
SnackbarLowInformationalTransient & dismissable0-1
AlertMediumCorrect a problem; Awareness of statePersistent, non-blocking, and dismissable1-2
DialogHighRequire a choice; AcknowledgePersistent, blocking (interruptive)1-2
Empty StateMediumInformationalPersistent, blocking0-2

Alert ​

Use alerts to deliver a persistent, in-app message that informs users of a particular change state.

An alert
An alert

Snackbar ​

Use a snackbar to provide brief feedback about an operation.

A snackbar
A snackbar

Empty state

When a UI is only available online and content has failed to load or sync, use an empty state. The user should be able to interact with as much of the rest of the app as possible. A link to reload can be presented to help a user accomplish their task.

Snackbar: an empty state
An empty state

Banners

A banner displays a prominent message and related optional actions.

Related article

Snackbars

Snackbars provide brief messages about app processes at the bottom of the screen.

Related article

Empty states

Empty states occur when an item's content can't be shown.

Related article

Pager
Previous pageStates
Next pageData formats

Released under the Apache-2.0

Copyright © 2018-Present Google

https://m2.material.io/design/communication/confirmation-acknowledgement.html

Released under the Apache-2.0

Copyright © 2018-Present Google