Not only the backend, but what happens 40 years in the future, when our phones don't run the app anymore, or we're all on phones that are totally unlike the phones of today, or if we don't even have phones or apps? I would expect the car to still work after that long, and making it dependent on a technology that is specific to a particular decade risks premature obsolescence.
> ...what happens 40 years in the future, when our phones don't run the app anymore...
40 years? How about, like, 3 to 5 years? Remember when Apple decided to kill all 32-bit iOS apps for new hardware? I have an old iPod and iPhone 4S with "landlocked" software I enjoy using but can't anymore because Apple.
Phone manufacturers have shown they don't give a damn about allowing old software to function. Physical devices tied to software is a terrible idea.
Relying on a mobile app is relying mobile operating system compatibility over the years and is just asking for combinatorial methods of obsolescence via OS/app/library breaking changes, plus if your old phone breaks, etc. Open sourced mobile app with open sourced back end might be somewhat acceptable but otherwise it's just asking to be bricked as soon as one of the companies involved goes under as we have seen time and again just in past couple of years.
I'll be ecstatic if my iron filter lasts 40 years.
I saw in another post that a person said there's a difference between "device dependent" and "device augmented" that really resonated with me.
There's diminishing returns on everything, and just throwing your hands up on any subject as bad/good might be a disservice.
If I live through an era where phones are no longer a thing and APKs are a thing of the past.. then I either...
A. Don't use the iron filter like that anymore. (manual programing now) B. Get a new iron filter. (ewwwww) C. Keep a legacy-device for the purposes of programming the iron filter. (doesn't need any internet connection or subscriptions)
(C) would be my most liked solution.