Components

Skeleton

Skeleton loaders create perceived performance and reduce user frustration around load times.

Loading user experiences are designed for creating apparent speed for users waiting for content to load. Loading skeletons help progressively populate content on web pages as it becomes available.

Skeleton loading is helpful for web page content that takes greater than a second to load:

A delay of 0.2–1.0 seconds does mean that users notice the delay and thus feel the computer is “working” on the command, as opposed to having the command be a direct effect of the users’ actions.

Jakob Nielsen, excerpt from Chapter 5 of his book Usability Engineering.

Skeleton loading is only useful for content loading within 10 seconds. For anything over 10 seconds, a progress bar is necessary.

Anything slower than 10 seconds needs a percent-done indicator as well as a clearly signposted way for the user to interrupt the operation.

Jakob Nielsen, excerpt from Chapter 5 of his book Usability Engineering.
import { Skeleton } from '@sproutsocial/racine'

Best Practices

Do

Use skeletons for content in container or data components.

Examples: table data, avatars, images, bodies of text.

Don't

Use skeletons for inputs.

Examples: buttons, textareas, text inputs, checkboxes.

Don't

Turn modal, dropdowns, popouts, toast notifications, or any sort of overlays into skeletons.

Use skeletons to replace the loading content inside of the overlay instead.

Don't

Use skeletons for content that takes over 10 seconds to load.

Use a progress bar.