In 2024, there were 79,2 million cars produced worldwide. Almost 79% of them already come with integrated telematics. That is about 58 million cars that can be potential “carriers” of your application.

Is AAOS really that promising?

Car companies have been trying to build their own operating systems for the past ten years, but the path turned out to be way too expensive: support, updates, UX, integration with smartphones, app stores, voice assistants required resources at the level of technology giants.

As a result, brands began to transfer infotainment management to ecosystem-scale platforms – Apple and Google. And while Apple is betting on the Next Generation CarPlay (which is still phone-dependent), Google has gone further. Unlike CarPlay, AAOS is not a projected phone screen but a full-fledged car OS running right in the vehicle.

Since 2022, AAOS has been gaining an advantage over other infotainment operating systems, and it is projected to surpass 60 million shipments by 2030.

Indeed, a few years ago, the platform was tested mainly by Volvo and Polestar. Today its implementation has been confirmed by Renault, GM, Ford, Honda, as well as Hyundai and Kia.
In 2023, General Motors stated that it uses Android Automotive as the base platform for infotainment systems in both its electric and internal combustion vehicles. Back in 2021, Ford announced a multi-year partnership with Google, including OS integration into future models. Honda has been producing Google Built-In cars since 2023 and plans to expand the range in 2025–2026. Renault has already launched the Megane E-Tech and Scenic E-Tech.

If we add up only these brands, it already becomes obvious that the large-scale expansion of AAOS is not a matter of “someday” but probably of the next two or three model cycles. Manufacturers update the product line every 2–4 years, and with each update, the share of models on AAOS automatically increases.

Why app creators should act now?

1. First movers define the category before others catch up

One of the main reasons to develop for Android Automotive OS is the opportunity to gain a real competitive advantage through early entry into the platform. In the mobile world, such windows closed years ago: the App Store and Google Play have long been oversaturated, and it is almost impossible to become a category leader there without huge marketing budgets.

The situation is the opposite with AAOS. The Google Play for Cars store currently consists of dozens of apps, not thousands. From 2021 to 2024, Google gradually expanded categories, adding navigation, podcasts, media, audiobooks. For example, at I/O 2023, Google announced updates to the Android for Cars App Library to allow new app categories like IoT and weather. Even so, many niche segments remain empty.

We asked Maxim Leykin, Chief Technology Officer at Bamboo Apps, how long will the low-competition window in Google Play for Cars last.

Maxim Leykin, CTO at Bamboo Apps

“Assuming massive AAOS adoption by OEMs and dominant market share, I would estimate the remaining window of “low competition” to be roughly 2 to 3 years (ending around 2027–2028). Right now, Google is actively working to simplify the transition of applications from mobile devices to automotive ones, specifically targeting the “low-hanging fruit” of parked apps. In early 2025, it announced the “Car Ready” program to allow mobile apps that are already optimized for large screens (like tablets) to be automatically reviewed and enabled for use in the car while parked. This change can bring thousands of new apps into the AAOS ecosystem with minimal development effort, flooding the “Parked” categories”.

Besides, it’s well-known that car applications are subject to strict safety, usability, and regulatory requirements, which significantly limit the number of apps that can be approved for in-vehicle use. These limitations might create an opportunity for some developers to enter the platform ahead of competitors and secure a foothold there for a long time.
Car screens are not an environment where the user switches between dozens of applications daily. On the contrary, if they see 2–3 offers in a category in a store, they pick one of them and use it for years.

This is especially noticeable in navigation: the user selects an app, tests it once, and rarely switches. The same applies to music, audiobooks, streaming platforms, and driver services.

For developers, this means that early entry into the AAOS provides category leadership, low competition, and almost guaranteed entry into the store’s recommendations.

The post 3 major reasons why app makers should explore Android Automotive OS now first appeared on Android Automotive Solutions by Bamboo Apps.

Cars are literally becoming digital devices on wheels. It’s no longer enough to just drive from point A to point B – drivers and passengers expect the car to entertain them, help with navigation, and understand their preferences. As vehicles become increasingly software-defined, consumers are placing higher demands on in-car digital experiences.

However, the opinions of automobile executives and consumer tastes differ significantly. According to a Capgemini Research Institute study, 73% of CEOs consider brand reputation a major consideration when purchasing a car, while only 48% of buyers cite this as the most important factor.

