Car app quality

To provide a great experience for users in cars, complete the car compatibility checklists and tests that follow as you design and develop your app.

The checklists and tests define an extensive set of quality requirements for the various app categories supported by Android Auto and Android Automotive OS. Many requirements apply only to specific categories, so be sure to filter by your app's category. See the Car quality tiers definitions for details on which guidelines your app must meet in order to be accepted on the Google Play Store.

Test your app

Test your app for the applicable criteria listed on this page before submitting your app to Google Play for review. As applicable, test both of the ways users can access your app:

Android Automotive OS
Use the Android Emulator to validate each checklist item. For more information, see Test using the Android Automotive OS emulator.
Android Auto
Use the Android Auto Desktop Head Unit (DHU) to validate each checklist item. For more information, see Test using the Desktop Head Unit.

App categories

Car quality tiers

The quality tiers define criteria to help you assess the level of support your app provides for cars. Each category builds upon those below it. That is, for an app to be Car optimized, it should also meet all of the applicable Car ready requirements.

In addition to the guidelines specific to cars, each tier has associated guidelines from the Large screen app quality that are relevant for activities implemented by your app.

Levels of support include the following:

Tier 3 - Car ready

Your app is large screen compatible and can be used while the car is parked. While it may not have any car-optimized features, users can experience the app just as they would on any other large screen Android-powered device.

This tier primarily applies to the parked categories of apps, which must meet all of the requirements in this tier to be accepted on the Google Play Store.

Tier 2 - Car optimized

Your app provides a great experience on the car's center stack display. To accomplish this, your app has some car-specific capabilities that users can experience across driving or parked modes, depending on your app's category.

Apps in categories built for use while driving must meet meet all of the applicable requirements in this tier to be accepted on the Google Play Store.

Tier 1 - Car differentiated

Your app is built to work across the variety of hardware in cars and can adapt its experience across driving and parked modes. It provides the best user experience designed for the different screens in cars such as the center console, instrument cluster, and additional screens - like panoramic displays seen in many premium cars.

Car ready

Criteria ID Applicable Categories Description
Permitted Categories PC-1 All

The app must not include features outside the app types intended for cars. See Supported app categories.

Expected Performance EP-1 All

The app must work as expected or described in the app's Google Play Store listing.

EP-2 Media, Navigation, POI, IOT, Video, Games, Browsers

When the app is relaunched from the home screen, the app must restore the app state as closely as possible to the previous state.

Display Orientation DO-1 Video, Games, Browsers

The app can be distributed to devices with fixed screen orientations. See Required Android Automotive OS features.

CPU Architectures CP-1 Video, Games, Browsers

The app must support both x86_64 and ARM CPUs.

App Rendering AR-1 All categories supported by Android Automotive OS

In activities implemented by the app, interactive UI elements must not be obstructed by system bars or display cutouts. See Work with window insets and display cutouts.

Driver Distraction DD-3 Video, Games, Browsers

The app must not be launchable or usable while driving and must not play any audio. See Ensure there are no distraction optimized activities.

Note: If your app plays audio, it must meet the DD-2 requirement.

Irrelevant notifications IN-2 Video, Games, Browsers

The app must not post any heads up notifications.

App Navigability AN-1 Video, Games, Browsers

Users can navigate through the app without encountering any dead ends.

Sensitive Data SD-1 Browsers

Browsers must not save or allow access to passwords or payment information unless the user can block access to passwords using a profile lock.

SD-2 Browsers

Before syncing data to the car, browsers that synchronize passwords or payments data must do the following steps:

  1. Prompt the user to authenticate.
  2. Notify the user on the car screen their data will be synchronized to the car.
(Learn how)

Associated large screen quality guidelines

While these guidelines are relevant for all activities implemented by your app, they are Tier 3 requirements only for parked apps.

Criteria ID Guidance for cars
Configuration and continuity LS-C1 Configuration changes in cars are primarily caused by moving an app between displays, such as when moving an app to or from a distant display.
LS-C2 No additional guidance.

