In-vehicle infotainment (IVI) in consumer and fleet vehicles has been shaken up by the rise of Android Automotive (also known as Android Automotive OS and AAOS) in recent years. Initially released 7 years ago, it has slowly expanded into many vehicle models across an ever-growing list of automotive OEMs – the Polestar 2 by Polestar, the Accord by Honda, and the Nautilus by Lincoln just to name a few.
Norman Palmhof E-Mobility
Android Automotive OS: GAS vs. NON-GAS
The case it makes for itself is certainly very enticing. It allows OEMs to utilize the Android developer community that has been built up for over 15 years. It makes the development of partner applications much more appealing to those potential partners, as most of them have Android applications already. It also provides a more standardized approach to infotainment application design that will lead to more consistent user experiences across the industry.
Before we proceed with a view of the AAOS landscape, it’s important to clarify what Android Automotive is not. Android Automotive is not Android Auto, the Android experience that most drivers may be familiar with. Android Auto is an app mirroring solution developed by Google, that allows users to project key Android features from their phone to a valid receiver IVI module.
So now we know that Android Automotive is distinct from Android Auto, and is much more powerful in terms of the kinds of experiences that can be developed. But what actually sets it apart from your standard Android OS? After all, several OEMs and tier 1s have developed many similar infotainment systems over the years, even some that build off of “vanilla” Android. So what does Automotive add to the mix?
So now we know that Android Automotive is distinct from Android Auto, and is much more powerful in terms of the kinds of experiences that can be developed. But what actually sets it apart from your standard Android OS? After all, several OEMs and tier 1s have developed many similar infotainment systems over the years, even some that build off of “vanilla” Android. So what does Automotive add to the mix?
So now we know that Android Automotive is distinct from Android Auto, and is much more powerful in terms of the kinds of experiences that can be developed. But what actually sets it apart from your standard Android OS? After all, several OEMs and tier 1s have developed many similar infotainment systems over the years, even some that build off of “vanilla” Android. So what does Automotive add to the mix?
