Onboarding And Permissions
Status: Current implemented behavior. Audience: Users and contributors. Implementation:
features/onboarding,healthconnect,features/settings. Navigation:Screen.Onboarding,Screen.SettingsPermissions,Screen.SettingsHealthConnect. Related: Feature map, Permissions, Health Connect.
Onboarding prepares OpenVitals for local Health Connect use without requiring an account or cloud sync.
For the exact permission reference, see Permissions. For platform behavior, see Health Connect.
First Run
Onboarding introduces the app, checks Health Connect availability, and helps the user grant useful permission groups.
OpenVitals can continue with limited data when some permissions are skipped. Missing permissions are surfaced later on the dashboard, detail screens, settings, imports, and entry flows where they matter.
Health Connect Availability
OpenVitals handles Health Connect states explicitly:
- Available and ready.
- Available but missing permissions.
- Not installed or not reachable on supported devices.
- Unsupported Android or device environments.
When Health Connect is not available, the app explains the limitation instead of showing misleading health values.
Read And Write Permissions
Read permissions are used for dashboard widgets, metric detail screens, readiness views, statistics, achievements, and local insights.
Write permissions are requested lazily for explicit write flows such as manual entry, route import, Apple Health import, activity recording, edits, and deletes.
The dashboard remains read-only even when write permissions are granted.
Optional Areas
Some permission groups, such as cycle data or sensor-related permissions, are shown only when they are relevant and requestable on the device.
Body Energy calibration can be collected during onboarding and adjusted later in settings.
Privacy Expectations
OpenVitals stores app preferences locally and reads or writes health records through Health Connect. It does not require an OpenVitals account.