A product built for the way life actually stores itself.
LifeRoster began as a simple observation: the practical records of a life are scattered across tools that were never designed to hold them, and installing nine more apps does not fix it.
Product story
Spending lives in a banking app that cannot say why. Health readings live in a notebook. A vehicle's service history lives in the glovebox. Money split on a trip lives in a group chat where everyone remembers a different number. Each has a dedicated app, and none of them share a workspace.
The gap was never storage — it was structure. A note app stores text, and text cannot produce a balance, a trend or a consumption figure. LifeRoster stores records with real shapes, which is what lets those figures be derived instead of maintained by hand.
Three commitments shaped everything after that. It had to work offline, because the moment you record a meter reading is the moment you have no signal. It had to be private by default, because health and financial records are the most sensitive data most people own. And it had to stay smooth on a 3–4 GB Android phone, because that is what the people it is built for actually carry.
Today it runs on web, Android and iOS in 23 languages including right-to-left, with 11 modules covering everything from a blood-pressure journal to a split-bill ledger.
Engineering philosophy
Rules that are enforced, not aspired to
Every one of these is checked automatically rather than left to discipline.
Derive, never duplicate
A ledger balance comes from its entries. Electricity usage comes from consecutive readings. A bill's payment history is the spending it produced. Wherever a number is worked out rather than kept alongside its source, two figures can never drift apart.
Never destroy your data
Updates only ever add; discarding records to make a change convenient is prohibited outright. Records with history refuse to disappear silently, and something deleted on one device can be recovered from another.
Measure before optimizing
Four rounds of performance work targeted a bottleneck that measurement on real hardware later proved was not the bottleneck. The ranking was wrong until something other than intuition produced it.
Say what you will not claim
Deciding the limits of the product's security in advance — and writing them down next to the work — is what makes it possible to describe it publicly without exaggerating a single sentence.
One system, not ten
Shared building blocks over one-offs, four required states on every surface, and one interaction model across every module. A one-off button size is a rule violation, not a judgement call.
Design for the cheapest phone
Smoothness on modest hardware is treated as correctness rather than polish. That single constraint rejected several designs early that would have been perfectly fine on a flagship and quietly slow everywhere else.
The maker
Created & engineered by Ahtasham
LifeRoster is designed, built and maintained by one person — the product decisions, the design system, the security work and the performance programme included. This site exists to show the product rather than the résumé, so the deeper detail lives in the case study rather than here.
See LifeRoster in action.
Open the app and start with whatever part of your life is least organized right now. It works offline from the first tap.
- Use it nowOpen the web app
- Coming soonGoogle Play
- Coming soonApp Store