Codex Pipeline experimental editorial illustration

CODEX PIPELINE — EXPERIMENTAL

Independent OpenAI pipeline experiment · predicted A · 43/45 · human judgment still wins

The Problem With a Car Touchscreen Is the Glance It Demands

Do not judge a dashboard by screen size or button count. Park the car and find out what it asks you to locate, remember, confirm, and undo—especially when the screen is busy doing something else.

Experimental car-interface guide based on official NHTSA guidance and Euro NCAP assessment materials, not a formal safety evaluation of any vehicle. Perform the audit only while safely parked and follow the vehicle manual and local law. Never treat a time or glance criterion as permission to operate a screen while driving.

quick-answer

The ten-minute parked audit

With the vehicle safely parked, start from its normal home screen and perform six ordinary jobs: change temperature, change fan or defog setting, adjust audio, find the driver-assistance status, switch the camera view if equipped, and return from phone projection to vehicle controls.

For each job record: where you began, how many different places you looked, whether the control stayed visible, how the system confirmed the change, and how you returned home. Then make one wrong input on purpose and recover. Do not conduct this experiment while moving.

comparison

A screen is a surface. A glance is a cost.

The same function can impose very different demands depending on how it is placed and confirmed.

Direct and stable

One identifiable control in a predictable place

It may be physical or touch. The advantage is that the driver knows where the interaction begins before searching.

Visible but conditional

The control appears only on one screen or in one mode

A large target is less useful when navigation, a camera, a warning, or phone projection removes it.

Remembered

The driver recalls a menu path

Memory can make a familiar car feel easy while hiding how hard the interface is for a new driver, infrequent function, valet, rental, or stressful moment.

Confirmed elsewhere

Input and feedback occupy different locations

A finger may act low on the console while the result appears high in the cluster—or vice versa. The eye now has two destinations.

specs

Count five demands, not taps

Tap count can be useful, but it misses why two one-tap controls feel completely different.

Locate

Where is the control now?

Does it have a permanent home, a physical shape, a stable edge location, or a label that changes with context?

Aim

How precisely must the input land?

Check spacing, target size, road-side reach, and whether a nearby control creates an expensive mistake.

Interpret

What does the symbol or label mean?

A familiar icon can reduce reading. An ambiguous icon creates a second task: decode before acting.

Confirm

How does the car show the new state?

Look for immediate visual, tactile, or audible feedback and whether the final state remains visible long enough to understand.

Recover

What happens after the wrong action?

Back, cancel, undo, and home are part of the interface. A clean first path with poor recovery is fragile design.

callout

Why official tests care about the glance

NHTSA's voluntary visual-manual guidelines evaluate in-vehicle secondary tasks using criteria that include individual eyes-off-road glances and cumulative glance time. Euro NCAP's current safe-driving work distinguishes physical, direct-touch, menu-based, and voice inputs, and its 2026 framework gives new attention to the placement, clarity, and ease of essential controls.

Those frameworks do not say that a driver receives a personal allowance to look away. They show why interface evaluation must consider the visual and manual task—not merely whether a feature exists. For a shopper, the safe translation is simple: perform the audit while parked and reject unnecessary uncertainty before it becomes a driving habit.

figure

Test the screen when it is already occupied

A showroom demonstration often begins with a clean home page. Real use begins with something else demanding the display.

Phone projection

Return to a vehicle function

From CarPlay, Android Auto, or the vehicle's equivalent projection state, find climate, cameras, and native navigation without asking the salesperson to take over.

Camera active

Change or dismiss the view

Confirm that camera controls are legible, the exit is predictable, and the system returns to a useful state.

Warning present

Find the meaning without clearing it blindly

A warning should not force a choice between obscuring essential information and dismissing something not understood.

Dark cabin

Reduce brightness without losing the route

Check glare, dimming, display-off behavior, and whether essential status remains available. Do this parked in an appropriate setting.

