Compatibility
The device classes we test against before a release. This page is generated from the same matrix QA works from, so it cannot drift away from what is actually tested.
iOS
| Device | Target | What we check | Required before release |
|---|---|---|---|
| recent iPhone | one current mainstream model | background GPS, permissions, battery | yes |
| older supported iPhone | one near minimum OS generation | performance and lifecycle | yes |
Android
| Device | Target | What we check | Required before release |
|---|---|---|---|
| Pixel phone | recent model | reference Android behavior | yes |
| Samsung phone | recent Galaxy model | vendor background restrictions | yes |
watchOS
| Device | Target | What we check | Required before release |
|---|---|---|---|
| Apple Watch | recent standard model | workout, HR, sync, compass | yes |
| Apple Watch Ultra | if available | long battery and outdoor display | recommended |
Not available yet: Wear OS. Those devices join this page in the release that ships for them.
Not on this list?
A device class we do not test is not necessarily a device that does not work — it is one we have not verified. Background location and health APIs are where vendors differ most, so an untested phone is most likely to differ in whether recording survives the screen going off.
Separately from which devices are tested, Known limitations covers the behaviour that is the same everywhere and still catches people out — what the watch does without the phone, what happens offline, and what no cloud copy means.