Only 1 label button (with label and optional icon) is allowed per template.
Button order is specified by the app.
Android Auto example
AAOS example
Template support
All templates support the action strip. Sometimes the action strip can reside in
the header.
Guidance
Use action strips for secondary or tertiary actions, rather than primary actions
– except on the Navigation template.
For details about when the action strip is displayed on the Navigation template
and when it’s hidden, refer to Visibility of action strips.
On templates with maps, the action strip can include up to 4 buttons, as shown
in these examples.
Android Auto exampleAndroid Auto example
Android Auto example
Pan mode
In pan mode, only the full-screen map and map action strip buttons are
visible. Pan mode is used for rotary and touchpad inputs.
For the pan button, apps can provide 2 icons: one for entering pan mode,
and one for exiting. The icon for exiting pan mode should clearly indicate
that it provides a way to exit. For example, this button can show an
**X**.
Visibility of action strips
The app library generally takes care of showing and hiding the action strip and
map action strip in the map-based templates based on user interactions, as shown
below.
When a map-based template opens, the action strip and map action
strip are visible. If 10 seconds go by with no user interaction, and if the
action strip and map action strip do not have user focus for rotary input,
they disappear. (Exceptions are noted below.)When the action strip and map action strip are hidden, any user
interaction with the screen will cause them to reappear.
Exceptions
Apps can flag actions in either action strip as persistent to keep them from
disappearing.
The app library may hide the action strip on small screens after 10 seconds
even when there is rotary focus, to minimize clutter.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eAction strips provide quick access to secondary or tertiary actions in Android Auto and AAOS apps using buttons, with limits depending on the template used.\u003c/p\u003e\n"],["\u003cp\u003eTemplates with maps can have an action strip with up to 4 buttons and may include a pan mode for rotary and touchpad input.\u003c/p\u003e\n"],["\u003cp\u003eAction strips and map action strips automatically hide after 10 seconds of user inactivity, except for persistent actions or on small screens.\u003c/p\u003e\n"],["\u003cp\u003eApps should not use both an action strip and a floating action button simultaneously.\u003c/p\u003e\n"],["\u003cp\u003eAction strips are generally used for secondary actions, except in the Navigation template where they may contain primary actions.\u003c/p\u003e\n"]]],[],null,["# Action strip\n\n\u003cbr /\u003e\n\nAction strips put secondary or tertiary actions a tap away.\n\n**Includes**:\n\n- Action [buttons](/cars/design/create-apps/apps-for-drivers/components/button) (up to 2, except for [templates with maps](#map-templates), which allow up to 4)\n\nOnly 1 label button (with label and optional icon) is allowed per template.\nButton order is specified by the app. \nAndroid Auto example\n\nAAOS example\n\n\u003cbr /\u003e\n\nTemplate support\n----------------\n\nAll templates support the action strip. Sometimes the action strip can reside in\nthe [header](/cars/design/create-apps/apps-for-drivers/components/header).\n\nGuidance\n--------\n\nUse action strips for secondary or tertiary actions, rather than primary actions\n-- except on the [Navigation template](/cars/design/create-apps/apps-for-drivers/templates/navigation-template).\nFor details about when the action strip is displayed on the Navigation template\nand when it's hidden, refer to [Visibility of action strips](#visibility).\n\nDo not include both an action strip and a\n[floating action button](/cars/design/create-apps/apps-for-drivers/components/fab)\nat the same time.\n| **Note:** Templates for navigation apps can also have a [map action strip](/cars/design/create-apps/apps-for-drivers/components/map-action-strip) with map interactivity buttons.\n\nAction strip on template with maps\n----------------------------------\n\nOn templates with maps, the action strip can include up to 4 buttons, as shown\nin these examples.\nAndroid Auto example Android Auto example \nAndroid Auto example\n\n\u003cbr /\u003e\n\nPan mode\n--------\n\nIn pan mode, only the full-screen map and map action strip buttons are\nvisible. Pan mode is used for rotary and touchpad inputs.\n\nFor the pan button, apps can provide 2 icons: one for entering pan mode,\nand one for exiting. The icon for exiting pan mode should clearly indicate\nthat it provides a way to exit. For example, this button can show an\n\\*\\*X\\*\\*.\n\n\u003cbr /\u003e\n\n| **Note:** Apps must include a pan button in the map action strip in order to enable user panning on all screen types, even though the pan button does not display on touch screens. Including the pan button causes touch gestures for map interactivity to be forwarded to the app.\n\nVisibility of action strips\n---------------------------\n\nThe app library generally takes care of showing and hiding the action strip and\nmap action strip in the map-based templates based on user interactions, as shown\nbelow.\nWhen a map-based template opens, the action strip and map action strip are visible. If 10 seconds go by with no user interaction, and if the action strip and map action strip do not have user focus for rotary input, they disappear. (Exceptions are noted below.) When the action strip and map action strip are hidden, any user interaction with the screen will cause them to reappear.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### Exceptions\n\n1. Apps can flag actions in either action strip as persistent to keep them from disappearing.\n2. The app library may hide the action strip on small screens after 10 seconds even when there is rotary focus, to minimize clutter."]]