I bought a screenless wearable because I wanted less technology to manage. Four hours later I was mapping the relationships between six health platforms.
Garmin announced CIRQA on July 21, its first screen-free health and fitness band, with no subscription required. I ordered one immediately. Less than a month later it showed up at my door, I put it on, and within four hours I had stopped thinking about the sensor on my wrist and started thinking about data architecture.
That shift is what this post is about. Not the band. The thing the band exposed.
Why I switched at all
I've worn WHOOP for more than three years, which should make me hard to pry away. Three years is a lot of accumulated context about a body: sleep, HRV, resting heart rate, workouts, stressful stretches, illness, recovery, travel, good training blocks, and all the unremarkable days that establish what "normal" actually looks like.
WHOOP also got the form factor right, and I want to be clear about that, because it's the part CIRQA didn't have to invent. I don't want a smartwatch. My left wrist is reserved for an actual watch. I like watches, and I have no interest in replacing one with a second screen that also happens to tell time. What I've wanted is something quiet on my right wrist that measures what I care about and otherwise leaves me alone. WHOOP has been exactly that for three years.
What CIRQA changed is the terms. WHOOP's value lives behind a recurring subscription, which means the meter never stops running on data collected from my own body. CIRQA offers the same screenless, stay-out-of-my-way experience without one, and it comes attached to an ecosystem that has spent years on a question I increasingly care about: not just how recovered I am, but what all of this training is actually doing.
I do a little bit of everything. Swim, run, bike, lift, plus a few sports where "play" is generous. Most of it is really an excuse to be outside. So I put the band on.
Apparently my body has several databases
My health data doesn't come from one device, because no single device is best at everything I care about.
WHOOP has years of physiological history. Apple Health holds another layer. My scale reports through Fitdays. I use Strava. For swimming, I use FORM goggles.
None of that is exotic. I picked different products because they solve different problems well, and FORM is the clearest case. For running or biking, CIRQA leaning on my phone for GPS is a tradeoff I can live with. In a pool, that arrangement falls apart. I'm not carrying my phone to the wall, and without it a screenless band can't tell me how far I actually swam. FORM can. The goggles are built around being in the water, they count laps and distance more accurately than a wrist sensor guessing at turns, and they put the numbers in front of my eyes instead of asking me to stop and check something.
I don't want Garmin to build better swimming goggles. I want FORM to be great at swimming and Garmin to be great at understanding training. That's a reasonable division of labor.
The software disagrees. FORM can send my swims to Strava and to Apple Health. Garmin activities can flow into FORM in supported scenarios. But a pool swim recorded by FORM cannot flow into Garmin Connect.
So the workout exists. It was captured by the device best suited to capture it, more accurately than Garmin would have managed on its own, and I can share it with other services. Garmin just won't accept it.
Then I got to Apple Health.
The one-way door
WHOOP wasn't perfect, but it made a design choice I didn't fully appreciate until I started leaving: it was willing to listen to other systems.
My scale already knows my weight, and Fitdays can send it into Apple Health. Apple Health holds other things I've deliberately chosen to keep there, including menstrual-cycle data I have exactly zero interest in maintaining by hand in a second app simply because I changed the sensor on my wrist. That is years of information, it is already accurate, and it is sitting on my phone right now.
WHOOP could read from Apple Health, so some of those decisions carried forward. I didn't have to reintroduce myself every time another product learned something about me.
Garmin Connect can push supported information into Apple Health. It does not pull health data back in.
That asymmetry is a choice rather than a limitation, and it's worth being precise about why. HealthKit already tags every sample with the app or device that recorded it. The provenance Garmin would need in order to decide what it trusts is attached to the data by default. The plumbing exists. Garmin has connected one end of it.
Which means the question isn't technical. Garmin wants information another system already has about me. I've already recorded it. I'm willing to grant permission. But Garmin won't ask that system. It asks me.
Why a reasonable company builds it this way
I want to be fair here, because there are real arguments for the one-way door, and a post that ignores them is just a complaint.
Garmin's models assume a known sensor pipeline. If a metric is calibrated on data collected by Garmin hardware at a known cadence, feeding it a weight typed in six weeks ago or a swim from an unfamiliar device can quietly degrade the output, and the customer will blame Garmin rather than the source. Read access to health data is also genuinely heavier than write access. Asking permission to see someone's health record is a larger request, with larger consequences if handled badly, than asking to add to it. And there's the commercial reality. Ecosystem gravity is an asset. Every product company would rather be the system of record than a node in someone else's graph.
Those arguments are legitimate. They just don't justify the outcome, because they all point to the same solution, and it's one modern systems already know how to build.
There is a large gap between "we didn't measure this ourselves" and "we know nothing about it." Health platforms keep treating those as the same state.
A measurement can be first-party, imported from a trusted source, manually entered, stale, incomplete, or unsuitable for one specific model while being perfectly fine for another. Garmin shouldn't blindly accept every number in Apple Health, and I wouldn't want it to. A weight from a connected scale is different from one I typed. A swim recorded by FORM is different from an activity I added after the fact. Where it came from matters, when it was captured matters, and Garmin should absolutely decide which inputs are good enough for which calculations.
That's a far more interesting product problem than opening every API. It's also the version of the argument that's hard to dismiss, because refusing my FORM swim isn't declining a nice-to-have. It's discarding a better measurement than the one Garmin would have produced itself.
My body doesn't know which company owns the row
This became the sentence I kept returning to while setting everything up.
My body does not know that my swim belongs to FORM, my weight belongs to Fitdays, my cycle belongs to Apple Health, and my recovery history belongs to WHOOP. Those are company boundaries. My body has no such architecture.
When I choose a product to measure part of my life, I've already made a trust decision. Buying a Garmin doesn't revoke those decisions and appoint Garmin the exclusive authority over my health. Yet a lot of health technology is designed as though trust works exactly that way: choose our ecosystem, then reconstruct yourself inside it. People don't behave like that. We trust different systems with different things, and the boundaries matter. I don't hand someone every key I own because I once asked them to water my plants.
So the useful question isn't "will you enter your weight." It's this: what sources do you already trust, and what are you comfortable letting us use?
If Fitdays is where my weight comes from, let me say that. If FORM is my source for swimming, take the workout, keep its origin attached, and decide which parts of the Garmin experience can use it. If Apple Health already holds years of cycle data, ask whether Garmin can read it rather than asking me to retype it. Keep those permissions narrow, so that access to my weight doesn't mean access to every health field on the device, and let me change my mind later.
The alternative is what I actually spent my first evening doing: FORM talking to one service, Garmin publishing to another, Apple Health receiving information Garmin won't read back, and scale data already sitting on my phone somehow becoming my responsibility to move around. I work in product and technology, so I can figure it out. That's not the compliment it sounds like.
The customer should not be the middleware.
Switching customers aren't blank slates
This is where I think CIRQA represents a larger opportunity for Garmin than "build a WHOOP competitor."
Someone buying their first fitness tracker may genuinely be starting from scratch. Someone leaving WHOOP after three years is not. I'm new to Garmin. I am not new to tracking my health, and that distinction should change the entire onboarding experience.
The health-data conversation has spent years on ownership and portability. Can I download my data? Can I get a CSV? Of course I should be able to. But a ZIP file containing three years of my body is not the experience I'm asking for.
Portability lets me leave with my data. Interoperability lets me arrive somewhere new without starting over. The more interesting version is letting some of the trust decisions travel with me too. Not adopting another product's conclusions, just recognizing that I've chosen it as a source for a specific part of my life.
That distinction matters commercially, not only experientially. Ecosystem friction looks like a moat when you're defending an installed base. It looks very different when you're trying to acquire someone else's customer. CIRQA puts Garmin in front of people with years invested in WHOOP, Oura, Fitbit, Apple Health, or some combination of them, and making those people abandon their accumulated context creates friction at precisely the moment the switch should feel easy. In that world, interoperability isn't plumbing. It's acquisition, onboarding, and eventually retention.
Compete on interpretation, not possession
There's an important boundary here, because Garmin's models are not WHOOP's models, and I don't want them flattened into the same thing. Different measurements, different standards for what counts as reliable, different conclusions. That's exactly where I want these companies to compete.
Take the same human being and tell me something the other system missed. Show me a relationship in the data I hadn't noticed. Help me understand why yesterday's session hit harder than expected, or whether I'm actually ready to push today.
There is enormous room for differentiation in what a company does with health data. There is very little in pretending data collected elsewhere doesn't exist.
If a particular Garmin metric requires measurements captured directly by CIRQA, tell me that. If a FORM swim can appear in my training history but can't feed a specific calculation, that's a reasonable constraint, clearly explained. If a weight came from Fitdays by way of Apple Health, keep the provenance attached and let the model decide what to do with it.
What's hard to justify is acting as though the swim never happened because Garmin wasn't standing there when it did.
I'm also not arguing for one giant universal health database where everything reads everything. Good interoperability still has boundaries. It preserves source, respects the permissions granted to each product, and leaves me in control of how far those relationships extend. The better system isn't one where every product knows everything. It's one where I don't have to keep telling each of them the same thing.
Four hours in
None of this is a review. I've worn the band for a matter of hours. I don't yet know whether I'll prefer Garmin's read on my training to WHOOP's, whether it will understand my sleep as well, or whether the switch will prove worth it at all.
What I know is that the hardware has delivered the thing that made me buy it. CIRQA sits quietly on my right wrist while an actual watch stays on my left, no second screen competing for my attention, no meter running in the background.
The next generation of health products will keep getting better sensors and better models. But most of us are already surrounded by devices that each know a different piece of us, and the harder, more valuable product problem is figuring out how those pieces come together without requiring a human being to manage every connection.
Garmin could earn a much larger role in my health ecosystem by being more useful than the alternatives, not by requiring itself to be the source of every measurement. That's a very different kind of loyalty. Trust earned through usefulness is harder for a competitor to displace than loyalty created by making switching painful. CIRQA has earned its place on my wrist so far; whether Garmin earns a larger place in the rest of my ecosystem is the part I'm now much more interested in watching.