Besides, the same study reveals that 77% of consumers are turned off by experiences that aren’t hassle-free, and 59% are dissatisfied with digital services that fall short of being best-in-class. The message is clear: users are quick to turn away when their expectations aren’t met.

In this regard, Android Automotive OS (AAOS) provides a technological foundation that allows you to flexibly create and deploy new types of in-car applications and services. As a result, there is a wide range of opportunities to adapt to the real needs of users and position user experience as a critical differentiator in the automotive market.

About Android Automotive OS

Android Automotive OS is a modified version of the Android operating system designed specifically to run directly on the car’s head unit. Unlike Android Auto, which projects the phone interface to the vehicle screen, AAOS is an independent platform that manages multimedia, navigation, climate, and other functions directly within the onboard system. It was created by Google and Intel, in partnership with automakers including Volvo and Audi, and debuted in March 2017.

Android Automotive has already become the in-vehicle infotainment system of choice. Since 2020, when the Polestar 2 became the first car to be equipped with Android Automotive, the industry has been keeping an eye on it.

Starting from 2022, AAOS is gaining the upper hand over other infotainment operating systems, predicted to reach more than 60 million shipments by 2030. Nowadays, more than a hundred production models use Android Automotive, including models from Polestar, Volvo, Renault, Chevrolet, Honda, Ford, and BMW. Nissan, Mitsubishi, Stellantis, Honda, Lucid, Porsche, and Hyundai are also interested in adopting AAOS in the near future.

Why Android Automotive matters for the automotive industry

AAOS’s potential is truly revealed when a wide variety of market participants come into play.

For some, it’s an opportunity to keep up. When services like Spotify turn out to be built into the car’s interface out of the box, their direct competitors, even if they hadn’t thought about this segment before, begin to quickly look for ways to get there.

For others, on the contrary, it is a reason to take a step forward. Suppliers like Bosch see AAOS as a tool that can be used to quickly assemble a unique solution to meet the requirements of a particular automaker, whether it’s smart navigation or an adaptive voice assistant.

And there are those who use the system as a strategic element of the brand. For example, Mercedes-Benz doesn’t just integrate Android Automotive – it builds its own digital experience around it, where voice control and climate control merge into a single user scenario.

New in-car services for a competitive edge

As competition between automakers and technology companies intensifies, the ability to offer unique embedded services becomes an important differentiation factor. For example, an opportunity to watch streaming videos, play simple games while charging an electric car, or receive proactive recommendations from AI-based systems allows you to turn cars into a truly ‘smart’ environment.

New user engagement opportunities

Android Automotive OS opens the doors to the automotive segment for companies not previously associated with this industry. Developers of media, messaging, and IoT applications have the opportunity to reach a new audience like drivers and passengers, who increasingly perceive the car as an extension of their digital ecosystem.

When familiar scenarios like listening to music, texting, and navigation adapt to driving, interaction with applications becomes more frequent and prolonged in new contexts: on the road, in the parking lot, while waiting for charging.

In addition, new monetisation models are emerging. The ability to implement in-app purchases directly from the car screen opens up additional revenue for both app developers and automakers. This can include access to premium content (such as paid podcasts or exclusive music selections), microtransactions in games, paid features in navigation services, or integration with subscriptions, such as a subscription to a video service optimised for cars.

Tailored solutions for OEMs

Tier-1s can refine AAOS in accordance with the individual OEM requirements to their infotainment system, starting from the visual design of the interface and ending with deep integration with the vehicle’s equipment and services. They take on the task of customising the platform: redesign the user experience in accordance with brand standards, adjust support for specific hardware components, ensure compatibility with the automaker’s internal systems, and are responsible for meeting industry standards for safety and performance.

Moreover, thanks to the support of the standard Android API and custom extensions, some specific functionalities can be integrated a way faster. Tier-1 vendors can quickly implement or replace components such as voice assistants, navigation, multimedia applications, and connectivity modules.

In fact, this is the level at which the standard version of Android Automotive turns into a unique proprietary system that is recognisable to the driver as part of the ecosystem of a particular brand.

Deep integration with car controls

Android Automotive OS can deeply integrate with vehicle systems: multimedia, climate control, navigation, sensors, and even voice assistants. This creates scope for applications that can adapt to real-world driving conditions and user preferences.

