I used to think I was uniquely bad at sticking with budgeting apps. Everyone around me seemed to have a system that worked — a spreadsheet they maintained faithfully, a YNAB account they updated daily, a Monarch Money dashboard they actually enjoyed checking. I tried all of them. I lasted, on average, eight days.
It took me an embarrassingly long time to realize that I wasn't the variable. The apps were. And the mechanism that killed every habit was the same across all of them: the backlog.
How the backlog forms
Day one: you log everything. Every coffee, every Uber, every grocery run. It feels good. You are the kind of person who tracks their finances.
Day three: you forget to log the lunch. You'll do it tonight. Tonight you forget. You'll do it tomorrow morning. Tomorrow morning the transaction has cleared and you sort of remember the amount but not exactly and the context is completely gone.
Day five: there are three unlogged transactions. The backlog has started. Each unlogged transaction is a small piece of guilt. The app has become associated with that guilt.
Day eight: you open the app, see the backlog, feel the guilt, and close it. You tell yourself you'll catch up this weekend. You don't. By day twelve, the habit is dead.
Why the backlog forms
The backlog forms because standard apps are designed for desktop-era usage patterns — a daily or weekly reconciliation session, sitting at a computer, going through bank statements. On mobile, this model fails. Mobile spending is continuous. Mobile logging, if it's more than two taps, happens inconsistently. The gap between spending and logging grows until the backlog is too large to feel worth addressing.
The apps' response to this has been better automation: automatic bank import, smart categorization, receipt scanning. These reduce the backlog by not requiring manual entry. But they also remove the moment of awareness — the 30 seconds of honest writing that makes the record mean something. Automatic import gives you data without understanding.
What's different about a text-only log
A text-only log has no backlog problem because there's nothing to reconcile. If you miss a transaction, you can log it an hour later with a note: "Forgot to log this — lunch at the Italian place, about $24, they were out of the thing I wanted so I ordered the pasta, it was fine." That's a valid entry. The information is less perfect than if you'd logged at the moment, but it's better than nothing and there's no guilt attached to the imperfection.
The text log receives whatever you give it, without judgment, without a reconciliation queue, without a growing sense of obligation. Which is why it keeps getting opened.
No backlog. No reconciliation. No guilt. Just type when you remember.