Car optimized

Criteria ID Applicable Categories Description
Parked Experiences PE-1 Media, Navigation, POI, IOT

Android Automotive OS only: with the exception of providing setup, settings, and sign-in flows while parked, the app must not provide any functionality through its own activities.

Screen Animation SA-1 Media, Messaging, Navigation, POI, IOT

The app must not display animated elements on the screen, such as animated graphics or video.

Visual or Text Ads AD-1 Media, Messaging, Navigation, POI, IOT

The app must not display text-based advertising other than the advertiser's name or the product name.

Image Usage IU-1 Media, Messaging, Navigation, POI, IOT

App elements do not display any images on the screen. Exceptions include:

  • Apps can 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.
  • Apps can display icons in the content navigation drawer.
  • Apps can display images and photographs to aid in driving decision-making.
  • Navigation apps can display an image for lane guidance or junction guidance.
Visual Information on Phone VI-1 Media, Navigation, POI, IOT

Android Auto only: If the user must go to the phone screen—for example, to act on a permission request—then the app must display a message instructing the user to only look at their phone screen when it’s safe to do so. For more information, see Handle general errors for media, and Handle user input for navigation, point of interest, and internet of things apps.

App Doesn't Crash AC-1 Navigation, POI, IOT

Users must be able to complete tasks in the app using five screens or fewer. For more information, see Template restrictions.

Scrolling Text ST-1 Media, Messaging, Navigation, POI, IOT

The app must not display automatically scrolling text.

Voice Commands VC-1 Media, Navigation

The app must support Google Assistant voice commands. For more information, see Support voice actions for media, and Support navigation intents for navigation.

Delayed Response DR-1 Media, Navigation, POI, IOT

App-specific buttons must respond to user actions with no more than a two-second delay.

DR-2 Media, Navigation, POI, IOT

The app must launch in no more than 10 seconds.

DR-3 Media, Navigation, POI, IOT

The app must load content in no more than 10 seconds.

Contrast VD-1 Media, Messaging, Navigation, POI, IOT

The app must provide icons and colors that meet Android Auto's contrast requirements. For more information, see Contrast.

VD-2 Media

The app must provide white icon sets that the system colorizes to provide automatic contrast compensation.

VD-3 Media

The app must provide colors that the system can optimize for easy in-vehicle readability.

Grey Buttons GB-1 Media

Interactive elements that are intentionally greyed-out must be nonfunctional.

Driver Distraction DD-1 Navigation

The navigation audio channel can only be used by navigation apps and for navigation instructions. For more information, see Voice guidance.

DD-2 Video, Games, Browsers

While driving, the app must not be launchable and the app's UI must not be visible. The app's audio must stop when the user starts driving and cannot be unpaused while driving. For more information, see Ensure there are no distraction optimized activities.

Payments PA-1 Navigation, POI, IOT

The app must have simple flows if purchases are enabled, using shortcuts such as recent or favorite purchases. For more information, see Purchase using an existing payment method.

The app must not allow any of the following:

  • Setup of payment methods
  • Multiple items to be selected for purchase
  • Commitment to recurring payments, such as subscriptions
Notification Ads NA-1 Media, Messaging, Navigation, POI, IOT

The app must not present advertisements through notifications.

Irrelevant Notifications IN-1 Media, Messaging, Navigation, POI, IOT

The app must display 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.

Media Autoplay MA-1 Media

The app must not autoplay on startup or without user initiated action to select the app or app media. For more information, see Implement play commands.

Messaging Functionality MF-1 Messaging

The app must receive incoming messages. For more information, see Build messaging apps for Android Auto.

MF-2 Messaging

Messages must be properly grouped and displayed in the correct order. For more information, see Build messaging apps for Android Auto.

MF-3 Messaging

The user can reply to a message. For more information, see Build messaging apps for Android Auto.

MF-4 Messaging

The app must use short-form messaging app design patterns. Traditional long-form messaging apps, such as apps for email, are not permitted.

