.png)
We are happy to share that we rolled out SDK 5.2.0, a major infrastructure-focused update across React Native, iOS, and Android. While this release is not about flashy UI changes, it delivers meaningful improvements to the foundation behind wearable-powered healthcare applications.
This update focuses on the areas that matter most for real-world digital health applications: faster synchronization, more reliable integrations, improved cross-platform development, and better scalability for large health datasets.
SDK 5.2 introduces several major improvements, including Expo Plugin support for React Native, an updated Samsung Health integration built on Samsung’s official SDK, major Apple Health performance optimizations, improved observability tooling, and more stable synchronization handling across platforms.
Together, these updates are designed to reduce integration friction, improve SDK reliability, and make continuous health data easier to work with at scale.
Let’s break down each part of the SDK and see in detail the new improvements!
One of the biggest improvements in SDK 5.2 focuses on reducing setup complexity for React Native teams. As cross-platform digital health applications become more common, developers need integrations that are easier to implement, maintain, and scale across ecosystems.
With SDK 5.2, the Thryve SDK is now available as an Expo config plugin, enabling seamless integration into Expo-managed workflows without requiring manual native setup.
This really simplifies implementation for React Native teams and lowers the barrier for integrating wearable data into mobile health applications. Instead of spending time configuring native dependencies manually, developers can now move faster from setup to production-ready integrations.
For many teams, this means:
To further improve the developer experience, the sample app has also been upgraded to the latest React Native version and now includes a dedicated Expo integration example.
Moreover, the new sample setup provides a more modern reference implementation for teams building wearable-powered applications with React Native.
SDK 5.2 also introduces improvements to initialization handling and TypeScript support.
The getOrCreate method now returns ThryveResponse<boolean> instead of Promise<any>, improving type safety and making SDK readiness states easier to handle reliably inside applications.
These changes help developers build more predictable synchronization flows and reduce edge cases during SDK startup and initialization.
A major part of SDK 5.2 is the implementation of a new Samsung Health integration for Android. With constant advancements in the wearable world, maintaining stable and future-proof integrations becomes critical for long-term reliability.
With Android SDK 5.2, Thryve introduces module_samsung_health, a new integration built on top of Samsung’s official Samsung Health Data SDK.
The new module replaces the legacy module_shealth integration and brings substantial improvements across synchronization speed, reliability, and network efficiency. Large data transfers are handled more efficiently, reducing synchronization overhead and lowering mobile data consumption during wearable sync operations.
The cherry on top is that the new architecture is officially supported and designed to remain compatible with future Samsung Health updates.
One important migration note: Samsung does not support migration of existing user connections. As a result, users upgrading to the new module must reconnect their Samsung Health accounts.
The previous Samsung Health integration relied on Samsung’s older architecture, which has now been deprecated. Over time, the legacy module began showing increasing instability with newer Samsung Health app versions and operating system updates.
Rather than continuing to patch an aging integration layer, SDK 5.2 introduces a cleaner and more future-proof foundation built directly on Samsung’s actively supported SDK infrastructure.
While the old module remains available for backward compatibility, it is now deprecated and will no longer receive further improvements.
SDK 5.2 also introduces the Thryve Observability Module for Android, following its earlier rollout on iOS.
The module provides:
This gives development teams and the Thryve platform itself better visibility into real-world SDK performance, synchronization behavior, and stability issues across production deployments.
Overall, telemetry collection remains fully configurable, allowing teams to enable or disable observability features according to their own privacy and compliance requirements.
SDK 5.2 also introduces major performance improvements for Apple Health integrations on iOS, particularly around synchronization speed, background processing, and large-scale data handling.
One of the biggest improvements is significantly faster Apple Health data processing. Synchronization, backfillEpoch, and backfillDaily operations are now up to 10× faster across different dataset sizes.
For applications processing large volumes of historical health data, this results in noticeably faster onboarding, reduced synchronization delays, and smoother user experiences overall.
The update also improves background synchronization efficiency for Apple Health data.
By reducing processing overhead during background operations, SDK 5.2 improves stability and minimizes unnecessary resource usage while synchronization tasks are running in the background.
This is especially important for continuous health monitoring applications where synchronization reliability needs to remain invisible to the end user.
Large health datasets can create significant network strain, particularly on unstable mobile connections. SDK 5.2 introduces more efficient network handling for large data transfers, improving synchronization stability while reducing unnecessary mobile data consumption.
These optimizations help applications maintain more reliable synchronization behavior across real-world usage scenarios.
SDK 5.2 resolves several synchronization race conditions and crash scenarios while improving observability through enhanced crash reporting and tracing capabilities.
Also, SDK readiness handling has been improved with more detailed initialization errors, making it easier for development teams to debug startup and synchronization edge cases.
SDK 5.2 is fundamentally focused on strengthening the infrastructure behind wearable-powered healthcare applications. Across React Native, iOS, and Android, the update improves synchronization speed, interoperability, reliability, observability, and the overall developer experience.
As wearable ecosystems continue to expand, reliable infrastructure becomes increasingly important for delivering stable and trustworthy digital health experiences. Together, these improvements help create the kind of invisible but highly reliable infrastructure layer that continuous health monitoring depends on.
For existing customers, full technical details are available in the API documentation.
As for potential newcomers, if you are looking to simplify wearable integrations and improve SDK reliability, then book a demo with Thryve.
