Why Foundational Software Matters in the Evolving SDV Landscape
The drive toward software-defined vehicles (SDVs) promises a revolutionary shift in automotive technology, offering drivers unprecedented levels of customization, connectivity, and intelligence. However, the path to realizing this vision is fraught with complexity, demanding a new approach to software development that prioritizes stability and efficiency. As the automotive industry grapples with evolving technical requirements and a tightening regulatory environment, the need for a robust foundational software layer has never been more critical. This article explores the challenges facing SDV development today and introduces a solution that enables automakers to focus on what matters most: the in-car experience.
The convergence of automotive and software engineering over the past two decades has ushered in an era of remarkable innovation. Yet, this integration has also exposed significant challenges in the development process. A recent study commissioned by QNX reveals widespread frustration among software developers globally, with many citing delays and inefficiencies in their work. These hurdles can have cascading effects, potentially impacting product launch timelines and overall vehicle quality. Understanding the root causes of this frustration is essential to addressing the complexities of the modern automotive landscape.
Increased Complexity and Regulation in the SDV Era
The rise of software-defined vehicles represents a paradigm shift in automotive design, moving away from traditional, hardware-centric architectures toward software-driven systems. This evolution enables the creation of vehicles with increasingly sophisticated features that can be enhanced and updated over time, keeping pace with rapidly advancing technological expectations. However, this new paradigm also introduces a heightened level of complexity. The integration of diverse hardware components and the proliferation of standard interfaces create a dense and intricate development environment that can be challenging to navigate.
Traditional approaches to automotive development, which rely heavily on integrated systems, are proving inadequate for the demands of the SDV era. The need for greater flexibility and the ability to adapt to evolving requirements necessitate a more agile and modular development approach. While SDVs offer the promise of enhanced system capabilities and long-term product evolution, they also bring an unwanted side effect: an increasingly complex web of interconnecting and overlapping interfaces. This complexity can make it difficult for developers to manage dependencies, ensure compatibility, and maintain system stability.
Adding to the challenge is the escalating scrutiny of consumer data protection and overall vehicle safety and security. This increased focus has resulted in a widening array of mandates and regulations that automakers must navigate. In 2024 alone, approximately 500 new regulations were proposed or added to the existing framework, with cybersecurity-related requirements causing the most significant concern. These regulations are reshaping the automotive development landscape, demanding a more comprehensive approach to security and data privacy.
A critical piece of this evolving regulatory puzzle is the European Union’s Cyber Resilience Act (CRA), set to take effect in 2027. This landmark regulation not only establishes new standards for consumer data protection but also mandates frameworks for both initial security assessments and ongoing lifecycle security management. Addressing the CRA effectively requires more than just coding; it necessitates a fundamental shift in organizational strategy and development practices. Automakers must implement robust processes for identifying, assessing, and mitigating security risks throughout the entire product lifecycle.
These regulatory shifts are not isolated to the EU. Other major regulations, such as ISO/SAE 21434, which focuses on automotive cybersecurity, are also shaping development priorities. This standard requires the establishment of a Cybersecurity Management System (CSMS) to continuously monitor and address security risks. The implementation of such systems demands significant investment in resources, expertise, and technology.
The impact of these increasing complexities and regulations is already being felt across the industry. According to the Under the Hood: SDV Developer report, commissioned by QNX and surveying 1,100 embedded automotive software developers globally, one-third of respondents reported delays in their development timelines in 2024 directly attributable to the introduction of regulations like the CRA. This highlights the significant burden these new requirements are placing on development teams.
More Recalls, More Frustrations
The challenges associated with SDV development extend beyond mere delays. Quality is also being impacted, as evidenced by the increasing number of software-related recalls. According to JD Power’s U.S. Initial Quality Study 2025, there were 202 software-related recalls in 2024, nearly double the 112 reported in 2023. This upward trend underscores the difficulty automakers are facing in delivering reliable software in the face of growing complexity and regulatory pressures.
The majority of developers surveyed (58%) indicated that their development processes and methodologies have been significantly impacted by these trends. Many developers feel constrained by development environments that are rated as merely “good” or “average.” A suboptimal software development environment inevitably leads to suboptimal software performance. When developers lack the necessary tools, frameworks, and support, their ability to create high-quality, reliable code is compromised. This situation is further exacerbated by a significant talent shortage in the automotive software sector, making it even more challenging to find the expertise needed to navigate these complexities.
The commingling trends of increasing development complexity and heightened consumer expectations are clearly not sustainable. While most developers (91%) predict that artificial intelligence (AI) will have a major impact on development within the next five years, the vast majority of those surveyed believe that the most effective way forward is to focus development efforts on areas where they can have the greatest impact—the application layer. This suggests a strategic shift toward prioritizing user-facing features and capabilities rather than getting bogged down in underlying infrastructure challenges.
Optimizing Innovation at the Application Layer
The rapid evolution of regulations and the growing emphasis on cybersecurity are having immediate and tangible impacts on software complexity and the overall product landscape. For example, Porsche’s 718 and its gas-powered Macan models were prematurely withdrawn from the European market due to non-compliance with local regulations. This situation underscores the urgency for automakers to adapt quickly to the changing regulatory environment or risk losing access to key markets.
How can automakers effectively handle this increasingly onerous situation? The most promising solution may lie in allowing specialists to handle the heavy lifting. Eight out of ten developers surveyed indicated that auto manufacturers should shift their focus to application-level development—the features and capabilities that customers actually interact with—rather than becoming mired in the foundational software infrastructure. This approach allows automakers to leverage their core competencies while offloading the complexities of lower-level development to experienced partners.
This is precisely where a solution jointly developed by QNX and Vector comes into play. By combining QNX’s proven operating system capabilities with Vector’s deep expertise in embedded software architecture and middleware integration, this solution addresses the core challenges of SDV development. It provides a solid foundation upon which automakers can build their innovative application-layer features, accelerating their development efforts while ensuring compliance and quality.
The Foundational Vehicle Software Platform
Between the fingerprint-covered touchscreen and the silicon chips buried deep within the chassis lies a complex ecosystem of software and interfaces. For the vehicle to deliver a seamless and satisfying user experience, all these layers must work together harmoniously. This intricate interplay is a vastly complicated undertaking, made all the more challenging by the variety of integrated hardware often found within a single model from a single manufacturer. This diversity makes initial software development and ongoing maintenance a massively complicated task, often requiring significant time and resources.
The Foundational Vehicle Software Platform, a joint effort by QNX and Vector, is designed to simplify this complex landscape. It combines a low-level hardware abstraction layer with a comprehensive middleware suite that handles much of the messiness associated with software integration. This integration layer addresses many of the challenges that frequently stymie automakers, even those with the best intentions. By providing a pre-integrated, lightweight foundation, the platform streamlines the development process and reduces the burden on automakers.
Certified to the automotive industry’s highest functional safety (ISO 26262 ASIL D) and security (ISO 21434) standards, this Foundational Vehicle Software Platform is designed for simplicity, built for performance, and capable of scaling across the entire vehicle. This makes it easier than ever for automakers to accelerate their SDV development efforts. The platform provides a robust and reliable base upon which automakers can build their innovative features, ensuring that the underlying infrastructure is secure and compliant.
Importantly, this Foundational Vehicle Software Platform is not intended to replace OEM software stacks; rather, it is designed to accelerate them. By enabling tighter integration, faster certification, and scalable deployment, the platform supports automakers without locking them into a specific architecture. This flexibility allows automakers to maintain control over their software development while benefiting from the expertise and capabilities of QNX and Vector.
In essence, this solution empowers software developers to focus their efforts on creating powerful, reliable, and engaging user experiences. They can worry less about the intricacies of system integration and the complexities of underlying infrastructure, knowing that the foundational layer is secure, compliant, and optimized for performance. This shift in focus allows developers to dedicate their time and energy to innovation, differentiation, and the creation of features that will delight customers and set their vehicles apart in the marketplace.
Optimization Through Prioritization
The trend of rising complexity and expanding regulation in the automotive industry is not abating; it is poised to intensify as demands for more comprehensive user experiences and more secure application environments continue to grow. In this evolving landscape, a standardized framework that streamlines both development and certification efforts can free developers from implementation and regulatory surprises. When developers spend less time grappling with these technical headaches, they have more time to focus on building experiences that surprise and delight, which is what the automotive industry—and the ride itself—should ultimately be about.
By leveraging the Foundational Vehicle Software Platform, automakers can position themselves to succeed in the SDV era. They can accelerate their development timelines, improve the quality of their software, and deliver innovative features that meet the growing expectations of consumers. The platform provides the stability and reliability needed to navigate the complexities of the modern automotive landscape, allowing automakers to focus on what matters most:
