Car UX Part 1: How to Design Car User Experience (Without Distracting the Driver)

Good car UX is a budget of two-second glances. Everything on the dashboard is competing for them.

Most designers assume the hardest screen to build is a busy dashboard packed with data. It's actually a car dashboard doing almost nothing. In the last post in this series, we asked a half-joking question: why does the car dashboard face the driver and not the passenger princess riding shotgun? The answer is obvious once you say it out loud. The driver is the one who can't afford to look away.

That's the whole challenge in a sentence. Almost everywhere else, you design to hold attention. In a car, you design to hand it back. Once that clicks, car UX stops feeling mysterious and starts feeling like a set of rules you can actually follow.

Here's how those rules work, and a simple process you can use the next time you design anything a person uses while moving.

What is car UX design, and why is it so hard?

Car UX design is how a driver sees, understands, and controls everything inside a vehicle: the dashboard, the infotainment screen, the buttons, the voice commands. The whole system has a name in the industry, the HMI, short for Human-Machine Interface. But the label matters less than the constraint behind it.

Here's a simple way to think about it. On a phone, your app is the main event. In a car, your interface is never the main event. The road is. The driver is doing something genuinely dangerous at speed, and your screen is competing with that for their eyes.

Most digital products want to keep users engaged. A car interface wants the opposite. The best outcome is a driver who gets what they need in a fraction of a second and looks straight back at the road. That single flip, from holding attention to returning it, is why car UX breaks most of the habits you built designing for screens that sit still.

The one rule that changes everything: designing for glance time

If you remember nothing else from this post, remember glance time. It's the amount of time a driver's eyes leave the road to look at your interface, and it's the number everything else serves.

This isn't a vibe. It's measured. The NHTSA driver distraction guidelines recommend that any single glance away from the road stays under 2 seconds, and that the total glance time to finish one task, like picking a song, stays under 12 seconds. That's your entire budget.

A quick way to feel how tight that is: at highway speed, two seconds is roughly the length of a football field driven blind. So when you decide where a button goes, how big the text is, or how deep a menu runs, you're really deciding how much of that budget to spend. A car dashboard isn't judged on how pretty it looks. It's judged on how little of the driver it steals.

The 5 principles of good car UX

Most car UX advice online is a long list of guidelines that blur together. Here's a tighter version. Five principles, each one earning its place.

1. Glanceability

A driver should understand your screen in under two seconds, ideally one. That means big type, strong contrast, clear hierarchy, and information grouped the way the eye already scans. This part is regulated, not optional. ISO 15008, reconfirmed as current in 2025, sets minimum requirements for legibility, contrast, and color on displays used while the car is moving. In practice, if a driver has to squint or hunt, you've already lost.

2. Design for day and night

This is the point from the dashboard post, and it's a real constraint. In daylight, your screen fights glare. At night, that same brightness becomes a hazard, because a bright screen pulls a driver's eyes off a dark road and wrecks their night vision. Good dashboards adapt on their own, dimming and shifting contrast as the light changes. It's the same reason dark mode isn't just a style choice here. In a car, a dark interface is a safety decision.

3. Keep cognitive load low

Muscle memory beats menus every time. The best car controls are the ones a driver uses without really thinking, like a volume knob they find by feel or a temperature dial that's lived in the same spot for years. This is just Hick's Law showing up in traffic: every extra choice costs time, and time is exactly what a driver doesn't have. When you're tempted to add one more menu layer, remember you're adding thinking to someone already busy driving.

4. Prioritize for safety, not features

Not everything earns a spot on the screen. For each element, ask one question: does the driver need this while moving, or can it wait until they park? Speed, navigation, and warnings earn permanent space. Typing an address doesn't. That's why NHTSA recommends locking things like manual text entry and video unless the car is stopped and in park. When in doubt, ship less.

5. Give feedback you can feel

A driver shouldn't have to look to know a tap worked. That's the job of a physical click, a small buzz, a short sound, a bit of ambient light. The best confirmation in a car is one the body registers without the eyes leaving the road. This is a small detail that makes a big difference, and it's the first thing that disappears when everything moves behind flat glass.

Are physical buttons or touchscreens better for cars?

