The alert gets through.
Our first product. Reach tests that a medical alert actually reaches the person, on every iOS release, on real devices, and writes it all down for your file. Built from scratch by people who have built medical alerts for a decade.
Low glucose
54 mg/dL and falling. Critical alert: sounds through Focus and the silent switch.
Phones are built to stay quiet.
Focus modes, deep sleep, earbuds, permissions that reset after an update, an OS release on a Tuesday. Each has silenced someone's glucose alarm. In February 2025 the FDA said it plainly: missed smartphone alerts from diabetes devices may have contributed to serious harm, including death.
The duty to test alert delivery does not end at clearance. It restarts with every release.
| Condition | What can go silent | What it records |
|---|---|---|
| Focus & Do Not DisturbEvery Focus mode, 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 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, 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, 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. Every line names the device and the build. | ||
A decade of medical alerts.
For a decade we have built the part of medical apps that has to wake people: the alert that sounds through Focus, the silent switch and a phone that has been asleep for hours. Reach is built from scratch on what that taught us.
The film of it
| IEC 62304 | SOUP records, every release. Identification, version, known anomalies evaluated against your hazards, a change notice before every release and a defect notice when one is found. |
|---|---|
| IEC 60601-1-8 | Applicability table. Which alarm-system clauses a phone can meet, which it cannot, and why. An argument your risk file can cite. |
| Section 524B | SBOM in CycloneDX or SPDX. Support status and end-of-support dates per component, a vulnerability notice inside thirty days. |
| Known anomalies | The list nobody wants to write. Written. What Reach cannot guarantee on which OS, stated plainly. |
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, for your quality teamWhen does it launch?+
November 2026. Leave an address and we write once, when it does. Until then nothing here is for sale, and the page says so.
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.
Does AI write the code that goes into our app?+
Some of it, under a written procedure: a person decides the change, reviews it, checks it on the device and puts their name to it. No client code goes to an outside AI model without written permission. In your codebase, your AI policy applies.
What about the clients you built alerts for?+
Everything we made for clients stays with them, 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.
Can you help with our alerts before then?+
Yes. That is the work we have done for ten years, and it is a project like any other. Start one.