I am referring to automation driven UI. It is clear that the V11 is oriented toward “no driver” use case - hiding all driving-related controls and focusing on entertainment would make sense. The issue is that such design outpaces the current automation capabilities.
Having two code bases - one with the trend of the V11 and one more “traditional”, driver-focused (even with the games as optional) - and giving customers the option to choose will be better. Yes, it is more costly to maintain two code based but it will preserve the perceived value for the customer base (now, there are quite a few unhappy, resentful people in addition to those who are happy). Proper market segmentation
Additionally, those two use cases require very different skill sets to maintain. Why cobble them together?
There is another benefit. The “traditional” interface will require significant investment only in the beginning; the rest would be mostly maintenance. That will free up long term resources to work on the “automation” UI. Also, there is an established practice of charging more for automation