Coding For Cars: The Next Generation of Mobile Apps
snydeq writes Developers will need to rethink UIs, connection strategies, and how to capitalize on new data streams — especially as autonomous cars start rolling off the lots, writes InfoWorld's Peter Wayner, in a forward-thinking article on developing apps for cars, including autonomous cars to come. "Delivering data to cars, autonomous or not, will take a whole new way of thinking. Rectangles will always be rectangles, but automobile network connections are spotty and the user interface needs to compete — if that's the right word — with the objects on the road for the right amount of attention from the driver. Here are eight ways developers will need to rethink their app strategies when it comes to delivering apps for cars."
the user interface needs to compete
No. A thousand times no. The UI of in-car equipment must not compete in any way for the driver's attention. A good UI would require no sight at all, but would provide a consistent placement, easy to find without taking your eyes off the key task you have as a driver - driving, provide consistent and non-visual feedback, and work 100% reliably every time. Ladies and Gentlemen, I give you... the "switch".
If you think about a real driverless car, why would it have much UI at all?
I would think, a screen that would tell you where it was going, an estimated time, and some way to select music.
Mostly it would be told where to go through voice and verify by showing you a map.
More complex things could be done with a tablet or phone app. The UI of the car doesn't need to compete with anything, because it's just a transport you are traveling in.
"There is more worth loving than we have strength to love." - Brian Jay Stanley