# Plan voice actions

<br />

Supporting voice actions helps users find and play media by talking to Google
Assistant, so they can keep their eyes on the road.

Google and car makers control how users invoke Google Assistant, typically via
hotword ("Hey, Google" or "Hey, G"), steering wheel button, or onscreen
affordance. Once invoked, Google Assistant can recognize requests to play
app-supported categories of media, as well as requests to pause media play or
advance to the next track.

To optimize the voice experience for your users, you need to:

- Decide which media categories to support. Possible categories for voice actions include genre, artist, album, playlist, and title. Choose those that make sense for your app.
- Anticipate non-specific requests. Decide how you want your app to respond to requests that don't ask for specific media content, such as "Play some music."

> [!NOTE]
> **Note:** For details about how to build support for voice actions into your app, consult [Support voice actions](https://developer.android.com/training/cars/media#support_voice) and [Google Assistant and media apps](https://developer.android.com/media/implement/assistant/).

## Voice plate example

![Mockup of media app home screen with a voice plate to indicate voice interaction](https://developers.google.com/static/cars/design/create-apps/media-apps/images/voice-plate-ex-1.png)

## Voice action requirements

In the table below, SHOULD requirements are recommended but not required.

| Requirement level | Requirements |
|---|---|
| **SHOULD** | App developers should: - Support voice actions for all media categories that are appropriate for their apps |

## Rationale

- **Minimize visual distraction**: Users controlling media via voice can keep their eyes on the road.