Navigation services can take into account battery charge or fuel level, media players can adjust volume depending on speed, and smart assistants can control the temperature in the cabin. This access to the vehicle’s systems gives developers the tools to create more useful and context-aware solutions. For technology companies and automakers, this opens opportunities to create new digital services embedded not on top of, but within the very logic of the car.

Key app categories built for Android Automotive

One of the main advantages of the AAOS is that it gives you an opportunity to deploy an ecosystem of applications in the car that are familiar to the user on a smartphone, but adapted to the automotive environment. Four key categories are developing especially actively now: media, messaging, navigation, and IoT.

Media apps

Media applications are, in fact, the basic standard. Music, podcasts, audiobooks – everything that the user is used to while being on the road. Spotify, YouTube Music, and Audible have already been adapted to AAOS and allow you to control playback via touch or voice. At the same time, the manufacturer can customise the interface to match the visual style of the brand.

Messaging apps

Messengers are a separate story. It is important for the driver not to be distracted from the road, but at the same time to stay in touch. But integrations with WhatsApp, Telegram, and Google Messages allow messages to be read out by voice, and users can respond via dictation. Everything is built around a hands-free approach.

Navigation apps

In addition to the default Google Maps, alternatives like Waze or Sygic are also supported on Android Automotive. Navigation apps can access vehicle data – for example, the remaining charge in the EV – and can suggest routes based on charging stations or traffic jams in real time.

Internet of Things

IoT applications in the context of Android Automotive are tools that let a car interact with other devices and digital services outside the vehicle. Through applications like SmartThings, the driver can turn on the heating in the apartment from the car, check whether the front door is locked, or open the gate in front of the entrance. All this is done directly from the infotainment screen or by voice control.

Available Android Automotive apps

The Android Automotive OS ecosystem continues to expand, and today 100+ customised applications are already available in cars with Google built-in support. This includes navigation, music, messengers, podcasts, as well as the first examples of games and video services (available for use in parking mode).
In February 2025, Google officially announced that such categories as videos, browsers, and games would be available for download on AAOS vehicles. They are intended to be used while the vehicle is parked. Among such apps are games like Farm Heroes Saga, streaming services like AMC+ and Paramount Plus, as well as a news app from NBC.

In the announcement, Google didn’t roll out a specific list of apps, but a constantly updated list of compatible apps is available on Google Play in a special section dedicated to car-ready apps.

How Android Automotive apps integrate with vehicle systems

One of the key advantages of the Android Automotive OS is the deep native integration of applications with vehicle systems. In contrast to solutions like Android Auto, where the smartphone acts as the main computing center, here, the operating system itself runs on the head unit of the car and interacts with its systems directly.

Integration with infotainment and display systems

Applications can make full use of the central screen (infotainment system), the digital dashboard (gauge cluster), as well as secondary displays for passengers. Android Automotive OS natively supports various control types, including touchscreens, rotary controls, and hardware buttons that are easily configurable through the standard Android input framework.
A special feature of the platform is its support for multi-displays, which allows content to be displayed not only on the central screen, but also on the dashboard, provided the OEM permits it. Only system applications or applications with manufacturer’s permissions can be used to display information in the cluster, which allows users to display navigation prompts, current track data, call and message notifications, and climate control indicators.
At the same time, Android Automotive OS receives real-time data through the Vehicle Hardware Abstraction Layer (Vehicle HAL), including speed, gear position, and driving mode. This way, users dynamically control the display of content, for example, disable video playback at high speed.
The infotainment system and the dashboard work in close synchronization: navigation instructions on the main screen can be duplicated or supplemented on the dashboard, information about the media being played is updated in both places, and the voice assistant responses are displayed where provided by the OEM design.

Integration with other vehicle controls and ADAS

The AAOS provides an API for interacting with vehicle functions, such as climate control, battery level, and lighting settings. This allows you to create customised interfaces and automation like starting seat heating at low outdoor temperatures. AAOS can also interact with ADAS systems: lane keeping assistants, blind spot monitoring, parking, and others. Although direct control of ADAS is not allowed by third-party applications for security reasons, applications can use its data, for example, for contextual notifications, alerts, or real-time route adaptation.
While some functions are fully controllable through the platform, others are limited to read-only access. The tables below outline which systems typically allow full control and which expose data for monitoring only.

Integration with sensors

Applications can access information from vehicle sensors: GPS, acceleration sensors, tire pressure, ambient temperature, and others. This expands the possibilities for creating context-sensitive functions, such as weather tips or driving style recommendations.