For about a decade, the industry chased one look: kill the buttons, bury everything in a glossy touchscreen, ship a cabin that looks like the future. And it does photograph beautifully. The problem is that flat glass gives your fingers nothing to find. You have to look to hit a target that isn't really there, which spends glance time you can't spare.

Regulators have now said so out loud. From January 2026, Euro NCAP will make it harder for touchscreen-only cars to earn a five-star safety rating. To score top marks, carmakers have to provide real physical controls, with tactile feedback, for five essentials: turn indicators, hazard lights, the horn, the wipers, and the emergency SOS call.

Here's the honest take. The touchscreen was never the villain. Putting the wrong things inside it was. A big screen is a great home for a map. It's a terrible home for hazard lights you might need to slap in a panic without looking. The knob is coming back because your hand can find it in the dark, and that turns out to matter more than a clean photo.

How do you actually design a car interface?

Principles are easy to nod along to and hard to apply. So here's a simple five-step process you can actually follow.

Step 1: Map the glance journey. Before you draw a single screen, list every moment a driver might look over and what they need in that half-second. You're designing a string of two-second glances, not a poster that sits still.

Step 2: Rank everything by safety. Sort every element into three piles: needed while moving, nice while moving, and parked only. That sort decides what gets permanent screen space and what gets locked the moment the car rolls.

Step 3: Design for the thumb. Put the things people use most where their hands already rest, and keep them in consistent spots so reflexes can build. This is Fitts's Law in the cabin: bigger, closer targets are easier to hit, especially when the car is moving and the target is a moving hand.

Step 4: Test in motion, never on your monitor. A layout that's obvious on a desk can fall apart at speed, in glare, over a rough road. Get it onto real hardware, in real light, in a simulator or a moving car. Your monitor will lie to you every time.

Step 5: Design the night state first. Most teams build the bright daytime screen and dim it later as an afterthought. Flip it. Build the dark, calm, 2 a.m. version first, then let it brighten for daylight. You end up respecting the road after dark instead of shouting over it.

Common car UX mistakes beginners make

• Burying climate and hazards in menus. If someone has to tap through screens to warm up or flick on hazards, they're looking away too long. Keep essentials one action deep, or physical.
• Screens that never dim. A fixed-brightness display is a genuine night hazard. Adapt to the light, always.
• Notification pile-ups. Every alert is a demand for a glance. Batch what isn't urgent and mute what can wait.
• Tiny tap targets. A target sized for a calm thumb on a still phone is nearly impossible to hit in a moving car. Go bigger than feels reasonable.
• Designing for the showroom. If your interface only impresses while the car is parked, it's a display piece, not a design.

Where car UX is heading next

The dashboard is about to change more in a few years than it has in decades, and most of the shift is about spending less glance time, not more.

Voice is finally good enough to handle the tasks that never belonged on a screen, with no glance at all. AR windshields are starting to paint directions onto the road itself, so a driver's eyes never drop. And the car is becoming a place where voice, touch, and gesture work together instead of forcing everything through one screen. This is where things get interesting: as cars take on more of the driving, the real question becomes how much attention we hand back to the human, and how we keep them ready to take the wheel again.

The tools keep changing. The core rule doesn't. Respect the driver's attention, because it's the one thing you can't give back.

Quick answers

How long should a driver's glance at a screen last?

No single glance should last more than 2 seconds, and the total glance time to finish one task should stay under 12 seconds, based on NHTSA guidance. Design every interaction to fit inside that budget.

How do you design a car dashboard for night driving?

Design the night version first: lower brightness, higher contrast, and dark backgrounds, so the screen never becomes the brightest thing in the cabin or harms night vision. Then let it adapt automatically to the surrounding light.

Coming up in Part 2

This post covered the principles and the process. Part 2 gets its hands dirty with the parts drivers actually touch and hear every day.

We'll dig into dashboard design up close, how the instrument cluster earns every pixel. Then sound design, the chimes, alerts, and engine notes that guide you without a single glance. And finally the main beam paradox: the light that helps you see better while making the road more dangerous for everyone else, and why leaving your high beams on is one of the most common driving mistakes there is.

While you wait, catch up on why car UX is so complicated to design, then read up on Hick's Law and Fitts's Law to see the psychology doing the heavy lifting behind everything above.