Why an offline medication reminder is the reliable kind
A reminder that needs a working connection, a live account and a company in good health has three ways to fail before breakfast. One that runs entirely on your own device has none of them. This is what local-first means for something as ordinary as remembering your tablets — and the honest list of what it cannot do.
What local-first actually means
Your list lives in a file on your machine. The app reads it, works out what is due, and asks your operating system to show a notification. No part of that needs a network. Compare it with the usual arrangement, where your list is on a company's server and the app is a window onto it. That design is why an app can stop working in your country overnight, why an account suspension takes your schedule with it, and why an outage on their side is silence on yours. Local-first is not a privacy stunt. It is the difference between a reminder that depends on nobody and one that depends on everybody.
What you give up
Be clear about the trade, because it is real. There is no automatic sync between your devices unless you provide it — typically by keeping the file in a folder that something else already syncs. You choose where your data goes, which also means you have to choose. There is no "log in on a new computer and everything is there". You copy a file, or restore a backup. And there is no server-side backup: if you lose the machine and never made a copy, the list is gone. It takes ten minutes to retype, but it is gone.
Making it safe without a server
Two habits cover everything. First, a backup: write the file somewhere you would still have if the computer died — a cloud drive, a memory stick, an email to yourself. Pillbell does this from Settings in one click, into a single readable file. Second, if you use two devices, keep the file in a folder that is already synced. Both copies of the app read and write it, and the newest change to each medicine wins, so you do not have to think about which device you edited last. That is the whole operational story. No account to secure, no password to recover, no vendor to survive.
Why this matters for medication specifically
Most apps failing for a day is an inconvenience. A reminder failing for a day is a missed dose, and for some medicines that is a real setback. It is also the category where the person most likely to be affected — someone elderly, chronically ill, or managing a lot at once — is least able to absorb an outage or a sudden charge. That is the argument for keeping the mechanism as dumb and as local as possible: fewer moving parts, fewer parties, fewer reasons for it to stop.
Frequently asked questions
Do offline reminders still work if I never open the app?
The app needs to be running for it to raise a notification, so leave it open or start it with your session. When it is running it checks the clock on its own and reminds you without any interaction.
Where exactly is my data stored?
In one JSON file in your own user data folder — Pillbell shows the exact path in Settings. You can open it in a text editor, copy it, or delete it, and nothing about it is sent anywhere.
Can I use it on two computers?
Yes. Point both at the same file inside a folder you already sync, and both stay level. The merge is per medicine and per dose, so edits from both sides survive.
More guides
Other things we made
Also in English, made by the same people.
Also in English, made by the same people.
Also in English, made by the same people.
Also in English, made by the same people.