DEV Community

Cover image for Every App Eventually Becomes a Dashboard. Please Make It Stop.

Every App Eventually Becomes a Dashboard. Please Make It Stop.

NorthernDev on October 29, 2026

Every good app starts with a lie. “We’re going to keep this simple.” I love that sentence. So optimistic. So innocent. So completely doomed....
Collapse
 
leob profile image
leob •

Haha yes this gave me a good chuckle, but of course basically you are right ...

Collapse
 
the_nortern_dev profile image
NorthernDev •

Hahaha, I’ll take that 😄
I was aiming for “funny because it’s painfully familiar.”

Collapse
 
ingosteinke profile image
Ingo Steinke, web developer •

Version 4.7 Added nothing. Product still works.

That's called maintenance or security update. I also prefer this kind of changelog to the feature creep you described. Thanks for the post. I even found the sloppy cartoons quite funny.

Collapse
 
the_nortern_dev profile image
NorthernDev •

Haha yeah, fair point 😄
Give me maintenance over feature creep any day.

And glad the cartoons made you laugh haha.

Collapse
 
anas_issath profile image
Anas Issath •

“A Getting Started panel despite me using the product for two years” is painfully accurate. And “Explore what? I came here to rename a file” made me laugh out loud. Feature creep bringing a toothbrush and then furniture is the best description of it I’ve read. Some apps really just need to do their one job and let us leave.

Collapse
 
the_nortern_dev profile image
NorthernDev •

Haha, I’m glad those landed 😄
That “Getting Started” panel is everywhere. At some point i’d love an app to recognize me and just quietly let me do the one thing i opened it for.
And yeah, some software really should just finish the job and let us leave.

Collapse
 
sizzlebop profile image
Jessica Doering •

I feel personally attacked by this post! 😂 I'm absolutely guilty of starting a project with the intention of keeping it simple, then thinking "oh, but it would be nice if it could also do this..." and before I know it, my tiny little utility has grown into something completely different.

The worst part is that every individual addition seems perfectly reasonable at the time! It's only when you look back that you realize how far you've wandered from the original idea.

But I completely agree with your point. Sometimes an app that does one thing really well is so much better than one that tries to do everything. And as someone who builds a lot of little tools, I definitely need to remind myself of that more often.

Also, the line about feature creep bringing a toothbrush and moving in is great. Too accurate!

Collapse
 
the_nortern_dev profile image
NorthernDev •

Haha, this is exactly how it happens 😄
Every little addition feels harmless on its own, and then one day you look at the project and barely recognize the thing you started with.
Glad the toothbrush line landed too haha. Feature creep is way too polite at the beginning.

Collapse
 
johnnylemonny profile image
𝗝𝗼𝗵𝗻 •

"The dashboard that exists because the product no longer knows what its main job is" - that hits way too close to home.

Half the time, slapping four metric cards and a donut chart onto the home screen is just a way to justify a "Pro" pricing tier or show stakeholders that the team shipped something this quarter. Showing restraint and letting a tool have clear edges; where you open it, do the task, and leave -genuinely feels like the ultimate luxury in modern software.

Collapse
 
the_nortern_dev profile image
NorthernDev •

Yeah, I like that way of looking at it.
If the metric doesn’t actually change what the user does next, it’s probably just decoration.
Sometimes a good default or a simple “here’s what to do” is way more useful than another chart.

Collapse
 
shiro20009 profile image
Shiro Satoshi •

Impressive, The line that really hits is “Sometimes the best feature is the one that never got built.”

The best software respects the user's time. It helps them accomplish what they came to do, then gets out of the way. Simplicity isn't a lack of ambition; it's the discipline to protect a product's original purpose as it grows. I will keep it in my mind. Thank you!

I'd love to see more release notes from you.

Collapse
 
the_nortern_dev profile image
NorthernDev •

Thanks, really appreciate that 😄
“Gets out of the way” is exactly what I like in good software too.

And yeah, maybe I need to start writing more brutally honest release notes haha.

Collapse
 
abolmute profile image
abolmute •

I was checking a routine management app today that it was exactly like what you described.
I've seen ads.
I've seen product tour.
even there was a fucking subscription plan that disabled the ads and could give you more analystics.
man, they are even selling dashboards

I think the most productive apps right now can be apps that you can choose for the style of it.
if you want dashboard it gives but you are not forces.

Collapse
 
the_nortern_dev profile image
NorthernDev •

Yeah, exactly 😅
Paying to remove ads and unlock more analytics in a routine app is basically the whole article in one product.
I like your idea though, give people the dashboard if they want it, but don’t make everyone live in it.

Collapse
 
robertpaschal profile image
Odinaka Robert Nnamani •

The houseplant one did it for me. Weekly moisture retention against last quarter is exactly how a simple app dies.

Collapse
 
the_nortern_dev profile image
NorthernDev •

Hahaha, I’m glad that one landed 😄
Give it another year and the plant app will have team workspaces and a premium analytics plan.

Collapse
 
robertpaschal profile image
Odinaka Robert Nnamani •

team workspaces for a plant app, then a premium analytics plan for watering schedules. that escalation writes itself.

Collapse
 
dasheck0 profile image
Stefan Neidig •

You know that this post needs? A dashboard!

Collapse
 
the_nortern_dev profile image
NorthernDev •

Hahaha, obviously 😄
I’ll add one with charts showing how many dashboards the post has prevented.

Collapse
 
jamescarter11 profile image
James Carter •

Hello... Nice, thx...

Collapse
 
alexshev profile image
Alex Shev •

The dashboard is often a symptom that the product has stopped making a decision for the user. Before adding another card, I would ask which action changes because of the metric. If the answer is unclear, an alert, default, or short explanation may be more useful than another chart.

Collapse
 
fintechrailsdigest profile image
Fintech Rails Digest •

the opening line is accurate to the letter: every dashboard I have seen arrive as a feature first arrived as a favor to somebody. the pattern that decides the outcome is who can say no and whether they are in the room when the request lands. when one owner holds the roadmap, dashboards lose; when the decision happens in a meeting the builder was not invited to, they win by default. the question that predicts it is not code quality, it is whether "what does this replace" has an answer before the ticket is accepted.

Collapse
 
mudassirworks profile image
Mudassir Khan •

the roles and permissions step is where a dashboard really locks in, because once enterprise customers have a permission model you can never remove the screens that explain it. we kept one rule that helped: every new panel needs an owner and a usage number after 60 days or it gets deleted. unglamorous but the panel count stopped growing. do you think a hard cap on top level nav items would work, or does product just route around it?

Collapse
 
paul-s profile image
Paul-S •

A product that knows where it ends is rare. Every new feature should justify the extra attention it demands from users.

Collapse
 
emilianooo profile image
Emiliano White •

the 'it asks if it can stay for the weekend, then brings a toothbrush' bit got me. building my own small stuff, the hardest part is saying no to the sidebar i already want to add.