Every modern app ships with a dashboard. Charts, graphs, streaks, streak-freezes, gamification badges. The assumption is that data visualization = motivation.
I broke that assumption by accident.
What Happened When I Removed the Dashboard
I built Monee -- a budget tracker with no bank sync, no cloud storage, no accounts. But the design decision I didn't think about until users started responding? No dashboard.
There's a single view: your transactions. A simple list. You type in what you spent. You see the total. That's it.
I expected this to be a complaint. Instead, the users who came back (22 of them, 15.6% voluntary return rate, zero push notifications) told me something I didn't expect:
"I actually think when I enter stuff."
The Cognition Problem With Dashboards
Here's what a dashboard does to your brain: it summarizes. It compresses weeks of behavior into a pie chart. And your brain, given a summary, stops processing the details.
Researchers call this cognitive offloading. You delegate awareness to the tool. The tool becomes the one tracking your spending -- not you.
Manual entry without dashboards does the opposite. Every transaction requires you to:
- Remember it happened
- Decide it's worth logging
- Type the amount
- See it in context of everything else you logged
That's four deliberate cognitive acts. Four moments of actual financial awareness. A dashboard skips all four and shows you a pie chart instead.
What the Data (Such As It Is) Shows
I don't have a massive dataset. I have 22 return users, an average session time of 2:47 minutes, and zero push notifications sending them back.
But 2:47 minutes is meaningful. That's not someone who clicked by accident. That's someone who sat down, opened a tab intentionally, and typed in their purchases.
That's a person who is thinking about money.
The Dashboard I Deliberately Didn't Build
When I started Monee, I had a rough sketch of what it "should" be: monthly spend by category, a bar chart showing this week vs last week, maybe a little flame for days you stayed under budget.
I deleted all of it.
Not because I couldn't build it. Because every time I added a graph, I felt the app get weaker. The raw list of transactions was more honest. More confrontational. More useful.
A bar chart lets you rationalize. "Oh, I'm only 10% over on dining." A raw list of 23 restaurant entries this month doesn't let you rationalize anything.
The Counterintuitive Design Rule
Here's what I learned: friction in the right place is a feature.
Dashboards remove friction from reading your data. But the reading isn't the hard part. The hard part is making the decision in the moment.
Manual entry adds friction to recording. That friction is the product. That friction is why people come back.
Every budget app that removes friction from entry also removes the moment of awareness that makes budgeting work. They automate away the only part that matters.
Monee is free, forever, no account needed: monee-budget-tracker.vercel.app
The code is public. The data never leaves your browser.
If you've ever felt like a budgeting app was managing your data instead of helping you think -- that's the problem I'm trying to solve.
What's the most important feature you've ever removed from something you built?
Top comments (0)