An Apple Watch can make shared walking progress easier to glance at, but the most important wrist feature is often the shortest path to reducing location access. A useful companion app should keep the current sharing state and Pause or Stop controls reachable.
Where the step total comes from
StrideSafe reads Apple Health and iPhone motion data on the iPhone. It syncs one privacy-safe daily total to the authenticated backend. The Watch does not carry a HealthKit entitlement and does not upload raw Health samples.
This means the Watch displays the latest summary that StrideSafe has synced; it is not a separate second step source that gets added to the phone total. The selected daily source remains Apple Health with an iPhone fallback or this iPhone only.
What the Watch can show
The companion experience includes daily progress, current streak, current sharing state, and recent supported encouragement. It can also present current commute status without turning the Watch into a route-history viewer.
A complication-ready snapshot model exists, but a user-visible WidgetKit complication target is not part of the current release. Marketing should not promise a watch-face complication until that target is implemented and tested.
What the Watch can control
The wearer can start a basic journey, choose a supported sharing level, pause, stop, mark arrival, and end. These controls are designed to stay glanceable and immediately reachable rather than hidden behind a long settings flow.
StrideSafe supports direct Supabase commands and approved latest-location updates over Watch networking, with WatchConnectivity as an opportunistic fallback. Automatic account handoff can occur when the signed-in iPhone and Watch are simultaneously reachable; native Apple or email sign-in is also available on the Watch.
Understand the independence limits
“Works on Apple Watch” does not mean guaranteed delivery in every condition. The Watch must be launched and confirm the approved state while in use before a visible background location session can continue. watchOS does not silently relaunch a terminated Watch app for location. Low Power Mode, network coverage, GPS quality, and system resource limits can reduce frequency.
The repository includes structural support for direct Wi-Fi or LTE operation, but final physical LTE and production-notification behaviour still requires end-to-end release testing. The website therefore describes the companion controls without making a guaranteed away-from-phone claim.
Keep consent consistent across devices
Adding a second device must not create a second privacy rule. Pairing, steps, commute sharing, and separately approved continuous sharing remain server-authoritative. Stopping on either device must reduce access for the paired person, and delayed older messages must not restore a more permissive state.
When both devices can publish continuous location, the backend temporarily prefers fresh Watch captures and lets the iPhone resume if the Watch has not delivered for two minutes. That prevents a left-behind phone from repeatedly replacing a current Watch location while preserving failback.
Questions about this topic
Does StrideSafe read Health data directly on Apple Watch?
No. The iPhone reads the selected daily source and syncs a privacy-safe summary. Raw Health samples are not sent to the Watch backend flow.
Can I stop sharing from Apple Watch?
Yes. Pause, Stop, arrival and journey-end controls are available from the Watch companion.
Is there a StrideSafe complication?
Not yet. A complication-ready data model exists, but no user-visible WidgetKit complication target is implemented.
