# Build media apps with MediaBrowserService

<br />

To create a media app with limited branding and customization, use the
MediaBrowserService (MBS). This is a lower-cost experience to let users browse
content and play media.

Because most aspects of the media UI are controlled by car makers and Google
(see [Partner roles for media](https://developers.google.com/cars/design/create-apps/media-apps/overview#roles)), the design-related tasks for app
developers are relatively simple.

Here are the basic tasks for app developers:

1. [Plan navigation tabs](https://developers.google.com/cars/design/create-apps/media-apps/navigation-tabs): Choose up to 4 top-level views of content and decide on icons or labels for navigation tabs.
2. [Plan browsing views](https://developers.google.com/cars/design/create-apps/media-apps/browsing-views): Plan how top-level and lower-level views of content will be organized and formatted (grid or list?).
3. [Customize playback
   controls](https://developers.google.com/cars/design/create-apps/media-apps/customize-playback-controls): Decide whether you want to provide custom actions and icons and whether to implement a queue.
4. [Plan voice actions](https://developers.google.com/cars/design/create-apps/media-apps/voice-actions): Determine which commands you would like users to be able to request by voice
5. [Provide branding
   elements](https://developers.google.com/cars/design/create-apps/media-apps/branding-elements): Provide your app icon and accent color to represent your brand.

**Optional extra steps for AAOS only**:

1. [Create a sign-in flow](https://developers.google.com/cars/design/create-apps/media-apps/signin-flow): Use the available templates to create a sign-in flow for users to sign in to your app on the car screen (if your app requires sign-in).
2. [Create settings](https://developers.google.com/cars/design/create-apps/media-apps/design-settings): Create in-vehicle settings screens for your app, if settings are needed.

**Optional extra step for Android Auto only**:

1. [Provide
   recommendations](https://developers.google.com/cars/design/create-apps/media-apps/recommendations): Identify 10 items of media content to be showcased as recommended

Use the aforementioned links to access more detailed guidance about each task.
For a summary of the design elements you'll need to provide, consult the
checklist.

## Partner roles for media

For apps running on AAOS-based
vehicles, car makers can customize the UI to reflect their brand and vehicle
styling. For apps running in Android Auto, Google creates a consistent look and
feel for the app across the range of compatible vehicles.
The following table
summarizes the design roles of app developers and car makers (in
AAOS) in ensuring a unified media app experience.

| Aspect of the media experience | Car maker's design role (or Google's, for Android Auto) | App developer's design role |
|---|---|---|
| **Navigating media apps** | Decide where the app bar goes and support app navigation and controls that can appear in the app bar | Decide which top-level content views to represent in the app bar's tabs and provide icons and labeling as needed (see [Plan navigation tabs](https://developers.google.com/cars/design/create-apps/media-apps/navigation-tabs)) |
| **Browsing content details** | Determine size and content of grid or list items and implement app header at lower levels of content | Determine format (grid or list) and organization for browsable media content at each level (see [Plan browsing views](https://developers.google.com/cars/design/create-apps/media-apps/browsing-views)) |
| **Playing media** | Implement playback view and minimized control bar with appropriate media metadata and playback controls, including controls for any custom actions in the app. Provide a queue affordance in playback view and styling for the queue. | Decide whether to implement custom actions on the control bar, and provide icons for them. Also decide whether to implement a queue and whether to provide an indicator for the currently playing track (see [Customize playback controls](https://developers.google.com/cars/design/create-apps/media-apps/customize-playback-controls)) |
| **Voice actions** | Provide Google Assistant UI and control how users invoke Assistant in specific cars | Specify which media categories to support for voice requests and what content to supply for generic requests ([Plan voice actions](https://developers.google.com/cars/design/create-apps/media-apps/voice-actions)) |
| **Brand attribution** | Display the app icon on all content screens and choose where to apply the third-party app color as an accent | Provide app icon and specify accent color (See [Provide branding elements](https://developers.google.com/cars/design/create-apps/media-apps/branding-elements)) |
| **Sign-in and settings** | Provide a settings affordance for search and settings on the app bar bar and connect users to sign-in screens as needed | Use templates to create a sign-in flow and settings screens. If needed, see [Adapt sign-in flow](https://developers.google.com/cars/design/create-apps/media-apps/signin-flow) and [Design settings](https://developers.google.com/cars/design/create-apps/media-apps/design-settings) |
| **Recommendations** | Provide UI for content recommendations to appear | Provide a source for appropriate content recommendations |