The Challenge

Slow loading times appear even slower when using a spinner-like loading design. There is no difference between loading and an error. The loading pattern is handled as a uniform form of loading regardless of context.

Loading charts on the dashboard is done on the user's computer which can't be a foreseen factor on more demanding graphs.

Psychology of loading times

The time spent on a loading animation or pattern should reflect the perceived complexity of a task. In the context of Zurvey.io, generating a dashboard would be a difficult task. In these cases, longer waiting times are appropriate.

However, loading the Home screen should feel snappy and effortless since this is a list view essentially. Most of the loading should happen on the dashboard and not here.

Beyond 1 second

When an expected loading time is longer than 1 second, that's when a loading animation should appear. For really long and complex tasks, there are a few options.

Suggestions

• Skeleton UI for list views, settings and dataset creators
• Fade-in microinteraction animations for dashboard → Lazyloading-like experience combining animations on chart elements

1. Predictable loading times

• A progress bar showing percentage
• A list of tasks the computer is doing, especially on the dashboard (over approx. 1000 rows):

2. Non-predictable loading times

• Spinner (Pulsing circle)
• Skeleton Screen