72 lines
1.6 KiB
Markdown
72 lines
1.6 KiB
Markdown
# MVP Scope
|
|
|
|
## MVP goal
|
|
|
|
Deliver a planner that is useful before the ride and minimally useful during the ride.
|
|
|
|
## MVP features
|
|
|
|
### Must have
|
|
|
|
1. Trip request form.
|
|
2. Routing adapter using a configurable provider.
|
|
3. Bikepacking route scoring summary.
|
|
4. Stage planner.
|
|
5. Route-corridor POIs for water, food, sleep, and bike repair.
|
|
6. Critical-gap warnings.
|
|
7. GPX export.
|
|
8. Offline-pack manifest and cached trip data.
|
|
9. Text-based local rule cards.
|
|
10. Structured report submission.
|
|
|
|
### Should have
|
|
|
|
1. Map layer toggles.
|
|
2. Surface/elevation/stage chart.
|
|
3. Bailout POI detection.
|
|
4. Weather overlay and wind/rain warnings.
|
|
5. TCX export.
|
|
6. Deep links to accommodation/search platforms.
|
|
|
|
### Could have
|
|
|
|
1. FIT export.
|
|
2. Garmin Courses API integration.
|
|
3. Wahoo integration.
|
|
4. In-app booking.
|
|
5. AI route explanation.
|
|
6. Trusted-local reputation system.
|
|
|
|
### Not in MVP
|
|
|
|
1. Full global offline routing.
|
|
2. Real-time social feed.
|
|
3. Payments marketplace.
|
|
4. Full legal advice engine.
|
|
5. 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.
|