Volvo Cars Moves Android Automotive Development onto Horizon

Volvo Cars Moves Android Automotive Development onto Horizon

Volvo Cars is moving its global Android Automotive Operating System development environment onto Horizon, the open-source software development platform created by Accenture and Google Cloud. The Swedish car maker will also become Horizon’s lead automotive industry partner, giving its engineers a direct role in refining the platform for wider use across vehicle manufacturing.

Behind the migration is a practical engineering problem. Vehicle software development still depends heavily on specialist workbenches, electronic control units, development boards and physical test rigs that are expensive, geographically constrained and difficult to reproduce at the scale expected of modern software development.

Horizon attempts to move more of that work into virtual environments. Builds can be accelerated, tests multiplied across virtual vehicles and development environments made available to engineers without waiting for specialist hardware to arrive on a desk.

Briefing

• Volvo Cars is migrating its global Android Automotive OS development environment to Horizon.
• Horizon was initiated by Accenture and Google Cloud as an open-source automotive software development platform.
• Virtual Cuttlefish-based environments are claimed to enable software testing up to nine times faster.
• Accenture and Google Cloud claim infotainment feature development costs can be reduced by up to 40%.
• Volvo Cars will act as lead industry partner, with its engineering experience helping shape future development of the platform.

Moving the Development Vehicle into the Cloud

Horizon combines cloud-native development infrastructure, virtual test environments and AI-assisted workflows around Android Automotive OS. Google described Horizon when it introduced the project in 2025 as an open-source reference development platform, with a virtual-first approach intended to reduce some of the integration work falling on automotive manufacturers.

A central component is Cuttlefish, Android’s configurable virtual-device architecture. Horizon uses Cuttlefish-based Android Automotive environments to run development and testing workloads without requiring an equivalent physical vehicle or hardware bench for every engineer and test instance.

Instead of reserving a limited piece of physical equipment, development teams can instantiate virtual environments as required and run tests in parallel. Physical device farms remain part of the system where actual hardware is necessary, but access can be managed remotely alongside their virtual equivalents.

Accenture and Google Cloud say this arrangement can make software testing up to nine times faster. They also claim infotainment feature development costs can fall by as much as 40%, while intelligent caching and optimised build pipelines can reduce feedback cycles that previously took up to two hours to minutes. Those figures originate with the platform’s developers and should be regarded as claimed performance rather than independently demonstrated results across Volvo Cars’ production engineering operation.

Volvo Cars as the Industrial Test Case

Volvo Cars gives Horizon a large automotive manufacturer already operating Android Automotive at production scale.

Its relationship with Google predates Horizon by almost a decade. Volvo partnered with Google in 2017 around Android-based infotainment, and the relationship has since expanded across connected services, in-car digital systems and, more recently, Google’s Gemini AI assistant.

Migrating the global AAOS development environment puts Horizon beneath software engineering processes serving a substantial installed vehicle base.

“We’re building some of the most complex products in the world, which requires a development environment built to match,” said Gregor Zetsche, Head of Connected Experience at Volvo Cars. “As Horizon’s lead industry partner, we can directly solve our toughest engineering challenges and empower our teams to deliver new experiences faster than ever.”

Volvo’s engineers will also expose the platform to the less tidy realities of automotive development: distributed teams, existing toolchains, multiple suppliers, hardware dependencies and software that eventually has to function reliably inside a vehicle rather than a generic computing device.

Accenture and Google Cloud say experience from the collaboration will be used to refine Horizon and expand its generative AI capabilities before extending the approach across other automotive and industrial manufacturers. Other organisations are already working with the two companies, although they have not been identified in the announcement.

The Economics of Virtual Engineering

The more interesting economics may lie in development infrastructure rather than AI. A physical automotive software bench consumes hardware, laboratory space, configuration time and engineering support, while its availability is inherently finite.

Virtual workbenches alter that relationship. Horizon is designed to let a new developer instantiate an environment in seconds rather than wait for specialist physical hardware and then spend additional time configuring it. Remote device farms can subsequently provide access to real hardware for work that cannot remain virtual.

This does not eliminate physical validation. Cars remain cyber-physical machines containing networks, sensors, processors and safety-critical systems whose behaviour cannot simply be assumed from a cloud simulation. The practical boundary lies between testing that genuinely requires hardware and the much larger volume of software development work that does not need exclusive access to it.

