A button communicates an action that will occur when a user touches it.
Buttons are standard Android Open Source Project (AOSP) components. They can either be filled with a solid background color, or unfilled (with a transparent background). Filled buttons indicate a primary or preferred action. Buttons can appear independently or in groups – unlike tabs, which always appear in groups.
Anatomy

2. Filled button container, indicating the primary or preferred action
3. Button label
Specs
Button min and max length

Button with icon vs. default button

Buttons can appear as elements in other components, such as the app bar or dialogs.
Button placement in app bar

Button in dialog

Hero button

Customization
OEMs can reflect their brand by modifying a button's visual appearance, such as:
- Specifying an accent color
- Supplying custom icons
- Adding custom fonts
- Changing the appearance of active, inactive, and disabled buttons
- Setting button dimensions, corner shape, and placements
- Using motion to provide feedback to users
The Car UI Library Integration Guide provides OEM guidance for customizing components.
Design system provides specific guidance for using layout, color, typography, sizing, shape, and motion to customize components.
Examples




