The best loading screen tells you what's coming

A spinner is the most honest thing in your product and the most wasteful. Honest, because it admits the machine is busy. Wasteful, because it says nothing about what the machine is busy with — and in that silence, the only thing left for your user to do is get bored, or leave.

There’s a specific piece of brain science hiding in that dead moment, and it changes what a loading state is for.

In 1994 the economist George Loewenstein tried to pin down where curiosity actually comes from. His answer was almost mechanical: curiosity is the feeling of a gap between what you know and what you want to know. Not a general thirst for knowledge — a localized itch. You have to first become aware that there’s a specific something you’re missing, and only then does the wanting switch on. He called it the information-gap theory, and the key move is that curiosity is manufactured the instant a gap is defined. Before the gap exists, there’s nothing to be curious about.

That has a shape, and the shape matters for building. Curiosity isn’t “more unknown = more interest.” It’s an upside-down U. If you know nothing at all about a topic, there’s no gap you can even feel — you’re indifferent, not curious. If you already know everything, there’s no gap left — you’re bored. The pull is strongest in the middle: when you know enough to know exactly what you’re missing, and the missing piece feels close.

Now go back to the spinner. A bare spinner sits at the far-left of that curve: no gap is defined, so no curiosity is on. The wait is pure subtraction. But the same wait, with the gap named, moves you toward the peak. “Analyzing your 1,240 photos…” tells the user precisely what they don’t yet know — what the analysis will say — and turns the wait into a countdown to a reveal they now want. Nothing about the machine changed. You just told the brain where to point.

This is why the good loading states you’ve seen do more than animate. They narrate a gap and then close it: a multi-step wizard that says next: connect your data is opening a small loop your user now wants shut. A result screen that counts up from zero to the final number is stretching the last inch of the gap on purpose, because the anticipation is the product. An onboarding line that says once this is set, you’ll be able to publish in one click plants a gap that the next screen pays off.

Two honest limits, because this is a sharp tool and sharp tools cut both ways.

First, the gap has to be real. If you promise a reveal and the reveal is nothing — “Analyzing…” followed by an empty screen — you haven’t created curiosity, you’ve trained disappointment, and the next time your copy makes a promise the brain discounts it. This is close to, but not the same as, dressing up a fast operation to look like hard work. That’s a different lever (perceived effort). This one is about anticipation, and anticipation only survives if the payoff lands.

Second, a gap you open and never close stops being curiosity and becomes anxiety. The cliffhanger that never resolves, the “1 thing left!” badge that’s still there three weeks later — those are open loops weaponized, and the brain reads them as nagging, not intrigue. The rule that keeps you honest: open a gap only where you can close it in the next moment. A loading screen is a promise with a very short due date. Make the promise specific, then keep it.