Connect a wearable in a couple of taps.
The challenge
Customers used many different wearables and fitness apps, and their data needed to arrive reliably, without exposing API keys or double-counting events.
Our approach
We built a web app that connects devices through an aggregator, keeps secrets server-side and processes webhooks idempotently.
Everyday impact
Users see all their fitness data in one place without typing anything in.
What we built
Customers connect wearables and fitness apps through an aggregator’s link widget.
API keys never reach the browser, and secrets are stored in a vault.
An event log makes sure each data event is processed exactly once.
Customers choose which device is the source for each metric.
Workout and metric charts, plus a demo mode for showing the experience.
How it works
A customer links a device in a couple of taps.
Data arrives from the aggregator through webhooks.
Each event is logged once and mapped to the preferred source.
Charts update with the customer’s latest data.
More work
Start a conversation
Tell us what you’re trying to build. We’ll talk through how we’d approach it and what a sensible first step looks like.
