Stay organized with collections
Save and categorize content based on your preferences.
Android Automotive OS presents media content on a car’s screen and allows users to browse and play content in a vehicle-optimized environment.
How media apps work in cars
Android Automotive OS includes a set of APIs that handle playback and browsing experiences for media apps in cars. These APIs allow app developers to take advantage of a standard template for media apps, including:
Navigation and playback controls
Browseable views of media content
App controls for in-app search and settings
This template supports the in-vehicle infotainment (IVI) experience in two ways:
Car makers can customize the look and feel of the interface to fit their cars and their brand.
App developers can connect their content to the interface to provide a consistent experience that reflects their app’s brand across multiple cars and manufacturers.
Google is designing the basic user experience for media apps based on safety considerations and principles such as those discussed in Design foundations and Visual principles. Car makers can adapt aspects of this user experience for their own infotainment systems without disrupting the functionality of apps that are built for Android Automotive OS.
For example, while one car maker's media apps might look and feel different from another's, a media app user will interact with that app's familiar controls no matter what type of car they're driving. At the same time, in a single type of car, switching from one media app to another will not change the basic browsing and playback operations involved in using media apps in that car.
Describes the primary, top-level navigation model based on tabs (plus variations for special cases) and controls for opening app-specific search and settings overlays
Describes how secondary navigation works within the content space, as users navigate from high-level views of content to more detailed views at deeper levels
[null,null,["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eAndroid Automotive OS provides a standardized template for media apps, allowing for consistent user experiences across different car manufacturers.\u003c/p\u003e\n"],["\u003cp\u003eCar makers can customize the look and feel of media app interfaces to match their branding while maintaining core functionalities.\u003c/p\u003e\n"],["\u003cp\u003eUsers interact with familiar media app controls regardless of the car they are driving, ensuring a seamless experience.\u003c/p\u003e\n"],["\u003cp\u003eThe system supports navigation, browsing, playback, and additional features like search and settings within media apps.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can leverage provided APIs to integrate their content, contributing to a unified and user-friendly in-car media experience.\u003c/p\u003e\n"]]],[],null,["# Interaction model\n\n\u003cbr /\u003e\n\nAndroid Automotive OS presents media content on a car's screen and allows users to browse and play content in a vehicle-optimized environment.\n\n*** ** * ** ***\n\nHow media apps work in cars\n---------------------------\n\nAndroid Automotive OS includes a set of APIs that handle playback and browsing experiences for media apps in cars. These APIs allow app developers to take advantage of a standard template for media apps, including:\n\n- Navigation and playback controls\n- Browseable views of media content\n- App controls for in-app search and settings\n\nThis template supports the in-vehicle infotainment (IVI) experience in two ways:\n\n- Car makers can customize the look and feel of the interface to fit their cars and their brand.\n- App developers can connect their content to the interface to provide a consistent experience that reflects their app's brand across multiple cars and manufacturers.\n\nGoogle is designing the basic user experience for media apps based on safety considerations and principles such as those discussed in [Design foundations](/cars/design/design-foundations) and [Visual principles](/cars/design/design-foundations/visual-principles). Car makers can adapt aspects of this user experience for their own infotainment systems without disrupting the functionality of apps that are built for Android Automotive OS.\n\nFor example, while one car maker's media apps might look and feel different from another's, a media app user will interact with that app's familiar controls no matter what type of car they're driving. At the same time, in a single type of car, switching from one media app to another will not change the basic browsing and playback operations involved in using media apps in that car.\n\n*** ** * ** ***\n\nWhat's in this section\n----------------------\n\n[](/cars/design/automotive-os/apps/media/interaction-model/navigating) [Navigating media apps\n---------------------](/cars/design/automotive-os/apps/media/interaction-model/navigating)\n\n\nDescribes the primary, top-level navigation model based on tabs (plus variations for special cases) and controls for opening app-specific search and settings overlays\n[](/cars/design/automotive-os/apps/media/interaction-model/browsing) [Browsing content details\n------------------------](/cars/design/automotive-os/apps/media/interaction-model/browsing)\n\n\nDescribes how secondary navigation works within the content space, as users navigate from high-level views of content to more detailed views at deeper levels \n[](/cars/design/automotive-os/apps/media/interaction-model/playing-media) [Playing media\n-------------](/cars/design/automotive-os/apps/media/interaction-model/playing-media)\n\n\nDescribes how users can play media content using controls supplied by car makers and app developers\n[](/cars/design/automotive-os/apps/media/interaction-model/signin-settings-search) [Sign-in, settings \\& search\n---------------------------](/cars/design/automotive-os/apps/media/interaction-model/signin-settings-search)\n\n\nDescribes how car makers support in-app search and access to app settings and sign-in flows"]]