Honey
Well-Known Member
- Joined
- Mar 22, 2022
- Threads
- 4
- Messages
- 387
- Reaction score
- 579
- Location
- SF Bay Area
- Vehicles
- Gen 2 Quad Launch Edition
- Occupation
- Firefighter
When will it end?
Sponsored
Apples, please meet Oranges.AA/CP is nothing more than a peek window to your phone where ALL your digital life resides. It has very little to do with Rivian’s unified interface. Just like Apple iPhone is a unified interface that allow tens of thousands 3rd party app developers to contribute to the platform. Imagine iPhone only permits Apple native apps — iPhone WILL die the next day.
Interesting historical fact - Steve Job's original plan was that the iPhone would always closed to developers and only Apple would release iPhone apps.AA/CP is nothing more than a peek window to your phone where ALL your digital life resides. It has very little to do with Rivian’s unified interface. Just like Apple iPhone is a unified interface that allow tens of thousands 3rd party app developers to contribute to the platform. Imagine iPhone only permits Apple native apps — iPhone WILL die the next day.
I'd argue all three of these points *ALSO* apply to using CarPlay.Key Reasons for Skipping CarPlay
- Unified Experience:
- Reduced Complexity:
- Future-Proofing:
Absolutely - his arguments go both ways. And there's no way for RJ to know how many people didn't consider Rivian (or Tesla for that matter) because CarPlay is a major factor (for their own reasons) in determining which vehicle to buy. I had my daughter wait a month to buy her Subaru in late 2017 because the 2018 HAD CarPlay and the 2017 didn't. She argued that she didn't need it - my counter-argument was that she'd have the choice whether or not to use it in the 2018 model. Just because it's there doesn't mean you HAVE to use it. That's what I love about the EVPlay solution...It's there for a long trip when I want it and invisible for my local driving when I don't.I'd argue all three of these points *ALSO* apply to using CarPlay.
I'm not saying I agree with all three points, on either side. Just that the arguments being made work both ways, and thus aren't valid arguments for one side or the other.
- Unified Experience: You get the same experience across all your vehicles, regardless of make and model, as long as they support CarPlay.
- Reduced Complexity: You have one system to deal with, across all your vehicles. Once you learn it, you don't need to learn something different.
- Future-Proofing: You aren't stuck with the same system the carmaker sold you once they stop supporting it, you get improvements over time as Apple improves CarPlay and you upgrade phones, a much cheaper thing to upgrade than your car.
Maybe that's why it's not that big of a deal to me. My phone is just a peek into my digital life.AA/CP is nothing more than a peek window to your phone where ALL your digital life resides. It has very little to do with Rivian’s unified interface. Just like Apple iPhone is a unified interface that allow tens of thousands 3rd party app developers to contribute to the platform. Imagine iPhone only permits Apple native apps — iPhone WILL die the next day.
Any post about CarPlay, no matter the intent, is like blood in the water for the CarPlay fanatics. My favorite posts are from people who buy a Rivian and then indignantly say they are going to sell it if it doesn't get CarPlay.I didn't realize that my post would be taken as a complaint about the Rivian not having CarPlay...I've edited it to show my intent to simply pass on information to those who might be interested.
My much younger, beautiful wife also struggles with this. So she pretty much refuses to drive my truck.My in-laws (78 & 80), have each stuck with the same make car (Mercedes for her and Porsche for him) for the past 15 years. They jumped on the CarPlay bandwagon as soon as it was available from both manufacturers because it gave them a common interface and limited what they needed to learn every 2-3 years when they got a new model OR when they switched to the other vehicle. They have a R2 reserved, but are concerned because they're not sure they'll be able to use the Rivian UI to do what they need to do. It's really not fair that they watch what we do while driving, including:
We TRY to explain that the system will do everything for them and that we're making other choices and that they won't have to do any of it. As they're in our Rivian on local trips obviously none of that happens, but they don't notice when we don't touch the screen! It's just the "delta" from the ICE world to the EV world - the make of the car (and whether or not it has CarPlay) doesn't change that. There's a learning curve involved in switching to an EV.
- Switching from All Purpose to Conserve and back on longer trips
- Changing the charge limit back to 70% after we've been on a long trip
- Choosing where to stop and charge - either letting the Rivian nav do it or us making other choices
- Manually initiating battery preconditioning if the system doesn't recognize our charge stop