Automotive

Automotive UX is designed around the road. Inside a car, the screen is never the main task: driving is. Every interaction has to be short enough to fit between glances, safe enough not to pull attention away for long, and predictable enough to use without looking closely. That turns many everyday interface patterns into hazards.

What separates good automotive interfaces

Glanceability. A good in-car interface shows only what the driver needs right now — the next turn, the current song, the incoming call — in large type with strong contrast that works in daylight and at night. It keeps frequently used controls in fixed positions so muscle memory can do the work, and it pairs the screen with physical buttons and voice for the actions people perform while moving. Phone projection systems such as Apple CarPlay and Android Auto apply the same idea: a reduced, driving-specific version of the apps people already know.

Where automotive UX usually breaks

Moving essential controls — climate, defrost, wipers — into touchscreen menus is one of the most criticised trends, because a touchscreen gives no feedback without looking. Deep menus, small targets, and animations that delay a response all compete with the road for attention. Notifications that pop up mid-turn, and voice assistants that misunderstand and then demand a correction, make things worse. Strong interaction design for cars starts with what should not be on the screen at all, and accessibility principles — clear contrast, large targets, more than one way to act — matter even for drivers with no disability.

This hub collects TYPENORM's automotive articles. For the navigation layer most drivers actually use, the catalog has teardowns of Waze, Google Maps, and Apple Maps, each of which also runs inside the car's own display.