Adding a Device

Adding a new wearable to AnyBio is a managed process - we handle the per-device protocol work so your application code stays at the biosignal layer.

When a custom integration makes sense

If your project depends on a wearable that isn't yet on the supported list, consider whether one of these paths fits first:

• Standard profiles. If the device implements Bluetooth SIG Heart Rate or another public profile, the platform may already work without any custom work.
• Substituting hardware. Many studies and applications can use any device of a given category (e.g., any ECG chest patch, any CGM). If your use case isn't tied to one specific model, a supported alternative may be a faster path.
• Cloud-to-cloud. For devices that don't stream over BLE but expose a vendor API (most CGMs, activity aggregators), the integration is cloud-to-cloud rather than via the BioSDK.

When none of those fit - the device is essential, has proprietary protocols, and isn't currently supported - reach out about a custom integration.

What we need from you

To scope a new integration, the following information helps us move quickly:

• Device specification. Manufacturer, model, firmware version range. The vendor's BLE protocol document if you have one.
• Signals. Which biosignals the device emits, expected sample rates, units, and any known quality artifacts.
• Use case. Whether this is a one-off study, a long-term partnership, or a deployment target. Affects integration depth and timeline.
• Sample data, if available. A few minutes of representative output (BLE captures, exported recordings) accelerates validation.

Contact us and we'll scope the work.

What we deliver

A supported integration includes:

• A device-specific decoder running inside the platform that translates the wearable's native format into the AnyBio biosignal catalog.
• Validation against the platform's standard quality framework (range checks, quality mask propagation).
• DSP wiring for any waveform signals the device produces (HR/HRV from ECG, HR/PRV from PPG, etc.).
• BioSDK support so applications can discover and connect to the device through the same scan-and-connect flow as any other supported wearable.
• A consistent biosignal API surface for your application: no new endpoints, no new code paths, just additional sources for the biosignals you already consume.

Versioning and maintenance

Once an integration is live, the platform tracks the device's firmware versions and applies decoder updates as the vendor releases changes. Your application doesn't need to coordinate with firmware updates - the integration layer handles compatibility.

For partnerships involving multiple device models or a long-running roadmap, we offer dedicated support and faster integration timelines for new models in the same family. Reach out for details.