- Labeling and bringing awareness to a specific element or feature (e.g., something is new or required)
- Providing feedback at the element level (e.g., displaying error messages). Use inline text instead.
- Requiring interaction from users, since Badges are always static and non-interactive
For general Badge best practices, refer to the Badge web documentation.
- Use only one or two words to describe Badge status
- Badge must always be paired with the element that they’re associated with
- Avoid displaying multiples Badges in the same experience, since they label a state to an element
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:
Badge text must be clear so that users can understand the status without relying only on Badge color.
Badge is available in six styles. Each type has a semantic meaning and represents a sentiment.
- Info (default)
Communicates helpful information or an important attribute. For example, ‘New’ or ‘Help’.
Indicates a constructive or successful state. For example, 'Available', 'Completed', 'Approved' or 'Added'.
Communicates cautionary or time-sensitive information to the user. For example, 'Busy', 'Missing' or 'Warning'.
Informs the user of problems or errors that require potential action to correct. For example, 'Deleted' or 'Cancelled'.
Indicates a general, non-critical status update. For example, 'Unavailable' or 'Not started'.
Highlights a suggestion that will improve the experience and achieve better results. For example, 'Recommended for you'.
Light wash / Dark wash
Badge with wash style may be used over media.
- Light wash
The light wash badge should be used over media that is dark or utilizes a dark gradient overlay.
- Dark wash
The dark wash badge should be used over media that is light or utilizes a light gradient overlay.
For writing best practices, refer to the Content standards.
- Use a single word to describe the status of an element. For example, “New” not “New post”
- Where applicable, describe the status in past tense. For example, “Archived” not “Archive”
- Use conflicting language with defined type sentiments. For example, the error badge should not say “Complete”