MF-5 Messaging

The app must implement a peer-to-peer messaging service and not notification services, such as those for weather, stocks, and sport scores.

NF-1 Navigation

The app must provide turn-by-turn navigation directions.

NF-2 Navigation

The app draws only map content on the surface of the navigation templates. Text-based turn-by-turn directions, lane guidance, and estimated arrival time must be displayed on the relevant components of the navigation template. Additional information relevant to the drive, speed limit, road obstructions, etc., can be drawn on the safe area of the map.

NF-3 Navigation

When the app provides text-based turn-by-turn directions, it must also trigger navigation notifications. For more information, see Turn-by-turn notifications.

NF-4 Navigation

When the navigation app provides text-based turn-by-turn directions, it must send next-turn information to the vehicle’s cluster display. For more information, see Navigation metadata.

NF-5 Navigation

The app must not provide turn-by-turn notifications, voice guidance, or cluster information when another navigation app is providing turn-by-turn instructions. For more information, see Start, end, and stop navigation.

NF-6 Navigation

The app must handle navigation requests from other Android Auto apps. For more information, see Support navigation intents.

NF-7 Navigation

The app must provide a "test drive" mode that simulates driving. For more information, see Simulate navigation.

NF-8 Navigation

The app must draw a light-themed or dark-themed map when instructed to do so. For more information, see Support dark theme.

Point of Interest Functionality PF-1 POI

The app must provide meaningful functionality relevant to driving.

Internet of Things Functionality IT-1 IOT
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.
Media Controls MC-1 Video

The app integrates with media session. Depending on the content, the app must support either the play/pause or stop playback commands. Additionally, the app must provide title and thumbnail metadata for every media item. See Control and advertise playback using a MediaSession.

Associated large screen quality guidelines

While these guidelines are relevant for all activities implemented by your app, they are Tier 2 requirements only for parked apps.

Criteria ID Guidance for cars
Multi-window and multi-resume LS-M2 When an activity is on a distant display, it loses the top resumed activity position when the user interacts with an activity on the main display.
UX LS-U1 Some cars have landscape screens with much greater aspect ratios than are common on other large screen devices. You can use the Automotive Ultrawide hardware profile to test on such a display.
LS-U2 Same as for LS-U1
LS-U3 To qualify as a car optimized app, your app must meet the LS-U3 requirement for touch target sizes. To qualify as car differentiated, it must meet the car UX-1 requirement.

Car differentiated

Criteria ID Applicable Categories Description
Navigation Functionality NF-9 Navigation

The app supports rendering on cluster displays, and only renders map tiles on these displays. See Drawing to the cluster display.

App Rendering AR-2 Video, Games, Browsers

The app renders into display cutouts to fully make use of the screen space available while maintaining the ability for users to continue interacting with all UI elements on the screen. See Adapt to irregularly shaped displays for more details.

User Experience UX-1 Video, Games, Browsers

Touch targets are at least 64dp.

UX-2 Video, Games, Browsers

Touch targets are at least 24dp apart from each other and 24dp away from screen edges.

UX-3 Video, Games, Browsers

Font sizes should be at least 24sp.

Associated large screen quality guidelines

While these guidelines are relevant for all activities implemented by your app, they are Tier 1 requirements only for parked apps.

Criteria ID Guidance for cars
UX LS-U4 Although keyboards are supported by Android Automotive OS, they're less common input methods in cars in comparison to other large screen devices. However, some cars have rotary input devices that rely on the same APIs as tab navigation with a keyboard, so they also require LS-U4 to be met to function properly.
Keyboard, mouse, and trackpad LS-I3 Same as for LS-U4

Frequently asked questions

What happens after I submit my app?

Apps for cars are subject to an additional manual review beyond normal Play Store review processes. Your app is tested to ensure compliance against the applicable criteria.

After submitting my app, how will I find out if my app does not meet all the requirements for Android Auto or Android Automotive OS?

If your app does not meet the app quality requirements described on this page, the Play Store team contacts you through the email address specified in the Google Play Console account associated with the app.

