Cloud sync should be a backup, not a leash.
The TrailFu web ecosystem starts with low-risk sync: garage, settings, route plans, and ride summaries. Raw GPS tracks come later, with privacy zones and explicit rider control.
Sync model
Optional cloud, local-first apps.
Build 3 previews the sync controls without turning cloud into a requirement. A rider can use TrailFu as a local riding tool first and enable backup later.
Garage
Ready for future syncBikes, components, mileage, setup notes, reminders.
Ride summaries
Contract draftedDistance, elevation, trail names, Ride Truth summary.
Route plans
Portal previewSaved route intents, confidence, gaps, send-to-phone handoff.
Raw tracks
Protected laterNot uploaded by default. Privacy zones first.
Diagnostics
Explicit exportOnly visible or shared when the rider chooses.
Conflict resolution favors newest explicit edit, not silent overwrite.
Every sync event should be inspectable when troubleshooting.
Mobile apps remain the source of on-trail truth.