Android Auto and Automotive OS Officially Graduate Games Category to General Availability

Google has officially announced that the games category for Android Auto and cars powered by Android Automotive OS with Google built-in is graduating from beta to general availability. Following a successful early access phase where select partners brought entertainment experiences to dashboard screens, the platform is now open for developers worldwide to publish their titles to the open testing and production tracks on the Google Play Store.

The expansion allows developers to engage users during natural moments of downtime while on the road, such as waiting at an electric vehicle charging station or picking up a curbside order. With early access titles already paving the way, users can now browse dedicated collections of games tailored specifically for Android Auto and Android Automotive OS directly through Google Play. This milestone marks a major step forward in bringing rich, immersive digital experiences into modern connected vehicles, transforming the dashboard into a new frontier for mobile gaming during stationary periods.

Implement Car Support for Your Game

Adapting an existing Android game for the car screen is a streamlined process for developers who already adhere to best practices for building adaptive applications. Bringing a title to the vehicle environment primarily involves updating the app manifest file and ensuring that the gameplay respects the physical context of the car, specifically the vehicle parked state. Because dashboards have unique requirements regarding driver safety, understanding these technical prerequisites is essential for a successful launch.

Mark Your App as a Game

To distribute an application within the designated games category, developers must explicitly declare its classification in the app’s configuration files. This requires adding a specific category attribute to the main application element within the project manifest. By designating the software as a game early in the setup process, developers ensure that the Google Play Store properly indexes and categorizes the title for users browsing the in-car entertainment catalogs.

Declare Support for Android Auto

Game compatibility for Android Auto is rolling out specifically for devices running Android 15 and higher. To signal that a game is built to support this platform, developers need to include a designated category element within the intent filter of an activity in their manifest file. While this car launcher category element is commonly placed alongside the standard application launcher element in the same intent filter, developers retain the flexibility to house it within a different activity if they wish to initiate a separate specialized user flow when the application is launched from the car interface.

Declare Support for Android Automotive OS

For vehicles powered directly by Android Automotive OS, developers must declare hardware compatibility by incorporating a specific features tag within their manifest file. The required attribute for this feature declaration carries distinct rules depending on the chosen distribution track. When releasing an application on the mobile track, the requirement must be explicitly set to false. Conversely, when opting for a dedicated Android Automotive OS distribution track, developers have the flexibility to set the requirement to true, false, or leave it entirely unset, with an unset value defaulting to true and restricting availability strictly to native automotive hardware.

Handle the Parked State

Integrating entertainment software into a vehicle introduces a distinct physical context governed by strict safety regulations. Because cars alternate between driving and parked states, certain applications—most notably games—are classified as parked apps. To prevent any form of driver distraction, these applications are strictly prohibited from operating while the vehicle is in motion.

Both Android Auto and Android Automotive OS automatically block applications from launching or running when the car is moving or when active user experience restrictions are enforced. Developers must ensure their applications comply with these safety guidelines by omitting specific optimization metadata elements from their manifest activities. Furthermore, developers must implement robust logic that immediately halts all game audio when a vehicle begins moving, ensuring that sound cannot be unpaused until the car returns to a completely stationary, parked state.

When a user eventually relaunches the application from the home screen after a trip, the game is expected to restore the user’s previous session state as closely as possible. Ensuring high performance, smooth frame rates, and reliable responsiveness during gameplay sessions is crucial for passing platform quality evaluations.

Declare Game Controller Support

While dashboard screens inherently support touch input, many drivers and passengers prefer a traditional tactile experience using a connected gamepad. Developers whose titles support external controller input can declare hardware compatibility within their manifest file. This declaration enhances the visibility of the software within the Google Play Store for users actively searching for controller-compatible in-car entertainment. Setting the requirement attribute to false indicates that while controllers are supported, they remain optional unless physical gamepads are mandatory for the core mechanics of the title.

Support Common Screen Sizes and Aspect Ratios

Automotive displays vary significantly across different vehicle makes and models, featuring diverse physical dimensions, resolutions, and orientations, including both portrait and wide landscape formats. To deliver a polished user experience, games must be fully adaptive, scaling seamlessly to fill the entire dashboard display without unsightly letterboxing or pillarboxing. Developers targeting Android Auto should reference official guidelines for testing against canonical screen sizes, while those building for Android Automotive OS can utilize bundled hardware profiles within the standard software development emulator.

Publish Your Game to Cars

Once the technical implementation and adaptive layout adjustments are complete, developers can officially opt in to the Android Auto and Android Automotive OS form factors directly through the Google Play Console. Before submitting builds to production, teams are strongly encouraged to evaluate their software against the comprehensive car app quality guidelines established for the gaming sector.

Testing procedures rely heavily on specialized developer tools. The Desktop Head Unit allows teams to verify Android Auto compatibility, while the dedicated Android Automotive OS emulator replicates the native dashboard environment. Every submitted title undergoes a thorough review process measured against strict car app quality standards before receiving final approval for open testing or production release tracks.

With the official transition of the games category into general availability, software creators now have a robust framework and an expansive audience base to bring innovative gaming experiences directly to the modern vehicle dashboard.