Starting a tracker is only the beginning. The useful part is being able to understand the working day afterwards.
Start with the review
PurrMiles starts with a working driver’s need to keep shifts, journeys and mileage together. A shift begins and ends with an odometer reading. Journey cards put the route beside its record, with gaps visible for review. Business and personal classification gives those records further context.
That structure gives us a useful design question: what will the person need to check when the work is finished?
Give the records context
For a driver, that includes which journeys belong to a shift and which records need attention. In another business it might be the jobs belonging to a visit, the photographs belonging to a request, or the changes made during a handover. The same practical step applies: define what a useful review should show before adding more ways to collect information.
Sketch the end of one routine
Start with one routine. Write down what begins it, what gets recorded along the way and what someone needs to understand at the end. Then sketch that final review. Any missing context becomes a concrete question for the app’s design.
PurrMiles 0.16 is in internal testing. Its current public phone captures show recording checks and appearance settings; recording accuracy and background reliability still need testing on real journeys.
Explore the PurrMiles project, or tell us about a routine your team needs to review.