Google is getting ready to turn Android from “just your car’s infotainment system” into the software backbone for most of your car’s non-safety features – and it’s doing it in open source. That’s a big deal for how quickly new car features roll out, how often they get updated, and how much control automakers keep over the experience they ship.

Today’s cars already act like rolling computers: they pre-heat before you leave, remember your seat position, sync with your phone, and get over-the-air updates. Behind the scenes, though, most brands are juggling a mess of different software stacks from different suppliers, which slows everything down and forces them to keep rebuilding the same basic plumbing every time. Google’s pitch is simple: instead of every carmaker reinventing that infrastructure, share a common, open foundation and compete on the experiences you layer on top.

That’s where Android Automotive OS for Software Defined Vehicles – AAOS SDV – comes in. It takes Android Automotive beyond the central screen and runs as a lightweight, headless platform across multiple computers in the car, handling things like climate control, lighting, mirrors, cameras, seat motors, telemetry, and the instrument cluster UI. In plain language: the same Android DNA that drives your apps and maps can now also drive the air-con, the digital speedometer, and the way your car talks to the cloud.

Later this year, Google plans to publish AAOS SDV into the Android Open Source Project (AOSP), opening up the whole stack for uses beyond infotainment. For automakers, that means production-ready building blocks, a standard “signal catalog” so everyone speaks the same language for things like door status or battery level, and a service-oriented architecture where functions can be updated at a granular level instead of with giant, risky firmware blobs. It’s also tuned for cloud-first development: engineers can spin up virtual cars using Android Virtual Device (Cuttlefish) and Google Cloud tools, test new features in a digital twin, and only then push them to real vehicles.

On the driver side, you’re not going to see “Now powered by AAOS SDV” on a badge, but you should feel the difference. Google is talking about more cohesive in-car experiences: one integrated voice assistant that can tweak your seats and AC, smarter, proactive maintenance alerts, faster rollouts of new features, and fewer awkward seams between the dashboard UI and the rest of the car’s behavior. Because it’s open-source, there’s also potential for a broader developer ecosystem around car functions – though automakers will still tightly control what actually ships in production.

Google isn’t doing this alone, either. The company is already working with Renault Group and Qualcomm, using Snapdragon-based digital chassis hardware as the underlying compute platform for upcoming software-defined models, including vehicles like Renault’s Trafic e-Tech planned toward the second half of this decade. Those early partnerships are meant to prove that AAOS SDV isn’t just a research project but something robust enough for real fleets and mass-market cars.

The obvious question is how comfortable car brands are letting Google this deep into their stack. Some will lean in, betting that a shared, open foundation helps them move faster and cut costs; others may prefer their own closed platforms or rival ecosystems. But the direction of travel is clear: if your next car feels more like a phone that keeps getting better every few months, there’s a good chance software like Android Automotive – now open-sourced for core car functions – is doing a lot of the heavy lifting.