The original Tesla software had a very well defined UI model - which was consistent across all of the apps. And while the functionality was limited, it was pretty intuitive to use.
8.0 breaks that. Activities that were simple before have become more complicated (or even much more difficult to do).
A quality user interface is much more than having it look cool - it needs to be intuitive and easy to use. And especially when the user is using the interface while also performing a critical function (such as driving a car), it's even more critical that the interface be easy to use.
For UI changes, there is a methodology for evaluating the effectiveness of the changes - something that clearly wasn't done with the 8.0 release.
When planning UI changes, typical operations are developed as "use case scenarios", things like changing media source, picking a favorite radio station, browsing through songs, ...
For those use case scenarios, it's possible to measure how well the interface works by having someone step through the scenario to perform the function, measure the amount of time required and the number of interactions (screen/button touches). And for someone that is also driving a car, another important measurement is how much time is required for the user's eyes to be on the interface - and not on the road.
This should have been detected by Tesla's beta testers. Since these problems were present when the software was released, either Tesla doesn't have enough hand-picked beta testers OR those testers don't have experience in methodically testing new software products OR Tesla ignored reports on major UI problems.
This should have been detected by Tesla's internal QA group.
And, this should likely have been detected while the software was being developed AND should probably have been addressed when the software changes were even being planned.
8.0 breaks that. Activities that were simple before have become more complicated (or even much more difficult to do).
A quality user interface is much more than having it look cool - it needs to be intuitive and easy to use. And especially when the user is using the interface while also performing a critical function (such as driving a car), it's even more critical that the interface be easy to use.
For UI changes, there is a methodology for evaluating the effectiveness of the changes - something that clearly wasn't done with the 8.0 release.
When planning UI changes, typical operations are developed as "use case scenarios", things like changing media source, picking a favorite radio station, browsing through songs, ...
For those use case scenarios, it's possible to measure how well the interface works by having someone step through the scenario to perform the function, measure the amount of time required and the number of interactions (screen/button touches). And for someone that is also driving a car, another important measurement is how much time is required for the user's eyes to be on the interface - and not on the road.
This should have been detected by Tesla's beta testers. Since these problems were present when the software was released, either Tesla doesn't have enough hand-picked beta testers OR those testers don't have experience in methodically testing new software products OR Tesla ignored reports on major UI problems.
This should have been detected by Tesla's internal QA group.
And, this should likely have been detected while the software was being developed AND should probably have been addressed when the software changes were even being planned.