Unity mobile platform setup
Platform setup turns a working Editor integration into a native health-data integration. Choose the target, then finish with provenance-aware device tests.
Apple HealthKit
Section titled “Apple HealthKit”Follow iOS and HealthKit setup to configure the App ID, entitlement, provisioning, usage descriptions, settings, and physical-device authorization flow.
Remember that HealthKit does not reveal every per-type read decision. A denied read can look like an empty successful result, so the UI must not infer that no health records exist.
Android Health Connect
Section titled “Android Health Connect”Follow Android and Health Connect setup to configure the first-scene initializer, manifest permissions, permission resolution, and device prerequisites.
The current Android provider requires READ_EXERCISE and READ_HEART_RATE for
core initialization. Treat other selected types and write permissions as
feature-level outcomes.
Prove the native path
Section titled “Prove the native path”Finish with physical-device validation. Record the app build, package version, OS/device, source health app or device, requested types, observed grants, and redacted result status. Editor mock data is not device evidence.