It's not criminal so they will continue to lower the cost. 50ms quickly becomes 500ms response time when you realize that no tier 1 supplier can hit within your OEM budget and your boss is becoming impatient :)
Another thing that happens is when there is a 50ms response time mandated and at the start of the project you have 30ms and it slowly creeps up until you get to 55ms. Then the blame game starts. Like I said previously, each component is usually won by a different tier 1 supplier. So everybody puts the blame on somebody else. One tier 1 is building the linux distro, the other is making basic system libraries and the applications are written by another 20 tier 1 suppliers.
Then the deadline hits and the car needs to be sent to the showrooms. So whatever 50ms was chosen initially is changed to whatever it currently is so to say they are within spec and can ship the damned car.
I think this describes a lot of how software is developed (which just goes to show how immature that part of the industry is.). Similar contracts and agreements exist between manufacturers of the brake system as well but if there is an issue there where the ABS system doesn't prevent lockup in 1% of cases, then the problem is solved or the car launch is delayed, because that's what the system is designed to do. The problem here of course is that these things are seen as gadgets without safety aspects and there is no regulatory oversight.
I guess it's also up to buyers: don't buy cars with shoddy infotainment.
ah, there is some regulatory oversight and there's awareness of the safety aspects.
Not much, but, there is some.
After working on infotainment, I'm doing my best to avoid purchasing a car with an infotainment system. I had to compromise and got a Civic with an infotainment system for my wife, but I'll probably stick to late 2000s, early 2010s for as long as I possibly can to avoid them. Seriously hate touchscreens, and there's just not enough value in an infotainment system for me to be OK with what I'm losing by having one.
Another thing that happens is when there is a 50ms response time mandated and at the start of the project you have 30ms and it slowly creeps up until you get to 55ms. Then the blame game starts. Like I said previously, each component is usually won by a different tier 1 supplier. So everybody puts the blame on somebody else. One tier 1 is building the linux distro, the other is making basic system libraries and the applications are written by another 20 tier 1 suppliers.
Then the deadline hits and the car needs to be sent to the showrooms. So whatever 50ms was chosen initially is changed to whatever it currently is so to say they are within spec and can ship the damned car.