However, as with other subsystems, access levels vary depending on the type of sensor and OEM restrictions.

Access to other vehicle data streams

Through the Vehicle Properties API, applications can read vehicle states, such as whether the doors are open, whether the headlights are on, and what mode the transmission is in. This is useful for building smarter interaction scenarios, such as blocking distracting content on the screen when moving.

Internet access and cloud services

Since Android Automotive OS works independently of a smartphone, it can use the car’s built-in cellular modem or Wi-Fi module to connect to the Internet. This allows applications to work with cloud services, synchronise profiles, receive OTA updates, and send telemetry.

Artificial Intelligence in Android Automotive

Artificial intelligence is becoming a key element in the transformation of the automotive interface. The latest IBM’s “Automotive 2035” study reports that 74% of executives surveyed believe that by 2035 vehicles will be software-defined and AI-powered.

AI-powered personalisation

Many automakers, including Volvo and Polestar, are already using Android Automotive with the ability to recognise a specific driver. For example, the system can, without a single command, activate the night mode on the display, suggest the desired playlist on Spotify, and turn on the seat heating if the temperature outside is below zero.

Context-aware suggestions

Depending on the situation, the driver can receive cues in a variety of circumstances. Google Assistant in Android Automotive can remind you to check out earlier than usual if traffic is forecast along the usual route. Or, knowing that you drive out of town on Fridays, it can suggest setting a route in advance, taking into account traffic jams and stops for charging an electric car.

Voice recognition and natural language processing (NLP)

AAOS allows integration with Google Assistant or alternative OEM voice assistants. Thanks to this, users can execute commands in a natural way. You can say “Show the nearest gas stations” or “Turn on soothing music” and get an instant response.

NLP systems are also used for personalisation: the assistant can take into account the context like time of day, location, preferences of the driver, and provide more relevant answers.

Object recognition

Although Android Automotive itself does not perform object recognition or manage autopilot or cameras directly, it can visualise and display data received from external systems. For example, if the ADAS detects pedestrians or cyclists nearby, Android Automotive can show warnings or alerts on the vehicle’s interface.

Navigating the challenges of Android Automotive app development

The development of applications for Android Automotive OS opens up new horizons, but it is also accompanied by a number of technical and organisational difficulties, especially when compared with the Android mobile ecosystem.

Compatibility across car models

Manufacturers adapt AAOS to specific models by adding or removing functions. As a result, the same application may run differently on different vehicles. It is important for developers to test their applications in emulators and on real devices from different manufacturers using Vehicle HAL (Hardware Abstraction Layer) and Google templates.

Customisability

The AAOS imposes restrictions on UI/UX design, especially for security-related applications (such as navigation or messaging apps). The interface must match the templates of Material Design for Cars, otherwise Google will not allow it to be published. Therefore, it is impossible to simply ‘migrate’ a mobile application. It’d be required to adapt screens, simplify logic, and work with the CarApp or Jetpack for Cars frameworks.

Safety and compliance standards

Since we are talking about software inside a moving vehicle, the requirements for stability and fault tolerance are higher than those for conventional mobile applications. AAOS applications must be checked for compliance with the Android Compatibility Test Suite (CTS) and Car Quality Guidelines, especially if they relate to media, communications, or navigation. Google also restricts the use of WebView in browser applications and prohibits third-party video streaming solutions if they may distract the driver.

Over-the-Air updates

Many OEMs implement OTA updates for the system and applications, which adds flexibility but also complicates the work of developers. Applications must be resistant to different firmware versions, able to work offline, and updates should not require driver intervention, this is the rule of UI-less updates.

Data privacy concerns

The AAOS provides access to vehicle data, but strictly regulates its use. For example, access to data on speed, location, battery charge, or driving modes must be justified and authorised by the user. The Vehicle Data API can only be used within permitted application types (e.g. EV charging or navigation). But McKinsey’s survey shows that only fewer than 20 percent of all car owners are willing to share their data.

Looking ahead: the future of Android Automotive

Android Automotive is positioned as the future cornerstone of connected car technology and in-vehicle infotainment. Most major car manufacturers have adopted or announced plans to adopt AAOS, with only a few exceptions like Tesla and Mercedes, which use Linux-based platforms but may integrate Android apps as third-party services.

