Android Automotive OS and Google Automotive Services

Why this problem mattered

A phone should not have to be in a driver’s hand or line of sight for navigation, communication or assistance to work. I wanted the car itself to carry those capabilities in a way that felt native, reliable and calm. A built-in system was a platform decision in service of a human outcome: stay connected without holding the phone.

Overview

Android Automotive OS (AAOS) is the infotainment platform built into a vehicle and customized by the car maker. Google Automotive Services (GAS), marketed to drivers as Google built-in, is an optional layer that can add services such as Google Maps, Google Assistant and Google Play.

The user problem

Phone projection helps many drivers, but a deeply integrated vehicle experience needs to work without a connected phone and adapt to each automaker’s hardware and brand. Automakers also need a platform that can support apps and services without rebuilding the full software stack.

What the team shipped

Public Google materials describe AAOS as an open, built-in infotainment platform and GAS as the optional software layer for Google services. By September 2021, Google said people could buy or test-drive vehicles with Google built-in, including the Polestar 2 and Volvo XC40 Recharge, with additional automaker partners announced.

Product decisions

The public architecture separates a customizable open-source vehicle platform from optional Google services. It also creates a direct in-car app model through Google Play, supports automaker visual customization, and enables deeper vehicle integrations than a phone-projected experience.

Publicly supportable impact

Google’s 2021 announcement named Ford, General Motors, Honda, Polestar, Renault and Volvo Cars among participating or announced brands. This is ecosystem evidence from Google; no unverified adoption, revenue or personal contribution metrics are included.

Lessons

Platform strategy works when responsibilities are legible. Separating the operating system, optional services, automaker customization and developer surface gives partners room to differentiate while maintaining a coherent product foundation.

Related public announcements and coverage

Public sources: Android for Cars overview, https://developers.google.com/cars; Google built-in update, https://blog.google/products-and-platforms/products/assistant/upgrade-your-drive-google-your-copilot/; AAOS design overview, https://developers.google.com/cars/design/automotive-os

Team acknowledgment

This platform is collaborative work across Android, Maps, Assistant, Play, vehicle integration, design, engineering, research, safety, policy, developer relations and automaker partners. No individual should be presented as having created the system alone.