Health data aggregation app: Apple Health, Google Health Connect and more, in one record
We worked on the iOS and Android app of a consumer health records company. It links Apple Health, Google Health Connect, home devices and patient portals, merges the readings into one record, builds reports a doctor can read, and answers questions about the person's own data. It keeps working offline and sells plans through both stores.
November 22, 2026 · 12 min read · Jitendra Choudhary, CTO & Co-Founder
This was custom healthcare software development on an app already in the stores, built around health data interoperability.
Why a health data aggregation app
People already collect health data, but it sits in many places: the phone's health store, a blood pressure cuff, a scale, a glucose sensor, a hospital portal. Nobody sees the whole picture, least of all the doctor in a ten-minute visit.
Work ran from May to July 2025, with builds on TestFlight and Play internal testing throughout.
The architecture: from every source to one record
The React Native app reads from the phone's health store and linked accounts, queues entries when offline, and sends readings to the company backend. There they are put in one common model, duplicates are merged, and the record feeds trends, reports and the assistant.
Open full sizePhone-specific work is native: health store access, permissions, sync, offline queue, Face ID, store billing. Content screens reuse the company's web record, so a web release reaches the app the same day. Our healthcare product engineering work starts from that kind of trade-off.
What a person does in the app
1. Link their data

Linked accounts, with the last sync of each.

The phone asks, type by type.

Sync status, with duplicates skipped.
2. See trends, the timeline and reports

My trends.

Health record: one timeline, every source.

A report to share with the doctor.
3. Ask about their own data

Ask anything: answers from their data, with sources.

Offline: entries wait on the phone.

A note changed in two places: the person chooses.
4. Sign in and subscribe

Face ID, offered once on first open.

Plans through the store.

Plan bought on another account.
The hard problems, and how we solved them

Two health stores that behave differently+
For the API details, see our Apple Health HealthKit API integration guide and how to send HealthKit and Health Connect data to a FHIR server.
The same reading from two sources+
Reports a doctor can read+

An assistant that stays in its lane+

Logging with no signal+

Subscriptions that both stores accept+
Also in the work+

Buy, build or reuse
| Capability | Choice | Why |
|---|---|---|
| Phone health data | Reuse: HealthKit and Health Connect | The platforms' own stores, with the person's permission. |
| Content screens | Reuse the web app | Same-day updates in the app. |
| Payments | Buy: App Store and Google Play billing | Required by store rules for digital plans. |
| Sign-in | Reuse the company's Keycloak | One login across web and app. |
| Linking, sync, offline queue, plans, Face ID | Build, native | The parts that need the phone. |
| Release pipeline | Build on Fastlane | Repeatable builds for both stores and three environments. |
Security and privacy
- The app reads only the health data types the person allowed, and they can change that in the phone's settings.
- Face ID and fingerprint checks stay on the phone.
- The assistant answers only from the signed-in person's own data.
- Sign-out ends the session on the server, not only on the phone.
- Code shrinking and obfuscation on both platforms.
For a mobile app built for care workers instead of patients, see our home care mobile app case study.
What we learned
| What we found | What we did | What improved |
|---|---|---|
| Health data work starts with permissions. | Mapped every data type to a reason before asking for it. | Smoother store reviews. |
| A taken-over app needs its user journey first. | Asked for a walkthrough of the app from the user's side before changing flows. | Fewer surprises in sign-up and plan screens. |
| Store review is part of the build. | Submitted early, read each finding, fixed it with the company. | An approved build. |
| Subscription edge cases hide in sandbox. | Wrote each case down as a scenario with expected behavior and agreed it with the backend team. | Clear rules for shared store accounts and restore. |
| Platform bugs need proof, not opinions. | Explained the Android web view behavior with references, then fixed it on our side. | Sign-out that works on both phones. |
How this engagement ran
Time and material, about three months. The code lived in the company's repository. Feature branches per ticket, pull requests reviewed by the company, release notes with every build, and testing on TestFlight and Play internal testing before any wider release.
The same company also asked us to build its clinician web app on a FHIR server. That was a separate assignment, told in our Medplum EHR clinician web app case study.
Building an app that brings health data together?
Tell us your data sources and platforms. We will map permissions, sync and reports before a line of code, built as custom healthcare software.
Sources: the project channels, May to July 2025, read Nov 22, 2026. Build sizes as reported by the team on Jun 23, 2025. No user or revenue numbers are claimed.
