trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
trails/openspec/changes/mobile-app/specs/mobile-route-editor/spec.md
Ullrich Schäfer fff77a2ed2
Add mobile app, map-core, nearby sync, and activity recording specs 
mobile-app: Unified React Native + Expo app combining Planner and
Journal. OAuth2 PKCE auth, MapLibre maps, versioned REST API with
Zod schemas, configurable server URL, offline SQLite, Web Push relay
notifications. TanStack Query + Zustand state management. Jest +
Maestro testing. 76 tasks across 5 phases.

map-core-package: Extract renderer-agnostic map definitions (tiles,
color palettes, POI categories, z-index) into @trails-cool/map-core.
Pure refactor preparing for MapLibre on mobile. 27 tasks.

mobile-activity-recording: GPS recording, live stats, HealthKit/Health
Connect export. Separated from mobile-app for independent scheduling.

mobile-nearby-sync: BLE route sync between nearby devices for offline
group riding. QR waypoint sharing as simpler v1. TXQR noted as future.

journal-rest-api spec: Full API contract — endpoints, auth, pagination,
errors, discovery, versioning, BRouter proxy.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-12 21:52:30 +02:00

2.2 KiB
Raw Blame History

ADDED Requirements

Requirement: Map-based waypoint editing

The system SHALL allow users to add, move, and delete waypoints on a native map view.

Scenario: Add waypoint

  • WHEN the user long-presses on the map
  • THEN a new waypoint is added at that location and the route is recomputed through it

Scenario: Move waypoint

  • WHEN the user drags an existing waypoint marker
  • THEN the waypoint position updates and the route segments connected to it are recomputed

Scenario: Delete waypoint

  • WHEN the user taps a waypoint and confirms deletion
  • THEN the waypoint is removed and the route is recomputed without it

Requirement: Overnight stops and POI snap

The system SHALL support marking waypoints as overnight stops and snapping to nearby POIs.

Scenario: Toggle overnight stop

  • WHEN the user taps a waypoint and toggles "Overnight stop"
  • THEN the waypoint is marked with an overnight icon and day segments update accordingly

Scenario: POI snap suggestion

  • WHEN the user adds a waypoint near a known POI (campsite, shelter, etc.)
  • THEN the system suggests snapping to the POI location and applying its name

Requirement: BRouter routing

The system SHALL compute route segments between waypoints via the BRouter routing engine.

Scenario: Route computation

  • WHEN two or more waypoints exist
  • THEN the system requests a route from BRouter (proxied through the Journal API) and displays the resulting polyline on the map

Scenario: Routing error

  • WHEN BRouter fails to compute a route between waypoints
  • THEN the system shows an error and falls back to displaying a straight line between waypoints

Requirement: Save route to Journal

The system SHALL save edited routes back to the Journal via its API.

Scenario: Save after editing

  • WHEN the user taps "Save" after editing a route
  • THEN the updated GPX is generated from current waypoints and route geometry, and saved to the Journal API as a new version

Scenario: Unsaved changes warning

  • WHEN the user navigates away from the editor with unsaved changes
  • THEN the system prompts the user to save or discard changes