From Engines to EV Operating Systems
As electric vehicles evolve, the most important part of the car is quietly shifting from the motor to the EV vehicle operating system. Nio’s SkyOS software is a clear example: instead of treating infotainment, driving assistance and battery management as separate islands, SkyOS is designed as a full‑stack vehicle OS that spans multiple ECU domains. According to its former engineering lead, the platform covers motion control, body control, the digital cockpit and AD/ADAS, built on multiple OS variants and an in‑house service‑oriented architecture framework. That unified layer is what lets Nio deploy features across different models and even brands through software, not hardware redesigns. For drivers, this means the car behaves more like a connected compute platform than a traditional vehicle, where improvements, personalisation and even new safety capabilities arrive via over‑the‑air updates instead of waiting for the next model cycle.
Nio’s SkyOS Leadership Loss and the EV Talent Battle
Nio’s recent loss of Ning Qu, the VP who led its SkyOS vehicle operating system, underlines how intense the global fight for top EV software talent has become. Over four years, Qu rose from senior director of software solutions and architecture to VP of engineering and global head of the software platform, overseeing SkyOS from concept to mass production. The software now runs on the Onvo L60 and three additional vehicle programmes, with over 120,000 vehicles delivered on the platform within its first 15 months. Qu’s move to autonomous‑driving software firm Applied Intuition, where he now serves as Head of Vehicle System, leaves Nio without its most visible software platform champion just as SkyOS is being positioned as the structural backbone of its software‑defined vehicle strategy. It signals how crucial deep OS expertise has become—and how aggressively autonomous and EV players are competing to secure it.
Inside the WeRide–SiEngine Chip Alliance
While Nio focuses on a unified EV software platform, others are tightening the link between software and silicon. The WeRide SiEngine partnership shows how autonomous driving chips and algorithms are converging. SiEngine brings high‑performance automotive‑grade chips, including its SE1000 smart cockpit chip, which leads installations among domestically produced chips for mainstream models priced below a specified threshold. WeRide contributes its full‑stack autonomous driving algorithms and experience operating Robotaxis, Robobuses and L2++ ADAS in more than 40 cities across over 12 countries. Together, they aim to deeply co‑optimise hardware and software to reduce reliance on expensive compute platforms, enabling cost‑effective, mass‑produced intelligent driving. Under a central computing architecture, they are exploring cabin‑driving fusion so functions can be flexibly deployed from entry‑level to high‑end vehicles. For consumers, this could mean that advanced driver assistance features once reserved for flagship models will filter quickly into more affordable EVs as the stack is standardised.
Why Controlling the OS and Chip Stack Matters to Drivers
Whether it is Nio’s SkyOS or the WeRide SiEngine partnership, the direction is the same: carmakers and AV firms want tight control over their EV software platform and compute hardware, much like smartphone brands control their operating systems and processors. A unified vehicle OS and optimised chip stack let companies roll out new features in weeks instead of waiting for new model years, while keeping safety, quality and costs in check. This foundation also supports long‑term software support: security patches, reliability improvements, and performance optimisations can be delivered over the air across the fleet. For drivers, the difference between a strong and weak platform shows up in everyday details—how quickly bugs are fixed, whether new apps and charging integrations appear, how smoothly the navigation, driver assistance and battery systems work together, and whether the car genuinely gets smarter and safer over time instead of feeling outdated.
What This Means for Malaysian and Regional EV Buyers
For Malaysian and regional consumers, these developments in China are not abstract—they are likely to arrive embedded in imported Chinese EVs. A Nio built on SkyOS or a Chery or GAC model using WeRide’s L2++ ADAS on SiEngine chips brings with it a specific software ecosystem, from the look and feel of the cockpit interface to how autonomous driving chips handle traffic and how often you receive over‑the‑air updates. Local user experience will depend on how well these EV vehicle operating systems are localised: language options, maps tuned to Southeast Asian roads, integration with regional charging networks and popular apps, and the responsiveness of remote diagnostics and service. As more Chinese EVs enter ASEAN markets, buyers will need to evaluate not just range and styling, but also the underlying EV software platform—because over the car’s lifetime, software will shape convenience, safety and resale value more than any single hardware spec.