Android Auto Review Guidelines
Last updated
Last updated
ONE store provides the same principles for the app quality of Android Auto as Google's quality standards of Android apps for cars.
Android apps for cars must not disturb the driver in any way. It is recommended that drivers follow practices that can help minimize distractions, such as using voice commands and a very simple visual design, etc.
With the Desktop Head Unit (DHU), development machines can emulate Android Auto head units, allowing them to run and test Android Auto apps.
DHU runs on Windows, macOS, and Linux systems. For instructions on installing and running DHU and testing the app, please refer to the App Testing Guide for Android Auto.
This criteria ensures that the app follows the core design and interaction patterns to provide a consistent, intuitive and satisfying user experience in Android Auto. The system sets up and renders various elements, such as search windows, card backgrounds, fonts, icon colors, etc. When running on devices connected to Android Auto, the app's unique design elements must meet the following criteria:
| Type | Description |
|---|---|
When running on devices connected to Android Auto, the following criteria ensure that the app is correctly configured and functions as it is expected to.
If any violations of the guidelines are found after the app has been approved, the app may become unavailable for sale and use.
In addition, in the case of any disputes or related problems with third parties, such as vehicle manufacturers and Google, in-vehicle operation may be excluded.
Driver caution
The app does not display animated elements on the screen such as animated graphics or video.
The app does not display text-based advertising other than the advertiser’s name or the product.
The app’s element does not display any images on the screen. Exceptions include:
The app may display a single static image for content context in the background of the consumption screen, such as album art or the advertiser's corporate logo.
The app may display an icon in the content navigation drawer.
The app can display images and pictures to help drivers make decisions while driving. Navigation apps may display an image for lane guidance or junction guidance.
The app does not include any features other than the type of app designed for cars.
If the user needs to move to the phone screen (e.g. in order to comply with a permission request) the app must prompt the user to view the phone screen only when it is safe. If an Android Auto user needs to open the Phone app to resolve an error, the message must provide that information to the user. For example, the error message must say "Please sign in to [app name]" instead of "Please Log in".
Layout
The app does not automatically display scrolling texts.
Visual contrast
The app provides icons and colors that meet Android Auto’s contrast requirements.
Type
Description
Visual contrast
The app provides white icon sets that the system colorizes to provide automatic contrast compensation.
The app provides colors that the system can optimize to be read easily in the car.
Interaction
The app must support Google Assistant voice commands.
App-specific buttons respond to user actions with no more than a two-second delay
Type
Description
Driver caution
Users must be able to complete tasks on the app using no more than 5 screens.
Interaction
The app must support Google Assistant voice commands. App-specific buttons respond to user actions with no more than a two-second delay.
Type
Description
Driver caution
Users must be able to complete tasks on the app using no more than 5 screens.
Interaction
App-specific buttons respond to user actions with no more than a two-second delay.
Type
Description
Driver caution
Users must be able to complete tasks on the app using no more than 5 screens.
Interaction
App-specific buttons respond to user actions with no more than a two-second delay.
Type
Description
General
The app features function properly as described in the app’s Google Play store listing.
Notifications
The app does not present advertisements through notifications.
The app displays notifications only when relevant to the driver's needs.
Examples: Good - Notifying the user that a new message has arrived. Bad - Notifying the user about a new album release.
Type
Description
General
The app launches in no more than 10 seconds.
The app loads the content in no more than 10 seconds.
When the app is relaunched from the home screen, it restores the app state as closely as possible to the previous state.
Intentionally disabled interactive elements must not work.
Notifications
Media apps do not automatically play at startup or when the user does not select the app or app media.
Type
Description
Message
The app receives messages.
Messages are grouped and displayed in the correct order.
Users are able to respond to messages.
The app uses an app pattern designed for short messages. Traditional messaging apps in long formats, such as apps for email, are not allowed.
The app implements a P2P messaging service, but does not provide notification services, such as weather, stocks, and sports results
Type
Description
General
The app launches in no more than 10 seconds.
The app loads the content in no more than 10 seconds.
When the app is relaunched from the home screen, it restores the app state as closely as possible to the previous state.
Navigation audio channels are only available for navigation apps and navigation guidance.
Apps must not allow users to make purchases using the car screen. For example, users cannot pay for parking on the car screen.
Navigations
The app must provide navigation to guide drivers through detailed routes.
The app only draws the map content on the surface of the navigation template. Text-based detailed route guidance, lane guidance, and estimated arrival times must be displayed on the relevant components of the navigation template. Additional information related to driving (e.g. speed limits, road obstacles) can be drawn on the safe area of the map.
When the app provides detailed text-based route guidance, navigation alerts must also be triggered.
When the navigation app provides detailed text-based route guidance, the next turn information must be transmitted to the vehicle instrument panel display.
If other navigation apps provide detailed route guidance, the app must not provide detailed route guidance notifications, voice prompts, or instrument panel information.
The app must handle navigation requests from other Android Auto apps.
Apps must use light-themed or dark-themed maps when instructed to do so.
The app must provide a “test drive” mode that simulates driving.
Payments
The app must have simple flows if purchases are enabled, using shortcuts such as recent or favorite purchases.
The app must not allow any of the following:
Setup of payment methods
Multiple items to be selected for purchase
The user to commit to recurring payments (for example, subscriptions)
Type
Description
General
The app launches in less than 10 seconds.
The app loads the content in less than 10 seconds
When the app is relaunched from the home screen, it restores the app as close to its previous state as possible.
Apps must not allow users to make purchases using the car screen. For example, users cannot pay for parking on the car screen.
POI functionality
The app must provide meaningful functionality relevant to driving.
Payments
The app must have simple flows if purchases are enabled, using shortcuts such as recent or favorite purchases.
The app must not allow any of the following:
Setup of payment methods
Multiple items to be selected for purchase
The user to commit to recurring payments (for example, subscriptions)
Type
Description
General
The app launches in less than 10 seconds.
The app loads the content in less than 10 seconds
When the app is relaunched from the home screen, it restores the app as close to its previous state as possible.
Apps must not allow users to make purchases using the car screen. For example, users cannot pay for parking on the car screen.
IOT(Internet of Things) functionality
The IOT app may allow the following while driving:
View the current state of devices. For example: to view if a garage door is open or closed, a light bulb is on or off, a security system is armed or disarmed, or a washer is running or completed.
Simple, one-touch features that control on and off functions. For example: the ability to turn various devices on and off or open and close them, including turning lights on and off, turning a thermostat on and off, or opening and closing a garage door or curtain. This also includes turning a pre-programmed scene or routine on and off.
Notify users about an event in the home or another location. For example: receiving notifications for a routine or scene, a security alert, or a change in a door's open or closed status.
The IOT app must not allow the following while driving:
Tasks related to app setup of any kind. For example: the ability to select devices, systems, or locations for use with the IOT app.
Tasks related to creation, modification, or reordering. For example: the ability to create, modify, or reorder a scene or routine, such as a sequence of events when departing or leaving a location, including opening and closing a garage door, or turning lights on and off.
Tasks related to fine-grained device control. For example: the ability to control certain functions, including adjusting thermostat temperatures or the level of lighting luminescence.
Payments
The app must have simple flows if purchases are enabled, using shortcuts such as recent or favorite purchases.
The app must not allow any of the following:
Setup of payment methods
Multiple items to be selected for purchase
The user to commit to recurring payments (for example, subscriptions)