PulseTrail watch UI, complications, widgets, and Live Activities
PulseTrail is an offline-aware outdoor fitness product split between iPhone and Apple Watch. Its system surfaces are projections of one durable session, not competing sources of truth.
Product decision
Which facts deserve a wrist, lock-screen, widget, or full-phone surface?
The smallest useful vertical slice is concrete: Show a small set of live metrics and pause or resume controls, then project the same session summary into glanceable system surfaces.
Boundaries that keep the design honest
- Keep the active workout authoritative on one device and make cross-device operations replayable and idempotent.
- Budget sampling, rendering, storage, and transfer from user value and measured energy cost.
- Preserve raw provenance and gaps while presenting clear derived summaries.
- Require physical-device and outdoor evidence for sensor, background, battery, and field-recovery claims.
- Avoid this failure: Putting dense charts on a moving wrist or making safety-relevant actions depend on precise taps.
Release evidence
No PulseTrail application, watch app, complication, widget, Live Activity, HealthKit session, background transfer, energy profile, or physical outdoor journey was executed.
This chapter records product and architecture decisions. Apple framework behavior still requires the matching Xcode target, configured service or account where applicable, and named Simulator or physical-device evidence. The browser Swift runner does not validate these Apple SDK surfaces.
Series navigation
- Previous: Part 119: PulseTrail HealthKit, WorkoutKit, maps, and location
- Next: Part 121: PulseTrail offline, battery, sync, and failure recovery
- Series index: Zero to iOS Hero