I have it from a good source that the red and yellow military-looking panic button is actually called the "MILD switch", which stands for Mother-In-Law Deletion switch. It works much like the ejection seat for jet fighters. As we know the roof is fixed and not removable, so the MILD device must be side-ejecting (video, please).That would be the emergency eject button for when things get a bit too adventurous!
We've gotten more details from 23 seconds on someone's cell than Rivian has given us in months, even with their recent update about the interior... WTH.
First time seeing the controls on the steering wheel in detail. Tried to get the best picture from the Twitter video. The other frames are mostly blurry.
some details visible in the UI, large display is vehicle settings. Seems RIDE is set to stiff, Break Regen to High and Stability on reduced. The other setting seems to be auto hold.
I'm happy to see the three cars on the driver's screen; it will have some smartness like Tesla's.
This seems wrong.I have a feeling that Apple doesn't work with any car makers with their own route/trip planner because it steers away from Apple Map.
This is incorrect.I have a feeling that Apple doesn't work with any car makers with their own route/trip planner because it steers away from Apple Map.
I'd argue that ALL manufacturer excuses for not supporting CarPlay are poppycock. None are good.Certain manufacturers have lists of reasons (some arguably good, others poppycock) to prefer locking people in to their own in-car UI, and therefore they don't want to support CarPlay.
That's B.S., imo. The simplest solution is to offer CarPlay but AutoPilot requires use of factory nav for routing. I typically use my factory navigation simultaneously while I use CarPlay for music and messaging. I've never had a problem with both working together.In a Tesla, for example, they need you to use in-car navigation because that's how to you point-to-point autopilot. It's believed this is a primary reason Tesla won't ever support CarPlay/AndroidAuto.
Again, a B.S. reason. CarPlay supports apps like ABRP and PlugShare. Apple Maps even has integrated EV routing (https://www.idownloadblog.com/2020/09/30/apple-maps-electric-vehicle-routing-tutorial/). Furthermore, this shouldn't be Rivian (or any other manufactuers) choice to force their users on what they can and cannot do. If I a user wants to use Apple Maps then just LET THEM. If you think your maps are better, then communicate your feature set to your customers. If your telemetry data shows people are still using CarPlay more than your factory nav then maybe that's evidence your factory nav isn't as fantastic as you thought it was???In-car nav is also preferred by EV makers because the in-car nav is the one that can schedule charging stops along the way. This could be one "arguably legitimate" reason on Rivian's list of why they won't support it.
Again, B.S. Acura, for example, uses Alexa in their newer vehicles and yet they still offer CarPlay and Android Auto.And with the Amazon roots here with built-in Alexa, you'd better believe it's simply Amazon calling the shots and not letting them.
As a user, you won't find me arguing with you. They're all BS, and obviously CarPlay can always be supported on top of built-in stuff (as I focused on).I'd argue that ALL manufacturer excuses for not supporting CarPlay are poppycock. None are good.
Again, a B.S. reason.
I did NOT mean to imply the existence of Alexa in a Rivian precludes CarPlay.Again, B.S. Acura, for example, uses Alexa in their newer vehicles and yet they still offer CarPlay and Android Auto.
Amazon is one of the most compelling arguments against buying a Rivian. I wish they weren’t connected.As a user, you won't find me arguing with you. They're all BS, and obviously CarPlay can always be supported on top of built-in stuff (as I focused on).
I was just listing the types of rationalizes that have been given, or would be likely to be given.
I did NOT mean to imply the existence of Alexa in a Rivian precludes CarPlay.
Acura is not the only counterexample.
The true focal point was Amazon's extremely deep pockets are inextricably intertwined with Rivian
I'd be THRILLED to learn that no CarPlay is simply because "we haven't gotten to it yet" and it is added with a software update later.
But I don't expect to learn that, because I fully expect that Amazon wants all that sweet, sweet data that they're paying for.
Money and control.
I do believe the ultimate end game for Amazon’s involvement is two-fold: the battle for people’s eyes and its companion, self-driving cars.Amazon is one of the most compelling arguments against buying a Rivian. I wish they weren’t connected.