Testing Wear OS fitness apps without breaking a sweat
summary
Testing options include the emulator and Health Services synthetic mode; the emulator only fakes heart rate while synthetic mode simulates multiple sensors and generates realistic, batched sensor streams on demand. Setup requires ADB over Wi‑Fi and enabling synthetic providers, then issuing the simulate command to produce fake exercise data. Apps must query supported data types (use a set intersection when building exercise configs) and handle device variations like missing auto‑pause, different elevation placement, and unusual permission or state transitions to avoid crashes.
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
18mFitness motion recognition with Android wear
28mCreate beautiful, power-efficient apps for Wear OS
23mCreating Applications for Small Screen, Low Memory Android Wearables
43mAndroid Apps Testing in 2019
39mModel Based Testing Shifting Right into the Real World
37mHow I Regained Athlete-Level Code with the Google Fit API