Shorten feedback cycle in Android Automotive development

Automotive industry is in disruption: transformation towards software-defined vehicles pushes the fundamental architecture towards high performance central computers. This will shake the foundations of the automotive software ecosystem: current absence of standardization drives the car OEMs to take software development in-house and launch their whatever.OS for the purpose. This shifts the software ownership away from their traditional tiers.

This change has already happened with in-car infotainment systems. Android Automotive OS (AAOS),  is already widely chosen by the world’s leading car manufacturers. Google is repeating the same takeover with the in-car infotainment system as it did in the mobile industry a decade ago. It’s simple: who wouldn’t want to support Android apps, and or provide monthly security updates via existing and robust OTA channels, or in general, benefit from the large developer community that keeps on innovating and bringing added-value? Recent history proves that those who turn blind eye to the ecosystem are at risk to lose their customers completely: no apps, no users – Windows Phone, Tizen, BlackBerry, just to name a few.

More and more OEMs select Android as their standardized in-car infotainment OS, but at the same time they all want to have a unique look and feel. Some are replacing the Google Automotive Services (GAS) with their own equivalent, and most tweak the UI in order to differentiate. There are some excellent toolkit providers that enable advanced design features on top of the AAOS; and there are some really experienced Android development providers who can integrate the AAOS into vehicle’s subsystem; replace the GAS with custom services and alternative voice control; and implement the GUI design with the more advanced 3D libraries.

How to ensure these integrations work in the long run: from a functional, stability, and energy consumption perspective? During the years we have witnessed that Android OS is not always a silver bullet: even today we see each Android based configuration having tens to hundreds of stability and performance issues per public SW release: AOSP, AndroidTV, WearOS, even the Google Pixel configurations have their unique problems. Android Automotive makes no exception here, and the automotive industry should set the bar even higher for these quality parameters.

Profilence has been helping Android smartphone, TV, and medical device vendors for years to make their products robust and error-free, leading to higher end-user satisfaction. We are now bringing our expertise to the automotive segment, where it is applicable to in-vehicle infotainment software stack:

  • We have the technology and know-how to credibly model long term driver experience in laboratory conditions and prove the correlation with failures in the field (FFR). This is how developers’ feedback cycle is shortened from weeks to hours.
  • We can harness your test fleets with world class telemetry diagnostics and optimize your investments in the fleet testing.

With our help, you will be able to deliver premium quality software to your end users, in a shorter time period and with reduced costs. And, you don’t need to worry about the quality degrading over time.

Our experts are happy to tell you more about Profilence capabilities. If you’d like to get a free stability analysis for your device under development or hear more Profilence’s thoughts on efficiently shipping high quality devices, write to sales@profilence.com and we’ll be happy to set up a meeting.