Why the best utility apps should do exactly one thing in one tap

A utility app is not used the way it is demoed. Nobody sits down with a scorekeeper or a bill scanner and explores it. They open it mid-sentence, one-handed, with a friend waiting or a nurse about to walk back in, and they need one specific thing to have already happened. Everything else in the app is, in that instant, in the way.

Design for the moment, not the list

Feature lists are written in calm rooms. The moment of use is never calm. So the useful design question is not "what can this app do" but "what is the person holding the phone trying to finish right now, and how many taps stand between them and it."

Write the moment down first, literally. Someone just got handed a bill. Someone just parked at a trailhead. Someone is mid-hand at a card table and needs to add points to a stack. Then build backward from that sentence. Anything that does not shorten the path from launch to done is a candidate for a second screen, or for deletion.

This is why the first screen matters more than any other. It is not a lobby. It should be the thing itself.

Spend the tap budget deliberately

Treat taps as currency and give yourself a budget of about three for the primary action. Then notice where they are actually going. Most apps spend their whole budget before the user does anything: a splash screen, a sign-in, a permission prompt, a tour, a paywall.

Cut those and the budget goes to the work instead. No account is not only a privacy stance, it is a tap refund. So is a form that pre-fills what the phone already knows: the date, the location, the last thing you did.

The measure of a utility app is not how much it can do, it is how much of what it does you can reach without thinking.

Say no to the second job

The hard part is not designing the one-tap version. It is keeping it. Every successful narrow app attracts requests to become a broader one, and each request is individually reasonable. Fifteen reasonable additions later, the thing that made it good is buried three menus deep.

The discipline is to add depth without adding width: more capability behind the same first tap, rather than more first taps. A scorekeeper can grow statistics and history. It should not grow a social feed. A scanner can get better at scanning. It should not get a chat assistant.

The apps we build are narrow on purpose, they run on the device, and they are free, with no subscriptions, ever. That combination is not a coincidence: an app with nothing to sell you has no reason to put anything between you and the first tap.

The next decade of phone software will be full of assistants that can do anything, which will make the small, specific, instant tool more valuable, not less. Sometimes you do not want to describe the problem. You want the thing to already be open.

Browse the whole catalog on the apps index, or read more of how we think about building them in the blog archive.