Member-only story
The Illusion of Speed: How Great Apps Win the First Two Seconds
Not a Medium Member? “Read For Free”
Put two phones side by side on the same office Wi-Fi. Launch a food delivery app, and before your thumb leaves the glass, the screen has already responded: a header docks into place, skeleton cards fill the layout, cached items render instantly, and a quiet network call fetches fresh inventory in the background.
Now tap a second app. The icon freezes. The screen flashes white. A spinner turns for 1.8 seconds. Then everything slams onto the screen at once.
Both apps did roughly the same amount of work — same payload size, same final millisecond of network completion. Yet one feels instant, and the other feels broken.
That gap isn’t a network problem or a CPU problem. It’s an architecture problem: a series of decisions about what the user is allowed to see, when they see it, and how state gets negotiated behind the scenes. The fastest apps aren’t the ones that finish their work earliest — they’re the ones that eliminate the feeling of waiting. This piece breaks down why the naive approach fails, and how to rebuild startup around that idea.
