Google Officially Launches Games Category for Android Auto and Android Automotive OS

Google has officially announced that the games category for Android Auto and vehicles powered by Android Automotive OS with Google built-in is graduating from its beta phase to general availability. Following a successful early access period that saw several developer partners bring interactive entertainment to the parked-only vehicle experience, the tech giant is now opening up access for all developers to publish titles to the open testing and production tracks on Google Play.

This major milestone arrives as automakers and software developers look for new ways to engage drivers and passengers during natural periods of downtime. Whether motorists are waiting at an electric vehicle charging station, parked while picking up a curbside order, or resting during a long journey, the dashboard screen is increasingly becoming a secondary hub for digital experiences. With the official rollout, developers now have clear pathways to adapt their existing Android games for the automotive environment, adhering to specific safety standards, technical requirements, and publishing criteria set out by Google.

Implementing Car Support for Your Existing Games

For developers who have already embraced best practices for building adaptive apps across the Android ecosystem, bringing an existing game into the car environment is a straightforward process. Primarily, the transition involves configuring the application manifest file correctly and ensuring that the software strictly respects the vehicle’s parked state. Because automobiles present a unique physical context defined by distinct driving and parked states, safety remains paramount.

To distribute an application within the newly available games category, developers must explicitly declare its category by adding a specific attribute to the application element within their manifest file. Furthermore, declaring support for Android Auto requires targeting devices running Android 15 and higher by including the appropriate category element within an activity’s intent filter. Similarly, bringing a title to Android Automotive OS requires integrating a dedicated hardware feature tag into the manifest. Developers can choose whether this feature is strictly required depending on whether they opt for a mobile-focused distribution track or a dedicated automotive track.

Prioritizing Safety and the Parked State

Perhaps the most critical aspect of developing games for the car screen is managing safety and driver distraction guidelines. Because games are categorized as parked applications, they are strictly prohibited from running while the vehicle is in motion. Android Auto and Android Automotive OS inherently block activities from launching or operating when a car is being driven or when user experience restrictions are active.

To comply with these safety measures, developers must ensure they do not include distraction-optimized metadata elements in their app manifests. In addition, game audio must automatically cease the moment a vehicle begins moving and remain muted until the car is safely parked again. When users relaunch the game from their dashboard home screen, the software is expected to restore the previous application state as seamlessly as possible. Smooth performance, responsiveness, and freedom from freezing or stuttering during gameplay are crucial for passing the rigorous review process.

Supporting Controllers, Screens, and Publishing Tools

While modern car screens universally support touch input, many drivers and passengers prefer the tactile feel of a traditional gamepad. Developers whose titles support external hardware can declare game controller compatibility directly in their app manifest. This declaration enhances visibility within the Google Play Store for users actively searching for controller-friendly experiences, provided the controller remains an optional rather than mandatory requirement, unless the gameplay strictly demands it.

In addition to input methods, developers must account for the wide variety of screen sizes and aspect ratios found across different vehicle makes and models. Ranging from portrait displays to wide landscape layouts, car dashboards require fully adaptive user interfaces that can scale to full screen without unwanted letterboxing or pillarboxing. Developers can test these layouts using canonical screen sizes for Android Auto or leverage bundled hardware profiles within the Android Automotive OS emulator.

Once all technical adjustments have been made, developers can opt into the Android Auto and Android Automotive OS form factors directly through the Google Play Console. Before submitting titles to production, teams are encouraged to evaluate their software against dedicated car app quality guidelines for games. Utilizing tools such as the Desktop Head Unit for Android Auto and the official emulator for Android Automotive OS allows creators to rigorously test their user experience. Once reviewed and approved, these titles will join the growing collections available to drivers on the road.