AutoGineer
Generated banner for Android For Cars Parked Apps
Generated logo for Android For Cars Parked Apps

Android For Cars Parked Apps

Android (Google)OfficialCreated by Google LLCDistributed by Android (Google)

  • Skill
  • Tool integration
  • Software development
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Adapt existing Android video streaming apps, games, and web browsers to run as parked apps on Android Auto and Android Automotive OS. Covers manifest configuration, Google Play hardware feature declarations, compatibility mode, back navigation affordances, orientation and display continuity, controllable system bar insets, irregular display cutouts, driver distraction lifecycle handling, MediaSession playback restrictions with CarUxRestrictionsManager, background audio while driving, and browser sensitive data protection. Use this skill when migrating, building, or auditing parked apps for cars to meet Car App Quality guidelines. Don't use for media audio apps, templated Car App Library navigation, point of interest, internet of things, weather, or communication apps designed for use while driving.
— the description by Google LLC

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured procedure for adapting existing Android video streaming apps, games, and web browsers to function as parked apps on Android Auto and Android Automotive OS. It covers essential configuration steps, including manifest updates, hardware feature declarations, and implementing driver distraction lifecycle handling. The guide ensures apps meet specific requirements for display continuity, system bar insets, and secure data handling, while providing instructions for auditing against car app quality guidelines.

What it does

  • Configures Android manifest files for parked app categories.
  • Implements driver distraction lifecycle handling and playback restrictions.
  • Manages display continuity and system bar insets for automotive screens.
  • Provides guidance on secure data protection for browser apps.
  • Outlines testing procedures using the Desktop Head Unit and Android Automotive OS emulator.
  • Details requirements for back navigation and orientation support.

When to use it

  • When migrating an existing Android app to support Android Auto or Android Automotive OS as a parked app.
  • When building a new video, game, or browser app intended for in-car use while parked.
  • When auditing an existing parked app to ensure it meets car app quality guidelines.
  • When configuring hardware feature requirements for automotive platforms.

Advantages

  • Ensures adherence to platform-specific requirements for parked apps.
  • Provides clear steps for handling vehicle-specific UI and lifecycle events.
  • Includes specific guidance for secure data handling in shared vehicle environments.
  • Offers actionable steps for testing and verification on automotive platforms.

Usage examples

“How do I configure my video app's manifest for Android Automotive OS?”
The agent provides the specific manifest tags, including the required appCategory and hardware feature declarations for automotive platforms.
“What are the requirements for handling driver distraction in my game?”
The agent explains how to use CarUxRestrictionsManager to pause gameplay and manage playback states when the vehicle is in motion.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/android/android-for-cars-parked-apps/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip android-for-cars-parked-apps.zip -d .agents/skills

Documentation by Google LLC

Adapt existing Android video apps, games, and web browsers to run as parked apps on Android Auto and Android Automotive OS. Follow these steps to meet the car app quality guidelines for Google Play distribution.

Prerequisites

  • Begin with an existing adaptive Android app in one of the supported parked app categories: video streaming apps, games, or web browsers.

Glossary

  • Parked apps: Parked apps run on Android Auto and Android Automotive OS only while the vehicle is parked. The three parked categories are video, games, and browsers; other categories can't be published as parked apps.

  • Android Auto: Android Auto is a phone-powered projection system. Apps execute on the user's phone and are projected to the in-car display over a wired or wireless connection. Android Auto is a separate platform from Android Automotive OS.

  • Android Automotive OS: Android Automotive OS, or AAOS, is a variant of Android that runs directly on the vehicle itself. Android Automotive OS is a separate platform from Android Auto.

  • Video category: Video apps display streaming videos while parked. Generally available on Android Automotive OS; unsupported on Android Auto.

  • Games category: Game apps provide gameplay while parked. Generally available on Android Automotive OS and Android Auto.

  • Browsers category: Web browsers let users browse the web while parked. Available in beta on Android Automotive OS; unsupported on Android Auto.

  • Media category: Not a parked category. Media apps play audio content (music, radio, audiobooks, excluding video) while driving or parked.

  • Android for Cars platform: Android for Cars is an umbrella term that consists of Android Auto and Android Automotive OS.

  • Generally available categories: Permitted on internal testing, closed testing, open testing, and production Google Play tracks for a supported platform.

  • Beta categories: Permitted on internal or closed testing tracks; open testing and production tracks require acceptance into an early access program.

  • Audio while driving: A beta feature on Android Automotive OS that lets video apps play audio while the vehicle is in motion.

  • Car app quality guidelines : When auditing an app against the Tier 3 (Car ready ), Tier 2 (Car optimized ), or Tier 1 (Car differentiated ) criteria, MUST check car app quality guidelines.

  • Android Automotive OS compatibility mode : Compatibility mode (android.software.car.display_compatibility) is a system feature on select vehicles providing a system back affordance, safe area rendering, density scaling, and opaque driving-mode blocking (moving activities to Stopped). Compatibility mode is only relevant to apps that support Android Automotive OS; it isn't relevant for apps that only support Android Auto.

