Ten seconds or it will not be used
An expense tracker that takes a minute per entry gets abandoned in a fortnight. Amount, a tap, a two-word note. Everything else is optional and remembered from last time.
Where does the money actually go — and what, specifically, should I do about it?
Paisa started as a personal problem. Money was leaving the house every month with no record of why — a little to a delivery app here, a little in cash there, and nothing at the end of it but the feeling of being short.
Every tracker I tried wanted an account, a bank connection, and a subscription, and gave back a pie chart. None of them asked the only question that matters afterwards: why did you buy this?
So I built the one I wanted. It keeps the detail that makes a spend explainable, it keeps all of it on the phone, and it turns a month of honest entries into a ranked list of changes with rupee values attached. It is the app I use myself, every day.
Designed, built and maintained by Arham Ashraf
An expense tracker that takes a minute per entry gets abandoned in a fortnight. Amount, a tap, a two-word note. Everything else is optional and remembered from last time.
"Spend less on food" is not advice. "Cut Zepto from nine orders to five and keep ₹16,320 a year" is. If the app cannot put a rupee figure on a suggestion, it does not make it.
A brand-new month scores well on every metric by default. So the habit score stays blank until there is enough logged for it to mean something, and the savings estimate is capped at what you actually spend on wants.
No account, no server, no network request. Not as a privacy selling point but because an app that needs a connection to tell you your own spending is badly designed.
Plain HTML, CSS and JavaScript. No build step, no bundler, nothing to go stale.
Every donut, bar, heatmap and trend line drawn by hand in SVG.
One stroked 24px system. Not a single emoji anywhere in the interface.
The entire app, including the Android shell it runs inside.
The whole app is plain HTML, CSS and JavaScript with no framework and no build step. Editing a file and reloading is the entire development loop. That keeps it fast on a cheap phone and means it will still run in five years.
The launcher icon is generated rather than drawn: a rupee sign built from rectangles never looks right, so the real glyph is rendered from a font onto a canvas and composed into a squircle at every density the system asks for.
Four releases in, every one has kept its data. Same package, same signing key, same storage origin, with a migration step for anything a newer version added.
Free, offline, no account. If it does not tell you something true about your spending within thirty days, delete it.