HealthKit, WorkoutKit, and health-data design
Health data changes the domain model. A quantity needs its type, unit, time interval, source, device, and provenance. A bare number is not enough.
Design the capability
- Request read and write types separately and only for a visible feature. Authorization outcomes do not reveal more than the framework permits.
- Normalize units at the domain boundary while retaining original source metadata needed for interpretation.
- Use anchored or observer queries according to the product and tolerate delayed background delivery.
- Treat denial as normal, minimize retention, avoid casual export, and make deletion and account behavior explicit.
Validation boundary
No HealthKit store, health data, workout session, background delivery, entitlement, review, or physical-device evidence was produced.
Series navigation
- Previous: Part 104: Core Bluetooth, nearby interaction, accessories, and connectivity
- Next: Part 106: Core ML, Vision, Natural Language, and on-device intelligence
- Series index: Zero to iOS Hero