Health
Pulseform
An offline-first care companion for two app stores, one codebase
- Industry
- Digital health
- Engagement
- MVP to launch
- Team
- 5 specialists
- Duration
- 18 weeks
The problem
Pulseform's care programmes were delivered on paper. Patients logged symptoms in clinics with poor connectivity, and clinicians only saw the data weeks later at the next appointment.
- Paper logs lost or incomplete for roughly a third of patients
- No usable connectivity in the rural clinics running their pilots
- Clinical review required data no later than 24 hours after logging
- A regulated launch window meant the date could not move
Our approach
React Native · Expo · Supabase
Offline as the default state
The app writes to a local store first and treats sync as an eventual background job, so logging never depends on a signal.
Conflict rules defined with clinicians
We workshopped merge behaviour for every field with the clinical team rather than guessing, so late-arriving edits behave predictably.
One codebase, native feel
React Native with platform-specific navigation and haptics, so neither store's reviewers treated it as a web wrapper.
Accessibility from the first sprint
Dynamic type, screen-reader labels and 4.5:1 contrast were acceptance criteria on every ticket, not a pre-launch pass.
Timeline
Discovery & prototype
Weeks 1-3Clinician interviews, sync model design and a clickable prototype tested with eight patients.
Core build
Weeks 4-11Local-first data layer, symptom logging, care plans and clinician web review portal.
Field pilot
Weeks 12-15Two rural clinics, 120 patients, weekly release cadence driven by field feedback.
Store submission
Weeks 16-18Accessibility audit, penetration test remediation and approved first submission on both stores.
Results
- 4.8
- Average store rating across platforms
- 180k
- Installs in the first year
- 92%
- Weekly logging compliance in pilot
- 0
- Store rejections at first submission
- Clinicians review patient data within hours instead of weeks
- Paper logging retired across all pilot sites
- Shared codebase keeps both platforms on the same release train
“The only agency we've worked with that pushed back on scope to protect the timeline. Our app shipped on the date we agreed at kickoff.”
