Android Games Move From Beta to General Availability for Cars, Opening New Horizons for Developers

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 initial partners introduced park-only entertainment options to dashboard displays, developers can now publish their games directly to open testing and production tracks on Google Play. This milestone transforms vehicle dashboards into new entertainment hubs designed to capture user engagement during moments of natural downtime, such as waiting at electric vehicle charging stations or parked for curbside order pickups.

The transition from beta to a fully supported general availability category represents a significant expansion for the automotive app ecosystem. Early access partners have already laid the groundwork by bringing a variety of titles to the parked-only experience for cars, and these early collections are now readily browseable across dedicated Google Play curation pages for both Android Auto and Android Automotive OS. With public access now open, the platform is inviting the broader developer community to adapt their existing portfolios for the in-vehicle environment, tapping into an entirely new touchpoint for mobile gaming.

Implement Car Support for Your Game

Adapting an existing Android game for the vehicle screen relies heavily on foundational mobile development principles. Developers who already adhere to best practices for building adaptive applications will find that bringing a title to cars primarily involves configuring the application manifest and ensuring the software responds appropriately to the vehicle’s parked state. Rather than requiring entirely separate codebases, the ecosystem encourages developers to leverage their current assets while applying specific structural tags that flag the software as compatible with vehicle infotainment systems.

Mark Your App as a Game

To ensure proper distribution within the Google Play Store’s newly graduated games category, developers must explicitly declare their application type within the manifest file. This is achieved by adding the specific application category attribute to the main application element. By designating the software as a game at this foundational level, developers signal to the platform how the title should be classified, curated, and displayed to users browsing for in-car entertainment options across supported vehicle displays.

Declare Support for Android Auto

Vehicle compatibility requirements vary slightly depending on the underlying platform architecture. For Android Auto, games are supported on devices running Android 15 and higher. Developers wishing to target this platform must include a specific category element within the intent filter of an activity inside their manifest file. While this category element is typically placed alongside the primary launcher intent filter, developers retain the flexibility to assign it to a different activity if they prefer to trigger a distinct entry point specifically designed for the vehicle interface.

Declare Support for Android Automotive OS

For vehicles running Android Automotive OS natively on the hardware, developers must declare support by incorporating a specific hardware feature element within their manifest file. The required attribute associated with this feature carries distinct restrictions depending on the chosen distribution track. When publishing an Android Automotive OS app through the mobile track, the required attribute must be explicitly set to false. Conversely, when utilizing the dedicated Android Automotive OS distribution track, developers have the flexibility to set the requirement to true, false, or leave it unset entirely, with an unset value defaulting to true and restricting the app exclusively to native automotive hardware.

Handle the Parked State

Because automobiles introduce a unique physical context defined by distinct driving and parked states, safety remains a paramount concern for in-car applications. Software categorized as games falls under the classification of parked applications, meaning they are strictly prohibited from running while the vehicle is in motion to prevent dangerous driver distractions. Both Android Auto and Android Automotive OS automatically enforce these safety protocols by blocking activities from launching or operating whenever the vehicle moves or when user experience restrictions are active.

To comply with stringent driver distraction guidelines, developers must ensure they omit specific optimization metadata elements from their application manifests. Furthermore, games must be programmed to instantly halt all audio playback the moment a vehicle begins moving, ensuring that sound cannot be unpaused until the car returns to a fully parked state. Additionally, the system demands a seamless user experience upon return; when a user relaunches the app from the home screen after parking, the game must restore its previous state as closely as possible, maintaining high standards of responsiveness without freezing or stuttering during active play sessions.

Declare Game Controller Support

While modern car screens rely heavily on touch input, many drivers and passengers prefer the tactile experience of a dedicated physical gamepad. To accommodate this preference, developers can declare hardware gamepad support within their manifest file. Declaring this capability enhances the visibility of the application within the Google Play Store for users specifically searching for controller-compatible entertainment. Developers can indicate that controller support is optional by setting the requirement attribute to false, ensuring the game remains accessible to touch-only users while appropriately highlighting advanced input options for hardware enthusiasts.

Support Common Screen Sizes and Aspect Ratios

Automotive displays vary wildly across different vehicle makes and models, featuring an array of unique shapes, dimensions, aspect ratios, portrait orientations, and wide landscape configurations. To deliver a polished user experience, games must be fully adaptive, scaling dynamically to fill various screen real estates without suffering from awkward letterboxing or pillarboxing. Developers targeting Android Auto are encouraged to consult official testing guidance against canonical screen sizes, while those building for Android Automotive OS can utilize bundled hardware profiles within testing emulators to verify visual fidelity across diverse dashboard layouts.

Publish Your Game to Cars

Once developers have completed the necessary manifest configurations, code adjustments, and safety integrations, they can opt in to Android Auto and Android Automotive OS form factors directly through the Google Play Console. Before pushing updates to production tracks, developers are strongly advised to run their titles against established car app quality guidelines specifically tailored for the games category.

Verification tools such as the Desktop Head Unit allow teams to thoroughly test Android Auto compatibility on external displays, while the Android Automotive OS emulator provides a robust sandbox for evaluating native performance. Every submitted title undergoes a rigorous review process measuring compliance with specialized automotive quality guidelines before receiving final approval for open testing or production release. With the games category now fully available to the public, the automotive landscape is poised to offer richer, more engaging digital experiences for passengers during every journey.