Design · Aug 23, 2026
Why there’s no counter in the corner
Every tool teaches you something through what it puts on screen. A credit counter teaches rationing, which is why this voice studio does not have one.

In 1891 a German engineer named Wilhelm Bruhn built a device that attached to a horse-drawn cab and displayed the fare as it accumulated. He called it the Taxameter, and it is the reason we say taxi. Drivers hated it at first, on the reasonable grounds that it removed their ability to price a journey by how lost the passenger looked. What nobody seems to have anticipated is what it did to passengers. Put a number where somebody can see it climbing and they will start driving the route themselves from the back seat. They take the short way even when it is the worse way. They stop asking to make one quick stop. Nothing about the journey changed. A number became visible, and behaviour rearranged itself around it.
That is the thing about a counter. It is presented as information, and it functions as instruction.
What a credit counter teaches
Watch someone work in a tool with an allowance in the corner and you can see them learning, take by take. They stop re-rendering the paragraph a fourth time to hear whether the pause lands better. They stop running the whole chapter to check pacing, and check one page instead, and consequently miss the thing that only shows up across a whole chapter. They start estimating before generating, which sounds like discipline and is actually a small tax on curiosity, levied at the exact moment curiosity would have been most useful.
None of this is the design team’s fault, and it is not usually anyone’s intent. If a product’s costs are metered, showing you the meter is the honest thing to do. Hiding a counter that is genuinely counting would be considerably worse than displaying it. The problem is upstream of the interface.
“You cannot design away the anxiety of a meter. You can only stop having one.”On the counter we removed
So Usovo does not show you a usage counter, and the reason is not restraint or minimalism. There is nothing to count. The work happens on hardware you already paid for, which means there is no unit cost for us to pass on and therefore no honest number to display. A counter here would be decorative anxiety.
What we do show is anything that helps you plan rather than ration. A long render tells you how long it will take before it starts. A queued job tells you its position in the line. The distinction we try to hold is between a number that answers when will this be done, which is useful, and a number that answers how much of this am I allowed, which mostly just teaches you to want less.
· · ·

Next note →
The cloud charges rent. Your Mac already paid.
Essays · 5 min read
