PastyPilgrim
Well-Known Member
Using the same logic, they should have gone with Google maps and/or support AA/CP.As for the Alexa integration, they would have had to build voice control into the car one way or another since every car has it. Why not use an out-of-the-box solution from one of the most popular and well-supported virtual assistants that's already on the market, saving you tons of time in the process?
Overall, Rivian's choice of maps isn't a huge deal for me because I think I can work with whatever maps. Like my apartment building is new and not in my current vehicle's maps, but it's not too hard to just set my home address as somewhere nearby, and all of the highway exit numbers are wrong because they recently renumbered the local highways but it's not too hard to just use exit street names instead of numbers.
My main disappointment is that, as a startup, I'd hope Rivian was still in their crowd-pleaser mode, but some of Rivian's product and business decisions are much more in the "we know what's best for you" camp that more mature companies like Apple are part of. It's not the end of the world, and Rivian executing as a more mature company is hugely beneficial in more cases than otherwise, there's just some minor disappointments stemming from my expectations of a startup. That does make my disappointments more my fault than Rivian's though.
Sponsored