Codebase exploration

Search the codebase for AndroidManifest.xml (or create Assets/Plugins/Android/AndroidManifest.xml in Unity projects), res/xml/automotive_app_desc.xml, build.gradle, build.gradle.kts, or gradle/libs.versions.toml files. Locate existing video players, MediaSession classes, requestedOrientation calls, and WindowInsets handlers. Unless instructed otherwise by the user, ask permission before adding dependencies.

Step 1: Configure the app manifest

Declare the app category, target platforms, hardware feature requirements, and activity configuration in AndroidManifest.xml.

1.1: Identify the app category

  • Video apps : Video apps MUST set android:appCategory="video" on <application> and MUST NOT include app/src/main/res/xml/automotive_app_desc.xml with uses name="video".

  • Games : Games MUST set android:appCategory="game" on <application>. Declare android.hardware.gamepad with android:required="false" if controller input is supported by the app.

  • Browsers : Browsers MUST include <category android:name="android.intent.category.APP_BROWSER"/> in the MAIN <intent-filter> of an exported <activity> (android:exported="true").

1.2: Identify target platforms and hardware features

  • Android Auto : Apps targeting Android Auto (Android 15+) MUST add <category android:name="android.intent.category.CAR_LAUNCHER"/> to an <intent-filter> in the AndroidManifest.xml file. Add it to the MAIN <intent-filter> unless the user specifies a different intent filter. NEVER add this category if the app is solely targeting Android Automotive OS.

  • Android Automotive OS : Apps targeting Android Automotive OS MUST declare <uses-feature android:name="android.hardware.type.automotive" android:required="false"/> ("false" for mobile or multi-form-factor tracks; "true" only if the app will be published on the dedicated Automotive OS track) in the AndroidManifest.xml file. NEVER add this feature tag if the app is solely targeting Android Auto.

  • Unrequired hardware features (DO-1) : To satisfy Google Play feature requirements and DO-1, declare unsupported features (android.hardware.wifi, android.hardware.screen.portrait, android.hardware.screen.landscape, android.hardware.camera) with android:required="false", and remove android:required="true" on features absent in cars.

  • Display continuity (LS-C1) : Configure android:configChanges for screenSize, smallestScreenSize, orientation, screenLayout, and density on <activity> so moving to or from a distant display does not recreate the activity or stutter playback.

  • Compatibility mode and distraction : Declaring compatibility mode is optional and is only relevant for apps that support Android Automotive OS. NEVER add compatibility mode for apps that only support Android Auto. Adding android.hardware.type.automotive disables compatibility mode unless <meta-data android:name="android.software.car.display_compatibility" android:value="true"/> is added to <application>. When an app declares android.software.car.display_compatibility in AndroidManifest.xml, the app MUST check PackageManager.hasSystemFeature("android.software.car.display_compatibility") at runtime and hide duplicate in-app back or close affordances when it returns true. Parked apps MUST NOT include <meta-data android:name="distractionOptimized" android:value="true"/> on any <activity> (DD-2, DD-3).

Step 2: Provide back navigation and orientation support

2.1: Add in-app back and close affordances

Android Automotive OS vehicles aren't required to have a hardware or software back button or gesture navigation (AN-1). Provide explicit UI back and close controls on every non-root screen, including detail screens and full-screen players:

  • If AndroidManifest.xml does not declare android.software.car.display_compatibility: Display explicit in-app back and close controls unconditionally.

  • If AndroidManifest.xml declares android.software.car.display_compatibility with android:value="true" : Show in-app back and close controls only when PackageManager.hasSystemFeature("android.software.car.display_compatibility") returns false.

