How AEVONA helps
Why AEVONA works with no signal, and what that changes
Offline is the normal case in a dialysis basement in a tier-3 city, not an edge case. Designing for that changed almost every decision inside the app.
The AEVONA care team6 min read
In short
- Every core tracker works fully offline. Sync is a convenience layered on top, never a prerequisite.
- Medication reminders are scheduled by the phone, so one still arrives with no network and no data pack.
- The diet and access guides are bundled in the app rather than fetched.
- It costs us a harder sync problem and a larger app, and it is the right trade.
Before you read this
AEVONA is a self-management diary and a booking service. It is not a medical device, it does not diagnose, and it never replaces your nephrologist or dialysis team. Always follow the advice of your treating clinician.
Most health apps treat a missing connection as an error state: a spinner, a retry button, a grey banner saying you are offline. That is a reasonable design if your users are usually online.
The phone we are designing for is in the basement of a dialysis unit in a tier-3 city, on a mid-range Android handset, on a data pack that ran out. That is not an unlucky Tuesday. It is the typical case, several times a week, at exactly the moment a pre-session weight or a blood pressure reading needs recording.
So AEVONA is built the other way round. The phone is where your record lives. The server is a copy.
What that means in practice
- Every core tracker — weight, blood pressure, fluid, medication — works fully offline. Entries are written to a database on the phone and shown back to you immediately, with no round trip to anything.
- Entries queue and sync when a connection returns, without you having to remember to do anything or press anything.
- Medication reminders are scheduled by the phone itself rather than pushed from a server, so a reminder fires in flight mode, in a basement, and with no data balance.
- The kidney diet guide and the fistula and catheter care guide are bundled in the app, so they open instantly and work with no signal at all.
- Emergency contacts, including your dialysis centre's number, display and dial with no server call — the moment you most need them is the moment a network is least dependable.
- Your lab history is on the device, so it opens in a waiting room whether or not there is coverage.
The thing we most wanted to avoid is a patient standing in a corridor, unable to record a reading, deciding to enter it later, and then not entering it at all. A record with holes in it is worse than useless at a review appointment, because nobody can tell which gaps are missing data and which are missing days.
What it costs us
This is not the easy way to build an app, and it is worth being honest about the bill.
| The cost | Why we pay it |
|---|---|
| Sync is a genuinely hard problem | Two devices — yours and a caregiver's — can both write while offline. That needs client-generated identifiers and a clear rule for resolving conflicts, rather than trusting the server to be the only writer. |
| The app carries content instead of fetching it | Bundling both guides in three languages makes the download larger. We hold the installed size down elsewhere so the app still installs on a phone with very little free space. |
| Guide updates need a route that is not the Play Store | AEVONA can push corrections to guide content remotely, so a fix does not wait on an app release — while the guide still works with no connection. |
| Nothing can depend on being online | Any feature that would need a live connection to be safe is either redesigned or left out. That has removed things from the plan. |
The two places it does not apply
Being straight about the limits matters more than the pitch. Two things genuinely need a connection, and both are Phase 2.
Browsing verified centres needs current data about capacity and pricing, and a booking request has to reach an AEVONA coordinator to be confirmed at all. Neither can be faked offline, and we would rather say so than show a stale centre list or accept a request that goes nowhere.
Ask your unit
Offline capability is about not losing your record. It is not a substitute for contacting your unit. If something is wrong — breathlessness, chest pain, a problem with your access, a fever, sudden swelling — call your dialysis unit or go to an emergency department. An app that works without a signal still cannot treat you.
Sources for the AEVONA claims above
PRS §4.2PRS §7.3PRS §7.2PRS §5.5 FR-5.6PRS §5.6 FR-6.6PRS §5.7 FR-7.5PRS §5.9 FR-9.5
The clinical explanation in this article is general orientation prepared by the aevona care team. It cites no protocol and sets no targets, because the targets that apply to you are the ones your own dialysis unit has given you.