Note: For information about how to publish your app in Google Play, see Distribute Android apps for cars.

How do I manage policy violations and appeals?

You can learn more about managing policy violations and appeals in the Google Play policy center.

My app targets more than just Android Auto or Android Automotive OS. If my app does not meet the car requirements, will my new or updated app still appear on Google Play for other devices?

No. When Google begins the approval process, your app undergoes an app quality review. Any subsequent updates are not available for distribution until the app is approved. If you need to make updates to your app for other devices, consider creating a separate release from the updates to your car app.

Important: Due to this restriction, you should not use your production APK for Android Auto support prototyping.

Change notes

May 2024

  • Introduction of the Car quality tiers
  • Driver Distraction
  • App Rendering
    • Categories affected: All categories supported by Android Automotive OS

    • New criteria: AR-1

      In activities implemented by the app, interactive UI elements must not be obstructed by system bars or display cutouts. See Work with window insets and display cutouts.

    • New criteria: AR-2

      The app renders into display cutouts to fully make use of the screen space available while ensuring interactive UI elements remain accessible. See Adapt to irregularly shaped displays for more details.

  • Media Controls
    • Categories affected: Video

    • New criteria: MC-1

      The app integrates with media session. Depending on the content, the app must support either the play/pause or stop playback commands. Additionally, the app must provide title and thumbnail metadata for every media item. See Control and advertise playback using a MediaSession.

  • UX
    • Categories affected: Browsers, Games, Video

    • New criteria: UX-1

      Touch targets are at least 64dp.

    • New criteria: UX-2

      Touch targets are at least 24dp apart from each other and 24dp away from screen edges.

    • New criteria: UX-3

      Font sizes should be at least 24sp.

  • Permitted Experiences
    • Categories affected: Media, Navigation, POI, IOT

    • New criteria: PE-1

      Android Automotive OS only: with the exception of providing setup, settings, and sign-in flows while parked, the app must not provide any functionality through its own activities.

  • Navigation functionality
    • Categories affected: Navigation

    • New criteria: NF-9

      The app supports rendering on cluster displays, and only renders map tiles on these displays. See Drawing to the cluster display.

  • Delayed Response
    • Categories affected: Video

    • Removal of criteria DR-1, DR-2, and DR-3 for the video category

October 2023

July 2023

  • App Categories: "Browsers" has been added
  • Sensitive Data
    • Categories affected: Browsers

    • New criteria: SD-1

      Browsers must not save or allow access to passwords or payment information unless the user can block access to passwords using a profile lock. (Learn how)

    • New criteria: SD-2

      Before syncing data to the car, browsers that synchronize passwords or payments data must do the following steps:

      1. Prompt the user to authenticate.
      2. Notify the user on the car screen their data will be synchronized to the car.

April 2023

March 2023

  • Grammar and formatting changes.

December 2022

  • Internet of Things Functionality
    • Categories affected: Internet of Things

    • New criteria:

      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.

