"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."
"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."
Connected vehicles now rely on remote servers, subscriptions, and third-party software for many core and convenience functions. Failure or bankruptcy of the companies behind that software can remove essential capabilities and render vehicles inoperable. Automotive software has evolved from basic engine management and diagnostics to controlling features such as door locks, headlights, and cabin preconditioning via smartphone apps. Some models require a manufacturer's app nearby to unlock, linking physical access to online services. Mechanical faults previously allowed rapid local diagnosis and repair, but software-defined systems often demand vendor updates or technician intervention, increasing dependency risks.
Read at Ars Technica
Unable to calculate read time
Collection
[
|
...
]