But I think that "car platform" should be clearly separated from the "userspace".
My sense is that why the legacy manufacturers are failing, at software, they have coupled the "userspace" to the "car platform". Updating UI in the center console is the same thing to them as updating the embedded code that controls the windshield wipers.
That being said, I admit you cannot fully leave the "userspace" to apple or google, because you, for example, probably have some custom kind of sunroof that doesn't fit in whatever generic APIs CarPlay and Android Auto offer for Sunroofs.
Additionally, if you go all in on Android Auto, you have no leverage when Google tries to extract more money.
At the same time, competing with Google or Apple on UX and continuity is a losing battle. When I enter the car, I want my car to continue playing the podcast I was listening to. No car manufacturer can do this, only Carplay/Android Auto can.
I guess the answer is to have good support for Android Auto/ CarPlay. But also have your own version as an insurance against being held hostage.
But Tesla shows that there are car companies that can build satisfactory entertainment software, which is not surprising as writing good software is something every car manufacturer need to do, considering how much software is used in a car.
Car manufacturers should engineer good cars.
Leave the good software engineering to good software engineering firms.