Wearables & the watch
Bluetooth bands, phone health hubs, and AverCare's own watch apps.
AverCare pulls vitals from four kinds of sources, then makes them all look the same to the rest of the app. Here's how each one works.
The four sources
Phone health hubs
Apple Health (iOS) and Health Connect (Android) are shared vaults other apps write to. AverCare reads the categories you approve and watches for changes in the background.
The JCVital band
A Bluetooth ECG smart band AverCare talks to directly over a custom protocol for live and historical readings.
AverWatch (Apple)
A native watchOS app that gathers vitals and relays them through your phone.
AverWatch (Wear OS)
The Android counterpart, built natively for Wear OS.
Speaking the band's language
The JCVital band doesn't expose a friendly SDK — it speaks a low-level Bluetooth protocol. AverCare implements that protocol directly: connecting, subscribing to the right channels, sending the right command bytes, and parsing the readings that come back. It even recovers gracefully when Bluetooth briefly drops, which it inevitably does.
Reverse-engineered, carefully
The exact commands the band understands were determined by studying how the manufacturer's own app talks to it. Small details matter enormously here — the right value in the wrong field gets you nonsense or silence.
The phone ↔ watch bridge
Watches don't talk to the internet the way phones do, so AverWatch communicates through your phone using each platform's official channel (WatchConnectivity on Apple, the Data/Message clients on Wear OS). Both sides exchange messages in a shared, versioned envelope format so the phone and watch always agree on what a message means.
One shape to rule them all
Each source reports data differently — different units, different field names, different sampling. A normalization layer converts everything into one shared schema before it's stored. After that point, nothing downstream needs to know or care where a reading came from: a heart rate is a heart rate, whether it came from an Apple Watch, the band, or AverWatch.
This is the same idea as the architecture page's "shared types" — define the shape once, and the whole system stays honest about it.