Workouts, complications, Smart Stack, and watch constraints
Workout and glanceable surfaces are system partnerships. The app declares useful state and eligible work, but the operating system controls presentation, scheduling, and much of the lifecycle.
Design the capability
- A workout session models active, paused, ended, failed, and recovered states and persists important transitions.
- Complications and Smart Stack widgets publish concise timeline entries from shared durable state.
- Avoid polling. Use supported sessions and delivery mechanisms, then tolerate delayed or missing opportunities.
- Health authorization is granular and revocable. Denial remains a normal product state.
Validation boundary
No HealthKit authorization, workout session, background delivery, complication, Smart Stack, or watch hardware evidence was produced.
Series navigation
- Previous: Part 91: watchOS app structure and Watch connectivity
- Next: Part 93: tvOS focus, remote input, shelves, and navigation
- Series index: Zero to iOS Hero