By Sharad Bairathi, Managing Director, Embitel
Vehicle engineering is shifting from a hardware-first model to a software-first one. In conventional vehicles, most functionality is fixed at the time of production. Software-defined vehicles (SDVs) decouple software from hardware, so features, performance and digital services can change long after a vehicle leaves the factory.
That shift is driving adoption of open and scalable platforms such as Android Automotive OS (AAOS). AAOS is now being extended beyond infotainment to support a broader range of vehicle applications and software-defined architectures.
Building the Software Foundation for SDVs
Built on the Android Open Source Project (AOSP), Android Automotive OS is more than an in-vehicle infotainment operating system. It draws on more than a decade of Android platform development, which gives automakers a mature and continuously evolving base. At the same time, it leaves them free to customise the user experience and vehicle functions to suit their brand.
At its core, AAOS combines an Android-based operating system with automotive-specific frameworks. These frameworks support capabilities such as communication, diagnostics, software updates and secure integration with electronic control units (ECUs). The architecture is modular, so OEMs can build software that is maintainable and can be deployed across multiple vehicle platforms.
As SDV architectures evolve, AAOS is extending well beyond the dashboard. It is now used in more of the vehicle’s computing domains, including the controllers behind the instrument cluster, climate control, lighting, cameras, mirrors and telemetry. That leaves OEMs with one software base to work from, rather than several.
More recently, AAOS is evolving towards a software-defined architecture built around headless Android, service-oriented software and virtualisation. This allows vehicle functions to operate more independently of the underlying hardware and enables software to be developed and tested in virtual environments before physical hardware is available. This can accelerate software development by allowing teams to develop and validate software earlier, while reducing dependency on physical hardware. The shift could help OEMs build more modular software that can be reused and updated across different vehicle platforms.
Why OEMs Are Turning to AAOS
Unlike proprietary software stacks, AAOS lets OEMs control both the user interface and the underlying software architecture, while remaining compatible with the wider Android ecosystem. Engineering teams can build differentiated digital experiences without writing a new platform from scratch.
AAOS also enables software reuse across vehicle programmes. That reduces engineering complexity, limits software fragmentation and shortens development cycles. Building on a common base helps OEMs control development costs and bring new models to market more efficiently.
AAOS supports independent updates to vehicle applications and services over the air. Manufacturers can add features, improve existing ones, strengthen vehicle security and fix software faults remotely through a vehicle’s life.
Manufacturers can also choose between Google Automotive Services (GAS) and non-GAS ecosystems when building on AAOS. GAS is a suite of Google applications and services, including Google Maps, Google Play and Google’s in-car voice assistant. OEMs that choose GAS can draw on Google’s ecosystem, while those opting for a non-GAS approach can integrate their own applications and services through a custom app store. This flexibility allows manufacturers to choose the ecosystem that best fits their strategy while continuing to differentiate the overall experience.
What Changes Inside the Cabin
Expectations for the in-vehicle experience are now set by the other digital devices people use every day. Personalisation and ease of use have moved from premium features to baseline requirements.
AAOS helps automakers meet those expectations through voice interaction, AI-based services and a growing application ecosystem. Each driver can also hold a personal profile that carries preferences for navigation, media, climate and other functions from one journey to the next.
Connected services can also work from shared context. Navigation, electric vehicle charging, media, telemetry and cloud applications can act on the same information about the route and the vehicle’s state, rather than each working in isolation.
Accelerating Automotive Software Engineering
AAOS also benefits the engineering organisations building next-generation automotive software. As software complexity grows, development efficiency has become a competitive factor in its own right.
Because AAOS is open-source, engineering teams can build on a shared codebase instead of developing AAOS domain software from scratch for every vehicle programme. This enables OEMs to reuse software components across programmes, reduce redundant engineering work and shorten development cycles. It also supports virtual development through tools such as Cuttlefish. Software can be built, validated and tested in a virtual environment before it reaches physical hardware.
The development environment is also becoming more AI-assisted. Google’s latest automotive tooling brings Gemini-powered assistance into Android Studio for Platform, alongside support for automotive software development using languages such as Rust, C/C++ and Java. This points to a broader shift towards cloud-based and AI-assisted engineering workflows, where software can be developed and validated earlier in the vehicle development cycle.
A further advantage is Android’s mature development ecosystem. Established tools, reusable libraries and a large global developer community let engineering teams move faster and manage software development at scale.
Where This Leaves OEMs
As the industry moves towards software-defined architectures, OEMs face growing pressure to accelerate the development and deployment of vehicle software. AAOS provides a foundation for addressing this challenge by enabling software reuse, virtual development and more modular architectures. Combined with OTA updates, a common operating system also allows OEMs to continuously evolve vehicle capabilities throughout the vehicle’s lifecycle.
As architectures become more centralised and software becomes increasingly modular, capabilities such as virtualisation and AI-assisted development can help OEMs develop, validate and deploy software faster. The goal is not simply to create a common software platform, but to establish a development approach that reduces redundant engineering work and enables software to evolve more quickly across vehicle programmes.