Automotive / Embedded UX
Voice-Driven Interaction Design for Stellantis Infotainment
Voice interaction design for in-vehicle infotainment, built inside Stellantis's embedded platform constraints.
Voice interaction design for in-car infotainment, built to run inside Stellantis's embedded platform rather than the cloud.
The problem
Drivers need to control navigation, media, and climate without looking away from the road, but voice systems in a moving vehicle carry a different burden than voice systems on a phone or a smart speaker. The interaction has to work with unreliable connectivity, strict latency limits, and safety review that a consumer app never faces. Get the design wrong and you either force the driver to glance at a screen mid-turn or you build a voice assistant nobody trusts enough to use. Stellantis needed voice interaction patterns that held up inside those constraints across its infotainment platform, not a demo that only worked in ideal conditions.
What Veradin did
Rachel designed the voice-driven interaction model for the embedded infotainment system: command structures, confirmation patterns, and fallback behavior for when recognition failed or the system ran offline. Every flow was built around the embedded platform's real limits, not a cloud-connected best case, so response timing and error recovery were treated as design decisions, not engineering afterthoughts. Interaction patterns were designed to minimize the number of glances and taps a driver needed to complete a task, with voice as the primary path and touch as the fallback rather than the reverse. The work sat inside Stellantis's platform architecture, meaning every pattern had to hold up across multiple vehicle lines and hardware configurations, not one reference device.
The outcome
This engagement ran inside Stellantis's internal platform, and detailed performance metrics are proprietary to the client. The deliverable was a voice interaction system designed to work within real embedded constraints, hands-free control that degrades gracefully instead of failing silently when the car is offline or the command doesn't parse.
No public link. OEM automotive work of this kind ships inside the vehicle platform, not to a public URL.