Reusable flows
Higher-level pairing, manual-entry, and health-access UI components
- Stable unknown
- Release candidate since 1.16.1-rc.3
- Development since 1.16.1-dev.2111+9796905
These higher-level components from @ovok/native/ui package common interaction
patterns while leaving product policy and persistence to the host app.
| Component | SDK handles | App provides |
|---|---|---|
PairingFlow | Discovered-device list, pairing state, pairing-code input, and persistence of bonded device IDs | BTProvider, async paired-device storage, code confirmation when required; custom rows to expose forget |
ManualEntryForm | Measurement-catalog fields, numeric validation, and save-pending UI | Async persistence callback, patient mapping, and product labels |
HealthImportCard | Adapter status display, access-request action, and optional sync progress | HealthImportAdapter, health permission policy, and the import service |
The components can be adopted independently. For setup and end-to-end examples, see
Reusable flows. For every @ovok/native/ui export,
theme behavior, and slots, see App UI components.
Last updated on