Capture drives
Trip drafts stay visible before details fade.
Product
A mileage workflow for customer visits, job sites, and supply runs.
MileLedger is organized around one loop: capture trips, review business versus personal versus commute, add purpose and job context, then export with confidence.
Product proof
The app keeps the whole mileage loop in view.
Capture, review, classify, and export are separate enough to stay clear, but close enough that records keep moving.
Review queue
Unfinished records are grouped for quick cleanup.
Classify fast
Business, commute, and personal choices stay explicit.
Export cleanly
Reports package mileage totals for sharing and review.
App surfaces
Four places. Four jobs. Less record cleanup later.
Trips
The daily capture surface.
Shows tracking health, recent captured drives, pending review, and the manual fallback when the day needs a quick correction.
Review
The heart of the product.
Turns captured trip drafts into cleaner records through category, purpose, client, job, and site context.
Reports
The output surface.
Previews monthly, quarterly, and yearly totals with CSV and readable summary exports.
Settings
The context layer.
Keeps saved places, vehicle, profession, mileage rate, permissions, and privacy controls understandable.
Operating loop
Linear by design, because users come here to finish a record.
-
Capture
Turn work driving into trip drafts before memory fades.
Automatic capture is the main path, with manual entry kept as a real fallback when tracking is paused, incomplete, or not available.
-
Review
Separate business, personal, and commute while the trip is still fresh.
The review queue keeps unfinished records visible so category, purpose, and confidence issues can be corrected before export season.
-
Add context
Attach the purpose, client, job, or site that explains the drive.
MileLedger is shaped for service work where a customer visit, job site, estimate, or supply run needs more context than miles alone.
-
Export
Share CSV and readable summaries instead of reconstructing the year.
Reports are built around monthly, quarterly, and yearly mileage records with completeness checks before the user shares them.
Design laws
What the interface protects when tracking and tax records meet.
Clarity beats cleverness
The interface should read quickly and explain itself without product theater.
Calm beats urgency
No scare tactics, no panic paywalls, no manipulative savings language. The product sells certainty, not adrenaline.
Local-first is a trust baseline
Trip records stay on-device by default. Privacy controls, export, and pause states are part of the information architecture, not hidden settings.
Permissions
Permission should be earned with context, not extracted with pressure.
Value before permission
Show why tracking matters before asking for background behavior. The product should earn permission, never ambush for it.
Manual fallback remains real
If a user declines location access, the app still needs a credible manual path so basic use is never held hostage.
Tracking health should stay visible
A calm product still explains whether capture is working, paused, or needs attention. Silent failure erodes trust faster than visible friction.
Access