Well, thats 41 minutes of my life I'll never get back apparently, Fisker never had ACTUAL drivers test the audio/navigation system at all, and it's executed poorly.. perhaps outsourcing that to someone with UI experience would have been a smart decision. But since they've only made about 300 Karma's total, and Fisker is having some "issues", who knows if it will ever be fixed. This is one of the issues buying a vehicle from a new manufacturer, with no experience, I hope Tesla does considerably better.
A $100,000 car can have much higher material costs than a $25,000 car, but it can't have higher R&D costs. There are a whole lot of costs Toyota can amortize that Fisker can't. EDIT: Ok, I went and watched 2 minutes of the video. Fisker has an utterly terrible system, not merely inferior. Hard to believe they can't hire another coder or two to fix their car.
Lol the AC issue is terrible, wait for the computer to load, then hit agree lol, WOW. Sorry for him getting freezing air being blast in your face during winter.
Thanks! I'm surprised I've watched the whole thing now. His radio memories defaulting to some value isn't specific to his car. Plenty of cars have this behavior. I do understand many of his other beefs though. Agree that the choice of colors in many cases sucks. The lack of tire pressure isn't that uncommon on cars. A former coworker's 03 350Z had TPMS and would show him the tire pressures in the trip computer. However, he claimed that it was inaccurate and thus always complain his tires were low, which he could never get fixed. It seems that on many Nissans later, they just don't bother showing you the tire pressure at all, maybe because of the above problem. Yep on the 1st point. On the 2nd point, well, it takes more than coders to fix stuff. I used test to software for a living for many years. It takes a good UX design person, hopefully some usability testing (and iteration based on what's learned) and a consistent set of design principles. Most often, engineers are notorious for producing pretty lousy UI aka "developer UI" or "engineers' specials". The coders then implement or fix based on what I mentioned. Also, unfortunately, many non-software companies are pretty lousy at writing good software either from a reliability POV or usability POV, or both. There are PLENTY of examples of that in the consumer electronics space. I'm guessing that it doesn't have lockout when moving >3 mph like Toyota/Lexus navs. It seems like their system needs it.
Funny thing is that Is This Video The End Of Automotive Journalism? | The Truth About Cars is currently the top story of TTAC. It features the same video posted by the OP.
I recommend everyone to watch it. There are a lot of good points he made and some of them I learned in the UI class in college. I learned some new things as well.
I'm guessing the video and Fisker are going to get a lot more attention now that it's made it on ABG: A 41-minute video about why the Fisker Karma infotainment system gets an F.
