All workEssay 10 / 12

Objects for everyday digital life

Less product.
More done.

Shorten a link. Share a code. Finish a calculation. Small tools have a demanding brief: earn their place in a few seconds, then let the person get on with their day.

Object 01 / A useful boundary

Give the tool a small, complete job.

A long destination needs a shorter link. A piece of information needs a scannable form. A repeated calculation needs a dependable place to happen. These are modest jobs, but they are specific enough to reveal unnecessary friction very quickly.

I built focused utilities around that specificity. Direct entry, the smallest useful input, visible validation and an output someone can carry away. The scope is narrow; the experience still needs to be complete.

That distinction is easy to miss. A tool with one successful button click is not finished if invalid input, an unavailable dependency or a failed copy action leaves the person stranded. Small products make these rough edges especially visible because there is so little else to distract from them.

A tiny text utility
a-useful-idea

Runs on this page. Nothing is sent to a server.

Illustrative example · not live product data
Object 02 / The handoff

Design the moment someone leaves.

A utility earns its value when its result can move into the next task. Short links, QR codes and shareable artifacts need a clean handoff. Copying, opening or carrying a result to another device should feel like the natural end of the interaction.

That makes portability a design concern from the beginning. The output should not require someone to understand the tool’s internal structure. Status should distinguish a result that is ready from an operation that has merely started.

Local-first location behavior raises a different kind of handoff. Sharing something temporary should be a deliberate decision. A convenient link must not quietly turn information intended for a moment into an indefinite record.

Object 03 / Restraint

Let every extra step argue for itself.

An account can add continuity, but it also adds friction and responsibility for retained data. Preferences can support different needs, but they can obscure the main job. A broader feature set can make a product harder to explain.

I try to ask what a new feature contributes to the task someone came to finish. Sometimes the answer is strong. Sometimes it is only that the feature would be interesting to build. Keeping those motives separate helps preserve the utility’s shape.

Narrow scope does not remove questions about maintenance or sustainability. It makes them easier to state. What needs to keep working? What data needs to exist? What would make someone trust this tool next time?

The small text utility on this page illustrates the whole loop: enter a title, inspect a result, copy it and continue. The output remains visible if the browser refuses clipboard access. That fallback matters because permission to perform a convenience action is not permission to make the result disappear when it fails.

Even this tiny example asks for clear limits. It creates a portable string; it does not reserve a web address or guarantee that the string is unique somewhere else. Naming the operation accurately keeps a small convenience from promising more than it performs.

Small software deserves serious care precisely because it asks for so little attention. The goal is a useful interaction that leaves very little residue.

CONTEXT / LINKS

Related work & references

Selected public entry points and related portfolio pages. A company website or profile is context, not a claim that private source code is available.

Scope, context & further questions

Supported by public utility, storage, scanner, calculator, short-link, landing, and local-first location work.

  • Product boundary: Single job. Each utility is framed around one primary outcome.
  • Default output: Shareable. Links and scannable artifacts move cleanly across devices and contexts.
  • Sensitive state: Local-first. Temporary location behavior prioritizes device control over central collection.

Questions I am still working through

Which small tasks deserve a dedicated tool instead of another feature inside a platform?

Tasks with a clear input, a repeated transformation, a portable result, and little need for shared state are good candidates. A dedicated tool is especially useful when platform context would add more ceremony than value.

The threshold changes when distribution, identity, or collaboration become essential to the task.

Can useful utilities remain sustainable without attention-harvesting mechanics?

Yes, when scope and operating cost stay intentionally small and the product has an explicit support model such as sponsorship, paid advanced features, studio funding, or strategic reuse of shared infrastructure.

Each utility still needs a deliberate answer for maintenance once novelty fades.

Stories, products & useful placesEsc to close