Overview
Buttons express what action will occur when the user clicks or touches it. Buttons are used to initialize an action, either in the background or foreground of an experience.
Usage
Use when
- Affording interaction to key behaviors and features.
- Confirming or submitting information entered into a form.
- Cancelling and action.
- Resetting a form or dataset.
- Closing a container or section.
- Opening a menu.
- Moving forward or backward through a wizard-type workflow.
- Creating an object within a group.
- Applying a non-critical action to a dataset.
Don’t use when
- Displaying a collection of links to sections. Use links instead.
- Linking to an external site. Use links instead.
- An action is less important. Consider using a link instead.
- Presenting the user with one or more high or medium-high -actions specific to a task.
Types
Primary Buttons
Use to draw attention to the primary action on a screen. There are four types of primary mobile buttons:
- Default Mobile Buttons: Use to draw attention to the primary action on a screen. You may choose a Default or Pill style for your primary buttons, but NOT BOTH.
- Stacked Mobile Buttons: Use as a primary button with a leading icon, if horizontal screen space is limited (e.g., in bottom/ footer navigation).
- Pill Buttons: Use to draw attention to the primary action on a screen. You may choose a Default or Pill style for your primary buttons, but NOT BOTH.
- Floating Action Buttons: 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 (e.g., “float” above all other content).
Button Progressions
There are two button progressions you can choose from: structural and color progression. The choice should be based on the particular needs of the product’s intended usage, aesthetic, and/or target user’s needs. Use only one button progression in a single product. Ancillary button types can be used in either progression.
Structural
| Example | Emphasis | When to use |
|---|---|---|
|
| High | Use to draw attention to the primary action on a screen. You may choose a Default or Pill style for your primary buttons, but NOT BOTH. |
|
| Medium | Use for secondary actions on a screen. Outline-style buttons work well on colored, dark, or image backgrounds. Consider how the style of an outline button might better suit the page. |
|
| Medium | Used for secondary actions to establish additional visual hierarchy. |
Color
| Example | Emphasis | When to use |
|---|---|---|
|
| High | Use to draw attention to the primary action on a screen. You may choose a Default or Pill style for your primary buttons, but NOT BOTH. |
|
| Medium | Use for secondary actions on a screen. These Buttons can be used on most pages without constrictions. They appear most often in high volume use cases like Tables, or in an Action Bar. Consider using an outline button on gray backgrounds. |
|
| Medium | Used for secondary actions to establish additional visual hierarchy or to use a secondary button that provides less emphasis. |
Ancillary Buttons
| Type | Example | Emphasis | When to use |
|---|---|---|---|
| FAB |
| High | Use a FAB for the most common or important action on a screen. |
| Icon Only |
| Medium | Primary use is in-line or in “Button Groups.” |
| Danger |
| High | Danger buttons have a different visual style to inform users of potentially destructive actions they are about to take. If using the danger button as a standalone, we recommend styling it as a secondary button. Within a set, the danger button should be styled as a primary button. |