2.2: Guard runtime orientation requests

Vehicle displays have fixed orientations. Requesting landscape on a fixed-portrait car display causes letterboxing or flickering loops (DO-1). Remove hardcoded android:screenOrientation manifest attributes and check PackageManager.FEATURE_SCREEN_LANDSCAPE and PackageManager.FEATURE_SCREEN_PORTRAIT before setting requestedOrientation.

Step 3: Adapt to system bars and irregular display cutouts

3.1: Track controllable system bar insets

On Android Automotive OS, OEMs are permitted to lock system bars visible so climate and vehicle controls remain accessible (AR-1). Track controllable insets with OnControllableInsetsChangedListener, hide only controllable bars, and apply windowInsetsPadding for uncontrollable statusBars, navigationBars, and displayCutout insets.

3.2: Render into irregular display cutouts safely

To meet Tier 1 criterion AR-2 on curved or non-rectangular car displays, NEVER use LAYOUT_IN_DISPLAY_CUTOUT_MODE_DEFAULT (0) or LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES (1). Configure LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS (3) or LAYOUT_IN_DISPLAY_CUTOUT_MODE_NEVER (2) using the car resource qualifier in res/values-car-v30/integers.xml:

<integer name="windowLayoutInDisplayCutoutMode">3</integer>

<br />

Protect interactive UI, app bars, and scrollable lists with WindowInsets.safeDrawing.

Step 4: Meet driver distraction and media playback requirements

4.1: Pause playback on lifecycle transitions and block driving resumption

When a vehicle begins moving, the OS covers parked activities with a blocking overlay and triggers onPause (and onStop on compatibility mode vehicles). To satisfy DD-2, DD-3, and MC-1:

  1. Pause playback on ON_PAUSE or ON_STOP using LifecycleEventEffect from androidx.lifecycle:lifecycle-runtime-compose.

  2. Expose a MediaSession (androidx.media3:media3-session) with play, pause, or stop commands and item metadata (MC-1), and release it in onCleared.

  3. Add useLibrary("android.car") in build.gradle.kts, wrap ExoPlayer in ForwardingSimpleBasePlayer, listen to CarUxRestrictionsManager, pause playback when isRequiresDistractionOptimization becomes true, and remove COMMAND_PLAY_PAUSE in getState so external MediaSession controls can't resume playback while driving:

@UnstableApi
class CarAwarePlayer(context: Context) :
    ForwardingSimpleBasePlayer(ExoPlayer.Builder(context).build()) {
    private var shouldPreventPlay = false
    private var pausedByUxRestrictions = false
    private lateinit var carUxRestrictionsManager: CarUxRestrictionsManager

    init {
        if (context.packageManager.hasSystemFeature(PackageManager.FEATURE_AUTOMOTIVE)) {
            val car = Car.createCar(context)
            carUxRestrictionsManager =
                car.getCarManager(Car.CAR_UX_RESTRICTION_SERVICE) as CarUxRestrictionsManager
            shouldPreventPlay =
                carUxRestrictionsManager.currentCarUxRestrictions.isRequiresDistractionOptimization
            invalidateState()

            carUxRestrictionsManager.registerListener { restrictions: CarUxRestrictions ->
                shouldPreventPlay = restrictions.isRequiresDistractionOptimization
                if (!shouldPreventPlay && pausedByUxRestrictions) {
                    handleSetPlayWhenReady(true)
                    invalidateState()
                } else if (shouldPreventPlay && isPlaying) {
                    pausedByUxRestrictions = true
                    handleSetPlayWhenReady(false)
                    invalidateState()
                }
            }
        }
    }

    override fun getState(): State {
        val state = super.getState()
        return state.buildUpon()
            .setAvailableCommands(
                state.availableCommands.buildUpon()
                    .removeIf(COMMAND_PLAY_PAUSE, shouldPreventPlay)
                    .build()
            )
            .build()
    }

    override fun handleRelease(): ListenableFuture<*> {
        if (::carUxRestrictionsManager.isInitialized) {
            carUxRestrictionsManager.unregisterListener()
        }
        return super.handleRelease()
    }
}

<br />

4.2: Support background audio while driving (optional beta feature)

