The alert
gets through.
Reach is the software that carries a medical alert to a phone, the tests that show whether it arrived, and the record that says so. On every OS release, on real devices, in the form a manufacturer has to file.
Phones are built to stay quiet.
Focus modes. Deep sleep. A new pair of earbuds that changes the volume. Permissions that reset after an update. An OS release that ships on a Tuesday. Each is a reason a phone stays silent, and each has happened to someone's glucose alarm.
In February 2025 the FDA put it on the record. Missed smartphone alerts from diabetes devices may have contributed to serious harm, including death. Manufacturers are expected to keep evaluating and testing alert delivery as phone settings, accessories and operating systems change. That duty does not end at clearance. It restarts with every release.
An OS update ships on a Tuesday. Which of your alerts stayed silent on Wednesday, on which phone, under which setting?
| Condition | What can go silent | What the Kit records |
|---|---|---|
| Focus & Do Not DisturbEvery Focus mode, scheduled and manual, with and without the Critical Alerts entitlement. | Banner suppressed, sound muted. The entitlement should break through. On this build, does it? | Delivery per Focus mode and per entitlement state, with the OS build. |
| Deep sleep & backgroundApp suspended, terminated, in Low Power Mode, overnight. | The app never wakes, so nothing sounds at 3 a.m. | Time from event to sound, the app state at the time, what happened on relaunch. |
| Permissions & resetsNotification permission revoked, re-granted, or reset by an update. | The app believes it can alert. It cannot. | What the app noticed, and what it told the person, per state. |
| Accessories & volumeCar audio, earbuds, hearing aids, a speaker in the kitchen. | The sound goes somewhere else, or nowhere, at four percent. | Where the audio routed, at what level, and whether the phone itself sounded. |
| Bluetooth reconnectionSensor out of range and back, phone rebooted, watch in between. | A silent gap between the last reading and the first alert. | Time to first reading and time to first alert, per path. |
| OS betas & updatesEvery iOS and watchOS beta, from the first seed. | What changed on Tuesday, in your users' pockets on Wednesday. | A regression table per beta, published before it ships. |
| Time-sensitive vs criticalWhich interruption level each alert uses. | A critical alert demoted to a banner nobody hears. | Entitlement honoured or not, per alert, per OS build. |
| Delivery receiptsDelivered, displayed, acknowledged. | "Sent" was never the question. | A timestamp for each state, in a form you can put in the file. |
| Run on current and previous iPhone and Watch generations, on the OS versions your users actually run. Every line names the device and the build. | ||
Run it on your app before Apple does.
An open device-in-the-loop harness. It runs the matrix on real iPhones and Watches against your build and writes the report.
- Real devices, not simulators
- Every setting a phone can be in
- A report you can file
The alert path, as a library.
Critical Alerts handling once Apple grants your app the entitlement, background survival, reconnection, delivery receipts, and the regression suite that runs on every OS beta. Shipped with its record.
- IEC 62304 SOUP records
- IEC 60601-1-8 applicability table
- CycloneDX SBOM, known anomalies
Our engineers in your repo.
OS-beta compatibility, alert regression, Bluetooth stack changes, SBOM refresh and vulnerability triage, delivered as a monthly compliance report.
- From your next release
- Your process, your definition of done
- A name on every line
What stayed silent, before the release ships.
One per OS beta, public. A table first: which alert, which device, which setting, which build. Prose second. Speculation never.
- Every iOS and watchOS beta
- Android from 2027
- Read by quality leads, free
A Kit run on your build
SDK integration
Embedded starts
A Report, in public
Ten years on the alarms of the world's most successful glucose monitor.
Since 2016, Bolted engineers have led the alarms of FreeStyle Libre, the component that wakes people before their glucose can hurt them. The platform serves more than six million people and was named the best medical technology of the last fifty years. We did not build that. We kept one part of it right, every release, for a decade.
Reach is that decade, written down and run by a machine, so that the next pump, pen or sensor does not have to learn it the hard way.
The Libre years, through the public recordSOUP records, every release
The software-of-unknown-provenance documentation your process requires, versioned with the library, with a change notice before every release and a defect notice when one is found.
Applicability table
Which alarm-system clauses a phone can meet, which it cannot, and why, so your risk file cites a paragraph and an argument, not a promise.
An SBOM in CycloneDX or SPDX
Updated with every release, with support status and end-of-support dates per component, and a vulnerability notice inside thirty days.
The list nobody wants to write
Written. What Reach cannot guarantee on which OS, stated plainly, so it never surprises an auditor.
Reach is software for manufacturers. It makes no medical claim of its own. The manufacturer's clearance covers the system, and Reach is documented so that it can.
Supplier facts, written for your quality teamDo you need our source code?+
The Kit runs against a build. The SDK is integrated by your team, or by ours. Embedded means we are in the repo, under your process and your definition of done.
Android?+
iOS and watchOS first, because that is where the Critical Alerts entitlement lives and where our decade is. Android follows the same matrix in 2027.
Why not wait for Apple and Google to fix it?+
They improve it every year, and every year the matrix changes with them. The regression duty and the record stay with the manufacturer under Section 524B and the quality regulation. Reach exists so that duty is a run, not a scramble.
Do agents write the code that goes into our app?+
Agents write plenty of it, under a written procedure: a person specifies the change, reviews the diff, verifies it on the device and signs it. No client source is sent to an external model without written permission, and Embedded engineers follow your AI-tooling policy, not ours.
You spent ten years inside Abbott's app. We partner with Abbott, or compete with them.+
Everything from those years stays with Abbott, under their agreements and ours. Reach is built clean-room, from the public standards and our own test devices. Where a conflict of interest exists, we say so before the first call and decline the work.
What does "in development" mean?+
It means we are running the matrix on our own builds now, and the Kit ships when it passes it. We publish dates when we have them, not before. Embedded is available now because it is the work we have done for ten years.
Send us the alert path.
We tell you what stays silent. One working day.