androiddevelopertutorialshow-togoogle

How to Publish Android Games to Car Screens in 2026

Games on Android Auto and Automotive OS left beta. Add manifest flags, handle parked state, then ship on Play production.

September 22, 2026 Yum News

On 21 September 2026, Google moved the games category for Android Auto and cars with Google built-in from beta to general availability. Developers can now publish titles to open testing and production on Google Play, not only internal and closed tracks.

The work is smaller than a new game engine. If your title already follows adaptive layout rules, you mainly edit the manifest, respect the parked state, and pass car app quality review.

This guide follows the official Android Developers Blog post by Jan Kleinert and the Build games for cars docs. Pair it with existing large-screen work you may already have for App Bubbles on Android 17.

What changed on 21 September 2026

Google opened open testing and production for the games category on two surfaces:

Android Auto on phones running Android 15 and higher, projected to a compatible head unit while the vehicle is parked.
Android Automotive OS (AAOS) with Google built-in, where the game installs on the car itself.

Early access partners already shipped titles such as Angry Birds 2, Farm Heroes Saga, Candy Crush Soda Saga, and Beach Buggy Racing 2 during beta. Play now lists public collections for games on Android Auto and games on Android Automotive OS.

The target session is downtime: a charging stop, a curbside pickup, or a parked wait. Games stay parked-only. The system blocks launch and interaction while the car is in motion or UX restrictions are active.

Android Studio still ships a car app template if you want a clean module to test launcher flags:

Mark the app as a game

Play only places the title in the car games category if the manifest says so. Add android:appCategory on the application tag.

<application
    android:appCategory="game"
    ... >
</application>

Skip this flag and the review path treats you as a generic parked app, not a game.

Declare Android Auto support

Android Auto games require Android 15 or later on the phone. Add CAR_LAUNCHER to an activity intent filter.

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
        <category android:name="android.intent.category.CAR_LAUNCHER" />
    </intent-filter>
</activity>

You can put CAR_LAUNCHER on a different activity if the car should open a dedicated entry screen. Keep that activity simple. Car screens vary in size and the first frame should already fill the display.

Declare Android Automotive OS support

AAOS needs a hardware feature flag. Set android:required based on the Play track.

<uses-feature
    android:name="android.hardware.type.automotive"
    android:required="false" />

Google’s distribution rules:

Mobile track that also ships to phones: android:required must be "false".
Dedicated AAOS track: "true", "false", or omit the attribute. An omitted value behaves like "true" and limits distribution to automotive devices.

Choose the dedicated track only if you maintain a car-specific APK or App Bundle.

Dashboard of a parked car with a wide infotainment display

Handle the parked state

Games are parked apps. Do not add the distractionOptimized metadata element on any activity. Android Auto and AAOS already block the activity when the vehicle moves.

You still own audio and resume behavior:

Stop game audio when the user starts driving. Do not leave a soundtrack running in the background.
Do not let the player unpause while UX restrictions are active.
When the user opens the game again from the car launcher, restore the previous session as closely as you can.
Keep the frame rate stable. Freeze or stutter during play fails quality review.

Google’s TrivialKart for Unity sample shows the parked overlay on the Desktop Head Unit. Use that sample if you ship a Unity title and need a reference for pause-on-drive.

Declare optional gamepad support

Car screens accept touch. Many players still plug in a controller. If your input layer already maps a gamepad, declare the feature so Play can surface the title to controller shoppers.

<uses-feature
    android:name="android.hardware.gamepad"
    android:required="false" />

Keep required as false unless the game cannot run without a pad. A required gamepad hides the title from touch-only cars.

Fit odd car screens

Head units ship as portrait stacks and very wide landscapes. Google asks for a full-screen layout with no heavy letterboxing or pillarboxing. The DO-2 car app quality rule calls out large unused bars on landscape Android Auto screens.

Practical checks:

Use adaptive layouts or a camera that recenters on the playfield when the aspect ratio changes.
Test Android Auto against the documented Desktop Head Unit sizes, including 800×480 at 160 dpi.
Test AAOS with bundled hardware profiles in the automotive emulator, not only a phone emulator.

If you already made the title work on foldables and tablets, reuse that layout path. Do not ship a phone-only canvas and hope the car scales it.

Person connecting a game controller next to a laptop

Test before you opt in on Play

Build a release or internal-test bundle with the new manifest flags.
Run the Desktop Head Unit for Android Auto. Confirm launch from the car launcher, pause when you flip the DHU into a driving restriction, and resume after park.
Run the Android Automotive OS emulator. Confirm the automotive feature flag does not crash on a non-car phone if you used required="false".
Walk the car app quality guidelines for games.
In Play Console, opt in to the Android Auto and Android Automotive OS form factors.

Play reviews the game against those guidelines before open testing or production. Closed and internal tracks still help you collect logs from a small driver group first.

Publishing checklist

android:appCategory="game" is on the application tag.
CAR_LAUNCHER is on the activity you want on Android Auto.
android.hardware.type.automotive matches the track you picked.
No distractionOptimized metadata on activities.
Audio stops when driving starts.
Session state restores after a relaunch.
Layout fills portrait and wide landscape without large empty bars.
Gamepad feature is optional unless a pad is mandatory.
DHU and AAOS emulator runs are recorded for the review notes.

Tips that save a rejection

Treat parked play as a short session. Save often. Charging stops end without warning.
Avoid multi-minute unskippable ads. Reviewers watch for distraction and for blocked back navigation.
Keep permissions lean. A parked game that asks for location in the background looks like a driving app and invites extra scrutiny.
If you ship both a phone APK and an AAOS module, keep shared game code in a common Gradle module so the parked-state logic cannot drift.
Read Add support for Android Auto to your parked app when the DHU crops your HUD. That page lists the canonical resolutions Google tests.

Conclusion

Games for Android Auto and Google-built-in cars are no longer limited to partner beta tracks. Mark the app as a game, add CAR_LAUNCHER and the automotive feature flag, stop audio when the car moves, and submit after DHU and emulator checks.

Start with one adaptive title you already sell on phones. The manifest work is small. The review is about parked-only behavior and screen fit, not a rewrite of your engine.