← All essays
Browse the archive
Software Defined Vehicles? Nokia Lost to Software, Not iPhones
Nokia launched the first smartphone in 1996, 11 years before the iPhone, and had superior technology with a massive R&D budget, thousands of patents, and advanced features like GPS and 5MP cameras. Yet they failed. Why? Not because of technology, but because they couldn't transform from a hardware company to a software company. Developers abandoned them for platforms that took software seriously. Today's carmakers are repeating Nokia's mistake: spending billions on research but focusing on the wrong things, while Tesla and Chinese EVs play by software-first rules, just as Apple and Samsung did against Nokia.
Automotive executives love talking about Software-Defined Vehicles (SDV), cars controlled by software rather than mechanical parts. On paper, that seems like the obvious next step; after all, our phones, TVs, and even doorbells are software-first. So why the frenzy? And if it’s such a clear idea, why are these cars taking so long to arrive, and why have so many attempts failed?
During my business studies, the classic case study of Nokia's collapse changed how I understand the automotive industry's transformation. The conventional narrative says the iPhone killed Nokia. Nokia was too slow to innovate, was arrogant, or made the wrong operating system choices. But that misses the real story.
The Surprising Nokia Discovery
Nokia's achievements before its fall were impressive:
- The first smartphone was launched in 1996 (11 years before the iPhone)
- €3.8 billion annual R&D budget, much higher than Apple's
- Over 20,000 patent families generating €1 billion annually today
- Nokia N95 featured GPS, a 5MP ZEISS camera, and video streaming before the iPhone existed
I owned an N95 and was proud of its features compared to the iPhone's initial mediocre touchscreen without even Bluetooth. Nokia had all the building blocks needed to dominate the smartphone market. The technology was there.
Yet they failed. Why? Not because of technology, but because they couldn't transform from a hardware company to a software company. They didn't take software seriously, so developers left them behind. It's a classic example of digital transformation failure.
Working in automotive software, I witness car companies making the same mistakes Nokia made.
Transformation: Fear and Bureaucracy Killed the Giant
The most revealing research (Vuori and Huy's study with 76 Nokia executives) exposed patterns we see in most big industrial companies:
- Middle managers were more concerned about office politics than beating competitors
- Teams competed against each other (Symbian vs MeeGo) instead of collaborating
- Problems never reached top management
- "Not Invented Here" syndrome, they rejected outside ideas, thinking "we know better"
Software: Consumer Electronics Played By Different Rules
Nokia focused on hardware, improving batteries, and making stronger phones. Apple focused on making phones easy and enjoyable to use. The first iPhone couldn't even use 3G internet and had a terrible camera. But Apple understood something crucial: software makes the difference, not hardware specs.
Samsung used its experience manufacturing TVs and appliances to mass-produce phones at every price point. Both companies treated phones as part of broader ecosystems rather than standalone devices.
They competed on dimensions that Nokia didn't even recognize as battlefields.
The Developer Experience That Changed Everything
As someone who tried developing apps on all three platforms, the contrast in developer productivity metrics and their impact on the company's business shocked me:
Nokia's Symbian Platform
- Setting up tools: 2-3 days of complicated steps
- Getting app approved: 6-8 weeks wait
- Development tools: Fragmented across multiple platforms
- Distribution: No unified store until Ovi (too late)
- Time-to-market: 3-6 months for simple apps
The consequence: Developers abandoned Nokia. The Symbian store had only 25,000 apps by 2011. Most were low-quality utilities. Major developers chose iOS or Android instead, where they could ship quickly and get paid: no Instagram, no WhatsApp, no popular games. Users followed the apps, not the hardware specs. Nokia sold its Devices & Services unit to Microsoft for €5.4 billion in 2013.
Apple's IOS Ecosystem
- SDK setup: 30 minutes with Xcode
- App review: 7 days (now 24 hours)
- Development tools: One integrated environment
- Distribution: App Store from day one
- Time-to-market: 2-4 weeks for simple apps
The consequence: Apple's App Store exploded to 500,000 apps by 2011. Developers could build, test, and launch apps quickly. This created a virtuous cycle, more apps attracted more users, more users attracted more developers. Apple captured 75% of mobile app profits despite having only 15% market share.
Samsung's Open-Source Collaboration Strategy
Samsung's approach fascinated me even more. While Nokia protected everything internally, Samsung embraced openness:
- Contributed more Android code than any other manufacturer
- Made 40,000+ commits to the Linux kernel
- Sponsored global hackathons and provided free devices
- Achieved 3x faster feature development through collaboration
The consequence: By 2012, Samsung had become the world's largest smartphone manufacturer. Their open approach meant every Android improvement benefited them. They could add features faster than competitors. Developers loved working with Samsung; they got free devices, technical support, and their improvements got integrated upstream. This multiplier effect helped Samsung dominate across all price points.
The Automotive Echoes Nokia
The similarities between Nokia versus Apple/Samsung and Traditional Carmakers versus Tesla/Chinese EVs are striking.
The Transformation Crisis in Automotive
- Volkswagen spent €5 billion on software. Result: 3-4 year delays, canceled projects, desperate $5 billion deal with Rivian
- Ford abandoned its "Fully Networked Vehicle" project in 2025 after $9.7 billion losses, eliminating 350 software positions and reverting to legacy systems
- GM quietly abandoned its software platform after significant investment
- 74% of car executives admit their mechanical-focused culture "won't change"
- VW's Scalable Systems Platform, initially scheduled for 2024, now has a delivery timeframe of 2027-2028.
Traditional carmakers spend €20 billion yearly on research. But like Nokia's €3.8 billion, it's spent on the wrong things.
These companies remain trapped in 5-7 year development cycles while Tesla and Chinese competitors iterate continuously.
The Developer Productivity Crisis
Current automotive software experiences mirror Nokia's mistakes:
- Complex toolchains require specialized knowledge (any developer who has worked with "qualified" automotive tools knows the pain)
- Different systems for each brand, and even "standards" like AUTOSAR don't work well together
- 6-month+ certification processes for simple updates, which go against any modern practices
- Limited access to vehicle APIs and data
Tesla's contrasting approach
- Unified development platform
- Weekly software updates
- Open API access for developers
- Continuous integration/deployment culture
Mindset, Not Technology, Determines Survival
Nokia had better technology, more money, and more patents, but failed because it couldn't adapt its thinking when the rules changed.
Three things decide who survives a platform transition. It isn't about adopting new terms like SDV or doing more open-source; it takes fundamental change:
- Culture beats technology: Nokia had better hardware but couldn't think "software first". Current automakers possess world-class engineering capabilities, but can't work like software companies. For example, SAFe is not the solution.
- Ecosystem thinking over product optimization: Apple built an ecosystem; Nokia built individual phones. Tesla builds updatable computers on wheels; traditional carmakers build mechanical products that require much longer cycles. This is the core of SDV.
- Openness beats secrecy: Nokia's "Not Invented Here" blocked Android adoption. Car companies often prefer to handle everything internally or maintain absolute control, despite repeated failures. AUTOSAR, for instance, is exclusive to its members, preventing the broader developers ecosystem from even using its specifications.
The car industry faces a moment similar to Nokia's 2007 moment today. Companies with 100-year histories often lose to newcomers who understand that software is what matters now.
I see positive changes emerging, including greater openness, new leadership, and diverse perspectives. But I still believe the mindset must change dramatically.
Originally posted on LinkedIn and featured in Best of LinkedIn: Next-Gen Vehicle Intelligence
FAQ
- Why did Nokia really fail?
- Not because of technology. Nokia launched the first smartphone in 1996, had a 3.8 billion euro R&D budget and over 20,000 patent families, but it could not transform from a hardware company into a software company. Developers left for platforms that took software seriously.
- How did developer experience differ between Nokia and Apple?
- On Nokia's Symbian, tool setup took 2 to 3 days, app approval took 6 to 8 weeks, and the store had only 25,000 apps by 2011. On Apple's iOS, the SDK set up in 30 minutes, review took about 7 days, and the App Store hit 500,000 apps by 2011, so developers and users followed the apps.
- How are carmakers repeating Nokia's mistake?
- Volkswagen spent 5 billion euros on software and hit 3 to 4 year delays, Ford abandoned its Fully Networked Vehicle project in 2025 after 9.7 billion dollars in losses, and 74% of car executives admit their mechanical-focused culture will not change. They spend on the wrong things while staying trapped in 5 to 7 year cycles.
- What three things determine who survives a platform transition?
- Culture beats technology, ecosystem thinking beats product optimization, and openness beats secrecy. Nokia had better hardware but could not think software-first, build an ecosystem, or drop its Not Invented Here mindset.
Fadi Labib runs this field lab. 15 years in automotive, robotics, and embedded systems; ESMT Berlin EMBA. I give AI real engineering problems, then check its work. More about the lab →
Related case studies
Related essays that extend the same thread
•8 min read
If Cars Can Be 'Software-Defined Vehicles', Why Aren't Phones 'Software-Defined Phones'?
Carmakers now call themselves "Software-Defined Vehicle" companies. Nobody calls a smartphone "software-defined". Phones were software-first from day one, so the label was never needed. The SDV prefix is automakers announcing they have to rebuild around software two decades after mobile did.
•6 min read
What if Google Test Didn't Exist? Chapter 1: The Hidden Economic Value
Open source software powers 96% of all codebases and would cost $8.8 trillion to rebuild, yet just 5% of developers create 96% of its value. Google Test alone saves companies billions. Imagine 2,000 companies each burning money to build their own testing framework, then to maintain it. That's billions down the drain, solving the same problem thousands of times. Meanwhile, bugs caught early save hundreds of thousands per year, and engineers get to build actual products instead of reinventing basic tools. Tech giants aren't sharing code out of generosity, they've figured out that giving away millions in development costs them less than the alternative.
•2 min read
Open-Source Qualification in Automotive: A Critical Industry Need
Every carmaker chasing software-defined vehicles qualifies the same foundational tools on its own: operating systems, toolchains, LLVM. The work is duplicated across the industry and none of it is a differentiator. The fix is to qualify those shared foundations together and compete on the product instead.