Home care mobile app for Dutch care workers: an iOS and Android app for visits, records and reports
We built the home care mobile app of a Dutch home care software company, for iOS and Android in React Native. Care workers link their phone with a QR code, unlock it with a PIN or fingerprint, plan visits with travel time, open a patient's record and write reports on the spot, with an AI summary from the company's own service. Every screen is in Dutch.
November 22, 2026 · 11 min read · Jitendra Choudhary, CTO & Co-Founder
This was healthcare mobile app development for a European client, built against their existing backend and sign-in server as custom healthcare software development.
Why a home care app for care workers on the road
Home care workers spend the day on the road between patients. The company's web console works well at a desk, but a care worker needs the day's visits, the patient's key facts and a place to write the report in their pocket.
Work started in June 2025 with a three-person React Native team, over four milestones of about a month each.
How the home care mobile app works
The app is React Native 0.79 for iOS and Android. It does not keep its own copy of patient records. It reads and writes through the company's mobile API, and the company's SMART auth server handles sign-in. One Redux middleware sits in front of every call, so the rules for tokens, network and errors live in one place.

The phone holds no copy of patient records. Every call goes through one middleware to the company's servers.
Our healthcare product engineering team worked inside the company's repository and issue tracker from day one, and the five flows below are drawn from the app's code. For the wider build process, see our healthtech app development guide.
Care worker app workflows, screen by screen
Each flow is drawn from the code, followed by the screens with their real Dutch labels. Names and patient details are invented. On a phone, scroll a flowchart sideways.
1. Activate the phone once, then unlock with a PIN or fingerprint

Activation runs once per phone. A failed sign-in goes back to the scan.

Welkom bij: six steps from the web console.

Scan QR-code.

Bedenk een pincode (create a PIN).

Ontgrendel met Biometrie (optional).

Daily unlock: PIN or fingerprint.
2. Home care scheduling: plan, change and close a visit

Edits to a repeating visit ask whether to change one visit or the series.

Agenda with Reistijd (travel time) blocks.

Creëer nieuwe afspraak (new visit).

Travel time Vooraf and Achteraf.

Afspraak: report, no-show, edit, delete.

No-show per participant.
3. Open the patient, write the report, add a photo

A patient outside your own caseload needs a reason first.

Caseload with search.

Reason for viewing outside my caseload.

Patiënt: key info first.

Creëer rapportage (write report).

Bijlagen: add a photo, resized on the phone.
4. AI nursing documentation: summarize a report

The care worker always chooses which version is saved.

Original text.

Samenvatting, one tap back to the original.
5. Catch up on visits without a report

Recent visits with no report stay on the list until a report is saved.

Afspraken zonder rapportage.

Instellingen: PIN, biometrics, deactivate.
The hard problems in a React Native healthcare app, and how we solved them

Every call takes this path. The refresh step saves the new refresh token each time.
Sign-in without a password on the phone+
Care workers were being logged out+
A server hiccup must not end the session+

An agenda that thinks in visits+
Seeing a patient outside your own caseload+
AI that saves time without changing the record+
Photos and files from the field+
Code the client's own team could own+

Buy, build or reuse
| Capability | Choice | Why |
|---|---|---|
| Sign-in | Reuse the company's SMART auth server | One identity for web and app, with standard OAuth2 and PKCE. |
| Calendar | Reuse react-native-calendars, in our own fork | A proven day view, changed where home care needed more. |
| Biometrics | Reuse the phone's own check | The fingerprint or face never leaves the phone. |
| AI summary and dictation | Reuse the company's AI service | The company keeps control of the model and the data. |
| Agenda, caseload, reports, attachments, sessions | Build, in React Native | The parts that make the app fit the care worker's day. |
Security and privacy
- The phone is linked to one account with a QR code. No password is typed or stored on it.
- Sign-in uses the OAuth2 code flow with PKCE, in a secure in-app browser.
- Daily unlock is a PIN or the phone's own biometric check.
- Viewing a patient outside your caseload needs a reason, which is recorded.
- Deactivating the app in settings clears the phone, and it must be linked again.
What we learned
| What we found | What we did | What improved |
|---|---|---|
| Token rules decide whether an app feels reliable. | Read the server's rotation rules first, then put every refresh in one place. | No logouts in the long test. |
| Not every error means “log out”. | Agreed one error rule with the client and wrote it down. | A passing outage keeps the session. |
| Agenda rules live in the planners' heads. | Asked about past dates, travel time and durations in daily reviews. | Rules agreed before code, not after a bug. |
| A client's code review is part of the build. | Planned time for it and answered each comment in its own commit. | Code the client's team accepted into its repository. |
How this engagement ran
Fixed milestones over about four months, from June 2025, with a three-person React Native team plus a tester and a delivery lead. The code lived in the company's repository, and the work was tracked in its issues. We joined the client's daily stand-up, sent builds to TestFlight and Google Play testing, and fixed findings from their acceptance testing in short cycles.
Planning a home care mobile app?
Tell us about your backend, your sign-in and your users' day. We will map sessions, agenda rules and reporting before a line of code.
