HealthBridge for Unity
HealthBridge for Unity presents Apple HealthKit and Android Health Connect through one C# API. Follow the learning path for a first read, then move to the guide for the feature you are building.
Getting startedImport the Asset Store package, initialize on each platform, and read typed step samples.
Understand the modelLearn how the service, providers, capabilities, permissions, and mocks fit together.
Build a featureRead health data, import workouts, monitor heart rate, use routes, and write owned records.
Prepare mobile platformsConfigure HealthKit or Health Connect and validate on physical devices.
Look up the APIFind public services, events, models, units, result contracts, and recovery behavior.
TroubleshootDiagnose imports, initialization, permissions, empty results, and device validation.
Choose a first task
Section titled “Choose a first task”- New integration: start with Unity onboarding.
- Existing integration: go directly to workouts, health data, or UI Toolkit integration.
- Preparing a release: review permissions and capabilities and physical-device validation.
Requirements and boundaries
Section titled “Requirements and boundaries”- Unity 6.
- A physical iOS device for real HealthKit evidence.
- An Android device with Health Connect for real Android evidence.
- A product explanation and consent flow for every requested health type.
The base SDK does not promise continuous live heart rate. Health platforms and connected devices may synchronize samples after recording, so active-workout UI must tolerate delayed or empty results.