Designing for offline: what changes when there's no spinner

Most software design systems assume network latency somewhere in the flow — a spinner while data loads, a skeleton screen while a request resolves, an optimistic UI hoping the server agrees with what it just showed you. Apeirogon doesn't have that excuse. If something feels slow, it's not the network's fault.

That's a healthy kind of pressure. It forced us to treat every interaction as something that should complete in the time it takes to notice it happened, not the time it takes to be polite about a loading state.

It also changed how we think about first launch. Cloud products can lean on account creation and onboarding flows to buy time while infrastructure spins up in the background. Apeirogon needs to feel instantly usable, because there's no background work to hide behind.

The result is a product that feels quieter than most AI tools. Fewer spinners, fewer skeletons, fewer moments where the interface is telling you to wait instead of letting you work.