621d91e14f
Both are blocked on the mobile-app foundation and on a user base that actually records activities or needs offline peer sync. With 3 users and 0 activities on prod today, these are engineering for a hypothetical population. Move the artifact sets out of openspec/changes/ (so openspec list stays clean) and under docs/ideas/ where self-host-overpass already lives. Each gets a short README documenting: - current parked status - revive triggers (when should we look at this again?) - key constraints not to rediscover (background-GPS privacy review; BLE dev-build requirement; QR-only subset as a cheaper path) Reviving is `git mv docs/ideas/<name> openspec/changes/<name>` and running /opsx:apply, same pattern as self-host-overpass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
22 lines
937 B
Markdown
22 lines
937 B
Markdown
## Why
|
|
|
|
The mobile app (when built) will show routes and allow editing, but won't record activities. Users want to track their rides/hikes with GPS, see live stats, and save recordings as Journal activities. This is a separate feature that depends on the mobile app foundation being in place first.
|
|
|
|
## What Changes
|
|
|
|
- GPS track recording via expo-location (foreground + background)
|
|
- Live stats overlay (distance, duration, speed, elevation gain)
|
|
- Save recorded track as GPX → Journal activity linked to the active route
|
|
- HealthKit (iOS) / Health Connect (Android) export
|
|
- Discard/pause/resume recording flow
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
- `mobile-activity-recording`: GPS recording, live stats, save as activity, health platform export
|
|
|
|
## Impact
|
|
|
|
- Depends on `mobile-app` change being implemented first
|
|
- New dependencies: expo-location, expo-health
|
|
- Background location permissions needed (App Store privacy review)
|