Trail Log

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.

Audience

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.

Process

A written specification and a competitive scan came first, then the build.

• Pick a bike. Each bike has its own record, because forks, shocks, tires and wear all differ.
• Three clocks. Every service item is tracked in its own unit: ride hours, miles or calendar months.
• Next service date. Projected from the last four weeks of riding, not an all-time average, because riding is seasonal.
• Service history. A timeline of every service, marked as verified by a shop, backed by a receipt, or self-logged.

Technology

• A single HTML page: vanilla JavaScript, no framework, no backend.
• Nothing saved between reloads, so it runs the same as a local file or a hosted page.

Outcomes

Prototype, running on sample data. The Strava connection, miles and ride time for each bike, is simulated. Real sign-in and saved records belong to a later version.