CoMaps Adds Navigation Provider Support in Gadgetbridge 0.93.0 and OpenVitals via Health Connect

CoMaps implemented external navigation hooks that expose route and guidance data only after users grant dedicated permissions in Settings > External Integrations. Gadgetbridge v0.93.0 reads these feeds to push directions to InfiniTime watches; OpenVitals pulls the same stream through Android Health Connect to layer live routes over activity metrics. Both integrations default to off and require manual enablement, preserving CoMaps' stated privacy boundary.

The changes mirror patterns seen in other FLOSS stacks where narrow, permission-scoped IPC replaces vendor silos. Primary source documentation on Codeberg lists the exact intent strings and required grants, while Gadgetbridge release notes confirm the navigation provider API addition. This reduces context-switching friction for users who already run fully open toolchains, analogous to how seamless data exchange in code editors and build systems lifts developer throughput without telemetry leakage.

Operationally, the integrations lower the barrier for daily navigation tasks inside constrained environments such as smartwatches or health dashboards. Because CoMaps remains the sole data source and never initiates outbound connections itself, the attack surface stays limited to the explicit permission surface. Early adoption will likely concentrate among existing Gadgetbridge and PineTime users who already reject proprietary companion apps.

Next steps include expanded Codeberg documentation for third-party widgets and potential additional consumers of the same navigation intent. No timeline or volume targets appear in the announcement.