Because this is an optional beta feature, NEVER implement this feature unless the user requests it. To implement the feature:

  1. Declare <uses-feature android:name="com.android.car.background_audio_while_driving" android:required="false" /> in AndroidManifest.xml, along with FOREGROUND_SERVICE and FOREGROUND_SERVICE_MEDIA_PLAYBACK permissions.

  2. Check runtime vehicle support with CarFeatures.isFeatureEnabled(context, CarFeatures.FEATURE_BACKGROUND_AUDIO_WHILE_DRIVING) from androidx.car.app:app. Only set shouldPreventPlay when !isBackgroundAudioWhileDrivingSupported && restrictions.isRequiresDistractionOptimization.

  3. Host the MediaSession and player inside an exported MediaSessionService with android:foregroundServiceType="mediaPlayback", and connect from the UI using MediaController.Builder and buildAsync.

Step 5: Protect sensitive data in browser apps

Because vehicles are shared devices, browsers MUST block access to saved passwords and payment methods unless protected by a profile lock (SD-1). Before syncing passwords or payment data to the vehicle, browsers MUST prompt the user to authenticate and display a notice on the car screen stating that their data will be synchronized to the car (SD-2).

Check whether a PIN, pattern, or password is set using KeyguardManager, open Settings.ACTION_SECURITY_SETTINGS if unset, and authenticate with BiometricPrompt using BiometricManager.Authenticators.DEVICE_CREDENTIAL only (vehicles don't have biometric hardware):

val keyguardManager = context.getSystemService<KeyguardManager>()
val isDeviceSecure = keyguardManager?.isDeviceSecure == true
lateinit var biometricPrompt: BiometricPrompt

if (!isDeviceSecure) {
    context.startActivity(
        Intent(Settings.ACTION_SECURITY_SETTINGS).addFlags(Intent.FLAG_ACTIVITY_NEW_TASK)
    )
} else {
    val promptInfo = BiometricPrompt.PromptInfo.Builder()
        .setTitle(context.getString(R.string.auth_title))
        .setSubtitle(context.getString(R.string.sync_data_to_car_notice))
        .setAllowedAuthenticators(BiometricManager.Authenticators.DEVICE_CREDENTIAL)
        .build()
    biometricPrompt.authenticate(promptInfo)
}

<br />

Step 6: Verify implementation

Build the app using ./gradlew assembleDebug. Find and fix any build errors.

Post-implementation guidance

Provide this guidance to the user after implementation:

  • For Android Auto apps, install the app on a phone and test using the Desktop Head Unit (DHU).

  • For Android Automotive OS, install the app on the Android Automotive OS emulator in Android Studio.

  • If the app is in a beta category for the target platform, acceptance into the early access program is required before submitting the app to an open testing or production track.

  • If the app implements the beta audio while driving feature, acceptance into the early access program is required before submitting the app to an open testing or production track.

  • Test the app against the relevant criteria in the car app quality guidelines before submitting the app.

Antipatterns

  • NEVER include <meta-data android:name="distractionOptimized" android:value="true"/> on any <activity> in a parked app, or include res/xml/automotive_app_desc.xml with uses name="video" in a video app.

  • NEVER assume a hardware or software back button exists on Android Automotive OS.

  • NEVER assume system bars are positioned only at the top and bottom or can always be hidden.

  • NEVER use LAYOUT_IN_DISPLAY_CUTOUT_MODE_DEFAULT or LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES on Android Automotive OS.

  • NEVER infer UX restrictions from vehicle speed or gear state instead of reading isRequiresDistractionOptimization from CarUxRestrictionsManager.

  • NEVER use biometric authenticators (BIOMETRIC_STRONG, BIOMETRIC_WEAK) with BiometricPrompt on browser apps on Android Automotive OS; use DEVICE_CREDENTIAL only.

  • NEVER add the CAR_LAUNCHER intent category if the user only requests Android Automotive OS support.

  • NEVER add the android.hardware.type.automotive feature tag if the user only requests Android Auto support.

Best practices

  • MUST declare android:required="false" on unsupported hardware features (wifi, screen.portrait, screen.landscape, camera) and guard requestedOrientation calls by checking FEATURE_SCREEN_LANDSCAPE and FEATURE_SCREEN_PORTRAIT (DO-1).

  • MUST provide in-app back and close affordances (AN-1) for Android Automotive OS when not in compatibility mode and protect all interactive UI and text from system bars and display cutouts using WindowInsets.safeDrawing and OnControllableInsetsChangedListener (AR-1, AR-2).

  • MUST pause playback when UX restrictions become active and strip COMMAND_PLAY_PAUSE from MediaSession while driving unless audio while driving is supported and enabled (DD-2, DD-4, MC-1).

  • MUST require profile lock authentication and display an on-screen sync disclosure before saving, accessing, or syncing browser passwords or payment information (SD-1, SD-2).

Files

references/android/docs/quality-guidelines/car-app-quality/index.md

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.

[!NOTE] September 2026 update: The Games app category is now generally available. See September 2026 for details.

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

[!IMPORTANT] Key Point: Select your app's categories to filter the guidelines on this page.

Supported categoriesAndroid AutoAndroid Automotive OS
Media✔✔
Media (templated) labs✔✔
Communication - messaging notifications✔
Communication - templated messaging labs✔
Communication - calling labs✔
Navigation✔✔
Point of Interest (POI)✔✔
Internet of Things (IOT)✔✔
Weather✔✔
Video✔
Games✔✔
Browsers labs✔

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 Adaptive app quality guidelines 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.

[!NOTE] Note: Through the Car ready mobile apps program, mobile apps meeting the requirements in this tier can be made available for download from the Google Play Store on Android Automotive OS vehicles with Google built-in.

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
CriteriaIDApplicable CategoriesDescription
Permitted CategoriesPC-1AllThe app must not include features outside the app types intended for cars. See Supported app categories.
Expected PerformanceEP-1AllThe app must work as expected or described in the app's Google Play Store listing.
Expected PerformanceEP-2Media, Messaging (templated), Calling, Navigation, POI, IOT, Weather, Video, Games, BrowsersWhen the app is relaunched from the home screen, the app must restore the app state as closely as possible to the previous state.
Expected PerformanceEP-3GamesThe app is responsive to input and does not freeze or stutter during gameplay.
Expected PerformanceEP-4Media, Messaging (templated), Calling, Navigation, POI, IOT, WeatherAndroid Automotive OS only: The app listing on Google Play Store must include screenshots for the Android Automotive OS form factor. See Provide Android Automotive OS screenshots. Note: For apps in the parked app categories, screenshots are optional. However, if your app includes features unique to cars, or the app differs significantly from the experience on mobile or tablet, it is recommended to include screenshots in your Google Play Store listing. See Provide Android Automotive OS screenshots.
Display OrientationDO-1Video, Games, BrowsersAndroid Automotive OS only: The app can be distributed to devices with fixed screen orientations. See Required Android Automotive OS features.
Display OrientationDO-2GamesAndroid Auto only: The app is not significantly pillarboxed when running on landscape displays. See Support common Android Auto screen sizes.
App RenderingAR-1All categories supported by Android Automotive OSIn 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 DistractionDD-3Video, Games, BrowsersThe app must not be launchable or usable while driving and must not play any audio. See Meet driver distraction requirements. Note: If your app plays audio, it must meet the DD-2 requirement.
Irrelevant notificationsIN-2Video, Games, BrowsersThe app must not post any heads up notifications.
App NavigabilityAN-1Video, Games, BrowsersUsers can navigate through the app without encountering any dead ends.
Sensitive DataSD-1BrowsersBrowsers must not save or allow access to passwords or payment information unless the user can block access to passwords using a profile lock.
Sensitive DataSD-2BrowsersBefore 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. For details, see Allow users to block access to sensitive data.
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.

CriteriaIDGuidance for cars
Configuration and continuityLS-C1Configuration changes in cars are primarily caused by moving an app between displays, such as when moving an app to or from a distant display.
Configuration and continuityLS-C2No additional guidance.
Car optimized
CriteriaIDApplicable CategoriesDescription
Parked ExperiencesPE-1Media, Navigation, POI, IOT, WeatherAndroid 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 AnimationSA-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherThe app must not display animated elements on the screen, such as animated graphics or video. Exception: Canvas animations while the user is parked are allowed if they are relevant to the driving task.
Visual or Text AdsAD-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherThe app must not display text-based advertising other than the advertiser's name or the product name.
Image UsageIU-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherApp elements don't 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 PhoneVI-1Media, Messaging (templated), Calling, Navigation, POI, IOT, WeatherAndroid 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, internet of things, and weather apps.
App Doesn't CrashAC-1Messaging (templated), Calling, Navigation, POI, IOT, WeatherUsers must be able to complete tasks in the app using five screens or fewer. For more information, see Template restrictions.
Scrolling TextST-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherThe app must not display automatically scrolling text.
Voice CommandsVC-1Media, NavigationThe app must support Gemini and Google Assistant voice commands. For more information, see Support voice actions for media, and Support navigation intents for navigation.
Delayed ResponseDR-1Media, Messaging (templated), Calling, Navigation, POI, IOT, WeatherApp-specific buttons must respond to user actions with no more than a two-second delay.
Delayed ResponseDR-2Media, Messaging (templated), Calling, Navigation, POI, IOT, WeatherThe app must launch in no more than 10 seconds.
Delayed ResponseDR-3Media, Messaging (templated), Calling, Navigation, POI, IOT, WeatherThe app must load content in no more than 10 seconds.
ContrastVD-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherThe app must provide icons and colors that meet Android Auto's contrast requirements. For more information, see Contrast.
ContrastVD-2MediaThe app must provide white icon sets that the system colorizes to provide automatic contrast compensation.
ContrastVD-3MediaThe app must provide colors that the system can optimize for in-vehicle readability.
ThemingTH-1Messaging (templated), Navigation, POI, IOT, WeatherApps that add custom theming to Car App Library components with version 1.9 or higher must support light and dark theme. See Contrastfor more information.
Grey ButtonsGB-1MediaInteractive elements that are intentionally disabled must be nonfunctional.
Driver DistractionDD-1NavigationThe navigation audio channel can only be used by navigation apps and for navigation instructions. For more information, see Voice guidance.
Driver DistractionDD-2Video, Games, BrowsersWhile 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 Meet driver distraction requirements. Exception: Video apps that support audio while driving can continue playback on supported devices. See DD-4 .
PaymentsPA-1Navigation, POI, IOT, WeatherThe 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 AdsNA-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherThe app must not present advertisements through notifications.
Irrelevant NotificationsIN-1Media, Messaging, Calling, Navigation, POI, IOT, WeatherThe 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. Bad: For weather apps, your app posts notifications that are not related to imminent alerts for the current location, route, or destination.
Media AutoplayMA-1MediaThe 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 FunctionalityMF-1MessagingThe app must receive incoming messages. For more information, see Extend messaging notifications to Android Auto.
Messaging FunctionalityMF-2MessagingMessages must be properly grouped and displayed in the correct order. For more information, see Extend messaging notifications to Android Auto.
Messaging FunctionalityMF-3MessagingThe user can reply to a message. For more information, see Extend messaging notifications to Android Auto.
Messaging FunctionalityMF-4MessagingThe app must use short-form messaging app design patterns. Long-form messaging apps, such as apps for email, are not permitted.
Messaging FunctionalityMF-5MessagingThe app must implement a peer-to-peer messaging service and not notification services, such as those for weather, stocks, and sport scores.
Navigation FunctionalityNF-1NavigationThe app must provide turn-by-turn navigation directions.
Navigation FunctionalityNF-2NavigationThe 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.
Navigation FunctionalityNF-3NavigationWhen the app provides text-based turn-by-turn directions, it must also trigger navigation notifications. For more information, see Turn-by-turn notifications.
Navigation FunctionalityNF-4NavigationWhen 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.
Navigation FunctionalityNF-5NavigationThe 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.
Navigation FunctionalityNF-6NavigationThe app must handle navigation requests from other apps. For more information, see Support navigation intents.
Navigation FunctionalityNF-7NavigationThe app must provide a "test drive" mode that simulates driving. For more information, see Simulate navigation.
Point of Interest FunctionalityPF-1POIThe app must provide meaningful functionality relevant to driving.
Internet of Things FunctionalityIT-1IOTThe 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.
Weather FunctionalityWE-1WeatherApp must include weather related content, which must be relevant to the user's current location or a user specified location.
Weather FunctionalityWE-2WeatherWeather information on map tiles must be readable and may not include complex legends. Apps may include a maximum of three legends. Apps with multiple legends may have a maximum of three colors, whereas single legend apps may have more than three colors.
Weather FunctionalityWE-3WeatherForecast information must include easily readable icons and symbols.
Weather FunctionalityWE-4WeatherCustomization of forecast intervals must not be made possible using templates.
Weather FunctionalityWE-5WeatherWeather apps must not show more than five unique weather map annotations in a given view (for example: Temperature markers, wind speed markers, humidity, radar overlay, lightning indicators, road conditions all in the same view).
Map RenderingMR-1Navigation, POI, WeatherBy default, apps that draw maps must draw a light-themed or dark-themed map when instructed to do so. For more information, see Support dark theme. Apps can let users choose to always display the app in either light or dark theme.
Media ControlsMC-1VideoThe 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.
Deep LinksDL-1Video, Games, BrowsersAndroid Automotive OS only: The app supports deep links. See Handling Android App Links.
Media Functionality (templated)MFT-1Media (templated)User must be able to navigate to the MediaPlaybackTemplate from media browsing views or support the minimized control panel for apps using the Car App Library Version 1.9 or higher. See Build templated media apps for more details.
Media Functionality (templated)MFT-3Media (templated)Handle SHOW_MEDIA_PLAYBACK intents: Templated Media apps must handle the androidx.car.app.media.action.SHOW_MEDIA_PLAYBACK intent action to direct the user to the MediaPlaybackTemplate. See handle system media playback intents for more details.
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.

CriteriaIDGuidance for cars
Multi-window and multi-resumeLS-M2When 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.
UXLS-U1Some 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.
UXLS-U2Same as for LS-U1
UXLS-U3To 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
CriteriaIDApplicable CategoriesDescription
Navigation FunctionalityNF-9NavigationThe app supports rendering on cluster displays, and only renders map tiles on these displays. See Drawing to the cluster display. Warning: Navigation apps that also support weather functionality must not include any weather-related information on the cluster display.
Templated Messaging FunctionalityTMF-1Messaging (templated)The app displays conversations as described in Display conversations: - The self property of each conversation is set accurately. - Users can send a message using the button provided for each conversation. - Conversations are refreshed to include new messages as they are sent and received.
Calling FunctionalityCF-1CallingThe app can be used to initiate, accept, decline, and leave calls. See Build calling experiences for Android Auto.
Calling FunctionalityCF-2CallingDuring a call, the app provides the following: - A call name and icon. - For meetings/group calls, the number of participants and the actively speaking participant. - The ability for a user to mute themselves.
Calling FunctionalityCF-3CallingCalls initiated while Android Auto is not connected continue when a user connects to Android Auto and are displayed on Android Auto.
Deep LinksDL-2Media, Navigation, POI, IOT, WeatherAndroid Automotive OS only: The app supports deep links: - For media apps, see Add support for Android Automotive OS to your media app. - For templated apps, see Add support for Android Automotive OS to your templated app.
Driver distractionDD-4VideoThe app supports audio while driving on capable devices. See Support audio while driving for additional details. Important: The app must meet DD-2 on devices that don't support audio while driving.
App RenderingAR-2Video, Games, BrowsersThe 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.
Media Functionality (templated)MFT-2Media (templated)App provides a differentiated experience by using templates for scenarios beyond basic browsing and playback. For example, by providing expanded playback controls or by allowing users to adjust driving relevant app settings. Tip: Try creating a car version of a feature that's unique to your mobile app. See Build templated media apps for more details.
User ExperienceUX-1Video, Games, BrowsersTouch targets are at least 64dp.
User ExperienceUX-2Video, Games, BrowsersTouch targets are at least 24dp apart from each other and 24dp away from screen edges.
User ExperienceUX-3Video, Games, BrowsersFont 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.

CriteriaIDGuidance for cars
UXLS-U4Although 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 trackpadLS-I3Same 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] Note: For information about how to publish your app in Google Play, see Distribute to 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.

