Why Rivian’s Boring Software Updates Are the Ones That Matter Most

We are a tough crowd, and I mean that about all of us, myself included. We want a new feature every single month, something fresh to poke at in the driveway, and the moment an update lands without one we act like we got shortchanged. Then in the very next breath we are online complaining that the navigation stutters or that the garage door prompt ghosted us again on the way home. Both of those reactions come from the same people, and plenty of the time it is the same person on the same day.

That is the corner Rivian is painted into, and a release from a while back, 2026.07, put it on full display.

That update was a fixes-and-polish build. Nothing splashy, just a quiet round of cleanup on the vehicle you already own. The reaction was about what you would expect, a shrug and some grumbling that the team should be doing more, even though that exact release was chipping away at the stuff those same owners have been mad about for months.

I write software in my other life, so I feel this one. A new feature gets a reaction, people notice it and start posting about it online within the hour. A fix is different. The whole point of a good one is that nobody notices anything changed at all, the lag that used to drive everyone crazy is just quietly gone, and nobody throws a party for the thing that stopped being broken.

Bug fixes have never sold a single vehicle and features do, so a reliability pass is never going to headline a keynote and the gravity always pulls back toward the shiny thing even when the boring one is what owners actually need. Every software shop I have worked at fights this same pull, and most of them were not also trying to build a vehicle around the code at the same time. Rivian is doing both at once, which makes the balancing act harder than people tend to give them credit for.

Apple ran into a version of this years ago with Snow Leopard, a release that shipped almost no new features and just fixed a mountain of stuff. People were annoyed at the time, and now it gets remembered as one of the better ones Apple ever put out. Funny how the boring updates age better than the flashy ones.

I don’t know the real size of the Rivian software team, but I would bet it is leaner than most owners assume, which means somebody is sitting in a planning meeting every month deciding whether this is the month they finally go after the nav lag or whether they spend the cycle on something splashy enough to earn a press release instead. You cannot always get both in the same build, so something always ends up waiting another month.

Patience is the answer here and I know that is a frustrating thing to land on, partly because my own patience runs out faster than almost anyone I know. There are mornings the lag makes me want to chuck the screen across the parking lot. But I would rather they take the quiet month and fix the thing than skip it for one more feature I am only going to end up complaining about later anyway.

author avatar
Jose Castillo Founder and Editor
Jose Castillo is the founder of RivianTrackr and has owned and driven Rivians since early in the brand's consumer history. He currently drives an R1S and an R2 in Florida and uses Universal Hands-Free every day. As a credentialed Rivian journalist, he has covered the R2 First Drive in Park City and SXSW firsthand and has spoken directly with Rivian's software and autonomy leadership.
Add RivianTrackr as a preferred source on Google

Share this story

7 Comments

  1. I would love a boring update that fixes the delay/pause/skip/no service on Sirius and Apple Music permanently.

  2. The core problem with Software nowadays is it’s acceptable and the norm to ship software features and an OS with known bugs, knowing it can be patched later. The fact we see so many minor incremental releases is proof of this. Quality control is software is pittyful.

  3. When they started the Joint Venture with Volkswagen, Rivian ‘layed off’ almost 900 software engineers so they could be hired by the JV. The issue there isn’t just the obvious face-value of 900 employees. Those are the people that knew the code better than anyone, and were best equipped to bug-fix it.

  4. Excellent post, Jose, but i fear you are shouting into the abyss. It’s amazing to me that close to a third of the posts after any update basically say “this should be easy, why can’t they get it right?”. If it’s so simple I always wonder why they don’t describe the obvious solution in their post.

Leave a Reply

Your email address will not be published. Required fields are marked *