You are the one who knows the schedule. Not your brother, not the pharmacy. You. Which means you are holding six bottles, three refill dates and one question you cannot answer from your own house: did she take the evening ones? So you call. She says yes. You believe her, mostly. Then the Tuesday she was tired and off has nothing written down beside it, because the record lives in your memory, a notes app and a pillbox nobody photographs. Then the appointment comes, the doctor asks how the last three months went, and you reconstruct it out loud from a phone screen while everyone waits. That is the real cost, and it is not a health cost. It is information loss. Every week nobody writes down is a week nobody can look back at. World's Best Tracker fixes the record, not the person.
Count the systems you are running. A pillbox that tells you today and nothing about last Tuesday. A notes app with three entries from March. A group text where 'yes' appears forty times and means forty different things.
None of them connect, so the questions you care about have no answers. When did the new dose start? Has she been more tired since, or was that already happening? How many days last month had no evening dose?
That is a recording problem, and recording problems get solved. World's Best Tracker gives each question a place to live, so in six weeks you answer by looking, not by remembering.
A medication goes in once. Photograph the label and it comes back as structured fields. Photograph the barcode and OCR reads the digits, which a lookup chain of Open Food Facts, USDA and NIH DSLD resolves. There is no live camera scanner: you point and shoot, or you type. That is the honest version.
Then you set the cadence: daily, every N days, chosen weekdays, monthly, or as needed. A dose is one tap: item, amount, exact timestamp, note. The day she takes half because she felt sick, that is a one-time multiplier with a reason, and her standing schedule is untouched. A notes app cannot tell you whether last Tuesday's half dose was a decision or a new normal.
How she felt goes in from a fixed list of 58 feelings across 11 categories, each with an intensity of 1 to 5 and a one-tap 'normal', so a good day logs as fast as a bad one. Free text is not analyzable six months later, which is why the list is fixed.
Photograph, confirm what it read, set the schedule. That is the whole setup for one medication, and you only do it once.
A caregiver link is its own path in the security rules: one to one, consented per person, no admin console, no view of any other account.
It runs in both directions. Your mother invites you to watch her tracking, or you ask and she consents when she accepts. Invite tokens are 128-bit random values, and listing invites is blocked, so nobody can harvest tokens or emails. Either of you can revoke the link. Neither of you can delete it.
With a link you see her day: doses taken, missed and upcoming, the next scheduled dose, her recent feelings, and a same-day adherence figure counted against the slots already due. With logDosing you enter the dose she forgot. With addMeds you add the new prescription.
What you cannot do is quietly rewrite her history. You cannot change who a record belongs to. The note you type about her confusion is filed under you, tagged as being about her, and the card says so before you apply it.
Changes a manager makes to her cabinet or her workouts are written to an append-only audit trail: only the actor named on it can create the entry, nobody can edit or delete one, and she can read the entries about herself. Dose and feeling entries are not in that trail yet.
Any app can hand you a confident number. This one is built to say nothing instead.
When a compound is looked up, the instruction is explicit: return null for any field you are not confident about; do not guess, estimate, approximate or infer, because an invented number silently corrupts a health record. What the model produced is stamped unverified.
Patterns are computed in code with hard minimums, and the language model only phrases what the code already found. A rising symptom needs at least 6 events and a 50 percent rise; an adherence gap needs at least 3 missed days.
After the model writes a proactive check-in, a regex screen checks it for a dose change, a start-or-stop and a diagnosis; any hit falls back to the plain computed sentence. It does not require a medication noun, because a test message reading 'consider stopping taking your lisinopril' sailed through the first version.
When there is nothing worth saying, you get nothing. Not a summary. Silence. And when two devices disagree about a night's HRV, both rows stay, because averaging them would invent a number neither device measured.
An app that refuses to guess is the one whose record you can hand to a doctor.
Strava is live, with full OAuth and paged history import. WHOOP connects today with full OAuth and signed webhooks, pushing once WHOOP finishes processing a night or a workout. The code states there is no live stream, and any metric it cannot read arrives blank, not estimated. Oura has no webhooks, because the verification handshake could not be confirmed against live documentation. It pulls when you connect it, and again whenever you tap Sync.
Fitbit, Pixel Watch and Wear OS are built but closed to new connections, pending an annual third-party CASA assessment costing $500 to $5,000 a year. Existing connections still sync. The Garmin watch app posts a dose from the wrist; it is sideloaded, not on the Connect IQ store, and does not import Garmin Connect data. Appointments are coming, not shipped.
Nothing to start. No card. The free account holds 25 items in the cabinet, 60 scans a month, and 40 assistant messages a day. Those limits were raised on 2026-08-15 for a reason written into the code: so a real week of use fits inside the free tier. Caregiver links, reminders, the calendar export and the audit trail are not metered.
Paid tiers lift the cabinet and raise scans. Every tier keeps an assistant ceiling, and the paid ceiling is 400 messages a day, because an unbounded assistant is an unbounded bill. Prices come live from Stripe.
Now the risk, because you are handling someone else's medical life. Data lives in Firestore on Google Cloud, and assistant replies work by sending that person's health context to Gemini. Platform admins have cross-account read access by design and never write access. This is not HIPAA compliant and does not claim to be. Ad pixels get three standard event names and nothing about health.
Start today and in ninety days you answer the doctor's question by reading. Start in ninety days and those ninety days are gone. There is no way to log the past.
Yes. A caregiver link gives you a per-person today view: doses taken, missed, upcoming and extra, a same-day adherence figure counted against the slots that have already come due, the next scheduled dose, and her most recent feeling check-ins (src/lib/careSnapshots.ts). She sends you an invite, or you send her one and she consents on accept, so there are two invite directions and two separate consents (src/types.ts). Either of you can revoke the link at any time, and neither of you can delete the record of it (firestore.rules).
Yes. Care links are one-to-one and consented per person, so each sibling holds a separate link with its own permissions. A caregiver cannot read another caregiver's link, and invites cannot be listed, so nobody can harvest tokens or email addresses from the system (firestore.rules). Changes a manager makes to her cabinet or her workouts are written to an append-only audit trail: only the actor named on it can create the entry, nobody can edit or delete one, and she can read the entries about herself (src/lib/audit.ts, firestore.rules).
No, and that is deliberate. The assistant is instructed that it is not a medical professional and must never give dosing advice, diagnoses, or tell anyone to start, stop or change a medication (server.ts). On the proactive check-in, a regex screen runs after the model on three patterns (dose change, start or stop, diagnosis), and if the text trips any of them the reply falls back to the plain computed sentence (server-lib/concierge.ts). The reference catalog holds 651 compounds, 404 of them carrying an interaction or caution note and 57 carrying a separation rule, so you can flag something for a pharmacist to look at, which is not the same as being told what to do.
You photograph the label. The image goes to Gemini Vision and comes back as structured fields (src/lib/scanLabel.ts). You can photograph the barcode too, though the digits are read by OCR rather than by a live camera scanner, and you can always type them. A UPC is then resolved through a lookup chain of cache, Open Food Facts, USDA FoodData Central and NIH DSLD (server.ts). The reader is forbidden from converting units, multiplying label values, or treating the % Daily Value column as the amount (server.ts).
Yes, with the logDosing permission. A caregiver with that permission can create, update and delete dose logs, feeling logs, sleep logs, food logs and journal entries on the linked account (firestore.rules). A one-off different amount is recorded as a multiplier with a reason and never rewrites her standing schedule (src/lib/titration.ts). What you cannot do is quietly change who a record belongs to: every update rule asserts the profile and owner ids are unchanged (firestore.rules). Worth knowing: dose and feeling entries a caregiver makes are not currently written to the audit trail, which today covers cabinet and workout changes only.
No. A note you type while viewing her account is filed under you, tagged with her profile id as the subject, and the confirmation card tells you that before you apply it (src/lib/journalOwner.ts). This closed a real leak found on 2026-08-16. Journal entries store the writer's own words verbatim rather than a paraphrase (server.ts), and are treated as observations rather than facts, so a suspicion in a note is never presented as a conclusion (server.ts).
It is not HIPAA compliant. It is a consumer wellness product and not a covered entity today (firestore.rules). The honest version: everything a signed-in account logs is stored in Firestore on Google Cloud, assistant turns send a bundle of that person's health data to Gemini for the reply, truncated only past 400,000 characters (src/App.tsx, server.ts), and platform admins have cross-account read access by design and never write access (firestore.rules). Advertising pixels receive three standard event names and nothing about medications, doses, feelings or profile contents (src/lib/analytics.ts).
A cabinet of 25 items, 60 label or barcode scans a month, and 40 assistant messages a day, with no card required (src/lib/limits.ts). Care links, push reminders, the calendar export and the audit trail are not metered. Those free limits were raised on 2026-08-15 specifically so a real week of use fits inside the free tier (src/lib/limits.ts). Paid tiers lift the cabinet and scans, and every tier keeps an assistant ceiling, 400 messages a day on the paid plans, because an unbounded assistant is an unbounded bill (src/lib/limits.ts).
WorldsBestTracker is a record-keeping tool. It is not a medical device, it does not diagnose,
and it does not tell anyone what to take. Always talk to your own clinician about your treatment.
Home ·
Demo ·
Privacy ·
Terms ·
[email protected]