Unity onboarding
Use this path when adding HealthBridge to a Unity project for the first time. Each step produces one concrete checkpoint before the next adds complexity.
1. Import the SDK
Section titled “1. Import the SDK”Install the Asset Store package
and confirm that Unity finishes dependency resolution and script compilation.
The imported package includes the Health Data Review sample under
Assets/HealthBridge/Samples/.
2. Initialize for the target platform
Section titled “2. Initialize for the target platform”Set up initialization.
Use AutoInitializeAsync in the Editor and on iOS. Android player builds
require a configured HealthBridgeInitializer component in the first scene.
3. Complete a typed read
Section titled “3. Complete a typed read”Read your first step samples.
Verify HealthDataReadResult.Success, then work with StepSample values
instead of assuming every generic sample has the same shape.
4. Understand permission outcomes
Section titled “4. Understand permission outcomes”Read permissions and capabilities before adding more types. A successful core initialization does not mean every optional capability or requested record type is available.
5. Build the product feature
Section titled “5. Build the product feature”Choose the guide closest to the feature:
- Import workouts
- Read generic health data
- Monitor deferred heart rate
- Read workout routes
- Write and delete owned records
- Connect the SDK to UI Toolkit
6. Replace mock confidence with device evidence
Section titled “6. Replace mock confidence with device evidence”The Editor proves integration logic, not native access. Configure HealthKit or Health Connect and complete the physical-device validation checklist before treating the feature as release-ready.
