Integrations
READYPLAY treats wellness data as context for how you actually play — recovery, strain, resting heart rate, and effort. We never see raw sensor streams. Each platform shares only daily summaries, and you can disconnect any of them at any time from Settings → Connected Apps.
Anything you install from the App Store right now ships with these.
iOS — read access
With your permission, READYPLAY reads heart rate, resting heart rate, height, weight, and date of birth to pre-fill your player profile and calibrate effort tracking. Workouts get written from Apple Watch (not from your phone) when you record an on-the-record game.
watchOS — live workout, scoreboard
Score from your wrist while a game runs. The watch records an HKWorkoutSession during on-the-record games so heart rate and active energy land in your Fitness rings. Live Activities mirror the score on the iPhone Lock Screen.
Code is shipped — we're either awaiting partner review or finishing the in-app surface.
OAuth — recovery, strain, daily summary
Server-side OAuth proxy is shipped. We're awaiting Whoop developer-program review before the Connect button goes live. Once enabled, daily recovery and strain feed the Fitness component of your player score. We never see raw sensor streams — just the daily summary.
Committed work, not yet started. Order is a function of audience overlap and how cleanly each API maps to a daily summary.
Once an Android client ships
On Android, Health Connect is the unified gateway to most wearable platforms. Supporting it once natively brings in Amazfit / Zepp, Samsung Health, Polar, Coros, and Garmin (via Connect Sync) — without a separate OAuth dance per vendor.
OAuth — activity, recovery, training load
Direct iOS path for users who already live in Garmin Connect. Scoped to post-game summary + daily readiness — same shape as the Whoop integration, different vendor.
OAuth — readiness, sleep, HRV
Sleep and readiness are the strongest predictors of next-day on-court effort. Oura's Cloud API has the cleanest shape of the rings ecosystem, so it earns a slot.
OAuth — heart rate, activity
Post-Google Fitbit API support, gated behind partner approval. Lower priority than the rings (Whoop, Oura) for the audience overlap, but we'll add it when we hit critical mass on Android.
If your wearable already syncs into Apple Health on iOS, the HealthKit integration above already covers it for the basics (heart rate baselines, body metrics). Brand-specific surfaces (Whoop's recovery score, Oura's readiness, Garmin's training status) need direct integrations — those are what the roadmap list is about.
On Android, most things route through Health Connect, which is on the roadmap above. Amazfit / Zepp, Samsung Health, Polar, and Coros all funnel through there — one integration on our side, every major Android-friendly wearable on yours.
Want a specific platform prioritized? Join the waitlist and tell us in the notes — every request gets read.
Join the run · Early access
Four fields. TestFlight invite hits your inbox the moment you submit. We'll ask for sport, park, and the rest after you're in.