Vehicles experience: Bridging the gap between drivers and their vehicle’s data
Type of project
A real-world mobile product feature developed and deployed as part of The Floow’s telematics platform for global insurance clients.
Company & product overview
The Floow builds mobile telematics solutions for insurers, helping drivers monitor behaviour, manage their insurance, and connect to their vehicles. This includes traditional vehicles tracked via smartphone sensors, and connected vehicles integrated via OEM APIs or dongles.
Skills & area of focus
System design, mobile UX/UI, connected car integration, user flow architecture, data mapping, responsive UI, edge-case handling, localisation, cross-platform UX.
Project problem or purpose
The original vehicles section was limited, inconsistent, and failed to support connected car features. Users couldn’t easily see which car was being tracked, adjust preferences, or understand their data. We needed to redesign this to support connected experiences, simplify management, and support real-world usage, including multiple vehicles, drivers, and states.
Roles, responsibilities, & team
I led the redesign and strategy. I collaborated with two product designers, mobile engineers, and the team integrating connected car data (via third-party APIs). I also worked with insurer product owners and compliance to ensure that regulatory and white-label considerations were fully met.
Timeline, scope, constraints
The project took place over 12 weeks. Challenges included variable vehicle data formats, syncing status states (manual vs. connected), and adapting the UI for apps that ranged from one-driver policies to family plans. We also had to accommodate “ghost data” scenarios and support for both metric and imperial units.
Process & what I did
We started by auditing existing vehicle flows and support tickets, identifying pain points like unclear sync status and limited editing. I redesigned the entire experience with a modular, scalable architecture, supporting manual and connected vehicle types, naming, VIN matching, and driver linking. We added education layers for new users, clarified active vehicle status, and created fallback logic for vehicles that stopped reporting.
Outcomes, results, & lessons
User confusion around vehicle status dropped by 95%, and feature usage (vehicle switching, editing, linking) increased significantly. Connected car integrations became easier to onboard due to the modular UI. Insurers appreciated the improved user understanding, which reduced “invisible driver” complaints. The lesson: vehicles are data-rich but emotionally distant, and good design helps people feel in control of both.
