Hacker News Reader

Comment by decafninja | Hacker News Reader

IIRC Tesla's touchscreen UI is running React Native?

Tesla uses Qt.

Ford is using an HTML-based interface in the Mach-E (and vehicles which get infotainment systems derived from that new generation of infotainment system). I've seen rumors that Ford is using React to power that interface, but I wasn't able to pin down any real sources.

This explains to some degree how Tesla is able to have such a buttery smooth UI on such terrible Intel Atom hardware (until recently.. they're switching to much better hardware now). At the same time, the Mach-E interface is not very smooth at all, but it is functionally pretty good. I think Ford should have a leg up on rapidly improving their infotainment interface, given that I would expect React to make some things easier than Qt... but Ford has so far failed to demonstrate that they can effectively distribute OTA updates, regardless of early promises. Hopefully they get that figured out soon.

"Buttery smooth" with complicated React UIs is entirely possible if you design it right. Unfortunately too many people just assume that whatever they throw at it will be fine.

Yes, but... it is difficult to do that on underpowered hardware. Modern browser engines seem to take a lot of resources to do anything at all, which gives you even less headroom before you write a single line of code. I don't think the Mach-E is equipped with a very powerful chip for the infotainment system. Since I can't find any reference to what it is, I would assume it's nothing to be proud of -- some kind of really old ARM chip, maybe.

If they equipped the Mach-E with a reasonably powerful SoC for the infotainment system, then I would agree 100% that a React-based UI could be implemented in such a way that it operates smoothly.

I've written fairly complicated React SPA UIs (certainly much more complicated than anything I've seen a car infotainment system other than, say, map rendering specifically) than run fine on relatively ancient phones and Chromebooks, so I think you're excusing just plain bad design a little too much here. I have to think they'd have the same issues regardless of platform, or if not only from using something that takes away control of the kind of things that can cause lag issues in React.

Reply on news.ycombinator.com