Barbara·4 min read

Small problems that deserve great software

A recipe archive, a basement washing-machine rota, a garden calendar: why the most useful apps are often built for one person, and how to build yours.

Yes, you can build an app just for yourself, and it's often the most useful kind of app there is. The problems worth solving in daily life are usually small, specific and shared by very few people: a family recipe archive, a rota for one shared washing machine, a calendar for one garden. No company will build those apps, because the market for each is one household. That's exactly why we built Leanfinit, and why our blog is full of them.

The long tail of problems nobody builds for

Software companies look for problems millions of people share. That leaves an enormous number of real problems unsolved, each owned by one person, one family or one small group.

These problems look trivial from outside. From inside, they're the things that cause friction every week: the shared chore nobody remembers, the medication a parent keeps mixing up, the spending that only makes sense when you see it laid out a certain way. People solve them with paper, group chats and spreadsheets that only their author understands.

We think these problems deserve the same quality of software as the big ones. Not a template that's close enough, but a tool that fits.

A tour of apps built for one situation

The stories on our blog each start with a single situation. A few examples, to show the range:

A family recipe archive. Nonna's Abruzzo recipe archive is about keeping a grandmother's recipes in one place.
A shared washing machine. Washing machine slots for a basement in Lisbon is about one shared machine and the neighbors who need to take turns.
Spending you can see. A spending heatmap diary shows where money goes, day by day, as a picture rather than a list.
Sleep, counted honestly. Sleep debt tracks the gap between the sleep you need and the sleep you get.
A cycle almanac. Cycle almanac is a private, personal view of a monthly cycle.
One garden's calendar. A seasonal garden calendar follows what to sow and tend, season by season, for one garden.
Kitchen math. A recipe scaler changes quantities for the number of people you're cooking for.
Bills on a calendar. A bill due calendar puts every due date in one view.

None of these would make sense as a product in an app store. Each makes sense as a tool for the person who needs it.

What these apps have in common

Look across the stories and a pattern shows up.

They start with one sentence. Each begins with a situation, not a feature list. A line like "my grandmother's recipes are scattered across notebooks" says more than a list of screens, and the features follow from it.

They use the owner's own words. Field names, categories and labels come from how the person actually talks. Nobody else would name the categories that way, and that's the point.

They're small. Each does one job. Small is what makes them fast to build and easy to keep using.

They're private by default. Leanfinit apps keep their data on the device, with no backend by default. That matters when the subject is health, money or family.

Why we publish these stories

During our beta, people who sign in and send prompts agree that their prompt and the app built from it may be shown on the blog, without their personal data. That lets us show real situations instead of invented demos.

The stories do three jobs. They show what's possible to someone who has never thought of building an app. They give prompt examples you can borrow. And they remind us, as a team, who we're building for: not an average user, but a specific person with a specific problem.

How to find your own small problem

If you're not sure what you'd build, these questions usually surface something:

1What do you track on paper, in notes or in a spreadsheet today?
2What do you explain to someone in your household more than once a month?
3Which app do you use for one screen only, and wish it did that screen differently?
4What would you hand to a parent, a neighbor or a new colleague if it existed?

The answer to any of these is a good first prompt. Write it as the situation, in your own words, and add the two or three things the app must show. Our post on how our best builders describe an app goes through the patterns that work.

Small first, then grow

You don't need to design the whole app up front. Start with the smallest version that removes the friction, use it for a week, and describe what's missing. An app can grow one request at a time.

That's what our slogan means: start lean, grow infinite. If you want the longer version of why we think this is the future of software, read Why we're building Leanfinit.

Describe your small problem in the studio: studio.leanfinit.com.