November 16, 2026 · 7 min read · Sugam Budhraja

A Free Health Library Is Enough Until Your Data Has to Leave the Phone: React Native and Flutter in 2026

Getting Apple Health data into a React Native or Flutter app takes an afternoon. The slow part starts when someone asks for that data on a server. Six popular libraries checked against 2026's permission changes, what a library leaves you to build, and a simple rule for when it is enough.

Getting Apple Health data into a React Native app takes an afternoon. Install a package, show the permission prompt, run a query, and today’s steps appear on screen. Flutter is no slower.

The slow part starts later, usually when someone asks for that data on the server: to send a coach an alert, to train a model, to show it in a web dashboard. That is the moment a library stops being the answer, and most teams find it after they have built on one.

Here are the libraries most teams use, how they stand against this year’s permission changes, and a simple rule for when a free library is enough.


Which libraries read Apple Health and Health Connect in React Native and Flutter?

Apple Health and Health Connect only have native APIs, in Swift and Kotlin. Cross-platform apps reach them through open-source bridge libraries, and a handful dominate. We checked the six most used against their source code and release history on 15 November 2026 [1][2][3][4][5][6].

Maintenance varies widely, and only one library so far can tell when iOS 27 has limited it to 30 days of history. Data: npm, pub.dev and GitHub, 15 November 2026.
  • React Native, iPhone: @kingstinct/react-native-healthkit is the most active, with about 2.2 million npm downloads a month and a release in October 2026 [1]. The older react-native-health still has the most GitHub stars, but its last release was in October 2024 and it has 157 open issues [2].
  • React Native, Android: react-native-health-connect, about 1.6 million downloads a month, last released in August 2026 [3]. The expo-health-connect plugin that paired with it for Expo is archived.
  • Flutter: the health package reads both platforms from one API, with about 245,000 downloads a month [4].
  • Capacitor: @capgo/capacitor-health covers both platforms and released this month [5].

Download counts include automated installs, so they overstate the number of teams. But the order is clear, and so is the point: these are healthy, widely used projects, maintained by a few people for free.

What changed in 2026 that these libraries have to handle?

Both platforms tightened how much history a new user hands over, as we covered in health data permissions in 2026:

  • iOS 27 lets users share only the last 30 days of history, and added an API to detect it. Kingstinct’s library shipped support in September 2026 [1][7]. The others had not added it by 15 November.
  • Health Connect reads only 30 days before the first permission grant unless the app asks for a separate history permission, and background reads need their own permission too [8]. The Health Connect and Flutter libraries support both; the Capacitor plugin supports history but not yet background reads.

None of this is a criticism of the maintainers. It shows the real cost of a library: every platform change becomes a dependency you wait on or patch yourself.

When is a free library enough?

When the data lives and dies inside your app. A library is the right tool if:

  1. You show health data only on the phone, such as today’s steps, last night’s sleep or a workout summary.
  2. You need a few metrics on one platform, or are happy to handle the two platforms separately.
  3. You write data to Apple Health or Health Connect, such as logging workouts, more than you read from it.
  4. You are prototyping to see whether users want health features at all.

In those cases, a platform is overkill. Use the library, and pick a maintained one.

What do teams find they still need?

A library ends at the phone. The list on the right is what grows when the data has to go anywhere else.

The moment data has to leave the phone, the work changes shape:

  • Background sync. Reading when the app is closed, within each platform’s limits, which is why wearable data often arrives late.
  • Getting it to your server. Apple Health has no server API, as we found in can a web app read Apple Health. Uploads, retries, deduplication and time zones become your code.
  • One definition on both platforms. Sleep stages and heart rate variability are recorded differently on iPhone and Android, and multiple sources overlap, the problem we covered in normalising wearable data across providers.
  • Wearables that skip the phone. Garmin, Oura and WHOOP keep their richest data in their own clouds, reached through separate APIs with their own access rules, as with Garmin’s new developer fees.
  • Meaning, not samples. Baselines, scores and changes a product can act on, which take validation work of their own, as we covered in validating health scores.
  • Keeping up. iOS 27’s 30-day option and Health Connect’s history permission were two changes in one year.

Library or platform: how should you decide?

If you needA free libraryA health data platform
Health data shown only in your appYesMore than you need
The same data on your serverYou build itDelivered by API or webhooks
The same definitions on iPhone and AndroidYou map themNormalised for you
Garmin, Oura or WHOOP cloud dataSeparate integrationsIncluded where supported
Scores and insights, not samplesYou design and validate themProvided
Platform permission changesWait for or patch the libraryThe vendor’s job to keep up with

The rule is simple: if the data never leaves the phone, use a library. If it does, price what is in the right-hand column before you build it. The broader build-or-buy trade-off is in our guide to the true cost of health data infrastructure.

Where Sahha sits. Sahha has SDKs for React Native, Flutter, Expo and Capacitor as well as native iOS and Android [9]. The SDK reads Apple Health and Health Connect on the device and delivers biomarkers and scores to your backend through the API or webhooks [10], with direct cloud connections for Oura, WHOOP, Garmin and Dexcom.

Free libraries are one of the best things about building health apps today, and for an app that keeps its data on the phone they are the right choice. The decision to revisit is the day the data needs to go somewhere else. Make it then, deliberately, rather than three months into building a backend you did not plan for.

References

  1. kingstinct/react-native-healthkit. GitHub repository and releases; npm package @kingstinct/react-native-healthkit. Accessed 15 November 2026. https://github.com/kingstinct/react-native-healthkit
  2. agencyenterprise/react-native-health. GitHub repository; npm package react-native-health. Accessed 15 November 2026. https://github.com/agencyenterprise/react-native-health
  3. matinzd/react-native-health-connect. GitHub repository; npm package react-native-health-connect. Accessed 15 November 2026. https://github.com/matinzd/react-native-health-connect
  4. carp-dk/carp-health-flutter. GitHub repository; pub.dev package health. Accessed 15 November 2026. https://pub.dev/packages/health
  5. Cap-go/capacitor-health. GitHub repository; npm package @capgo/capacitor-health. Accessed 15 November 2026. https://github.com/Cap-go/capacitor-health
  6. matinzd/expo-health-connect. GitHub repository, archived. Accessed 15 November 2026. https://github.com/matinzd/expo-health-connect
  7. Apple Developer. getEarliestAuthorizedSampleDate(for:completion:). HealthKit documentation, iOS 27.0 and later. https://developer.apple.com/documentation/healthkit/hkhealthstore/getearliestauthorizedsampledate(for:completion:)
  8. Android Developers. Get started with Health Connect. https://developer.android.com/health-and-fitness/guides/health-connect/develop/get-started
  9. Sahha. SDK installation. Sahha Docs. https://sahha.ai/docs/connect/sdk/installation/
  10. Sahha. Webhooks. Sahha Docs. https://sahha.ai/docs/connect/webhooks/

Related