[!CAUTION] Caution: Due to this restriction, you shouldn't use your production APK for Android Auto support prototyping.

Change notes

September 2026

  • The Games parked app category has graduated from beta to general availability. Developers can now publish games to all track types on Google Play. See Supported app categories for more information.

August 2026

  • Expected Performance

    • Categories affected: Media, Messaging (templated), Calling, Navigation, POI, IOT, or Weather

    • New criterion: EP-4

      Android Automotive OS only: The app listing on Google Play Store must include screenshots for the Android Automotive OS form factor. See Provide Android Automotive OS screenshots.

      Note: For apps in the parked app categories, screenshots are optional. However, if your app includes features unique to cars, or the app differs significantly from the experience on mobile or tablet, it is recommended to include screenshots in your Google Play Store listing. See Provide Android Automotive OS screenshots.

May 2026

  • Voice Commands

  • Theming

    • Categories affected: Media (templated), Messaging (templated), Navigation, POI, IOT, Weather

    • New criterion: TH-1

      Apps that add custom theming to Car App Library components with version 1.9 or higher must support light and dark theme. See Contrast for more information.

  • Media Functionality (templated)

    • Categories affected: Media (templated)

    • Updated criterion: MFT-1

    • Previous text:

      User must be able to navigate to the MediaPlaybackTemplate from media browsing views. See Build templated media apps for more details.

    • New text:

      User must be able to navigate to the MediaPlaybackTemplate from media browsing views or support the minimized control panel for apps using the Car App Library Version 1.9 or higher. See Build templated media apps for more details.

    • Categories affected: Media (templated)

    • New criterion: MFT-3

      Handle SHOW_MEDIA_PLAYBACK intents: Templated Media apps must handle the androidx.car.app.media.action.SHOW_MEDIA_PLAYBACK intent action to direct the user to the MediaPlaybackTemplate. See handle system media playback intents for more details.

