Portfolio
An InCar HMI concept that detects when delay becomes meaningful and surfaces the next best action, instead of waiting for the driver to ask. Built to test whether AI in the car belongs in a conversation window — or in the workflow itself.
When delay affects a meeting, reservation, or arrival, drivers fall back to their phone. They call, message, check maps — while in motion.
There is no proactivity by the system itself.
Current in-car systems don't help with the consequence. The phone does. The phone also kills.
Delay was consistently described not as a navigation problem but as a coordination one. When ETA shifted past a meeting, reservation, or arrival, drivers reached for the phone.
My brain is packed up — I'd want help and suggestions from the vehicle.
Cut the broader assistant concept. Focused on the moment delay becomes consequential.
Designed support to live inside the existing HMI surface, not as a separate AI mode.
Suggested actions, never executed silently. Confirmation required for messages, joins, reschedules.
Used calendar, ETA, and route together to decide when support is meaningful, not just if.
Built as a state-driven simulation rather than a click-through. Each scenario shows how the interface responds when route, ETA, and commitment data converge.
| Scenario | Type |
|---|---|
| Late for Meeting | Core delay |
| Late for Reservation | Core delay |
| Running Home Late | Core delay |
| Tiredness | Exploratory |
| Cabin Discomfort | Exploratory |
Each hypothesis was assessed across the three core delay scenarios (Meeting, Reservation, Late Home) — 15 total scenario responses.
Every participant said the support would replace reaching for the phone.
14 of 15 scenario responses positive.
Participants accepted suggestions. Rejected silent execution.
Held in principle. Presentation layer still needs tightening — wording, hierarchy, option count.
Three of four hypotheses validated strongly. The fourth held in principle but exposed iteration points.
JSON scenario data drives timing, triggers, and content. A JavaScript scenario engine sequences states. React components render the interface dynamically.
The architecture mirrors how a real vehicle context engine would have to behave — not a static screen sequence.