Alert Avatar Bottom sheet Button Card Carousel Cards Checkbox Chip Circular button Compact date input Copy Block Critical banner Date input Date picker Divider Dropdown Icon button Image Ratios Instruction Media Button Modal Money input Navigation option Nudge Password input Popover Progress Bar Progress Spinners When to useProgress Spinner vs Progress barBest PracticeContentPlacement Promo card Radio Screen loader Search input Section header Segmented control Select Snackbar Summary Switch Table Tabs Text area Text input Upload Upload input
Design at Wise Foundations Components AlertAvatarBottom sheetButtonCardCarousel CardsCheckboxChipCircular buttonCompact date inputCopy BlockCritical bannerDate inputDate pickerDividerDropdownIcon buttonImage RatiosInstructionMedia Button ModalMoney inputNavigation optionNudgePassword inputPopoverProgress Bar Progress SpinnersPromo cardRadioScreen loaderSearch inputSection headerSegmented controlSelectSnackbarSummarySwitchTableTabsText areaText inputUploadUpload inputPatterns Resources
Progress Spinners

Progress spinners provide reassurance to users that the app hasn’t crashed when they are executing lengthy and/or stressful tasks.

When to use
  • When the user is executing long and/or stressful tasks (e.g uploading documents, sending money or retrieving card details.)
  • Don’t use for actions that typically load within one second.

Use when user is executing lengthy and stressful tasks.

Progress Spinner vs Progress bar
Progress Spinners

Progress spinners are used to add reassurance when the user is executing long and/or stressful tasks. Stressful tasks can include situations like, uploading documents, sending money or retrieving card details.

Progress Bar

Progress bars are used when the user is performing generic tasks that usually load fast. Generic tasks can include situations like loading content following navigation or loading data in background after an action has been performed. To find out more on when to use progress bars click here.

Best Practice

Below are a few examples of best practices to consider when using the progress spinner.

Do not use on top of a forest green themed background.

Add contextualised message to explain why the user needs to wait.

Do not add a blur effect when transitioning from one state to the next.

Content

The spinner and content is always displayed immediately and cycles indefinitely until screen has loaded. The content cycles between four different lines of messaging. The first line of messaging can be changed to give context and explain why the user needs to wait.

Four examples of different messaging used underneath the spinner
Placement

The spinning progress indicator should be centred horizontally and vertically within containers on mobile and web. Test the whole flow to check the screen loaders are consistent in terms of screen location and size. This will help to ensure that spinners that occur one after the other on different screens have the same size and position.