Why we build small apps that do one thing

Every app on your phone started life as a simple idea. Then it grew. A feature here to answer a competitor, a tab there to lift engagement, a banner to push whatever the growth team measured last quarter. Five years on, the weather app wants a social feed and the notes app wants your location. We build in the other direction.

Pocketleaf makes small apps that each do a single thing. Not a suite, not a platform, not a super-app. One tool, one job, done as well as we can do it. That sounds modest. In practice it's the hardest discipline we know.

Big apps forget what they were for

Apps bloat not out of laziness but out of incentive. A product that has to grow forever eventually runs out of core improvements, so it annexes adjacent jobs. The calculator adds a currency converter, then a news card, then an account. Each addition is defensible on its own. Together they bury the one screen you opened the app to see.

Bloat isn't only visual clutter. Every extra feature is more code to break, more settings to misread, more permissions to grant, and more of your attention spent navigating instead of doing. A tool that does ten things is rarely good at the one thing you need right now.

Constraint is the feature

When an app is allowed to do only one thing, every decision gets easier. There's a right answer to 'should this button exist?' — does it serve the single job, or not. The empty states, the first launch, the fastest path from open to done all get the attention a sprawling product spreads too thin.

That focus shows up as things you can feel:

• It opens faster, because there's less to load and less to decide.
• It asks for less — fewer permissions, fewer fields, often no account at all.
• It's easier to trust, because you can see the whole of what it does.
• It stays out of your way, then gets out of your way when you're done.

What 'one thing' actually means

One thing isn't one feature. Everfield's single job is to make a habit streak feel worth protecting — that needs a grid, a streak counter, reminders and an export, but all of them serve the one job and nothing else sneaks in. The test isn't feature count; it's whether you could explain the app in a sentence a friend would repeat.

So we start every app by finding a single real annoyance worth fixing, design every screen before we write code, then cut until only the essential remains. Ship small, polish deep.

The trade-offs we make on purpose

Small apps give some things up. There's no all-in-one dashboard, no cross-app account, and — for most of our apps — no cloud sync yet, because keeping your data on your device is worth more to us than the convenience of a server. We think that's the right trade.

A tool you can trust, that does one thing beautifully and then leaves you alone, is worth more than a suite that does everything and owns your attention. Ten small apps, each its own world, each with a single job — that's the whole idea, and the reason none of them will ever ask to be your everything.