Imagine turning the key or pressing the start button of your car - and nothing happens. Not because the battery is dead or the engine is broken but because a server no longer answers. For a growing number of cars, that scenario isn’t hypothetical.
As vehicles become platforms for software and subscriptions, their longevity is increasingly tied to the survival of the companies behind their code. When those companies fail, the consequences ripple far beyond a bad app update and into the basic question of whether a car still functions as a car.
Over the years, automotive software has expanded from performing rudimentary engine management and onboard diagnostics to powering today’s interconnected, software-defined vehicles. Smartphone apps can now handle tasks like unlocking doors, flashing headlights, and preconditioning cabins—and some models won’t unlock at all unless a phone running the manufacturer’s app is within range.
However, for all the promised convenience of modern vehicle software, there’s a growing nostalgia for an era when a phone call to a mechanic could resolve most problems. Mechanical failures were often diagnosable and fixable, and cars typically returned to the road quickly. Software-defined vehicles complicate that model: When something goes wrong, a car can be rendered inoperable in a driveway—or stranded at the side of the road—waiting not for parts but a software technician. READ MORE - and beware!
Take for example KTM and their 890 Adventure R motorcycle - then remember KTMs legendary reliability - or lack thereof and add to that KTMs horrific financial issues. Remember in the olden days when you bought something & it was actually yours? Now - not so much! I'm a technologist by trade - but really don't want tech in my car or motorbike!
