Android Automotive OS Alternatives without GAS

In the previous articles in our series, we have introduced GAS, or Google Automotive Services, which is a collection of applications and utilities developed by Google that an OEM can license for use in their Android Automotive system. Since GAS has applications that are seen as integral to a modern IVI system, it can seem like it is almost necessary to integrate into an AAOS-based IVI system. However, there are alternatives to GAS! In this final article in the GAS series, we would like to describe the two main options an OEM has if they do not power their IVIs with GAS.

GAS Alternatives?

The first option is to leverage one of the many AAOS-based platforms that are in the marketplace. Google is not the only player in the space when it comes to offering a package of applications and services that an OEM can integrate into their broader AAOS system. There are a wide variety of emerging solutions that are attempting to fill in the same gaps that GAS does. The main difference between these solutions is in how encompassing the solution is – it can range from something as simple as just an automotive app store for OTA app delivery to something as complex and fully featured as a full fork of AAOS with an extensive list of added services, utilities, applications, and tools.?

We would now like to list out and describe a few of these solutions to show the breadth of options in this space:?

Faurecia Aptoide – Faurecia Aptoide is a joint venture between Forvia (formerly Fauercia) and Aptoide that is centered on building out an industry-standard automotive application market. To that end, they offer a curated app store application on AAOS for OEMs that can be given custom branding and a curated application selection (including highly desired applications for cars such as Spotify, Zoom, and others).?

SnappOS - Snapp Automotive, an automotive-focused division of Snapp, has developed a modular, customizable AAOS system that offers useful solutions that baseline AAOS does not have, such as an advanced theming engine and a ready-to-go SDK for building a companion application for phones.?

SparqOS - SparqOS is another full infotainment system building off of AAOS, developed and integrated by P3. Much like Snapp, it has a full design language and a large suite of services that fill the gaps AAOS has, such as navigation. In addition, it also has its own automotive application store on offer, equivalent to Faurecia Aptoide.??

TomTom Digital Cockpit – TomTom has developed a full framework for building out Android Automotive-based digital cockpits. This includes many customizable and replaceable reference applications for things like HVAC, navigation, and EV charging, as well as expansive SDKs and APIs for building out even more differentiating experiences.

One particular word that you see come up repeatedly in the description of these products is customization. This focus is in direct response to some of the complaints leveraged against GAS; particularly that GAS imposes design constraints and requirements upon an OEM that may prove a bit too restrictive. So, if an OEM wants a high degree of differentiation for their system, it is a very valid route to take to leverage one of these third-party solutions that are much more eager to allow design flexibility and customization.?

So, as you can see, there are a wide variety of other ready-made solutions besides GAS for filling in the functionality gaps in AAOS. An OEM can integrate solutions for only the most complex, development-intensive applications needed for their system, or they can integrate a full platform solution with reference apps for all core functionalities and a full suite of SDKs and APIs added on top of AAOS, or anything in-between.

AAOS In-House Development?

The second option is to take development either mostly or completely in-house. That is, developing all the major applications and services you might need with your own developers or working with a service provider to build a bespoke AAOS IVI solutions. If you are thinking about this problem strictly from a resource cost perspective, you might have immediately rolled your eyes at that option. How is an OEM supposed to develop and / or manage its own play store, its own fully featured navigation application, and its own custom voice assistant, amongst other things? These are not just standard Android client applications, of course – if nothing else, each of these functionalities require fully working cloud backends for features that users expect. They are some of the most complex pieces of software that run in the IVI.?

Indeed, it would be a hefty investment to take this route. But the truth of the matter is that in-house development allows an OEM complete control of the services and data that flows from its vehicle out to cloud services and other parts of the vehicle. Even with the additional customization and flexibility provided by the GAS alternatives above, there will always be some control given over to a third party, some constraints placed on the final vision, unless the OEM develops and owns the full solutions themselves. It is not without precedence – OEMs such as Lucid have already created full AAOS experiences internally.?

Summary and Conclusion?

That is not to say that there is not a middle ground option – it is valid to leverage a third party turnkey solution like the ones list above for some missing functionalities, while still developing and maintaining all of the other differentiating functionalities internally. This is even an intrinsic part of how some said solutions work (such as the TomTom platform). The intricacies of IVI development are complex, and there is no one singular best fit solution. The key takeaway, however, is that even if Google is the primary developer of the Android Open Source Project and Android Automotive Operating System, they are not the only ones who can help OEMs get Android running in their infotainment.?

That concludes our article series on GAS and how it fits into the overall Android Automotive ecosystem. Stay tuned for more articles on Android Automotive!

Nick Dedenbach, Manager Android Automotive Team

For more information you can visit our Android Automotive Solutions page: https://valtech-mobility.de/portfolio/android-automotive-solutions/ or get in contact with our Business Development & Sales colleague Nils: [email protected]