Transforming cars into a racing machine with performance metrics

A driver-first prototype brought the experience to life — helping the team align on the vision and enabling effective usability testing.

Designed for two key personas: aspiring young racers and race school instructors. Based on research, the app targets occasional drivers who want more from their Dodge — turning everyday drives into a premium racing experience.

Since this was a brand-new project, I began by diving into Android Auto guidelines and exploring design patterns from Alfa Romeo and older GM systems.

We started in black & white — sketching ideas, testing layouts, and figuring things out as we went. It felt messy at first, but the structure slowly emerged as we explored what could work.

Like any complex project, it is a good thing to work on logics, flows and understand principles of how it should work in between.

To shape features like track selection and sector breakdowns, I looked beyond traditional UX — turning to racing games like Gran Turismo and Need for Speed. They offered great insights into how to make performance data feel exciting and intuitive.

When everything felt urgent, I facilitated workshops to align priorities and build a clear roadmap. This visual became our north star — helping the team stay focused, communicate progress, and make informed trade-offs.

Before designing, I immersed myself in the world of drag racing — watching videos, reading forums, and even attending a live race. Talking to drivers gave me insights into how they use data in real time.

Interface design

To bridge the system with the real world, I used familiar racing elements. For example, the race start icon was inspired by the actual drag racing “Christmas tree” light — something every racer instantly recognizes.

1

'Go Race'

Launches drag mode instantly. Testing showed that audio recording needed to be optional.

2

Empty states

First-time users see a placeholder explaining where data will appear.

3

Outings

This section lets drivers review their recorded tracks and performance data.

4

Options

The line above indicates that the app functions goes only as far as Outings.

Pre-Record & Staging

Before recording starts, drivers enter the Staging area — where they prep tires and line up. At this point, the Delta Timer sits at 0.0, acting as a neutral baseline. During races, it compares your performance to the previous run, showing if you're gaining or losing time in real-time.

Starting a drag race

In line with our “automatic” principle, there’s no manual start button. The system detects full-throttle acceleration and begins timing automatically using G-force sensors — no taps needed, just drive.

Race in progress

The race ends automatically based on track length. Drivers can also manually stop it — either by hitting the brakes or pressing the stop button.

Designing the app meant thinking beyond the screen — considering how drivers use steering wheel controls, dashboard displays, and car widgets. Most interactions happen through the wheel while driving; the app itself is meant to be used when the car is stationary.

Testing without a real car was tricky — so I built interactive prototypes to simulate the in-car experience. We focused on drag mode and track selection, leading to key updates like smarter location-based track logic.

One insight: users wanted to save races from unofficial tracks. We supported it with a simple label — "Unnamed Road" — balancing user freedom with ethical design.

Before

• Track type was selected deep within the flow, with all race modes grouped together — drag, circuit, and rally.

After

• Race type is now selected upfront. Drag racing was separated due to its unique logic and flow, making the experience more intuitive from the start.

To streamline collaboration, I used wireflows to show all user paths and edge cases — complete with arrows, documentation, and prototype videos. This clear, self-serve format kept developers and stakeholders aligned, reduced meetings, and ensured smooth handoff.

To keep the experience consistent and on-brand, I followed Stellantis’ UI guidelines and dug deep into Android Auto best practices.

The result: an app that feels native to Dodge — cohesive, intuitive, and distinctly branded. Components were clearly organized and documented for the dev team, making implementation smooth and aligned.