That boundary becomes increasingly important as vehicle software expands. Android Automotive applications already encompass navigation, media, voice interaction, connectivity and vehicle settings, while engineering around the platform can extend deeper into hardware abstraction layers, vehicle networks, operating-system components, over-the-air updates, diagnostics and cybersecurity.

Virtualising the development environment does not simplify the vehicle. It makes more of that complexity reproducible across engineering teams.

Open Source and the Automotive Toolchain

Horizon is being positioned as an open-source platform rather than a proprietary development environment available only through a closed automotive supplier ecosystem.

Automotive software crosses numerous organisational boundaries between manufacturers, Tier 1 suppliers, semiconductor companies and specialist software developers. Google noted when introducing Horizon that vehicles contain complex systems assembled from components supplied by different companies, including closed systems that can make integration difficult.

A common development environment cannot remove those boundaries, but it can reduce some of the friction created when organisations maintain different combinations of tools, hardware and development infrastructure.

There is also a commercial tension. An open-source development layer can reduce dependence on proprietary tooling while moving more automotive engineering workloads onto cloud infrastructure. Manufacturers gain flexibility in one part of the stack while potentially concentrating another around large cloud platforms.

For Volvo Cars, that calculation sits within a much longer relationship with Google’s automotive technology and an increasingly software-intensive vehicle architecture.

Software Becomes Part of Vehicle Manufacturing

The factory has traditionally provided the obvious measure of automotive industrial capacity: presses, body shops, paint lines, assembly plants and the supply chains feeding them. Software-defined vehicles add another production system, although much of it sits beyond the factory floor.

Code must be built, integrated, tested, validated, released and subsequently maintained across vehicles that can remain in service for many years. Over-the-air updates extend that engineering relationship beyond the point when a car leaves the assembly line.

Horizon addresses the infrastructure used by engineers before software reaches the vehicle. If Volvo’s migration performs at the scale claimed by its developers, the interesting result will not be that automotive engineers are using AI or cloud computing, both of which are already established within software engineering.

The deeper change is in the development environment itself: less dependence on rooms full of dedicated workbenches, greater use of reproducible virtual vehicles and engineering infrastructure that can be instantiated wherever development teams happen to be. The software-defined vehicle is beginning to acquire something resembling a software factory behind it.

Key Industry Questions

1. What is Horizon? Horizon is an open-source software development platform initiated by Accenture and Google Cloud for developing, testing and deploying automotive software, initially centred on Android Automotive OS.
2. What is Volvo Cars doing with Horizon? Volvo Cars is migrating its global Android Automotive OS software development environment to the platform and acting as Horizon’s lead automotive industry partner.
3. Does Horizon replace Android Automotive OS? No. Horizon is a development environment around AAOS rather than a replacement operating system.
4. Why are virtual vehicles useful to software engineers? They allow software builds and many tests to run without reserving physical vehicle hardware, making parallel development and automated testing easier to scale.
5. Will virtual testing eliminate physical vehicle testing? No. Hardware-dependent behaviour and vehicle-level validation still require physical systems. Virtualisation can move suitable development and testing workloads away from scarce physical equipment.
6. How much faster is Horizon? Accenture and Google Cloud claim Cuttlefish-based virtual environments can provide testing up to nine times faster, while some build feedback can fall from as much as two hours to minutes. These are supplier claims rather than independent benchmarks of Volvo’s complete development operation.
7. Is Horizon open source? Yes. Google describes Horizon as an open-source reference development platform.
8. Is the technology limited to passenger cars? The initial emphasis is automotive and AAOS, but Accenture and Google Cloud say they are working to extend Horizon into other automotive and industrial organisations.

Strategic Takeaways

1. Virtual development environments can reserve expensive physical test hardware for engineering tasks that genuinely require it.
2. Volvo Cars gives Horizon a production-scale automotive environment in which its architecture and claimed performance can be tested.
3. Faster build cycles reduce the time engineers spend waiting for feedback after changing code.
4. Open-source tooling may reduce some supplier boundaries, although cloud infrastructure introduces its own strategic dependencies.
5. Automotive manufacturing increasingly includes a persistent software production system alongside the physical factory.