Current limitations
Known limitations before public release.
These notes keep support guidance honest while connected services, mapping, and hardware coverage continue to expand.
Android maps need production key setup
The Android app requires a real Google Maps API key supplied outside source control before production runtime testing.
Turn prompts follow route shape
Route prompts are inferred from imported route geometry and do not yet include street names or full rerouting.
Road-ahead previews stay conservative
Route-free terrain is now live, but the current heading-corridor provider is still more cautious than route-based climb detection and is not yet a full road-network-aware branch resolver.
Alert timing uses ride-safe defaults
Climb alerts focus on clear defaults today; custom sound packs and detailed timing controls are not available yet.
Sensor compatibility is still growing
Android and iPhone BLE paths are now live for heart rate, cadence, speed, and power categories, and compatibility guidance will expand as more hardware is validated.
Production rollout work still remains
Portal login, consent, telemetry, and dashboards are live locally, but hosted beta rollout still needs production secret handling, sender infrastructure, support workflow, and deployment runbooks.