Skip to content

Most visited

Recently visited


Building and Displaying a Pop-Up Message

This lesson teaches you to

  1. Use a CoordinatorLayout
  2. Display a Message

You should also read

You can use a Snackbar to display a brief message to the user. The message automatically goes away after a short period. A Snackbar is ideal for brief messages that the user doesn't necessarily need to act on. For example, an email app could use a Snackbar to tell the user that the app successfully sent an email.

Use a CoordinatorLayout

A Snackbar is attached to a view. The Snackbar provides basic functionality if it is attached to any object derived from the View class, such as any of the common layout objects. However, if the Snackbar is attached to a CoordinatorLayout, the Snackbar gains additional features:

The CoordinatorLayout class provides a superset of the functionality of FrameLayout. If your app already uses a FrameLayout, you can just replace that layout with a CoordinatorLayout to enable the full Snackbar functionality. If your app uses other layout objects, the simplest thing to do is wrap your existing layout elements in a CoordinatorLayout, as in this example:


    <!-- Here are the existing layout elements, now wrapped in
         a CoordinatorLayout -->

        <!-- …Toolbar, other layouts, other elements… -->



Make sure to set an android:id tag for your CoordinatorLayout. You need the layout's ID when you display the message.

Figure 1. The CoordinatorLayout moves the FloatingActionButton up when the Snackbar appears.

Display a Message

There are two steps to displaying a message. First, you create a Snackbar object with the message text. Then, you call that object's show() method to display the message to the user.

Creating a Snackbar object

Create a Snackbar object by calling the static Snackbar.make() method. When you create the Snackbar, you specify both the message it displays, and the length of time to show the message:

Snackbar mySnackbar = Snackbar.make(view, stringId, duration);
The view to attach the Snackbar to. The method actually searches up the view hierarchy from the passed view until it reaches either a CoordinatorLayout, or the window decor's content view. Ordinarily, it's simplest to just pass the CoordinatorLayout enclosing your content.
The resource ID of the message you want to display. This can be formatted or unformatted text.
The length of time to show the message. This can be either LENGTH_SHORT or LENGTH_LONG.

Showing the message to the user

Once you have created the Snackbar, call its show() method to display the Snackbar to the user:;

The system does not show multiple Snackbar objects at the same time, so if the view is currently displaying another Snackbar, the system queues your Snackbar and displays it after the current Snackbar expires or is dismissed.

If you just want to show a message to the user and won't need to call any of the Snackbar object's utility methods, you don't need to keep the reference to the Snackbar after you call show(). For this reason, it's common to use method chaining to create and show a Snackbar in one statement:

Snackbar.make(findViewById(, R.string.email_sent,
This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields


Follow Google Developers on WeChat

Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a short survey?
Help us improve the Android developer experience. (April 2018 — Developer Survey)