The story follows a "fireman", tasked with burning books, who through a chance encounter is finally tempted to read one... and it's the start of an adventure, and new hope.

Probably easier with an application than a platform. New API features used by one or more customers are difficult to withdraw and can start accumulating legacy costs.

Doing nothing costs money too of course 😀

La Ioniq 5N au hasard ?

J'ai une collègue avec la même, en grise. C'est une expérience !

I won't name the case I'm thinking of, but it seems that the developer needs to be experienced in software design... to avoid code becoming a VB-style mess mixing UI & business code, poor reusability, debug headaches, using lousy HTTP client that couldn't cache correctly, and non-native feel.

It solves some problems but creates others; it depends on the type of application you want to build.

It'll take a lot to convince me to use it again in a professional context, but again it depends on the use-case.

Nevertheless, I've been able to travel from France to Scotland by EV without difficulty for 2 years. Not so long ago, it would've been a real challenge.

There are still some issues, but the quantity and choice helps overcome quality shortcomings.

Quality is improving, maybe not as fast as quantity, nor consistently by network.

You're correct: maintenance is important, including fault anticipation, detection (and deduction...).

However, a lot of charger models remain substandard. Operators must chose suppliers carefully.

I suspect mobility-as-a-service will change ownership relationship to vehicles; perhaps more vehicle sharing and more opportunities for shared vehicles to play a part in energy grids when idle.

Less need for cars if urban transport rethought; more bikes, walking, public transport and on-demand.