**Solving SDV Complexity: Why Foundational Software Matters**
Designing, developing, and deploying software is a complex endeavor at the best of times. However, when combined with the intricate demands of the automotive sector, the process becomes exponentially more challenging. The well-known Silicon Valley mantra of “move fast and break things” doesn’t translate well when the code governs a device responsible for transporting people and their families.
The automotive software development environment is uniquely challenging and continues to evolve rapidly. Consumer expectations for more advanced in-car experiences are constantly rising, driven by the increasing capabilities of the mobile devices we carry daily. Simultaneously, an increasingly dense web of global regulations threatens to impede even the most well-conceived development processes.
Over the past 20 years, the automotive and software industries have become increasingly intertwined, though not always seamlessly. A recent study commissioned by QNX highlights growing frustration among software developers worldwide. Stymied developers can lead to late or unreliable code, a situation that can ultimately delay product launches.
What is causing this frustration, and how might a new combination of two existing products provide a solution? Let’s delve into the details.
**Increased Complexity and Regulation in the SDV Era**
The rise of software-defined vehicles (SDVs) offers numerous benefits for both consumers and manufacturers. It enables the creation of increasingly capable vehicles with advanced features that can evolve over time to keep pace with a rapidly changing automotive landscape.
Traditional automotive development approaches, based purely on integrated systems, are incapable of keeping up with this pace of evolution. While SDVs enable new levels of system capability and long-term product evolution, they also introduce a complex mesh of interconnecting and overlapping standard interfaces.
Furthermore, increased scrutiny and concern for customer data protection and overall safety and security have resulted in a widening array of mandates. In 2024 alone, 500 new regulations were proposed or added, with those related to cybersecurity causing the most concern.
A critical regulation is the European Union’s Cyber Resilience Act (CRA). Set to take effect in 2027, this regulation not only defines new standards for consumer data protection but also requires frameworks for both initial assessment and ongoing lifecycle security. Tackling this requires more than just code; it necessitates an organizational shift.
Some of these same concepts are addressed in ISO/SAE 21434, another major regulation focused on automotive cybersecurity, which mandates the definition of a Cybersecurity Management System (CSMS) to continuously monitor and address security risks.
These are not trivial changes, and they are having significant impacts. According to the “Under the Hood: SDV Developer” report commissioned by QNX, which surveyed 1,100 global embedded automotive software developers, one-third of respondents experienced delays in development timelines in 2024 due to the introduction of such regulations.
**More Recalls, More Frustrations**
Delays are not the only impact of this increased complexity and regulation. Quality is also suffering. According to JD Power’s U.S. Initial Quality Study 2025, there were 202 software-related recalls in 2024—nearly double the 112 software-related recalls in 2023.
The majority (58%) of developers surveyed indicated that their processes and methodologies have been impacted by this trend. Many felt stymied by development environments that were rated as only “good” or “average.” A sub-optimal software development environment leads to sub-optimal software performance.
Compounding this issue is a significant talent shortage. It is clear that the combined trends of increasing development complexity and heightened consumer expectations are not sustainable. Although most developers (91%) predict that AI will have a major impact on development within the next five years, the vast majority of those surveyed believe the best way forward is to focus development efforts where they can have the most impact—the application layer.
**Optimizing Innovation at the Application Layer**
Fast-changing regulations and cybersecurity demands are having immediate impacts on software complexity and the product landscape. For instance, Porsche’s 718 and its gas-powered Macan were both prematurely withdrawn from the European market due to non-compliance with local regulations.
How can this increasingly onerous situation be managed? The optimal solution may be to let someone else handle the heavy lifting. Eight out of ten developers surveyed indicated that automakers should shift their focus to application-level development—the features and capabilities that customers actually see—rather than becoming bogged down in foundational software infrastructure.
This is precisely where a solution jointly developed by QNX and Vector comes into play, combining QNX’s proven OS capabilities with Vector’s deep expertise in embedded software architecture and middleware integration.
**The Foundational Vehicle Software Platform**
Between the fingerprint-covered touchscreen and the silicon chips buried in the chassis lies layer upon layer of software and various interfaces. For all of this to create a satisfactory user experience, all these layers must work together seamlessly.
This delicate dance is vastly complicated, made even more so by the variety of integrated hardware sometimes found across a single model from a single manufacturer. This makes initial software development and ongoing maintenance a massively complicated task.
The Foundational Vehicle Software Platform is a joint effort by QNX and Vector to simplify this process. It combines a low-level hardware abstraction layer with a comprehensive middleware suite that handles much of the integration messiness that frequently challenges OEMs with the best intentions.
Pre-integrated, lightweight, and certified to the automotive industry’s highest functional safety (ISO 26262 ASIL D) and security (ISO 21434) standards, this Foundational Vehicle Software Platform is simple by design, performant by nature, and capable of scaling vehicle-wide. This makes it easier than ever for automakers to accelerate their SDV development efforts.
Importantly, this Foundational Vehicle Software Platform is not intended to replace OEM software stacks; it is designed to accelerate them. By enabling tighter integration, faster certification, and scalable deployment, the platform supports OEMs without locking them into a specific architecture. In essence, software developers can concentrate on creating powerful, reliable user experiences and worry less about the nuts and bolts of system integration.
**Optimization Through Prioritization**
The trend of rising complexity and expanding regulation is not abating; it will only intensify as demands grow for both more comprehensive user experiences and more secure application environments. A standardized framework behind the scenes to streamline both development and certification efforts will free developers from implementation and regulation surprises. Spending less time on these headaches allows for more time spent building experiences that surprise and delight—which is what this industry and this ride should be all about.
