> This is a decision. It's generated, I said there's many millions of decisions, many of them will never get noticed and they're just under the surface. One of those decisions that's been noticed quite a bit is the fact that we've intentionally not included CarPlay in the vehicle. And that's not to say we don't think a close partnership with Apple is important. So we have Apple Music integration, we have a bunch of Apple integrations that are yet to come, we have a great relationship with the team at Apple. But it was more to say, we just felt and continue to feel very strongly about creating a consistent, fully integrated digital experience where you're not jumping between apps, let's say from a CarPlay app back to the vehicle app. And it's quite jarring when you don't have, let's say vehicle level controls when you're in the CarPlay environment. That view we've had since the early, early days. I think that's going to become even more important and more true in a world of integrated AI.
They could easily make their screen compatible with Carplay/Android Auto and provide whatever experience Rivian wants to at the same time, and they could let the drivers choose which to use.
And I write this as someone with a Model Y who does not miss Carplay (although it would be nice to have).
We may both disagree with their decision, but that doesn’t mean the explanation is bullshit.
And to be fair, as you point out, if they do a really good job with the UI/UX (as Tesla have mostly done) then you’ll probably not miss CarPlay most of the time.