Modern cars are becoming computers on wheels, with vehicle functions increasingly controlled by software from pre-heating your car to using your smartphone as a car key. Yet Google's latest push into the automotive space reveals a tension that will shape your next vehicle: carmakers want the benefits of software standardisation, but they're reluctant to let anyone, including Google, run the show.
On Monday, Google announced Android Automotive OS for Software Defined Vehicles (AAOS SDV), extending beyond the car's screen to provide an open infrastructure for non-safety parts of vehicles, allowing carmakers more choice and time to focus on delivering unique experiences. This is a significant expansion from what Android Automotive currently does. Right now, Android Automotive lets carmakers build premium infotainment experiences while significantly reducing development costs and time to market, including Android apps for media streaming, navigation, and even games.
The new version aims to tackle a real problem. Cars are becoming software-defined, but different manufacturers have developed different software architectures, integrating software modules from dozens of different suppliers. This fragmented approach means carmakers have to spend time on building infrastructure rather than what truly differentiates them in a fast-moving market. Google's pitch is straightforward: use our platform, reduce costs, speed up development, and get new features to customers faster through over-the-air updates.
Renault is leveraging the Android Automotive OS SDV platform for its upcoming Renault Trafic e-Tech, with production set to begin in late 2026. Qualcomm is scaling the Android Automotive OS SDV platform through a strategic partnership; at CES 2026, Qualcomm introduced Snapdragon vSoC on Google Cloud and announced a scaling collaboration to deliver a turnkey, pre-integrated AAOS SDV stack on Snapdragon Digital Chassis platforms.
The Control Problem
Here's where things get complicated. The new AAOS expansion provides a compact, performant and scalable software foundation extending deeper into the vehicle architecture to power software components throughout the vehicle such as the seat actuator, instrument cluster, climate control, lighting, cameras, mirrors, telemetry, and more. This sounds good in principle, but carmakers remain protective of their software architectures. They've learned that software has become a core part of the customer experience, and increasingly, a source of ongoing revenue.
Adoption has been measured. AAOS will be featured in nearly 90% of mid-to high-level vehicle models shipped in 2026, but that includes many carmakers using the open-source platform without Google's proprietary services. Less than 6% of new vehicles shipped with AAOS will feature Google Automotive Services in 2025, and carmakers are cautious about deploying full Google services due to limitations in customisation and ownership, and uncertainties over long-term support.
The Subscription Question
There's a consumer angle that shouldn't be overlooked. New features that can be deployed via software updates could require subscriptions, as companies already do with subscriptions for heated seats, performance modes, and upgraded cruise control. The infrastructure that makes Android Automotive attractive to carmakers is the same infrastructure that could lock consumers into ongoing payments for features that once came standard.
For Australian drivers, this matters. If your next car runs Android Automotive SDV, software updates could introduce features that weren't available at purchase, but may require a subscription to unlock. That's not necessarily a negative; the same infrastructure enables faster bug fixes and genuine improvements. But it's a trade-off worth understanding.
Open-source availability is planned for later this year, which could fragment the platform further as different carmakers customise it for their needs. That fragmentation is precisely what Google claims AAOS SDV solves.
The reality is messier than Google's pitch. Carmakers want lower development costs and faster deployment of features, but they also want to own and differentiate their software experience. Google wants to become the backbone of automotive software. These goals can coexist, but the friction over who controls the vehicle and what data flows where will likely shape the next decade of automotive software development. What carmakers choose will ultimately affect what you experience in the driver's seat.