Project 01

iDriver

Login-to-route is 2 steps instead of 4.

01

Problem

Newspaper drivers were losing time to an app that felt older than the vans. Suburb lists were buried, a compliance check gated every login, and proof-of-delivery photos were not clearly tied to the address they belonged to. On a run, that uncertainty is not a UX nit — it is a delayed street and a photo that might not stand up if a customer complains.

Problem visual 1
02

Constraint

Drivers change how they navigate as a run gets familiar: map when the suburb is new, list when they already know the streets. The app had to support both without adding a mode to learn. Delivery happens from the driver's seat, so every extra tap is time the paper is still in the van.

Constraint visual 1
03

Decision

I rebuilt the flow around the run, not the menu. The per-login compliance gate came out. Map and list sit together, with package counts and delivered status on every stop, so a photo is taken against the address it belongs to. Drivers who already know the area can stay in the list; drivers who don't can stay on the map.

04

Outcome

Drivers who walked the prototype understood the flow from the first screen. They no longer repeat a compliance check to start work, and they can see yesterday's performance before they leave the depot. Login-to-route is 2 steps instead of 4.

Outcome visual 1