# Reusable flows

Canonical page: https://docs.ovok.com/native-sdk/guide/components/ui/reusable-flows

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`](/native-sdk/guide/components/ui/pairing-flow) | 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`](/native-sdk/guide/components/ui/manual-entry-form) | Measurement-catalog fields, numeric validation, and save-pending UI | Async persistence callback, patient mapping, and product labels |
| [`HealthImportCard`](/native-sdk/guide/components/ui/health-import-card) | 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](/native-sdk/guide/how-to/reusable-flows). For every `@ovok/native/ui` export,
theme behavior, and slots, see [App UI components](/native-sdk/guide/components/ui/).