Android Auto app development, for the categories Google allows.
An Android Auto app is not a separate product you publish for cars. It is your Android phone app with a service inside it that Android Auto reads and projects onto the car display, drawn in Google's own templates, in one of a short list of categories Google allows while driving. That list decides everything. Most of the questions people carry over from cross-platform app development stop mattering here: the framework the rest of your app uses is irrelevant, because the car layer is native Android code, and how good the idea is does not matter if it falls outside the list. This guide is the list, the rules around it, and what Google Play's car review asks before an app reaches a dashboard.
It also settles the question behind many searches for the Android Auto phone app: there is nothing to download. Android Auto is built into phones running Android 9.0 and higher, and every app Android Auto shows on the car screen is an ordinary phone app that declared support and passed review.
The short version
Nine categories, one native library, and a review that reads your release track.
As of Google's documentation dated 14 September 2026, Android Auto supports nine app categories: media (audio), messaging notifications, templated messaging and calling (both labelled labs and limited to testing tracks), navigation, point of interest, IoT, weather, and games while parked. Video and browsers run only on Android Automotive OS, the Android that is built into the car itself. Anything outside the list cannot be listed for Android Auto. You build the car side inside your phone app, with the Android for Cars App Library for the templated categories, upload the same bundle to Google Play, add Android Auto as a form factor, and pass a car app quality review that blocks a production release when it fails.
Two platforms, one library
What an Android Auto app actually is.
Google runs two car platforms and one library that targets both. Android Auto is projection: the phone does the work, the car display shows a driver-optimised version of the app, and the phone must run Android 9 (API level 28) or higher. Android Automotive OS is the car as its own Android device: the app installs on the vehicle, no phone required. The Android for Cars App Library, androidx.car.app, lets one codebase serve both, which is why Google's category table lists platforms per category rather than per app.
The part that matters for the app for Android Auto you are planning: it is the same APK or app bundle as your phone app. There is no second listing, no second package, and no second store account. There is a service, a manifest entry, and a review.
Your app never draws pixels on the car screen. It sends templates as data; the Android Auto host on the phone renders them at the car's size, in the car's style, within driver distraction limits.
Android Auto
Runs from the phone
Android 9.0 or higher, over USB or wireless. Nine categories. Ships inside the phone app on Google Play, after opting in to the Android Auto form factor.
Android Automotive OS
Runs on the car
Installed from Google Play on the vehicle, optionally on a dedicated release track. Adds video and browsers, and does not support messaging or calling apps.
CarPlay
Apple's equivalent for iPhone
Also category-limited, and gated by a carplay entitlement you request from Apple. A separate native integration in the iOS app, with its own templates.
If you have shipped to other screens that are not phones, the pattern will feel familiar. A fire tv app is built around a remote and a living-room distance; an Android Auto app is built around a driver who must not look. The platform decides the interaction model and the app fits into it, not the other way round.
The restricted set
The categories Google lets on the car screen.
This is the whole list. Google publishes it as the Supported app categories table in the Android for Cars overview, and it is honest about its own edges: two communication categories and templated media are labs or early access, restricted to testing tracks, and two parked categories never reach Android Auto at all. Every row below is copied from that table as published on 14 September 2026.
| Category | What it covers | Built with | Android Auto | Automotive OS | Google Play tracks |
|---|---|---|---|---|---|
| Media (audio) | Music, radio, audiobooks and other audio. Video is a separate category. | MediaBrowserService and MediaSession. Car App Library templates only through Google's Early Access Program. | Yes | Yes | All tracks. Templated media: internal and closed testing only. |
| Messaging notifications | Incoming messages read aloud, replies by voice. | MessagingStyle notifications plus a Service for reply and mark-as-read. | Yes | No | All tracks |
| Templated messaging (labs) | Browse conversation history, read and reply by voice. | Car App Library | Yes | No | Internal and closed testing only |
| Calling (labs) | Make and take calls on the car screen. | Telecom Jetpack library plus the Car App Library | Yes | No | Internal and closed testing only |
| Navigation | Turn-by-turn directions, including driver and delivery services. | Car App Library | Yes | Yes | All tracks |
| Point of interest (POI) | Find and navigate to places: parking, charging, fuel, and actions on them. | Car App Library | Yes | Yes | All tracks |
| Internet of Things (IoT) | Act on connected devices: garage door, lights, home security. | Car App Library | Yes | Yes | All tracks |
| Weather | Conditions at your location or along the route, optionally with navigation. | Car App Library | Yes | Yes | All tracks |
| Games (parked only) | Play while parked. Android Auto exits the app when the car moves. | Views or Compose | Yes | Yes | All tracks, generally available since September 2026 |
| Video (parked) | Streaming video while parked. | Views or Compose | No | Yes | All tracks |
| Browsers (labs, parked) | Web pages while parked. | Views or Compose | No | Yes | Internal testing only |
Source: Android for Cars overview, Supported app categories, developer.android.com, last updated 14 September 2026. Games moved from beta to general availability in the same month.
Be honest with yourself about the gaps. There is no category for shopping, social, banking, fitness, note taking, field service, or a company's internal tools. The car app quality guidelines open with criterion PC-1: "The app must not include features outside the app types intended for cars." A reviewer applies it before anything else, and polish does not change the answer. If your product belongs on a car screen, it belongs there because one of its features is navigation, places, audio, messages, calls, connected devices, weather, or a game to play while parked.
Try it
Does your idea fit an Android Auto category?
Pick the one thing your app would do on the car screen. The answer comes straight from Google's supported categories table, dated September 2026.
How the library works
Templates, a host, and a quota of five.
The library is the part that surprises developers coming from phone UI. You do not lay out views. You hand the host a template, a list, a grid, a pane, a message, a map, and the host draws it in the car's style, at the car's size, with the car's input method. That is how Google keeps every Android app on Android Auto inside driver distraction limits without reviewing pixels.
| Template | What it shows | Who can use it |
|---|---|---|
| List, Grid | Information items in a list or grid layout | All templated apps |
| Sectioned Item | Mixed browsing structure using lists and grids | All templated apps |
| Pane | Detailed information and prominent actions, optional image | All templated apps |
| Message, Long Message | A brief or longer full-screen message with actions | All templated apps |
| Search | Search bar and a results list | All templated apps |
| Sign-in | Options for signing in to the app | All templated apps |
| Tab | Tabs at the top switching between embedded templates | All templated apps |
| Navigation | Full-screen map with an action strip and optional routing card | Navigation |
| Place List (map) | A list of locations next to a map the library draws | POI |
| Map + Content | A map with a view of another template | Navigation, POI, Weather |
| Media Playback | The currently playing media | Media |
Template list from Google's Design for Driving templates overview, last updated 5 May 2026.
The five-template quota
Google's template restrictions cap a single task at five templates, and the last one has to be a Navigation, Pane, Message, Media Playback, Sign-in or Long Message template. Refreshing a template with the same type and main content does not count. Going back restores quota. Exhaust it and the host shows the user an error and closes the app.
This shapes the whole flow: three taps to a decision, one screen to confirm, done. During development you can turn on the debug overlay in Android Auto's developer settings and watch the step count on screen.
Categories live in the manifest
You declare a CarAppService with an intent filter for the category, androidx.car.app.category.NAVIGATION, POI, IOT, WEATHER, MEDIA, MESSAGING or CALLING, plus a com.google.android.gms.car.application metadata entry that points at an XML file listing the capabilities the app uses.
The car category is separate from the category you pick for the Google Play listing. One is what the host and the reviewer check; the other is how people find you in the store.
Everything from here is Android Studio work in Kotlin or Java: the Gradle dependency, the session and screen classes, the Desktop Head Unit test loop. It is native code even when the rest of the app is React Native or Flutter, and it lives in the Android project. If you are still deciding how the phone app itself gets built, the survey of Android app makers covers that layer. None of those tools draw car screens, so budget the car layer as separate native work whichever one you pick.
Google Play and review
From Play Console to the car, in seven steps.
Android Auto has exactly one distribution channel. Google's own overview says apps must be installed from a trusted source to run on a real vehicle, and lists Google Play and ONE store. There is no sideloading your way onto a dashboard, which makes the Play Console steps the actual launch plan.
- 1
Confirm the category before writing code
Match your feature to one row of Google's table. If nothing fits, stop here: criterion PC-1 rules out features outside the car app types, and no build passes review without a category.
- 2
Build the car layer inside your phone app
The Car App Library for navigation, POI, IoT, weather, templated messaging and calling. MediaBrowserService and MediaSession for audio. MessagingStyle notifications for messages. It is native Android code in the same app bundle.
- 3
Declare it in the manifest
A CarAppService with an intent filter for your category, and a com.google.android.gms.car.application metadata entry pointing at an XML file that lists the capabilities the app uses: template, media, notification.
- 4
Design inside the template quota
Each task gets at most five templates, ending on a Navigation, Pane, Message, Media Playback, Sign-in or Long Message template. Refreshes do not count. Exhaust it and the host shows an error and closes the app.
- 5
Test on the Desktop Head Unit
Google's DHU runs on your development machine and is the tool the quality guidelines tell you to validate every checklist item on. Turn on the debug overlay in Android Auto's developer settings to watch your template count.
- 6
Opt in to the form factor on Google Play
In Play Console, Advanced settings, Form factors: add Android Auto, then release an app bundle or APK containing the car support to a testing track. The same account and listing as your phone app.
- 7
Pass the car review, track by track
Every submission with an Android Auto artifact is reviewed against the car app quality guidelines. Closed testing only warns you; open testing and production block. The result arrives by email to your developer account.
Review by track
The review reads your release track
Once you have opted in, every submission that includes an Android Auto artifact is reviewed against the car app quality guidelines, and Google warns that this takes longer than a phone-only release. What a failed review does to the submission depends on where the artifact sits:
| Track | Car review | What a non-compliant build does |
|---|---|---|
| Internal app sharing (Android Auto only) | None | Nothing is checked. Useful for the first look on a real head unit. |
| Internal testing | None | No car review. Your internal testers get the build as is. |
| Closed testing | Non-blocking | A non-compliant build is flagged, but the submission is still approved. |
| Open testing | Blocking | A non-compliant build is rejected and the submission fails. |
| Production | Blocking | A non-compliant build is rejected. Fix, remove the rejected artifact, resubmit. |
Track behaviour from Distribute to cars, developer.android.com, last updated 14 September 2026.
The review uses Google's car app quality guidelines, organised in three tiers. Tier 3, car ready, is large-screen compatibility for parked apps. Tier 2, car optimised, is what every driving category must meet to be accepted on Google Play. Tier 1, car differentiated, is the extra credit. The page moves: in 2026 alone it added a screenshot requirement for Android Automotive OS listings (EP-4), light and dark theme support for custom-themed apps on library version 1.9 or higher (TH-1), and in September moved games from beta to general availability.
Before you press submit
- The declared category matches what the app does on the car screen (PC-1)
- Relaunching from the car home screen restores the previous state (EP-2)
- Test account details are in Play Console if the app needs sign-in
- A POI app's booking flow has a test account that can book without being charged
- A navigation or POI app not available in the United States allows a mock GPS location app
- Android Auto is added under Form factors and the artifact sits on a testing track
- Every task on the Desktop Head Unit finishes inside five templates
For drivers, not developers
The Android Auto phone app, answered plainly.
Where do I get the app for Android Auto?
You already have it. Google's help page puts it in one line: Android Auto is integrated into phones, you do not need to download it. There is no separate Auto app for Android to install. The requirements are an Android phone on Android 9.0 (Pie) or higher with an active data plan, a compatible car or stereo, and a good USB cable. Android Auto is not available on Android (Go edition) phones.
Wired or wireless?
Wired works on any phone that meets the Android 9.0 requirement. Wireless projection needs a phone with 5 GHz Wi-Fi support running Android 11.0, and a car or stereo that supports wireless Android Auto; in the EU, the phone also has to meet additional regulatory requirements for 5 GHz use in a car. The developer side does not change: your app does not know or care how the phone is connected.
Why is an app missing from my car screen?
Three reasons cover almost every case. Which Android app Auto will project is decided by the category table, not by how popular the app is, so an app outside the supported categories can never appear. The app is in a category but its developer has not opted in to the Android Auto form factor or has not passed the car review. Or the app was not installed from a trusted store: Google's overview says apps must come from Google Play or ONE store to run on a real vehicle. Requirements above are from Google's Android Auto help, as published in September 2026.
Where a builder fits
Where an AI app builder fits, and where it stops.
Newly builds the phone app: describe it, and it produces a native iOS and Android app from one codebase, then ships the iOS build to App Store Connect for TestFlight and review. It is a subscription at $25 a month with no free plan. Its own documentation is equally plain about the limit that matters here: v2 does not produce Android release builds, signing keys or Google Play uploads, and Android Auto apps exist only as Google Play releases. It does not generate Car App Library code either. So it cannot ship an Android Auto app today, and nothing on this page should be read as saying otherwise.
Where it earns its place is the phone app around the car feature, which is most of the product anyway: the accounts, the content, the dispatch board, the parking payments, the customer side. Teams whose workflow does not fit an off-the-shelf tool end up building that app themselves, and describing it to a builder is the fast way to get there. If one feature of that app genuinely fits a Google category, the car surface is a later, native Android addition, made by a developer and shipped from your own Google Play account, once the category question is settled.
Sources
Where the specifics came from.
Everything factual on this page comes from four Google pages, opened in September 2026. Google revises them; check the date stamp at the foot of each before you plan a release around it.
FAQ
Android Auto apps, answered.
No. Google's Android Auto help page says Android Auto is integrated into phones and you do not need to download it. You need an Android phone running Android 9.0 or higher with an active data plan, a compatible car or stereo, and either a good USB cable or, for wireless projection, a phone with 5 GHz Wi-Fi support running Android 11.0 or later. Android Auto is not available on Android (Go edition) devices.
Build the phone app first. The car screen is a category question.
Most of an Android Auto product is the phone app around it. See what people have described and shipped with Newly before you decide how yours gets built.