We asked Maxim Leykin, Chief Technology Officer at Bamboo Apps, whether he believed Android Automotive would serve as a driving force or just one of many competing platforms in the next 3–5 years.

Maxim Leykin, CTO at Bamboo Apps

“I don’t see much of a contradiction in the question. The specifics of the automotive industry and the market is that they are highly fragmented and extremely competitive, thus, the same goes for in-vehicle software. So, I don’t think there will be one and only software platform solely adopted by the industry.

At the same time, I’m sure that Android Automotive, already adopted by many major automakers like Ford, General Motors, Honda, Nissan, Renault, Volvo, Polestar and more, has the strong potential to be a significant driving force in the software-defined vehicle landscape over the next 3–5 years. The reasons are: its deep integration with vehicle functions, openness for customisation via AOSP, access to the Google ecosystem (Maps, Assistant, Play Store), and support from a large global developer community”.

According to predictions, Android Automotive is set to grow rapidly in the coming years. The next few years might be crucial for Android Automotive’s expansion, and it is expected to capture around 18% of the market share by 2027. And around 80% of Volvo’s cars are forecast to have the system by then.

Partner with us for Android Automotive app development

When it comes to developing Android Automotive OS apps, Bamboo Apps is your trustworthy partner. Our team has successfully collaborated with leading companies in the sector such as Jaguar Land Rover, Mitsubishi Electric, Škoda Auto, Rinspeed, and Gentherm. We have 10+ years of experience in creating user-friendly automotive media and connectivity apps that integrate with modern in-car systems.

Let’s talk about building your next AAOS app – contact us to start planning.

FAQ

What is the difference between Android Auto and Android Automotive OS?

Android Auto is a projection system in which your mobile device is connected to the car and its interface is displayed on the car screen. Android Automotive is a separate operating system installed in the car itself, running independently of the phone.

What types of apps are available for Android Automotive?

As of 2025, media, navigation, messaging, and IoT apps, as well as (in extended format) videos, browsers, and games are supported, provided they meet driving safety requirements.

How can developers get started with developing apps for Android Automotive?

Google provides SDKs, emulators, and documentation for adapting Android applications to AAOS. There are also specialised guidelines for each type of application (media, navigation, etc.).

What are the benefits of integrating Google services into Android Automotive?

With Google Automotive Services, developers gain access to Google Assistant, Google Maps, the Play Store, and other services, simplifying the user experience and expanding monetisation opportunities. However, working with GAS requires separate certification and partnership with Google.

The post Elevating in-car experiences with Android Automotive apps first appeared on Android Automotive Solutions by Bamboo Apps.

BlackBerry QNX has been a staple of the Automotive industry for well over a decade as a highly secure OS for connected cars. Despite stepping back from infotainment systems in recent years, its market stronghold on safety-crucial functionality remains very much palpable.

On the other hand, Android Automotive OS is a relatively new industry player, which has been steadily gaining steam among OEMs and Tier-1 suppliers. With robust and easily accessible functionality, it’s a system worth considering for any new automaker.

Having experience with both technologies, we’ll compare their strengths and weaknesses, and see which system may be best for you.

Basics

In the most basic sense, QNX and Android Automotive are embedded systems that power the main functionality of a smart vehicle.

QNX is a Unity-like proprietary OS that has established a strong presence in the Automotive market. Initially released all the way back in 1982, it was one of the first commercially successful microkernel systems.

Android Automotive OS released in March 2017 as a full-stack, open source platform running directly on in-vehicle hardware. It’s notable for being able to directly integrate with GAS (Google Automotive Services), such as Maps, Play Store, Assistant, etc.

Functions

Both systems offer a similar feature set, in that they can handle a large variety of entertainment, connectivity, security, and comfort functions.

QNX and AAOS provide the following functionality:

• Apple CarPlay and Android Auto compatibility;
• voice control with speech recognition and natural language understanding;
• multimedia discovery and playback;
• GPS navigation;
• OTA updates;
• rear view camera;
• comfort settings control;
• and others.

QNX is notable for its support for both HTML5 and Android apps and enhanced security. On the other hand, AAOS’ signature feature is Google Automotive Services (GAS). As was already mentioned, it provides instant and seamless integration with car versions of Google Assistant, Google Maps, and the Play Store.

Hardware and Software

Setup Process

AAOS

The setup process of Android Automotive OS

