How MoveTogether connects every wearable through one integration

Competitions only work if every device reports in

MoveTogether is a social fitness app for iPhone, with an Apple Watch companion app. Users join competitions, leagues, and group challenges with people they know, and an AI coach nudges them along based on real activity, not manual logging.

None of that works unless activity data flows in reliably, no matter what device someone wears. Supporting a wide range of wearables was a day-one requirement, not a future roadmap item.

Building and maintaining a separate OAuth flow and data model for every vendor would have been a heavy, never-ending tax on a small, independent team. Each provider runs its own authentication, its own data shape, and its own quirks, and those quirks change over time.

One connection model, one normalized data shape

Open Wearables is MoveTogether's entire third-party wearable layer. Rather than integrate each vendor directly, MoveTogether connects everything through Open Wearables.

Through Open Wearables, MoveTogether users connect Fitbit, Garmin, WHOOP, Oura, Strava, and Polar. Apple Health is supported separately through HealthKit, alongside the Open Wearables layer.

The integration runs entirely server-to-server. When a user connects a device, Open Wearables handles the OAuth handshake and token storage directly, without routing through MoveTogether's own backend. MoveTogether reads back normalized daily activity and sleep summaries, refreshed on a schedule and on demand. Steps, active calories, exercise minutes, workouts, and sleep feed directly into competition scoring, leaderboards, streaks, and the AI coach's messages.

Every device treated equally

A WHOOP user and an Oura user land in the same normalized schema. The scoring engine does not care which device someone wears, so competitions and leagues stay fair across a mixed-device community: the same workout produces the same signal, regardless of the wristband it came from.

Credentials stay out of MoveTogether's servers

Wearable credentials never touch MoveTogether's infrastructure. They stay with Open Wearables, which handles the OAuth handshake and token storage on MoveTogether's behalf. That separation reduces the compliance surface a small team has to reason about, while keeping the activity data MoveTogether needs flowing in on schedule.

Open Wearables is our entire third-party wearable layer. We connect Fitbit, Garmin, WHOOP, Oura, Strava, and Polar through a single integration, no per-vendor OAuth to maintain, one normalized data shape feeding our whole competition and coaching engine. It let a small team ship a broad device lineup and keep it current.

Sam Pullen, Founder, MoveTogether

Built to absorb a shifting provider landscape

Wearable provider APIs change over time, including shifts like the Fitbit Web API's transition to the Google Health API. Each change would otherwise land as unplanned rebuild work for MoveTogether's app. Open Wearables absorbs that churn at the platform level, so MoveTogether keeps its existing users connected and can pick up new devices without a rebuild on the app side.

What shipped

MoveTogether shipped a broad device lineup, Fitbit, Garmin, WHOOP, Oura, Strava, and Polar, without building or maintaining per-vendor OAuth flows and data pipelines. Every connected device feeds the same normalized schema, so competition scoring, leaderboards, streaks, and the AI coach all work identically regardless of what a given user wears. A small, independent team shipped and maintains that entire device lineup through a single integration.