Trail Log
Personal Projects · Case study
A service record that follows a mountain bike for its whole life, so the maintenance history survives the sale.
1. Summary
People buy mountain bikes costing five to fifteen thousand dollars and then do not maintain them on schedule, because the schedule is complicated. Suspension is due by ride hours, drivetrains and tires by miles, brake bleeds and sealant by the calendar. Three clocks on one bike. Trail Log tracks all three for each bike and keeps the service history with the bike when it is sold.
2. Goal
People buy mountain bikes costing five to fifteen thousand dollars and then do not maintain them on schedule, because the schedule is complicated: suspension is due by ride hours, drivetrains and tires by miles, brake bleeds and sealant by the calendar. Three clocks on one bike. The goal is a service record that tells the owner what is due and stays with the bike when it is sold.
3. Users and context
Riders who own a good bike and rely on a shop to service it, the shops that do the work, and the second owner who would otherwise inherit a bike with no history.
4. How it works
A written specification and a competitive scan came first, then the build.
5. Data, privacy, and governance
Each tool collects only what it needs to work and tells the user what that is. Privacy, security and accessibility are reviewed before a pilot starts, not after.
Status
Prototype, running on sample data. The Strava connection is simulated and nothing is saved between visits. Real sign-in and saved records belong to a later version.