May 2022

  • App Categories: "Parking & Charging" has been replaced with "Point of Interest"
  • Screen Animation
    • Categories affected: Media, Messaging, Navigation, and Point of Interest

    • Previous text:

      The app does not display animated elements on the screen such as animated graphics, video, or progress bars.

    • New text:

      The app does not display animated elements on the screen such as animated graphics or video.

  • Image Usage
    • Categories affected: Media, Messaging, Navigation, and Point of Interest

    • Previous text:

      App elements do not display any images on the screen. Exceptions include:

      • Apps 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.
      • Apps may display icons in the content navigation drawer.
      • Navigation, parking, and charging apps may display images and photographs to aid in driving decision-making.
      • Navigation apps may display an image for lane guidance or junction guidance.

    • New text:

      App elements do not display any images on the screen. Exceptions include:

      • Apps 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.
      • Apps may display icons in the content navigation drawer.
      • Apps may display images and photographs to aid in driving decision-making.
      • Navigation apps may display an image for lane guidance or junction guidance.
  • Since cars are large screen devices, apps should fill thtegories
    • Categories affected: Media, Messaging, Navigation, Point of Interest, and Video

    • Previous text:

      The app does not include games or other features outside the app types intended for cars. For more information, see Supported app categories.

    • New text:

      The app does not include features outside the app types intended for cars. For more information, see Supported app categories.
  • Visual Information on Phone
    • Categories affected: Media, Navigation, and Point of Interest

    • Previous text:

      Android Auto only: If the user must go to the phone screen—for example, to act on a permission request—then the app must display a message instructing the user to only look at their phone screen when it’s safe to do so. For more information, see Handle general errors for media, and Handle user input for navigation, parking, and charging.

    • New text:

      Android Auto only: If the user must go to the phone screen—for example, to act on a permission request—then the app must display a message instructing the user to only look at their phone screen when it’s safe to do so. For more information, see Handle general errors for media, and Handle user input for navigation and point of interest apps.
  • Navigation Functionality
    • Categories affected: Navigation

    • Previous text:

      The app draws only map content on the surface of the navigation templates. Text-based turn-by-turn directions, lane guidance, and estimated arrival time must be displayed on the relevant components of the Navigation template. Additional information relevant to the drive— for example, speed limit and road obstructions—can be drawn on the right side of the map.

    • New text:

      The app draws only map content on the surface of the navigation templates. Text-based turn-by-turn directions, lane guidance, and estimated arrival time must be displayed on the relevant components of the Navigation template. Additional information relevant to the drive—speed limit and road obstructions—can be drawn on the safe area of the map.
  • Point of Interest Functionality
    • Categories affected: Point of Interest

    • Previous text:

      The app must provide meaningful functionality in its category relevant to driving.

    • New text:

      The app must provide meaningful functionality relevant to driving.

    • Removed criteria:

      If a parking app is displaying a list of locations next to a map—for example, the Place List Map template—then the locations in the list can only be parking spots.

      Similarly, for a charging app, the locations must be charging stations.

April 2022

  • Display Orientation
    • Categories affected: Video

    • New criteria:

      UIs drawn by the app support both landscape and portrait screens.

  • Driver Distraction
    • Categories affected: Video

    • New criteria:

      While driving, the video app must not be launchable and the video app's screen must not be visible. The video app's audio must stop when the user starts driving.

  • Settings Flow
    • Categories affected: Video

    • New criteria:

      App must proceed to the home page after (attempted) sign-in.

  • Automotive Functionality
    • Categories affected: Video

    • New criteria:

      App does not contain driver optimized activities.

  • CPU Architectures
    • Categories affected: Video

    • New criteria:

      App supports both x86_64 and ARM CPUs.

  • App Navigability
    • Categories affected: Video

    • New criteria:

      App allows users to navigate through the app without encountering any dead ends.

November 2021

  • Visual Information on Phone
    • Categories affected: Media, Navigation, and Parking & Charging

    • Previous text:

      While the app is interacting with the car screen and the car is not parked, the app does not activate the phone screen to present any form of visual information such as notifications, toasts, video, images, advertising, or similar. For more information, see Build a navigation app for navigation, parking, and charging. Similarly, while the app is running Android Auto UI on the phone screen, the app does not present any visual information on the phone screen that is unrelated to Android Auto.

      If the user must go to the phone screen—for example, to act on a permission request—then the app must display a message instructing the user to only look at their phone screen when it’s safe to do so.

    • New text:

      Android Auto only: If the user must go to the phone screen—for example, to act on a permission request—then the app must display a message instructing the user to only look at their phone screen when it’s safe to do so. For more information, see Handle general errors for media, and Handle user input for navigation, parking, and charging.

  • Payments
    • Categories affected: Navigation, Parking & Charging

    • Previous text:

      The app must have simple flows if purchases are enabled.

    • New text:

      The app must have simple flows if purchases are enabled, using shortcuts such as recent or favorite purchases. For more information, see Purchase using existing payment method.

      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.