May 2025

  • App Categories: "Communication --- messaging notifications" replaces the "Messaging" category. "Communication --- templated messaging" and "Communication --- calling" have been added, including the related "Templated Messaging Functionality" and "Calling Functionality" criteria.

  • Expected Performance

    • Categories affected: Games

    • New criterion: EP-3

      The app is responsive to input and does not freeze or stutter during gameplay.

  • Display Orientation

  • Deep Links

  • CPU Architectures

    • Categories affected: Video, Games, Browsers

    • Removed criterion: CP-1

      The app must support both x86_64 and ARM CPUs.

  • Driver Distraction

    • Categories affected: Video

    • New criterion: DD-4

      The app supports audio while driving on capable devices. See Support audio while driving for additional details.

      [!IMPORTANT] Important: The app must meet DD-2 on devices that don't support audio while driving.

December 2024

  • App Categories: "Weather" has been added, including the introduction of the Weather Functionality criteria.

  • Map Rendering

    • Categories affected: Navigation, POI, Weather

    • New criterion: MR-1

      By default, apps that draw maps must draw a light-themed or dark-themed map when instructed to do so. For more information, see Support dark theme.

      Apps can let users choose to always display the app in either light or dark theme.

  • Navigation Functionality

    • Removed criterion: NF-8

    • Categories affected: Navigation Replacement of criterion NF-8 by the MR-1 criterion.

    • Updated criterion: NF-9

    • Categories affected: Navigation

    • Previous text:

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

    • New text:

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

      Navigation apps that also support weather functionality must not include any weather-related information on the cluster display.

  • Screen Animation

    • Updated criterion: SA-1

    • Categories affected: Media, Messaging, Navigation, Point of Interest, Weather

    • Previous text:

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

    • New text:

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

      Exception: Canvas animations while the user is parked are allowed if they are relevant to the driving task.

