Case study · Client name withheld

Home Blood Pressure Monitoring App

A Flutter app that pairs with Bluetooth home devices and uploads readings to the client's service

An app that lets patients send readings from Bluetooth home devices to the client's service. Patients sign in, scan and pair a Bluetooth blood-pressure monitor and a Bluetooth scale, take readings, and see their history and blood-pressure charts. Our team built the Flutter app, published on Google Play and the App Store.

Recreated screens of a home monitoring app with example values: a phone showing a received reading of 122 over 78 with pulse 70 and two paired devices, beside an enlarged chart of systolic and diastolic readings from 14 September to 12 October
Screens recreated with neutral naming and example data.
Client
Confidential client · Health
Platforms
iOS · Android
Our scope
Flutter app · Bluetooth integration · Uploads
Period
2026

The product

What it does, and for whom

The hard part of a connected-device app is what the device does between the button press and the upload. Here, the monitor sends its readings only after it receives a Set Time command, so the app has to synchronise the device's time first and then handle the Bluetooth indications that carry the readings. The app also removes duplicate readings by device, timestamp and values, and retries failed uploads.

Scope: The back end and API are the client's service, and the monitor and scale are third-party devices; we did not make them or their firmware. Our work was the mobile app, including its Bluetooth integration. The monitor and scale are not pictured on this page.

Our contribution

What our team built

  • Flutter app

    Patient sign-in, device scanning and pairing, readings, reading history and blood-pressure charts, in Flutter with native Kotlin and Swift integration. Built with fl_chart and flutter_secure_storage.

  • Bluetooth integration

    Scanning, pairing and readings over Bluetooth Low Energy with flutter_blue_plus: device time synchronisation and handling of Bluetooth indications.

  • Uploads

    Uploading readings to the client's service through its API with Dio, de-duplicating by device, timestamp and values, and retrying failed uploads.

Technologies: Flutter · Kotlin · Swift · Bluetooth Low Energy · flutter_blue_plus · Dio · flutter_secure_storage · fl_chart

User flow

From device to chart

Four screens that follow a reading from the home device to the patient's history.

Recreated screens of the app in order, left to right: pair a device, take a reading, reading history, blood-pressure charts
The app's main screens, in the order of the steps below. Numbered markers match the steps below.
  1. Pair a device

    Scan for a Bluetooth monitor or scale, then pair it.

  2. Take a reading

    The app sets the monitor's time, receives the reading and uploads it.

  3. See the history

    Readings are listed for the patient to look back on.

  4. Follow the charts

    Blood-pressure readings are plotted over time.

The product in use

Inside the app

  1. Scanning and pairing

    The app scans for Bluetooth home devices and pairs a blood-pressure monitor and a scale.

    Recreated Add a device screen on a phone beside an enlarged list of devices found: a Bluetooth blood-pressure monitor marked Paired and a Bluetooth scale with a Pair button
    Scan and pair. Close-ups on phones: tap any image for the full screen.
  2. Time sync, then the reading

    Because the monitor sends readings only after a Set Time command, the app synchronises the device's time and listens for Bluetooth indications. The reading then appears on screen and goes to the client's service through its API.

    Recreated Take a reading screen on a phone beside an enlarged card showing systolic 122, diastolic 78 and pulse 70 with an Uploaded label and the words Example values
    A received reading. Close-ups on phones: tap any image for the full screen.
  3. History, de-duplication and retries

    The reading history lists a patient's readings. Behind it, duplicates are removed by device, timestamp and values, and failed uploads are retried.

    Recreated History screen on a phone beside two enlarged rows: a weight reading of 72.4 kg marked Will retry and a blood-pressure reading of 122 over 78 marked Uploaded
    History with upload state. Close-ups on phones: tap any image for the full screen.
  4. Blood-pressure charts

    Charts plot the patient's blood-pressure readings over time.

    Recreated charts screen on a phone beside an enlarged line chart of eight example systolic and diastolic readings from 14 September to 12 October
    Thirty days of readings. Close-ups on phones: tap any image for the full screen.

About these images: the screens are recreated for this case study, with neutral naming and example data in place of the client's brand, patients and devices, the layouts are illustrative, and they are not screenshots of the app. Every reading shown is an example value, not medical information or guidance. No real monitor or scale is pictured.

Delivery

The engagement

  • Published on Google Play and the App Store.
  • Built in 2026.

Connecting an app to Bluetooth hardware?

Tell us which devices it needs to talk to and where the readings should go. We'll reply with the questions about pairing, data and store rules that shape the scope.