Mobile product · Customer engagement · 2014 - 2015

Designing Metromile’s app around everyday driving

Customer interviews shaped a mobile redesign around trip history, driving insights, and street-parking support. I also simplified the quote flow for prospective customers.

The work gave customers useful information between insurance tasks and a clearer way to get a quote.

Metromile · Senior Product Designer

Role

Senior Product Designer

Team

Product, engineering, data science, operations, and customers

Scope

Customer research, iOS and Android design, prototypes, and quoting

Duration

Senior role · 2014 - 2015

Metromile mobile product screens showing a driver overview, fuel-efficiency trends, street-sweeping parking guidance, and trip history
The mobile overview brings together trip history, fuel information, driving insights, and street-parking guidance.

Context

An app customers rarely opened

Metromile’s app gave customers little reason to return between insurance tasks. Most of the experience centered on policy administration. I wanted to understand what else would be useful to people driving and owning a car in a city.

My role

I led customer research, feature definition, and iOS and Android design, working with product, engineering, and data science on what we could support. I also redesigned the quote flow for customers and the teams processing their applications.

Talking with city drivers

I interviewed current customers and target drivers about their day-to-day needs. They talked about where they had driven, what trips cost, how their driving changed over time, and whether they would remember street-sweeping rules. Those needs shaped the mobile redesign.

Design

Design decisions

01

Choosing features from driver interviews

I focused the redesign on trip history, driving insights, and street-parking support. Each addressed a need that came up in research with city drivers.

I worked with data science and engineering on feasibility and designed the mobile interactions and prototypes. The feature set gave the app a purpose between bills, claims, and support requests.

02

Making driving information easier to explore

I organized the mobile experience around an overview, trip summaries, and map detail. Drivers could move from a summary into the information behind a trip.

The shared navigation and empty states also covered features that needed more driving data or setup before they could show useful information.

03

Making the quote steps clear

I redesigned the quote flow as a sequence covering vehicles, drivers, rates, coverage, documents, and payment. Per-mile pricing stayed in context as customers worked through their choices.

A save-for-later option let people return to their application. I also considered the information the internal team needed to process it.

A closer look

Product screens

Metromile desktop quote flow showing progressive vehicle entry, driver and rate steps, coverage controls, per-mile pricing, and save-for-later behavior

The quote flow shows vehicle, driver, and coverage steps alongside per-mile pricing, with a way to save progress.

Metromile mobile navigation, trip history, trip detail, overview, and empty-state screens

Overview, trip history, and map detail share the same navigation. Empty states cover features that need setup or more driving data.

Product flow

Connecting trip information and the insurance experience

Trip data supports history, driving insights, and parking help. The quote flow gives interested drivers a way to explore coverage and pricing.

Results

What changed

Shipped

Driver-focused features

Trip history, driving insights, and parking support gave customers information beyond policy administration.

Feedback

Interest in the app

Customers shared the driving insights, and some people became interested in Metromile through the app itself.

Redesigned

The quote experience

A progressive flow kept pricing and the remaining steps visible, with a way to save progress.

About these results

Customer interest and word-of-mouth outcomes are qualitative. The original analytics are unavailable, so no numerical engagement or acquisition lift is claimed.

Next case study · LaunchChair.io

Designing and building LaunchChair, a planning tool for coding agents

Protected case study

Inside the NetDocuments work.

A closer look at the product decisions behind PatternBuilder. This case is shared privately; the rest of my portfolio is open.