1Money: expense tracker budget reviews

Users deliberately choose manual entry precisely because nothing leaves for a server and the app never touches a bank account. This segment isn't looking for automation — it's fleeing from it, and pays and stays for years for the feeling that the money data lives only on their phone.

"So fast to use, so little fuss" — the app wins not on features but on logging a spend taking seconds with an uncluttered UI. That's what turns tracking into a daily ritual instead of a chore dropped after a week: users report using it "every day" for 5-6 years.

Beyond simple entry the app handles credit accounts, debts with lend/repay mechanics, subcategories and fully editable transactions. It's this depth-with-simplicity combination that retains people who "tried 17 money managers" — they want flexibility without overload, and few apps strike that balance.

Local-only storage with no mandatory login is the flip side of privacy: switch phones, reinstall, or hit a glitch and years of data vanish because the backup had to be made by hand. Users lose 4-6 years of records and realize the privacy "convenience" was the trap. It's a structural product risk: loyalty is built over years and collapses in a single day with no warning.

For a large share of payers, sync was the entire reason to buy — a shared budget with a partner, access from two phones. When sync was removed the app became instantly "useless" to them and they left for competitors; when it returned, the same people came straight back. It reveals what actually holds the top segment: not categories, but data following the person across devices.

For expats and anyone spending across currencies, conversion is the core of the value. After an update old transactions were retroactively recomputed as 1=1 (1 won = 1 euro) and all accumulated stats became meaningless. The nature of multi-currency tracking is that an FX error isn't local — it retroactively poisons every past report, fixable only by re-entering every transaction by hand.

The free tier doesn't cap an advanced feature — it caps a basic growth moment: the instant a user wants a second account or second category (i.e. actually starts budgeting), they're blocked. The limit sits right at the move from "tried it" to "built it into life," so it reads as confiscation of a working tool rather than an honest demo boundary.

A bug broke the very point of tracking: a spend reduces the account balance but never lands in the category list/history, and sometimes entering an expense silently turns into a transfer between accounts. For a tracker this is fatal — the user stops trusting the numbers because balance and analytics diverge, and the app's whole value is that they reconcile.

Happy 4-5★ users keep hitting the same ceiling: you can't attach a receipt or invoice photo to a transaction. This isn't a gripe but a signal of the next job-to-be-done — people want the tracker to replace the shoebox of receipts, not just the numbers. Closing this gap would turn the tracker into a proof archive and raise the switching cost.

Loyal users actively recommend the app to friends — but the friends can't find it: it doesn't surface in store search, as if shadow-banned. For a product that grows almost entirely on word of mouth rather than ads, this kills the very distribution engine: the referral exists but can't be acted on.

The UI overhaul hit exactly what was the strength: fonts grew larger, less fits on screen, the same actions take more taps, and scrolling appeared where everything used to be visible at once. When a product lives on "see your budget at a glance" and fast entry, cosmetics that break information density feel like degradation, not a refresh.

Recurring transactions are implemented and valued, but users ask for the next layer: a confirm button for a scheduled payment, future recurrences shown on the timeline, and a calendar view. Without these the automation stays "blind" — you can't quickly verify charges matched the plan, yet predictability of recurring spend is the whole reason to set them up.

The budget is tied to a calendar month/week, but on a job change or non-standard payday, shifting the start date breaks already-closed past months. Users ask to "lock" prior periods and set an arbitrary interval. For a money app this is a meaningful segment — freelancers and job-switchers whose real financial cycle doesn't line up with the 1st of the month.

Even satisfied users go years without a single reply to support emails. For an app where data is local and there's no account, missing support is especially dangerous: when something breaks (restore, FX bug, missing transactions) the user has nowhere to turn and the only exit is a competitor. Support silence turns any minor problem into a churn trigger.