Short description

Spinners communicate to the user that their action is being processed, without telling them what is happening in the back end.

When and how to use it

Use a spinner or skeleton loader to provide feedback that content is loading, but when we don’t have a time estimate.

A progress bar or a spinner can be used in a modal with text, if there is something important to communicate to the user, for example what we are doing or if they must stay on the page for the process to finish.

Spinner combination

Spinner & "wait-confirm"

This combination is suitable for processes that requires a combination of loading and successful confirmation checkmark, for example "User is successful when booking an advisory meeting". It's perfect for time consuming loading processes. 

This process requires two sub-processes:

1. The actual time the systems take to complete the booking (just loading and spinning)
2. When booking is successfully completed and the spinner is transformed into the checkmark.

The combination is not suitable for only refresh/loading a page or a set of data. Use progress bar or ordinary spinner, for instance. Remember to design a fall-back solution if the process fail. The spinner is only designed for happy flow.

Behaviour

When triggering the spinner (e.g. from “Book meeting” button) the viewport should be freezed and the loading spinner is started.The spinner takes full viewport. After the checkmark sequence, we are sending the user to a confirmation page.

If the waiting time is long enough, you can show a text explaining to the user:

• What is happening or will happen
• What we (the bank's system) are doing
• What the customer soon will know or see