.png)
We’re starting 2026 with a release that focuses on what developers actually care about: fewer integration headaches, clearer guidance, and faster access to reliable health data.
Last week, we rolled out SDK 5.1.0, and while it’s not a flashy redesign for the sake of change, it’s a meaningful step forward. This update is about removing friction from real-world integrations and making it easier for teams to go from “we’re evaluating” to “this is live and working.”
The new version brings three major improvements: a redesigned sample app, new Bluetooth Low Energy (BLE) support for medical devices, and real-time heart rate measurements processed directly on the device. Together, these updates reflect months of careful engineering, testing, and iteration based on real developer feedback and real product needs.
Let’s break down what’s new and why it matters.
One of the most common pain points we hear from developers isn’t missing features, it’s uncertainty during setup. Even with good documentation, small integration mistakes can lead to broken data flows, unexpected behavior, or wasted debugging time.
That’s why SDK 5.1.0 introduces a completely redesigned sample app.
This isn’t just a cosmetic refresh. The new sample app is built to demonstrate best-practice integrations from end to end. It shows how the SDK is meant to be initialized, how permissions should be handled, how data flows through the system, and how edge cases are addressed in a clean, maintainable way.
The goal is simple:
Instead of guessing how things should work together, developers can now reference a working, production-aligned example that mirrors real implementation scenarios. For many teams, this alone removes days or weeks from their integration timelines.
The second major update in SDK 5.1.0 is the introduction of Bluetooth Low Energy (BLE) support for heart rate monitors and blood glucose monitors.
If you’ve ever integrated Bluetooth devices into a mobile app, you already know the challenges: platform-specific permissions, unreliable discovery, unstable connections, and devices that claim to follow standards but don’t quite behave as expected.
In healthcare, these issues aren’t just annoying, they’re critical. A dropped connection can mean lost measurements. Delayed data can mean delayed insights. And unstable integrations quickly lead to frustrated users who stop trusting the app altogether.
With the new BLE support, the SDK now handles this complexity directly. Applications can connect supported heart rate and blood glucose devices without building and maintaining custom Bluetooth logic from scratch.
This includes:
By abstracting Bluetooth complexity into a consistent SDK layer, teams can focus on building product features instead of debugging low-level connectivity issues.
The third key addition in SDK 5.1.0 is real-time heart rate measurement processed locally on the device.
This is a feature we’ve heard requested repeatedly, especially from teams working on:
Instead of waiting for periodic syncs or cloud roundtrips, heart rate data can now be accessed immediately on the device. This makes feedback faster, improves reliability in low-connectivity environments, and reduces dependency on background syncing behavior.
At the same time, the data is still uploaded securely in the background, ensuring that real-time use cases and long-term analytics stay aligned.
The result is a more responsive experience for users and a more flexible foundation for developers building real-time health features.
On paper, SDK 5.1.0 might look like a collection of technical improvements. In practice, it represents something more important: a shift toward developer efficiency and real-world reliability.
This release is built around a few core principles:
Every change in this version is rooted in real feedback from teams building with the SDK. Whether it’s reducing integration mistakes, simplifying Bluetooth connectivity, or enabling real-time data access, the focus is on making health data integration easier to get right.
If you’re already building with the SDK, version 5.1.0 helps you move faster with fewer surprises. Cleaner examples, more robust connectivity, and real-time data access mean less time troubleshooting and more time iterating on product value.
If you’re exploring what’s possible and evaluating options, this release makes it easier to see how things work in practice. The new sample app and expanded capabilities provide a clearer picture of what you can build and how quickly you can get there.
SDK 5.1.0 is not an endpoint, it’s a foundation. As real-time data, connected devices, and on-device processing become more important in digital health, having a reliable, well-documented, and extensible SDK matters more than ever.
This release is another step toward making health data integration feel less like infrastructure work and more like product development.
For existing customers, full technical details are available in the API documentation.
For teams exploring new integrations, you can book a demo directly on our website and see the new SDK in action.
