Testing Wear OS fitness apps without breaking a sweat
summary
Summary of concrete testing steps and caveats for Wear OS fitness apps: use the Android Studio Device Manager emulator to inject emulator heart-rate sensor only events and check UI across screen shapes; use Health Services synthetic mode (enable synthetic providers, tell it which exercise to simulate, revert when done) to generate multi-sensor exercise data; connect via ADB over Wi‑Fi (hotspot if network isolates clients); guard against device differences by using a set intersection check to request only supported data types and handle unusual Health Services states.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:21A User Journey
- 0:43What makes testing hard?
- 1:22State Transitions
- 2:03Emulator
- 2:34Synthetic Mode
- 3:08Setting up adb
- 3:40Simulating an Exercise
- 3:57Different Capabilities
- 4:19Checking for Capabilities
- 4:37State Changes
related talks
06mTesting Wear OS fitness apps without breaking a sweat
14mCreating helpful fitness experiences with Health Services and Health Connect
28mCreate beautiful, power-efficient apps for Wear OS
18mFitness motion recognition with Android wear
20mDeep dive into Wear OS app architecture
37mHow I Regained Athlete-Level Code with the Google Fit API
23mCreating Applications for Small Screen, Low Memory Android Wearables
49mBootstrapping Multiplatform Development and Android Wear