Innova RepairSolutions2

RepairSolutions2 presented engine codes, sensor data, and diagnostic charts in terms a mechanic could interpret. Drivers needed a different starting point: what the finding meant and how urgently it needed attention.

I led the redesign around that gap, connecting diagnostics, trip data, and maintenance while preserving access to the technical detail. The work spanned information architecture, core workflows, and a shared design system for iOS and Android.

A language the driver already speaks

The visual language needed to support quick reading. I updated the app identity and typography alongside the information hierarchy, so plain-language findings were easier to scan.

I brought trip data, diagnostics, and maintenance into a connected experience, giving drivers context for how their vehicle was performing.

The screen that mattered most

The post-scan screen was the critical decision point. A result such as “P0301: Cylinder 1 Misfire Detected” identified an issue without helping a driver interpret its significance.

I organized the result around severity, the finding in plain language, and supporting evidence. A summary alone would have hidden useful detail; leading with the raw code put the interpretation work on the driver.

The same principle shaped the relationship between trip insights and vehicle health: make the summary readable, then provide a path into the detail.

Severity first. Vehicle Health used color to distinguish detected issues from a scan with none, giving drivers an immediate starting point for reviewing the results.

Plain-language findings. Each issue explained the symptom and its urgency alongside familiar checks such as brake life and tire pressure.

Technical evidence within reach. Trouble codes and sensor data remained available under “Learn More About This Issue,” supporting both drivers who wanted more detail and mechanics reviewing the result.

A reason to open it every day

I designed navigation into the experience through the Waze SDK, extending the app's use beyond diagnostic scans. It introduced integration and maintenance requirements in exchange for a useful role during everyday driving.

Consistent patterns across modules

I established shared typography, spacing, color, and components across modules. Defining these foundations early helped keep vehicle health and diagnostic states consistent as the app expanded.