FYI
@ilikewhey,
@richpjr
Which sounds like a go-to defense of someone who doesn't get why people might want CarPlay on a Tesla.
Tesla maps and navigation is quite good and includes integration with the charging systems to help manage navigation to charging spots. CarPlay can include that information if the manufacturer is willing to include that in its CarPlay connector. Both are helpful in those cases where your navigation needs to include charging. For daily driving where charging is not needed, such integration is less important.
Beyond that, CarPlay provides a level of personalization and privacy that Tesla will not. Our phones are our personal information centers. Our contacts, call history, email, etc are there are those do not need to be shared with the car, but can be starting points for navigation. If I'm going to a new business across town, I will probably start with a web search on my phone and that will produce a location on my phone. I'd rather just use the phone maps to navigate rather than transferring the location to the car's navigation in a separate step.
For me, I am almost always listing to podcasts while driving and my subscriptions, downloaded episodes, listening history are all on my phone. I don't want to give that up, just to setup a completely separate podcast app on the car (is there even such a thing?). How would I seamlessly transition from listening while walking to listening while driving on the same podcast?
For these situations, Tesla only offers the bluetooth interface but that is very limited. No chapters, no large chapter artwork, no switching feeds, etc. I don't want to have to use the phone screen to manage those things while driving, even at a stop sign. It's not even legal in some jurisdictions.
Those are just a couple of scenarios where not offering CarPlay produces a substandard experience for the driver. If Tesla were to allow phone projection, it would address the need of personalizing the experience without compromising the overall Tesla driving experience.