If you’ve ever set up an Android phone, you know what setting up an Android Automotive OS is like. Being a Google product, the system requires you to provide usage data and diagnostics to the company. Once that is done, you can sign into a Google account – or stay logged out, which will limit you to just the default set of apps (radio, Bluetooth, Google Maps).

AAOS supports multiple users, so one car can store multiple user profiles with different comfort settings (seat position, mirror position, temperature, etc.) and apps installed. It also has a Guest user feature for cases where the car owner lends the vehicle out to a friend, for instance.

Additionally, the system can integrate with the driver’s Android phone to pull up contacts and Google Maps bookmarks from their account.

QNX

Unlike Android, QNX doesn’t require integration with Google. It also doesn’t force any email-based sign-in or configuration on the user’s end – all features are available from the get-go.

Though, consequently, the software does not pull contacts and bookmarked locations from an existing user account and only supports one driver profile at a time.

Home Screen

AAOS

Default AAOS homescreen

Android Automotive’s home screen (or Car Launcher) can display all the expected widgets, including navigation, media playback, communication, the status bar, notifications, and other components. By default it displays a list of the apps installed on the system, but it doesn’t have to.

The Car Launcher is designed with the expectation that it will be customised. Its layout, colours, icons, status bar, widgets, and so on can all be modified to fit any brand image – as long as it passes the hard safety and minimal distraction guidelines.

On the whole, the interface will be immediately familiar to anyone who has ever used an Android smartphone or tablet before.

QNX

Example QNX interface (non-default)

QNX home screens are what most of us think of when they imagine a standard in-vehicle HMI. They typically feature a similar array of information to AAOS, with a non-fullscreen map, media playback, notifications, weather, and other status data.

The default interface relies on the bottom bar menu to switch between navigation, media, calls, settings, app list, and so on. But much like AAOS, that preset is highly customisable and can be completely revamped depending on the automaker’s wishes.

Play Store Ecosystem

Google Play Store for AAOS

Google Play Store is absolutely massive – but its dedicated Android Automotive section isn’t. Google is very particular about what apps can and cannot be installed on AAOS due to strict safety regulations. As a result, the section contains a decent, but still relatively modest number of solutions.

The current selection includes not just GAS services, but media streaming services (Youtube, Audible, Spotify, iHeartRadio, etc.), POI apps, parking apps, fuelling and charging apps, news applications, in-vehicle onboarding software, and even games.

BlackBerry Ecosystem

The software ecosystem of BlackBerry

BlackBerry has its own software ecosystem, which includes speech recognition solutions (Nuance and open source alternatives), HERE navigation, open source options for cloud and embedded TTS, Bluetooth functionality with Mindtree, and more.

QNX itself incorporates a multitude of infotainment services, with its own Multimedia Suite, Blink-based Web Browser, Acoustic Management Platform, Speech Framework, BlackBerry OTA Platform for updates, among others.

Customisation Options

The Future of Android OEM Customisation

Android Automotive is fully skinnable, meaning car manufacturers can make it look however they like using the existing code, APIs, and the app ecosystem as the basis. Yet the possibilities for system customisation are continuously expanding.

I/O 2023 has demonstrated Google’s commitment to continuously enriching the system, with Youtube support, games, and smart message replies greatly expanding Android Automotive’s entertainment and communications possibilities. In addition, this year’s Detroit Auto Show marked the reveal of Amazon Prime Video, Zoom, and the Weather Channel apps on AAOS.

Google’s Android for Cars App Library now also officially supports IoT applications. These will enable users to control various smart home devices, such as the thermostat, locks, garage doors, cameras, and so on – all from inside their cars.

Material Design is planned to come to AAOS – though only for developers, not for drivers. According to the official documentation, OEMs will be able to use so-called design tokens that represent repeated design decisions implemented across the system. These will allow for dynamic changes in the interface depending on the situation.

Material design tokens on Android

Security features will continue to be customisable depending on local market requirements, with automakers being able to disable or adjust certain features during driving. This includes the Play Store, car manual, keyboards, text messages, videos, and so on. Though, if the car has a front-seat passenger, said features can be made available for them.

The Future of QNX Customisation

BlackBerry has also been presenting some exciting opportunities for QNX enhancement over the course of this year. The company has been especially keen on cloud technologies.

