LifeWell

The year somebody in a house is pregnant is often the year somebody else in it is managing blood pressure.

Those two facts sit in different applications built for different people, and neither one knows the other exists.

One app assumes a woman in her twenties. Another assumes a new parent. A third is designed around somebody with a long-term condition and a clinician waiting for numbers.

A household is all three at once.

So the records scatter across accounts and phones, and the view that would actually help — everyone, over years, in one place — is the one nobody ends up with.

LifeWell runs on a single Firestore backend on the free tier, with no server that has to be kept alive for it to work.

That constraint matters more here than anywhere else in this portfolio. A health record you cannot open in three years is not a record, and a tracker that stops paying for itself stops existing, taking the history down with it.

Keys never sit in the browser bundle. The calls that need one go through a Cloudflare Worker token proxy, so the secret stays on the server side of that line.

45+ health tools cover vitals, water, medications, exercise, sleep and nutrition.

Periods and fertility live in the same product as baby milestones, because in a real household those are frequently the same year.

Around them sit people, memories, notes and a community layer, so a reading has somebody attached to it instead of being a row in a table.

One product, two surfaces.

It runs as a PWA and ships as a Capacitor Android build on Google Play.

200+ routes and 10 languages, Arabic with right-to-left layout among them. Per-route static HTML with JSON-LD makes the public pages readable to a crawler, and there is a public documentation site alongside the product.

Two of the rules this whole practice now works to were paid for on this project.

The first is the central logger. Every direct console call came out across 95 files and the linter refuses new ones, which is a refactor that produced no feature any user will ever see and closed a class of leak that only shows up in production.

The second came from the Play Console.

A camera permission the app did not need was in the merged manifest, and the submission was rejected for it. Every Android build since is audited against its merged manifest rather than against the one written in the repository, because those two are not the same document.

Shared family records raise a question a single-user tracker never has to answer: who is allowed to see whose. That is a security-rules problem rather than a screen, and it is the part of this product that is easiest to get quietly wrong.

Ten languages is ten times the surface every new string has to cross.

And a tracker only ever knows what somebody typed into it. LifeWell keeps that record and shows it back over time. It does not interpret the record, gives no medical advice, and nothing in it is a diagnosis.

There is no iOS half. There is no Apple Developer account behind this work, so Android and the web are the two surfaces it has genuinely reached.

The history is the product. Everything above exists so that it is still openable in five years, on a phone I will never see, by somebody who has never heard of me.