Design system. Components Flashcards
Snackbars
Snackbars contain a single line of text directly related to the operation performed. They may contain a text action, but no icons.
Snackbars provide brief feedback about an operation through a message at the bottom of the screen.
Usage
Only one snackbar may be displayed at a time. Each snackbar may contain a single action, neither of which may be “Dismiss” or “Cancel.”
Toasts
(Android only) are primarily used for system messaging. They also display at the bottom of the screen, but may not be swiped off-screen.
Dialogs
Dialogs provide important prompts in a user flow.
Dialogs can require an action, communicate information, or help users accomplish a task. There are two types of dialogs: basic and full-screen.
Dialogs focus user attention to ensure their content is addressed
Dialogs should be direct in communicating information and dedicated to completing a task
Dialogs should appear in response to a user task or an action, with relevant or contextual information
Date picker
Date pickers let people select a date, or a range of dates.
There are three kinds of date pickers: docked date picker, modal date picker, and modal date input.
Date pickers can display past, present, or future dates relevant to a task
Clearly indicate important dates, such as current and selected days
To ensure picking a day or time is intuitive, use common picker patterns, such as a calendar
Badges
Badges are used as indicators to convey dynamic information, such as counts or status. A badge can include labels or numbers.
Bottom App Bars
Bottom app bars display navigation and key actions at the bottom of mobile screens.
Bottom sheets
Bottom sheets are surfaces containing supplementary content, anchored to the bottom of the screen.
Buttons
Buttons help people take action, such as sending an email, sharing a document, or liking a comment.
There are five types of common buttons: elevated, filled, filled tonal, outlined, and text.
Choose the type of button based on the importance of the action. The more important the action is, the more emphasis its button should have.
Cards
Cards contain content and actions that relate information about a subject.
A card is identifiable as a single, contained unit
A card can hold anything from images to headlines, supporting text, buttons, lists, and other components
A card’s layout and dimensions depend on its contents. There is no one right way to make a card.
Checkboxes
Checkboxes allow users to select one or more items from a set and can be used to turn an option on or off. They’re a selection control that often appears when users are asked to pick a choice from options.
Chips
Chips help people enter information, make selections, filter content, or trigger actions.
There are four types of chips: assist, filter, input, and suggestion.
Chips can show multiple interactive elements together in the same area, such as a list of selectable movie times, or a series of email contacts.
Chips represent options in a specific context, unlike buttons, which are persistent
Dividers
A divider is a thin line that groups content in lists and layouts.
FAB
Use a FAB for the most common or important action on a screen
Icons in a FAB must be clear and understandable since these buttons do not have a text label
The FAB should persist on the screen when content is scrolling
Icon buttons
Icon buttons help people take supplementary actions with a single tap.
Use icon buttons when a compact button is required, such as in a toolbar or image list. There are two types of icon buttons: standard and contained.
con buttons can take the form of a wide range of system icons
Ensure the meaning of the icon is unambiguous
On hover, include a tooltip that describes the button’s action, rather than the name of the icon itself
Use the outline-style icons to indicate an unselected state and a filled style to indicate selection
Lists
Lists are continuous, vertical indexes of text or images.
Lists consist of one or more list items, and can contain actions represented by icons and text. List items come in three sizes: one-line, two-line, and three-line.
Lists should be sorted in logical ways that make content easy to scan, such as alphabetical, numerical, chronological, or by user preference
Lists present content in a way that makes it easy to identify a specific item in a collection and act on it
Lists should present icons, text, and actions in a consistent format
Menu
Menus display a list of choices on a temporary surface.
Menus appear when users interact with a button, action, or other control.
They can be opened from a variety of elements, most commonly icon buttons, buttons, and text fields.
Menus should be easy to open, close, and interact with
Menu content should be suited to user needs
Menu items should be easy to scan