For one, BlackBerry IVY was revealed at CES 2023. It’s a cloud-connected automotive AI platform developed in tandem with Amazon Web Services designed to help OEMs deploy third-party apps at a faster pace. It’s currently pre-integrated on 3 commercially-available digital cockpits, but will gradually become available on a wider range of systems.

BlackBerry innovations at CES 2023

Another cloud technology revealed at CES was QNX Accelerate, a cloud version of QNX Neutrino RTOS. This is a big milestone for the development of embedded vehicle systems that will drastically reduce development cycles for new automotive and IoT solutions. Select OEMs and Tier-1 suppliers (Marelli, Continental) have already received early access to it.

“[Cloud computing] is going to be foundational to all our products — the operating system, and the hypervisor, and safety products,” says John Wall, Senior Vice President and Head of QNX at BlackBerry.

Models Applicability

QNX

BlackBerry QNX remains massive among leading brands, including Bosch, Ford, BMW, Aptiv, General Motors, Toyota, Volkswagen, Honda, Mercedes-Benz, and many others. It’s a well-established industry partner with a lot of trust behind it.

According to TechInsights, BlackBerry QNX is embedded in over 235 million cars worldwide as of 2023 – that is a 20 million year-over-year increase.

“In ten years, BlackBerry QNX has expanded from being in over 16 million vehicles to over 235 million today.  Undoubtedly, we are the market leader for secure and safety-certified automotive software,” states John Chen, Executive Chairman & CEO, BlackBerry.

Android Automotive

Android Automotive is still in its early stages of adoption, so the current list of models supporting this technology is relatively short. Nevertheless, it includes models from such brands as: Audi, Cadillac, Chevrolet, Chrysler, Dodge, Ford, GMC, Honda, Lincoln, Lucid, Maserati, Polestar, Rivian, Volvo, and Renault.

This lineup will only expand over time. Currently, Ford and Volkswagen are looking to integrate AAOS into their cars more broadly (namely for the F-150 Lightning and VW ID.2all models). Porsche and Mercedes-Benz are also preparing to incorporate Android into some of their vehicles. So the majority of OEMs will offer at least one model compatible with AAOS by 2024.

By 2025, AAOS is predicted to become the predominant automotive OS in new vehicles, surpassing QNX and Automotive Grade Linux. In 2026, 90% of new car models (mid and high level) will be using Android Automotive OS. Though it bears mentioning that less than 6% of those vehicles will feature GAS due to data safety and privacy concerns.

Shipments of new vehicles by infotainment OS in 2019-2030 by ABI Research

BlackBerry QNX vs AAOS: How to Choose an Automotive OS

The choice ultimately depends on what you want to prioritise and how much resources you’re willing to dedicate to infotainment development. Let’s look at the basic pros and cons of each system to make it more clear.

Blackberry QNX OS Pros & Cons

Pros

• Security. QNX is compliant with multiple security standards (including ISO 26262) and is well-protected from cyber attacks thanks to its built-in security model, which makes it the go-to choice for many mission-critical systems.
• Stability. The system’s microkernel architecture allows it to run different services in separate protected memory spaces, resulting in very stable performance.
• Customisation. QNX is decently flexible, in large part owing to its modular architecture. This makes it easy to shape for a variety of markets and customer requirements.
• Fast time to market. QNX follows the POSIX programming standard, which helps reduce the time it takes to turn an idea into a market-ready product.

Cons

• Cost. The system is commercial, meaning you’ll need to pay licensing fees, which can get rather expensive compared to open-source solutions.
• Few third-party apps. QNX supports a very limited scope of third-party applications compared to its competitors, which restricts the system’s functionality. And obviously, its own ecosystem is no match for Google’s.
• Learning curve. QNX has its own specific architecture, tools, and programming model that developers will need to understand. The learning curve for that can get pretty steep.
• Underwhelming design. While QNX runs the core functionality of the system behind the scenes, carmakers usually build their own interfaces on top of it (e.g. Audi’s MMI and Ford’s Sync). However, since automakers tend to lack UI design expertise, these interfaces often end up underwhelming.
• Support. A point of contention, but a point nonetheless: some developers note that QNX support can be slow and unresponsive, with updates and fixes taking a long time to roll out.

Android Automotive OS Pros & Cons

Pros