Fresh start

Power-cycle and inspect what the car remembers

A shortcut is not dependable if it moves, vanishes, or resets with the profile or startup state.

buyer-match

Good redundancy gives one function more than one sensible door

Redundancy is valuable when each route suits a different condition and they agree on the final state.

Physical

Fast identification and feedback

Useful for repeated functions when the control is well placed, distinct, and behaves consistently.

Direct touch

Context plus visible labeling

Useful when the target remains available, large enough, separated, and close to the information it changes.

Steering wheel

Frequent control without reaching away

Useful only when symbols, press direction, mode, and feedback are clear. A glossy unlabeled pad is still an interface problem.

Voice

A hands-available alternative

Useful when the command is discoverable, response is quick, privacy is acceptable, and a non-voice route remains. Voice should not be the only door.

Automatic

The car acts without a request

Automation helps when its state and override are obvious. An invisible rule that surprises the driver adds uncertainty instead of removing work.

quick-check

Make one mistake on purpose

While parked, tap the adjacent climate target, enter the wrong settings page, or activate a mode you do not want. Then stop and observe.

Recognition

Can you tell what changed?

A highlighted icon, persistent status, sound, or physical position should make the state legible.

Escape

Is back actually back?

Some systems mix close, cancel, home, and previous screen. Confirm which action returns you without discarding something important.

Undo

Can the previous state be restored directly?

A mistake should not require reconstructing several settings from memory.

Timeout

Does a temporary panel vanish before it can be understood?

A disappearing control can force the user to restart the task. A panel that never clears can hide more important information.

Explanation

Can the interface explain a disabled control?

A grayed-out function should reveal why it is unavailable and what condition would change that state.

skip

What we'd skip during the showroom pitch

A polished demo proves that one practiced person can present the system. It does not prove the system teaches or protects its own logic.

Skip

Letting the salesperson perform every task

Ask for the car in its normal start state, then locate the controls yourself while parked.

Skip

Counting buttons without using them

A physical control can be too similar to its neighbors, hidden behind the wheel, mode-dependent, or disconnected from clear feedback.

Skip

Judging only the home screen

Projection, cameras, settings, warnings, and profiles change what is visible and where home lives.

Skip

Assuming voice rescues a buried menu

Voice can fail because of wording, connection, noise, account state, or privacy choice. Verify a second route.

Skip

Calling familiarity proof of simplicity

Habits can make a weak interface survivable. Evaluate how the system behaves before muscle memory does the unpaid design work.

quick-check

Leave the test drive with six yes-or-no answers

Score the system only after performing the same parked tasks in each car.

One

Can I locate repeated controls from the normal home state?

No coaching and no memorized shortcut.

Two

Do essential status and feedback appear where I naturally look?

The action and confirmation should form one understandable loop.

Three

Can I recover from a wrong input immediately?

Back, home, cancel, and undo should not be a vocabulary quiz.

Four

Do phone projection and cameras preserve a predictable return path?

A feature that takes over the display should not strand the driver inside it.

Five

Is there sensible redundancy for repeated functions?

Physical, touch, wheel, voice, and automation should complement rather than contradict one another.

Six

Will the logic survive a profile change or software update?

No shopper can guarantee this. Favor stable placement, explicit state, and documented controls over novelty that depends on one arrangement.

verdict

Verdict: buy the interface you can recover from

The best interface is not the one that wins a photograph of the dashboard. It is the one that makes repeated actions easy to locate, makes state changes hard to misunderstand, and makes mistakes cheap to reverse. A physical button can succeed or fail that standard. A touchscreen can succeed or fail it too.

During the parked audit, notice when you stop understanding where you are. That moment matters more than animation quality or screen resolution. If the system requires the salesperson's memory to feel simple, it is not yet simple for you. Choose the car whose controls explain themselves—and whose road manners, safety, fit, and ownership case also survive the rest of the evaluation.