Android has been creeping into cars for more than a decade, first with the phone-based Android Auto and later with built-in Android Automotive OS. Even when Android is running on cars, it has not been allowed outside of the infotainment box. That could begin changing soon with Google’s new plans for software-defined vehicles (SDVs), but don’t expect most carmakers to step on the gas right away.
Car companies are notoriously protective of the software running on their vehicles, which has become a core part of the experience as cars have shifted to “computers on wheels.” Part of that is a matter of safety, but the data collected by automotive software is also highly valuable. As a result of everyone going their own way, vehicles have different software stacks that can include incompatible components from myriad suppliers. Google says it can fix this “fragmentation” mess with a more powerful version of Android Automotive OS (AAOS) designed for SDVs.
For better or worse, cars are increasingly reliant on software for new features—for example, remote climate controls or using smart keys on your phone. Google’s car efforts didn’t start there, but they’ve definitely trended in that direction. Early on, the company’s in-car play was Android Auto, which could run on a phone or be projected from a phone to supported car displays. Google eventually dropped the phone-based Auto to focus on the projected Android Auto experience and Android Automotive OS, which runs Android locally on the vehicle. That’s where Google’s latest initiative is focused.
