Foldwren

Loading states and the feeling of speed

How skeleton screens, progress indicators and instant feedback make an app feel faster, and why a spinner on every screen works against you.

How fast an app is and how fast it feels are two different things. You can measure the first with a stopwatch. The second lives in the user's head, and it is the one that determines whether they think your product is quick or sluggish.

Real speed still matters most. But once your developer has done what they can, design decides how the remaining wait is experienced.

Why does waiting feel longer than it is?

A wait feels longer when you do not know what is happening, how long it will take, or whether your tap even registered. Think of standing at a counter with nobody in sight, compared with a staff member saying "be with you in a minute". Same wait, very different feeling.

Three rough thresholds are useful when thinking about this:

  • Instant. A response within a blink feels like the screen reacted directly to your finger. Nothing extra is needed.
  • A short pause. Around a second, people notice the delay but stay focused. A subtle sign that something is happening is enough.
  • A real wait. Several seconds or more, attention drifts. People need to know that progress is being made, and ideally how much is left.

The design response should match the length of the wait. Most apps get this wrong by using the same spinner for everything.

What is wrong with spinners everywhere?

A spinner says "wait" and nothing else. It does not say what is loading, how long it will take, or whether it is stuck. A spinner that has been turning for ten seconds looks exactly like one that will turn forever.

They have their place: a small one inside a button after you press it, or for a short, unpredictable wait. Just not as the answer to every delay.

Skeleton screens

A skeleton screen shows the outline of the page straight away, with grey blocks standing in for the text and images that are still arriving. As the real content loads, it replaces the placeholders.

Say you have a physio clinic app with a list of upcoming appointments. Instead of a blank screen with a spinner, the person immediately sees the header, the tab bar and three grey card shapes where the appointments will be. Half a second later the details fill in.

Why this works:

  • The person sees the structure at once and knows what is coming.
  • The screen never looks blank or broken.
  • Content arriving in place feels like progress.
  • Nothing jumps around, provided the placeholders match the size of the real content.

That last point is important. If images pop in and shove the text down just as someone is about to tap, you have swapped one annoyance for another. Reserve the space.

Showing progress for longer waits

When something takes more than a few seconds, such as uploading photos or generating a report, show how far along it is.

  • Use a real progress bar when you can measure it. "Uploading 3 of 8 photos" is far more comforting than a looping animation.
  • Name the steps when you cannot measure precisely. "Checking availability", then "Confirming your booking". Changing text tells people the app has not frozen.
  • Let people carry on. If a builder is uploading site photos to a job record, do not lock the whole screen. Show progress in a corner and let them keep typing notes.

Instant feedback on every tap

The cheapest way to make an app feel fast is to acknowledge every touch immediately, even if the result takes longer.

  • Buttons should visibly react. A change of shade the moment a finger lands.
  • Disable a button once pressed and show it is working, so people do not tap "Pay" three times.
  • Move first, load second. Slide to the next screen at once and load its content there, instead of freezing on the old screen until everything is ready.

Assuming success

For small, low risk actions, the app can behave as if the action has already succeeded. Tap a heart to save a favourite and it fills in at once, while the request is sent quietly in the background. If it fails, the app undoes the change and says so.

This suits likes, favourites, ticking off a checklist item or marking a message read. It does not suit payments, bookings or anything where a false "done" would cause real trouble. For those, wait for confirmation and show clearly that you are waiting.

A quick review of your own app

Open your app on a middling phone with a weak signal. A car park or a lift lobby is ideal. Then check:

  1. Does every tap produce a visible response straight away?
  2. Is any screen completely blank while loading?
  3. Does content jump around as it arrives?
  4. For waits of more than a few seconds, can you tell what is happening and roughly how long is left?
  5. Can you tap a payment or submit button twice?
  6. If loading fails, do you get a clear message and a way to retry, or an endless spinner?

Each "no" is a small job for your designer or developer. Fix the screens people visit most often first. The app's raw speed may not change at all, yet users will describe it as faster.

Your order