Skip to main content
Back to thoughts

What 'simple' actually means in app design

#product-design#philosophy#noted

Every app landing page says the same thing: "Simple. Intuitive. Easy to use."

It's meaningless. It's what you say when you don't have anything real to say.

I've been building software for years, and I've learned that "simple" is one of the most abused words in tech. So let me tell you what it actually means - and what it doesn't.

Simple is not lazy

A lot of apps are simple because their creators didn't finish them. Missing features aren't simplicity. They're just missing features.

If your notes app can't sync, that's not minimalist design. That's a bug you're marketing as a feature.

Simple means you thought about every possible feature, understood why someone might want it, and then deliberately chose not to include it. That's different from never thinking about it at all.

Simple is not easy

Building simple software is brutally hard. Every feature you remove creates edge cases. Every decision you skip means users have to make it themselves.

When we built Noted, we spent weeks on the input field. Just the input field. How do you let someone type "big salad" and turn that into a reasonable calorie estimate? How do you handle "coffee with oat milk"? What about "leftover pasta from last night"?

The user sees a text box. They type words. They get a number. Simple.

Behind that simplicity is a mountain of complexity we absorbed so they don't have to.

The simplicity test

Here's how I evaluate whether something is actually simple:

Can a stranger use it in 10 seconds? Not after a tutorial. Not after reading the FAQ. Right now, with no context.

Does it work offline? Requiring an internet connection for basic functionality is complexity you're pushing onto the user.

Does it need an account? Every login screen is friction. Every password is cognitive load. If you can avoid it, avoid it.

Can you explain it in one sentence? "Log what you eat by typing it." "Get a fake phone call when you need an exit." If you need a paragraph, you've already lost.

The feature trap

Product managers love features. Features are easy to measure. You shipped 12 features this quarter. Good job. Here's a promotion.

But features are debt. Every feature needs to be maintained, documented, and supported. Every feature adds cognitive load for users. Every feature makes the next feature harder to add.

The best apps I've ever used have remarkably few features. They do one thing. They do it perfectly. They stop.

This requires saying no constantly. No to users who want "just one more thing." No to investors who want competitive feature parity. No to your own ego when you have a clever idea.

No is the most important word in product development.

Complexity is easy

Anyone can build a complex app. Just keep adding features. Keep adding settings. Keep adding options for every edge case.

You'll end up with something that technically does everything and practically does nothing. Something that requires a manual. Something that makes users feel stupid.

This is the default outcome. This is what happens when you don't actively fight against it.

Simplicity is a choice

Every simple app is simple because someone decided it would be. Someone looked at the feature request and said "no." Someone deleted the settings page. Someone chose to absorb complexity instead of passing it on.

At While True Love, we have a rule: if a feature requires explanation, it's probably wrong.

Not "needs better documentation." Wrong. The feature itself is wrong. Go back and redesign it until it's obvious.

This is slow. This is expensive. This is why most companies don't do it.

What we actually ship

Our apps are small. Noted is under 10MB. Call Me Angela is under 5MB. They launch instantly. They work offline. They don't ask for accounts.

They're missing features that competitors have. On purpose.

Because every feature we don't build is complexity we don't pass on to you. Every setting we don't add is a decision you don't have to make. Every option we remove is cognitive load we absorb.

That's what simple actually means.

Not lazy. Not incomplete. Not "MVP."

Simple means we did the hard work so you don't have to.

All thoughts