The 'beauty' of GCP is that I can effectively use my ipad's browser to manage some stuff on the go, or keep google cloud open in a small browser window on a secondary monitor, with full flexibility and full featureset. On azure, the pages don't always work, or break, and the app has way less functionality.
The best thing would be naturally a design that adapts better to display size than what they currently have, but I would call it badly optimized instead of bad design.
Users want to spend as little time engaging with the UI but that’s hard to measure. The best way to minimize engagement time would be to just remove everything. But then there’s no data. So the thing that can be measured is chosen.
When people learn the UI the engagement metric trends downward and a new UI is designed which “fixes” the “problem”.
Their attitude to testing, safety or otherwise (i.e. braking) has been horrifically lacking, at best.
I'd be surprised if this move saw much more than a User Story from the MMI PM before going into production.
It would be unfortunate, but not entirely surprising given what we've seen, if the people responsible for these changes hadn't even tried them in their own cars for a reasonable amount of time. I'd say at least 1 year is reasonable, since all weather conditions need to be experienced.