Mirrored from /mnt/DATA/git/pikebacker/docs/02_mvp_scope.md.
Origin: repository.
Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
MVP Scope
MVP goal
Deliver a planner that is useful before the ride and minimally useful during the ride.
MVP features
Must have
- Trip request form.
- Routing adapter using a configurable provider.
- Bikepacking route scoring summary.
- Stage planner.
- Route-corridor POIs for water, food, sleep, and bike repair.
- Critical-gap warnings.
- GPX export.
- Offline-pack manifest and cached trip data.
- Text-based local rule cards.
- Structured report submission.
Should have
- Map layer toggles.
- Surface/elevation/stage chart.
- Bailout POI detection.
- Weather overlay and wind/rain warnings.
- TCX export.
- Deep links to accommodation/search platforms.
Could have
- FIT export.
- Garmin Courses API integration.
- Wahoo integration.
- In-app booking.
- AI route explanation.
- Trusted-local reputation system.
Not in MVP
- Full global offline routing.
- Real-time social feed.
- Payments marketplace.
- Full legal advice engine.
- Fully automated OSM editing.
MVP success criteria
A test user can plan a 5-day gravel bikepacking route and identify:
- daily endpoints,
- longest water gap,
- last shop before remote section,
- sleep options each night,
- bike repair options,
- uncertain access segments,
- bailout points,
- exported GPX.
Target regions for MVP validation
Pick one or two data-rich regions first, for example:
- Germany/Austria/Switzerland,
- Netherlands/Belgium/Germany,
- UK,
- Pacific Northwest,
- Colorado/Utah.
Data quality varies heavily by region. Start where OSM and POI data are strong and bikepacking demand exists.