Notes on building small tools

Small tools work when they respect the shape of the annoyance. They do not need a big surface area. They need a clear loop, a clean handoff, and enough taste to avoid becoming another dashboard.

The best version usually starts as a narrow tool that does one job without asking the user to adopt a whole new worldview.

Keep the loop short

The useful question is not "how large can this become?" It is "how quickly does this remove the drag?" That tends to produce better defaults, fewer settings, and more honest product decisions.

Let the tool stay small

Some things want to become platforms. Many things are better as sharp little utilities. Knowing the difference is part of the craft.