Pill ledger

A small personal medication supply ledger that runs entirely in your browser. It is a single static page with no build step, no framework, and no server. All data stays on your device in local storage.

What it does

For each medication you record the name, how many pills you take per day, and how many days each pharmacy fill covers. You can also enter a last pickup date to start the schedule before you have logged any refills. From there the app keeps a ledger of entries:

• Refill adds pills you picked up. The date of the latest refill also anchors the pickup schedule.
• Recount sets the total to what you actually counted on a given date.
• Adjust adds or removes a few pills for missed or extra doses.
• Dose records pills you actually took, in any amount such as 0.5, 1, or 1.5.

Turn on Log each dose for a medication to track doses one by one. You define up to three dose slots with a label and amount, for example AM 1 and PM 0.5. The card then shows a button per slot for today, plus an Other link that reveals three quick amounts: 1/2, 1, and 1.5. One tap logs the dose and a toast offers Undo for a few seconds. Tapping a taken slot again asks before removing it. Pills per day stays editable as the planned rate for days left and surplus, so you can set 2 when the buttons are AM 0.5, PM 1, and PM 1.5. Leave it blank to use the slot total. With dose logging on, the count only goes down by the doses you log, so recount now and then if you forget to tap. With it off, the count drops by pills per day automatically and Dose entries are a record only.

The current count is derived from the ledger: the latest recount, plus later refills and adjustments, minus your daily dose for each day since the recount. From that the app shows:

• Pills on hand and days left at the current dose.
• The projected run out date.
• The next four pharmacy pickup dates, calculated from the date of your latest refill entry plus the days supply. Pharmacies count from the day you picked up the prescription, so the refill entry is the anchor. The manual last pickup date is only used until the first refill is logged.
• A pickup window for each date. Pharmacies usually let you collect a refill a couple of days early, so each medication has an early pickup setting (default 2 days) and the schedule shows "Oct 8 to Oct 10" style windows. Set it to 0 or 1 for controlled medications with stricter rules.
• A reminder chip. Each medication has a reminder setting (default 4 days before the due date). When the due date is that close, the card shows a Check pharmacy chip and the summary line counts it, so you know to review the pharmacy app.
• Prescription tracking. Optionally enter refills remaining, the date the prescription was written, and how many months it is valid for (12 by default, 6 for Schedule III and IV). Logging a refill counts one refill down, and deleting a refill entry puts it back. When refills reach zero, the prescription has expired, or an upcoming pickup falls outside either limit, the card shows a New Rx needed chip, the affected dates are marked, and the summary line counts it.
• Surplus at the earliest pickup: how many pills (and days) you will have left over on the first day you can collect the next fill, or how short you will be if the number is negative. This is the figure the home card shows as "surplus".
• A status of OK, Low, Shortfall, or Out. Low uses the per medication warning threshold in days.

The page installs to your home screen, follows your system light or dark setting, and works with no network after the first visit.

Using the app

• Home lists your medications. Each card shows the name, then a row of three figures: pills on hand, days left, and your surplus at the next pickup. Surplus appears only when it is positive, because a shortfall is already spelled out in the status sentence. Below that come the dose buttons if dose logging is on, and one status sentence such as "Next pickup Sep 29 to Oct 1, 2026" or "Running low, 5 days left".
• Tap a card to open its detail screen: supply numbers, the pickup schedule, prescription status, the entry form for refills, recounts, adjustments, and back dated doses, and the full history. Edit and Delete live there too.
• Add in the top bar creates a medication. The form shows the basics first; pharmacy dates, reminders, refills, and prescription details are under More settings.
• Menu (the three dots) holds Copy backup and Paste backup.

Enable GitHub Pages

1. Push this repository to GitHub with main as the default branch.
2. Open the repository on GitHub and go to Settings, then Pages.
3. Under Build and deployment, set Source to GitHub Actions.
4. Push any commit to main (or run the Deploy to GitHub Pages workflow from the Actions tab). The workflow in .github/workflows/pages.yml uploads the repository root and deploys it.
5. The site will be available at https://<your user>.github.io/<repo name>/. All paths in the app are relative, so it works under that subpath without changes.

There is no gh-pages branch. The .nojekyll file tells Pages to serve files exactly as they are.

Install on iPhone

1. Open the site in Safari.
2. Tap the Share button (the square with an arrow).
3. Tap Add to Home Screen, then Add.

The icon appears on your home screen and opens without the Safari toolbar. Data is stored separately for the installed app, so run a backup and restore if you already entered data in the Safari tab.

Install on Android

1. Open the site in Chrome.
2. Tap the three dot menu.
3. Tap Install app or Add to Home screen, then confirm.

Chrome may also show an install banner at the bottom of the page. Either route gives the same standalone app.

Move data between devices

Backups are plain text, so any channel that carries text works: an email or message to yourself, a notes app, or a password manager.

1. On the device that has your data, tap Copy backup. The full ledger is copied to the clipboard as JSON. If the browser blocks clipboard access, a box appears with the text selected so you can copy it manually.
2. Send that text to the other device.
3. On the other device, copy the text and tap Paste backup. The app reads the clipboard, or shows a box to paste into if the browser does not allow reading the clipboard.
4. Confirm the replace. The backup replaces everything currently in the app, so copy a backup of the destination first if it has anything you want to keep.

Update the service worker cache version

The service worker caches the app shell so the page opens offline. Because the shell is served cache first, browsers keep using the old copy until the worker itself changes. Whenever you edit index.html, the manifest, or the icons:

1. Open sw.js and change the VERSION string, for example from "v1" to "v2".
2. Commit and push to main.

On their next visit users get the new worker in the background and see an Update available bar in the app. Tapping Reload activates the new version and deletes the old cache.

Regenerate the icons

The icons are drawn from icons/icon.svg. The PNGs the manifest needs are produced by a small Pillow script:

pip install pillow
python scripts/make_icons.py

This writes icon-192.png, icon-512.png, icon-maskable-192.png, and icon-maskable-512.png into the icons folder. If you change the SVG, update the drawing code in the script to match.

Files

index.html                    the whole app
manifest.webmanifest          install metadata
sw.js                         offline cache
icons/                        SVG source and generated PNGs
scripts/make_icons.py         icon generator
.github/workflows/pages.yml   deploy workflow
.nojekyll                     serve files as is