Fast, on Purpose

Every product page on the internet contains the word “fast”. It sits somewhere between “secure” and “trusted by teams at”, and it might be the most promised, least kept word in software.

We use the word too. It is one of the four things we say we build around — focus, privacy, speed, honesty — and we have already written about focus and privacy. So here is the speed one, and what the word means when we use it.

Speed is decided early

The usual story is that performance is something you do at the end. The product gets built, somebody runs a profiler, images get compressed, and the word “fast” becomes true.

We have never seen it work that way. By the time the profiler runs, the speed has already been spent or saved — in the choice of framework, in how much JavaScript ships to the browser, in whether the first useful thing on the screen waits for a network call before it can appear. Optimization recovers milliseconds. Architecture decides seconds.

So speed is a day-one decision for us, the same as scope and data handling are.

Every product is fastest on launch day

Left alone, software gets slower. Features arrive and nothing removes itself. Dependencies update. Someone adds a two-line script that seems harmless. Six months later, the app that opened instantly opens eventually, and nobody can say exactly where the speed went.

Staying fast is therefore not maintenance in the casual sense. It is an active refusal, repeated with every release. We treat performance as a budget that resets each time we ship: if a change spends the budget without paying for it, the change gets smaller or it does not go out.

What it looks like

The principle is easiest to see product by product.

Utiliify is a utility toolkit, and a utility only earns its place by beating the workaround — the terminal command you half remember, the search result buried under ads. It works offline and searches as you type, because a tool that needs a round trip to find a Base64 decoder has already lost to the address bar.

ICE5e runs at a table, in real time, while the whole party waits. When the DM asks for your armor class, the answer should not come with a loading state. What a session needs is ready before it is asked for.

NotedCLI is local-first, which we chose for privacy and would choose again for speed. There is no network between your keystroke and the character appearing on screen. Typing that waits on a server is not typing; it is correspondence.

The Recipe Book lives in kitchens — hands occupied, screen propped against the flour, clock running. You change the servings and every amount rescales, including the ones written into the steps, before your attention returns to the pan.

Remote Rituals is a party game played over a video call. Comedy has timing, and lag is not timing. The game has to keep up with the room.

And MailChrono is the honest exception. It fetches email in real time and stores nothing, which means the first load is slower than a client with a synced archive would be. We knew that when we chose it. Speed is a pillar, not the only one, and when it loses to another principle we would rather say so plainly than quietly reverse the trade.

Where we build shapes what we ship

We build from South Africa, and that matters here. Metered data is normal, and the median device is not this year’s flagship on fiber. A page that assumes both is not neutral — it is a page that works well for a shrinking few. Every kilobyte we ship is somebody’s data plan.

So we test the way the median visitor arrives: a mid-range phone, a throttled connection, a cold cache. If it is fast there, it is fast.

What it costs

Being this strict about speed has a price, and we will state it the way we did with privacy.

It costs convenience. The heavy framework everyone already knows. The analytics script that answers questions nobody has asked yet. The feature that only works as a round trip. Some things ship later than they otherwise would. Some do not get built at all, because they cannot be carried at the weight we are willing to send over the wire.

We think it is a good trade. A tool that is focused, private, and honest, but takes four seconds to open, is still — at the exact moment it matters — in your way.

The point

The goal of every AveFrame product is the same: you think about your campaign, your dinner, your inbox — not the software. A tool that responds instantly disappears, and disappearing is the entire job.

That is what we mean by fast. It is not a claim we make on launch day. It is a promise we keep on purpose, every time we ship.

— The AveFrame Team