Hi devs 👋
When I started building free tools, I made a lot of assumptions.
I thought users needed more features.
More options.
More flexibility.
So I added things like:
• extra settings
• multiple formats
• advanced controls
I believed it made the tools better.
But when people actually used them, something surprising happened.
Most users ignored those features.
They used the simplest option.
Finished the task.
And left.
They didn’t want control.
They wanted speed.
They didn’t want customization.
They wanted clarity.
One click.
One result.
Done.
That’s when I realized:
Builders like features.
Users like simplicity.
Since then, I focus more on removing friction than adding functionality.
Curious —
what’s a feature you built that nobody used?

AllInOneTools

A developer reflects on building free tools with too many features, only to discover users consistently chose the simplest option and ignored advanced controls. The key insight: builders crave features while users crave simplicity, speed, and clarity. The lesson learned was to focus on removing friction rather than adding functionality.

What I Thought Users Needed vs What They Actually Used

I disagree with this. You have to remember that there are two types of users. Some people just want to save time and do something convenient, so a single button works perfectly for them. Others prefer to know what’s happening behind the scenes and want to configure settings that fit their specific needs. That’s why you’ll notice most apps have a switch for “Advanced” or “Expert mode” instead of offering only basic settings with little to no customization options.

Uh, WARNING ⚠️ This can easily lead to survivor bias.
Average behavior tells you about usage patterns, but not necessarily about value.
Not all users behave the same way, and some users may actually be far more important than the average… power users, loyal users, or people who teach others and amplify the product.
Good UX should keep things simple and fast for the majority (the happy path), but still allow deeper paths for advanced users who rely on the more powerful features.
This balance matters not only in software, but in many disciplines.
“Simple things should be simple. Complex things should be possible.”

One real example for me was adding multiple export options. I thought it was useful, but almost everyone used the default. Removing extra choices actually made the tool faster and easier to use.

That’s why creating a user-centered project is the best! Always get inside the shoe of your target audience before shipping a feature. Know what they need. When you at least get the general idea, you already have a good foundation to start building what matters.

This is a tough and nice process… I am init. Actually considering making a long beta to optimize the product like crazy… ;) Before launch. Personaes, interviews and all that…