Why the Next Generation of Cars Might Actually Have Fewer Features Than Today’s Models
A New Foundational Vehicle Software Platform Aims to Streamline the Complex, Costly Software Behind Modern Vehicles
By Tim Stevens
March 12, 2026
We’re living through one of the most transformative periods in automotive history. The shift to electrification is certainly a major factor, but it’s the rapid rise of the software-defined vehicle (SDV) that’s causing the most significant upheaval in the industry. What started as a simple concept—replacing discrete hardware components with over-the-air (OTA) updatable algorithms—has evolved into a complex nightmare for some of the world’s largest automakers.
The escalating demand for ever-evolving vehicle functionality is clashing head-on with a tangled web of regulations and development requirements. The result? Many manufacturers are facing an almost untenable situation that could paradoxically lead to future cars offering fewer features, not more.
Thankfully, a potential solution is emerging. QNX, a leader in hardware virtualization, and Vector, a specialist in automotive middleware, have joined forces to create something they’re calling the Foundational Vehicle Software Platform. If this collaboration lives up to its promises, it could eliminate many of the most complex and challenging aspects of automotive software development that are currently plaguing the industry.
The Software-Defined Shift: More Than Just a Buzzword
The term “software-defined vehicle” may not be entirely new, but its meaning has been evolving rapidly as this low-level concept has moved to the forefront of vehicle design.
“It’s a term that’s been around for seven or eight years,” explains John Wall, president at QNX. “I think in the last few years, it’s really come to mean something very specific. For me, what it really signifies is that the vehicle is getting more and more dependent on software for features.”
For some organizations, the transition to SDVs has been promoted as a panacea for all their development woes. The vision is a dramatic reduction and simplification of hardware within the car, creating a platform that can stay relevant on the market for much longer through continuous software updates.
“I think one of the main factors driving SDV in the traditional car companies is the ability to continue to enhance the vehicle over time, and to be able to add new features, and to be able to monetize those new features within the vehicle,” Wall notes.
However, behind these ambitious promises lies a troubling reality that has left the software divisions of some manufacturers in disarray.
The Organizational Overhaul Automakers Didn’t See Coming
Achieving new heights in automotive software doesn’t just require more advanced code; for many traditional automakers, it necessitates an entire organizational reboot.
“At the moment, they are struggling, especially in the development processes,” observes Matthias Traub, a member of the board of directors and CTO at Vector. “Also from a cultural perspective. They are coming from a clear waterfall-based process with clear roles.”
The waterfall approach is a legacy software development methodology characterized by linear, sequential phases—design, development, testing, and deployment—with strict boundaries between each stage. This rigid structure is ill-suited for the increasingly dynamic automotive software landscape.
“Now it’s time to go towards a real DevOps approach,” Traub explains. “So you have smaller teams, which have the responsibility for the whole chain, so the design, the build, the software development, the test, and so on.”
QNX’s Wall points out another misguided belief among many companies: the necessity of developing every piece of code in-house. “I think that’s where a lot of them have fallen down,” he admits.
The push to own the entire software stack forces developers to write code for extremely basic functions, such as securely transmitting data over the car’s built-in modem or simply rendering pixels on the vehicle’s displays. Companies that are fundamentally in the business of building cars have instead found themselves writing layer upon layer of software that their customers will never even see.
“Their energy should be focused on features that delight their customers, not on operating systems and networking stacks,” Wall argues.
If an ever-tallening software stack wasn’t daunting enough, the sheer breadth of modern software regulatory frameworks presents a massive challenge. The list of requirements that developers must navigate continues to grow longer by the day.
“Things like the software bill of material, the provenance of where your software came from, you have what’s going on in the U.S., no Chinese code,” Wall lists. “There are a lot of things to think about. It’s a really dynamic situation.”
A New Platform Emerges to Address Industry Pain Points
Evolving regulations don’t just create moving targets for initial compliance; they also demand ongoing updatability and the ability to respond quickly to security vulnerabilities. This regulatory pressure, combined with the inherent complexity of modern vehicle architectures, has created a critical challenge for the industry.
“The industry is at a tipping point where software complexity threatens to outpace innovations,” Traub warns. If this trend continues, he worries that next-generation cars might actually offer fewer features than those on the road today.
Complex regulatory environments are something QNX has navigated repeatedly in the past. The company’s foundational operating system can be found in a wide range of applications, from nuclear power plants to military aircraft, where security, reliability, and certification are non-negotiable.
“A lot of the security requirements came from the medical field, and we saw them a little bit earlier, based on the Biden administration, some of the things that they put in place,” Wall recalls. This experience in highly regulated industries has provided QNX with invaluable insights into the challenges facing the automotive sector.
The Foundational Vehicle Software Platform is built on this deep expertise. It’s a comprehensive suite of interfaces and tools from QNX and Vector designed to streamline modern automotive software development. The platform leverages both companies’ long history of abstracting and simplifying the complicated aspects of integrated systems development. In the automotive context, this translates to providing secure, reliable, and certifiable hardware integration that automakers can depend on.
“We’re trying to remove a lot of those difficult things to deal with by bringing them together and providing one source of truth for the platform,” Wall explains. This approach allows automakers to focus on building differentiating features rather than wrestling with low-level infrastructure issues.
QNX and Vector have collaborated on various projects for years, but they have worked particularly closely over the past 18 months to develop this new platform. Although still an evolving and ongoing project, it’s already showing significant promise not just in terms of simplification but in performance as well.
According to Traub, solutions running on the platform have demonstrated as much as a 50 percent reduction in CPU load compared to custom-written code. This efficiency gain is critical in modern vehicles where processing power is at a premium. Furthermore, latency—the delay between one system making a request and receiving a response—was reduced by an impressive 85 percent, and overall data transmission rates more than doubled.
“And we are just at the beginning,” Traub emphasizes. “Eighteen months is not so long, and I’m sure at the end there will be much more acceleration available.” This ongoing optimization potential means that as the platform matures, automakers can expect even greater performance improvements, further reducing complexity and cost.
The performance benefits of this platform have significant implications for vehicle manufacturing. When software can run faster and more efficiently, it requires less powerful—and therefore less expensive—hardware. This could lead to substantial cost reductions in the production of next-generation vehicles, helping automakers offset the rising costs associated with developing and integrating complex software systems.
A Promising Path Forward, but It’s Still Early Days
QNX and Vector’s Foundational Vehicle Software Platform represents a significant step forward in addressing the critical challenges facing automotive software development. By tackling the root causes of complexity and inefficiency, the platform offers a compelling solution for automakers struggling to keep pace with the demands of the software-defined era. However, it’s important to recognize that this is still an evolving system, and its ultimate impact will depend on its continued development and adoption by the industry.
The early response to the platform has been overwhelmingly positive, indicating that it’s hitting the mark on many of the industry’s most pressing pain points.
“It’s really amazing to see how many companies are asking us about our solution,” Traub notes. “Before, we had only one handful of names on our list. Now it’s two handfuls or more.” This rapid expansion of interest demonstrates a clear industry need for the type of solution QNX and Vector are providing.
Furthermore, the breadth of QNX and Vector’s client base will continue to ensure that the platform evolves to meet the diverse needs of the automotive market.
“Because Vector and QNX work with so many customers, just about every customer in the world, we get a good view of a road map,” Wall explains. “We get a good view of what the car companies want.” This industry-wide perspective allows the developers to anticipate future trends and requirements, ensuring that the platform remains relevant and effective as the automotive landscape continues to shift.
For consumers wondering when they’ll actually see the tangible benefits of this new platform, the timeline might be sooner than expected.
“If you had asked me at the beginning of this project, I would have said 2029, 2030,” Wall admits. “We’ve seen things accelerate recently, though I think it could be sooner than that.” This accelerated timeline suggests that automakers are recognizing the urgency of the situation and are moving quickly to adopt solutions that can help them navigate the complexities of software-defined vehicle development.
The Evolution of the Automotive Software Landscape
The automotive industry is
