I agree with the author: CarPlay is table stakes for me. Whenever an automaker says a car won't support CarPlay, I mentally cross it off my list. Which is fine, because there are plenty of other viable options.
I think what’s become more interesting/impactful for me is why they elect not to support it.
Most firms moving away from it (or who never implemented it) seem determined to either sell additional subscription services to their user base (connectivity) or sell their user base to a third-party (either as data, or eyeballs). And for a product at this price point I find myself very annoyed at the attempted payment extraction.
Either way, I’m with you. Lots of vehicle manufacturers out there that will support it.
We bought a Honda Prologue last year and didn’t even test drive the built-on-the-same-platform GM cars (e.g. the almost-identical Chevy Blazer EV) because they didn’t have CarPlay.
People like us have got to be affecting GM’s sales by some measurable amount, right?
Tesla is more of a technology company than a car company, that's why they managed to make a good UX.
Classic car makers are not able to make decent UIs. Plus, each car would be different. So I prefer Android Auto: it's always my Android Auto, regardless of which car I'm driving.
I owned a Model Y for several years, but, at least in my city, I always felt Tesla’s navigation had pretty poor route selection during busy times of the day - like dorecting me to streets that were notoriously stop and go during rush our when the highway alternative was known to be much quicker.