May 2024

  • Introduction of the Car quality tiers

  • Driver Distraction

  • App Rendering

    • Categories affected: All categories supported by Android Automotive OS

    • New criterion: 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 criterion: 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 criterion: 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 criterion: UX-1

      Touch targets are at least 64dp.

    • New criterion: UX-2

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

    • New criterion: UX-3

      Font sizes should be at least 24sp.

  • Permitted Experiences

    • Categories affected: Media, Navigation, POI, IOT

    • New criterion: 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 criterion: 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

July 2023

  • App Categories: "Browsers" has been added

  • Sensitive Data

    • Categories affected: Browsers

    • New criterion: 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 criterion: 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

  • App Categories: "Games" has been added

  • Irrelevant Notifications

    • Categories affected: Games, Video

    • New criterion: IN-2

      The app must not provide any heads up notifications.

  • Settings Flow

    • Categories affected: Video

    • Removed criterion: SF-1

      The app must proceed to the home page after sign-in or attempted sign-in.

  • Automotive Functionality

    • Categories affected: Video

    • Removed criterion: AF-1

      The app must not contain any distraction-optimized activities.

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 don't 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 don't 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 the categories

    • 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.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Google LLC
Publisher
Android (Google) (Official)
Distributed by
Android (Google)
Source
android/skills · cars/android-for-cars-parked-apps · commit bf68e2d
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE.txt)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google LLC or Android (Google).

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download android-for-cars-parked-apps.zip