- Briefly acknowledging a user action without interrupting their flow.
- When acknowledging an action that relates to another surface, provide a link that navigates the user to that surface.
- To undo actions after acknowledgement, if there isn’t already a way to do so on the current surface.
- For system processes like showing that a process is loading, or when there are internet connectivity issues.
- When, due to an error, a user can’t even continue performing basic tasks like browsing already loaded Pins.
- When asking a user to confirm that they want to perform an action. Use Sheet instead.
- When you want to suggest a user spend more money or try new features; use Upsell instead.
- For errors that relate to a specific section or page. Use Callout or SlimBanner instead.
Place Toasts out of the way so that a user can still navigate and complete tasks. Keep a top or bottom margin that is the same size as the left and right margins.
Block navigation controls with Toasts or align too close to the edge of a navigation bar.
Show one Toast at a time, with errors and acknowledgements taking priority.
Stack multiple toasts as that will block the user.
Include a way to dismiss the toast when it is actionable or contains multiple lines of text. Mobile toasts can be dismissed via swiping up if placed on the top or down if placed on the bottom.
Leave toasts on screen for a long time without a way to dismiss. Exceptions are blocking error toasts where a user can’t take any action until the error is resolved.
People use Android’s accessibility features, such as TalkBack and dynamic text sizing to personalize how they interact with their devices. Supporting these personalizations ensures that everyone has a great user experience. See Material Design and development documentation about accessibility for Android:
Accessbile design on Android
Accessible development on Android
Some people may take longer to read toasts than others due to low vision or cognitive impairments. Use the guide below to set duration for Toasts:
- Brief text of approximately 10–15 words (including button text): 5 seconds
- Longer than 15 words: Slow readers can read about 125–200 words per minute. Base your duration on the slowest number. For example, a toast with 20 words should be set to 10s. Source
Use these tokens for applying size and color styles to Toast.
A generic acknowledgment after an action is taken.
Used rarely for connection issues or unknown errors where we don’t want to completely block the users flow, but want the message to persist if the user goes to another surface. Providing a way to solve the error or get help is recommended.
A simple, generic acknowledgment after an action is taken. These should not be actionable.
With an image for Pin or Board actions.
With an Avatar for Profile or Pinner-related messaging. An optional link can be included. When there’s a link on mWeb, the entire toast is tappable, using TapArea.
As a secondary element, to drive users to another surface, or change a recently completed action.
Toast with link
As a secondary element, to drive users to another surface.
Placement is always centered at the top or bottom of the screen and not blocking any navigation or important buttons.
- Consider internationalization and how other languages may be take up more space
- Be brief and concise
- Use conversational language
- Use lengthy, technical jargon or local idioms that will be hard to translate to other languages