• Open source. AAOS is completely open source, making it much cheaper than its proprietary competitors.
• GAS. AAOS offers deep integration with car versions of Google Assistant, Google Maps, and the Play Store by default.
• Predeveloped extensions. Developers can use predeveloped automotive extensions and a variety of libraries for Bluetooth, navigation, and other functionality, which significantly speeds up the development process.
• Accessibility. It’s an Android system, meaning finding developers that know how to work it is as easy as can be.
• Robust customisation. As long as designers stick to the automotive safety guidelines enforced by Google, AAOS customisation capabilities are pretty much limitless.

Cons

• Not real-time. AAOS cannot be used to power lower-level processes the same way QNX can due to its less fault-tolerant performance.
• Limited adoption (so far). As of today, Android Automotive is supported by a limited range of vehicle models, most of which are in the higher price range.
• Privacy. Automakers that agree to implement AAOS into their cars also agree to share all vehicle data with Google, and not all OEMs and drivers are comfortable with that prospect.
• Safety concerns. The open-source nature of the system and the distrust towards Google’s data protection measures are slowing adoption, particularly when it comes to GAS.

Pay Attention Points

If we boil it down to the most crucial factors, QNX is extremely safe and reliable, but lacks user-friendliness and can have a very resource-intensive dev cycle. On the other hand, AAOS is cheap, pretty, and easy to work with, but isn’t as stable.

AAOS is perfect for creating a great user experience as an infotainment system, while the real-time architecture of QNX is a better fit for mission-critical functionality, such as brakes, sensors, etc. So technically you can integrate both to fulfil different purposes.

BlackBerry QNX vs Android Automotive OS: Final Verdict

Expert Opinion

Bamboo Apps has experience in working with both QNX and Android Automotive OS, so we reached out to the company’s CTO for his opinion on the matter.

Maxim Leykin, CTO at Bamboo Apps

“The major benefit of BlackBerry QNX is the microkernel architecture, which minimises downtime and cyberattack surfaces through isolation and separation mechanisms,” says Maxim Leykin, the Chief Technology Officer at Bamboo Apps.

“Device drivers and system services run alongside applications, separated from one another and the kernel. Such architecture makes Blackberry QNX especially good for usage on mission-critical embedded systems with a limited amount of resources and high requirements for performance, scalability and security.”

Maxim goes on to mention the usual gripes people have with QNX, including licensing costs, the longer learning curve, limited customisability, and the relatively small number of libraries. This is where AAOS compares favourably to it.

“…Android Automotive OS (AAOS) is based on the open source and very commonly used Android OS which simplifies the learning curve and allows to engage more developers. It is highly customisable and suitable for rapid development of a fancy and complicated UI. The number of libraries ported for AAOS is big.”

“Unfortunately, AAOS is not a real-time OS,” he continues. “It’s not as reliable and fault-tolerant as QNX, thus it can hardly be used when developing software for low-level embedded systems with a limited amount of resources and high reliability requirements.”

User Opinion

The general consensus online seems to be that QNX is a very solid system for those looking to maximise security at the cost of user experience and development speed. “A bit challenging to develop for”, “not the most affordable operating system available”, “could be more user friendly”, and “the app selection is not as robust as other platforms” are some of the common complaints about the product.

On the other hand, Android Automotive is very much beloved for its sleek interface and ease of development – while being not so beloved for enforced feature lockouts, complete data submission to Google, and its Play Market store section being a little underwhelming (though, still offering a considerably bigger app selection than QNX).

Users have to say the following when comparing the two systems:

• “In my eyes [AAOS]’s not a competitor, they are a partner! AAOS runs on the Blackberry QNX hypervisor so it can run non-critical applications that need to interface with the vehicle. QNX does have an Infotainment system that used to be a player in the market, but BB has effectively dropped that to focus on the core mission critical systems that run the car!”

• “QNX is a lower level operating system that controls the sensors, brakes, etc. Basically the car components that require realtime guarantees. QNX also provides a hypervisor (to run multiple QNX instances for different car subsystems) and an infotainment system that’s likely not going to be as popular as AAOS.”

In other words, QNX-based infotainment isn’t seen as a viable competitor to AAOS. However, Blackberry’s lower-level safety systems can work alongside an Android interface to deliver the ultimate driving experience that’s both secure and pleasant to navigate.

The post QNX vs AAOS (Android Automotive OS): Compare the Platforms first appeared on Android Automotive Solutions by Bamboo Apps.

The post Developing Android Automotive OS apps with multimedia capabilities first appeared on Android Automotive Solutions by Bamboo Apps.