react-content-loader vs react-loading-skeleton vs react-placeholder
Placeholder Libraries for React
react-content-loaderreact-loading-skeletonreact-placeholderSimilar Packages:

Placeholder Libraries for React

These libraries are designed to create placeholder components in React applications, enhancing user experience during data loading. They provide visual feedback to users, indicating that content is being fetched or processed, which can help reduce perceived loading times and improve overall application responsiveness. Each library offers unique features and customization options to suit different design needs and performance considerations.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
react-content-loader661,28413,999164 kB212 months agoMIT
react-loading-skeleton04,18626.7 kB7a year agoMIT
react-placeholder01,613-235 years agoISC

Feature Comparison: react-content-loader vs react-loading-skeleton vs react-placeholder

Customization

  • react-content-loader:

    react-content-loader allows extensive customization of the placeholder shapes and sizes using SVG. You can define the exact layout of your content, making it possible to create loaders that match your application's design and structure closely.

  • react-loading-skeleton:

    react-loading-skeleton offers limited customization options, focusing on basic skeleton shapes. You can adjust the width, height, and border radius, but it lacks the advanced customization features of react-content-loader, making it less flexible for complex layouts.

  • react-placeholder:

    react-placeholder provides a moderate level of customization, allowing you to define the shape and size of placeholders. It supports various types of placeholders, enabling you to create a mix of text and image loaders, but it may not offer the same level of detail as react-content-loader.

Ease of Use

  • react-content-loader:

    react-content-loader has a steeper learning curve due to its SVG-based approach, requiring some familiarity with SVG syntax to fully utilize its capabilities. However, once understood, it offers powerful features for creating visually appealing loaders.

  • react-loading-skeleton:

    react-loading-skeleton is very easy to use, with a straightforward API that allows developers to quickly implement skeleton screens with minimal configuration. This makes it an excellent choice for rapid development and prototyping.

  • react-placeholder:

    react-placeholder is also user-friendly, providing a simple API that allows for quick integration of various placeholder types. It strikes a balance between ease of use and flexibility, making it accessible for developers of all skill levels.

Performance

  • react-content-loader:

    react-content-loader is optimized for performance, but the use of SVG can lead to increased rendering times if not managed properly. It is important to optimize SVG assets to ensure that they do not negatively impact application performance.

  • react-loading-skeleton:

    react-loading-skeleton is lightweight and designed for performance, ensuring minimal impact on loading times. Its simplicity allows for quick rendering, making it ideal for applications that prioritize speed.

  • react-placeholder:

    react-placeholder performs well in most scenarios, but its performance can vary depending on the complexity of the placeholders used. It is generally efficient but may require optimization for more complex loading states.

Visual Appeal

  • react-content-loader:

    react-content-loader excels in visual appeal, allowing developers to create realistic and engaging loaders that enhance the user experience. Its ability to closely mimic the final content layout makes it a favorite for applications where aesthetics matter.

  • react-loading-skeleton:

    react-loading-skeleton provides a clean and minimalistic design that fits well with modern UI trends. While it may not be as visually detailed as react-content-loader, its simplicity can be appealing in many contexts.

  • react-placeholder:

    react-placeholder offers a variety of placeholder styles, making it versatile for different design needs. Its visual appeal is decent, but it may not match the level of customization available in react-content-loader.

Community and Support

  • react-content-loader:

    react-content-loader has a strong community and good documentation, making it easier for developers to find resources and support when needed. Its popularity ensures ongoing maintenance and updates.

  • react-loading-skeleton:

    react-loading-skeleton is widely used and has a supportive community, though it may not have as extensive documentation as react-content-loader. However, its simplicity often reduces the need for extensive support.

  • react-placeholder:

    react-placeholder has a smaller community compared to the others, but it is still actively maintained. Documentation is adequate, providing enough guidance for developers to implement the library effectively.

How to Choose: react-content-loader vs react-loading-skeleton vs react-placeholder

  • react-content-loader:

    Choose react-content-loader if you need highly customizable SVG-based placeholders that can mimic the actual layout of your content. This package is ideal for projects where visual fidelity is important, allowing you to create loaders that closely resemble the final content structure.

  • react-loading-skeleton:

    Opt for react-loading-skeleton if you prefer a simple and lightweight solution for creating skeleton screens. This package is easy to implement and offers a minimalistic approach to loading indicators, making it suitable for applications where speed and simplicity are key.

  • react-placeholder:

    Select react-placeholder if you want a versatile library that supports multiple types of placeholders, including text and image placeholders. This package is great for applications that require a mix of loading indicators and offers a straightforward API for quick integration.

README for react-content-loader

react-content-loader

Example's react-content-loader

SVG-Powered component to easily create placeholder loadings (like Facebook's cards loading).

Features

  • :gear: Customizable: Feel free to change the colors, speed, sizes, and even RTL;
  • :ok_hand: Plug and play: with many presets to use, see the examples;
  • :pencil2: DIY: use the create-content-loader to create your own custom loaders easily;
  • 📱 React Native support: same API, as same powerful features;
  • ⚛️ Really lightweight: less than 2kB and 0 dependencies for web version;

Index

Getting Started

npm i react-content-loader --save
yarn add react-content-loader

For React Native

npm i react-content-loader react-native-svg --save
yarn add react-content-loader react-native-svg

CDN from JSDELIVR

Usage

There are two ways to use it:

1. Presets, see the examples:

import ContentLoader, { Facebook } from 'react-content-loader'

const MyLoader = () => <ContentLoader />
const MyFacebookLoader = () => <Facebook />

2. Custom mode, see the online tool

const MyLoader = () => (
  <ContentLoader viewBox="0 0 380 70">
    {/* Only SVG shapes */}    
    <rect x="0" y="0" rx="5" ry="5" width="70" height="70" />
    <rect x="80" y="17" rx="4" ry="4" width="300" height="13" />
    <rect x="80" y="40" rx="3" ry="3" width="250" height="10" />
  </ContentLoader>
)

Still not clear? Take a look at this working example at codesandbox.io Or try the components editable demo hands-on and install it from bit.dev

Native

react-content-loader can be used with React Native in the same way as web version with the same import:

1. Presets, see the examples:

import ContentLoader, { Facebook } from 'react-content-loader/native'

const MyLoader = () => <ContentLoader />
const MyFacebookLoader = () => <Facebook />

2. Custom mode

To create custom loaders there is an important difference: as React Native doesn't have any native module for SVG components, it's necessary to import the shapes from react-native-svg or use the named export Rect and Circle from react-content-loader import:

import ContentLoader, { Rect, Circle } from 'react-content-loader/native'

const MyLoader = () => (
  <ContentLoader viewBox="0 0 380 70">
    <Circle cx="30" cy="30" r="30" />
    <Rect x="80" y="17" rx="4" ry="4" width="300" height="13" />
    <Rect x="80" y="40" rx="3" ry="3" width="250" height="10" />
  </ContentLoader>
)

Options

Prop name and type
EnvironmentDescription
animate?: boolean
Defaults to true
React DOM
React Native
Opt-out of animations with false
title?: string
Defaults to Loading...
React DOM onlyIt's used to describe what element it is. 
Use '' (empty string) to remove.
baseUrl?: string
Defaults to an empty string
React DOM onlyRequired if you're using <base url="/" /> document <head/>
This prop is common used as: 
<ContentLoader baseUrl={window.location.pathname} /> which will fill the SVG attribute with the relative path. Related #93.
speed?: number
Defaults to 1.2
React DOM
React Native
Animation speed in seconds.
viewBox?: string
Defaults to undefined
React DOM
React Native
Use viewBox props to set a custom viewBox value,
for more information about how to use it,
read the article How to Scale SVG.
gradientRatio?: number
Defaults to 1.2
React DOM onlyWidth of the animated gradient as a fraction of the view box width.
rtl?: boolean
Defaults to false
React DOM
React Native
Content right-to-left.
backgroundColor?: string
Defaults to #f5f6f7
React DOM
React Native
Used as background of animation.
foregroundColor?: string
Defaults to #eee
React DOM
React Native
Used as the foreground of animation.
backgroundOpacity?: number
Defaults to 1
React DOM
React Native
Background opacity (0 = transparent, 1 = opaque)
used to solve an issue in Safari
foregroundOpacity?: number
Defaults to 1
React DOM
React Native
Animation opacity (0 = transparent, 1 = opaque)
used to solve an issue in Safari
style?: React.CSSProperties
Defaults to {}
React DOM only
uniqueKey?: string
Defaults to random unique id
React DOM onlyUse the same value of prop key, 
that will solve inconsistency on the SSR, see more here.
beforeMask?: JSX.Element
Defaults to null
React DOM
React Native
Define custom shapes before content, 
see more here.

See all options live

Examples

Facebook Style
import { Facebook } from 'react-content-loader'

const MyFacebookLoader = () => <Facebook />
Facebook Style
Instagram Style
import { Instagram } from 'react-content-loader'

const MyInstagramLoader = () => <Instagram />
Instagram Style
Code Style
import { Code } from 'react-content-loader'

const MyCodeLoader = () => <Code />
Code Style
List Style
import { List } from 'react-content-loader'

const MyListLoader = () => <List />
List Style
Bullet list Style
import { BulletList } from 'react-content-loader'

const MyBulletListLoader = () => <BulletList />
Bullet list Style

Custom Style

For the custom mode, use the online tool.

const MyLoader = () => (
  <ContentLoader
    height={140}
    speed={1}
    backgroundColor={'#333'}
    foregroundColor={'#999'}
    viewBox="0 0 380 70"
  >
    {/* Only SVG shapes */}
    <rect x="0" y="0" rx="5" ry="5" width="70" height="70" />
    <rect x="80" y="17" rx="4" ry="4" width="300" height="13" />
    <rect x="80" y="40" rx="3" ry="3" width="250" height="10" />
  </ContentLoader>
)

Custom

Troubleshooting

Responsive - Mobile version

In order to avoid unexpected behavior, the package doesn't have opinioned settings. So if it needs to be responsive, have in mind that the output of the package is a regular SVG, so it just needs the same attributes to become a regular SVG responsive, which means:

import { Code } from 'react-content-loader'

const MyCodeLoader = () => (
  <Code
    width={100}
    height={100}
    viewBox="0 0 100 100"
    style={{ width: '100%' }}
  />
)

Server-side rendering (SSR) - Match snapshot

As the main component generates random values to match the id of the SVG element with background style, it can encounter unexpected errors and unmatching warning on render, once the random value of id will be generated twice, in case of SSR: server and client; or in case of snapshot test: on the first match and re-running the test.

To fix it, set the prop uniqueKey, then the id will not be random anymore:

import { Facebook } from 'react-content-loader'

const MyFacebookLoader = () => <Facebook uniqueKey="my-random-value" />

Alpha is not working: Safari / iOS

When using rgba as a backgroundColor or foregroundColor value, Safari does not respect the alpha channel, meaning that the color will be opaque. To prevent this, instead of using a rgba value for backgroundColor/foregroundColor, use the rgb equivalent and move the alpha channel value to the backgroundOpacity/foregroundOpacity props.

{/* Opaque color in Safari and iOS */}
<ContentLoader
  backgroundColor="rgba(0,0,0,0.06)"
  foregroundColor="rgba(0,0,0,0.12)">


{/_ Semi-transparent color in Safari and iOS _/}
<ContentLoader
    backgroundColor="rgb(0,0,0)"
    foregroundColor="rgb(0,0,0)"
    backgroundOpacity={0.06}
    foregroundOpacity={0.12}>


Black box in Safari / iOS (again)

Using the base tag on a page that contains SVG elements fails to render and it looks like a black box. Just remove the base-href tag from the <head /> and the issue has been solved.

black box

See: #93 / 109

Browser supports SVG-Animate

Old browsers don't support animation in SVG (compatibility list), and if your project must support IE, for examples, here's a couple of ways to make sure that browser supports SVG Animate:

  • window.SVGAnimateElement
  • document.implementation.hasFeature("http://www.w3.org/TR/SVG11/feature#SVG-Animation", "1.1")
  • Or even use https://modernizr.com/

Similar packages


Development

Fork the repo and then clone it

$ git clone git@github.com:YourUsername/react-content-loader.git && cd react-content-loader

$ npm i: Install the dependencies;

$ npm run build: Build to production;

$ npm run dev: Run the Storybook to see your changes;

$ npm run test: Run all tests: type checking, unit tests on web and native;

$ npm run test:watch: Watch unit tests;

React Native

As React Native doesn't support symbolic links (to link the dependency to another folder) and as there is no playground to check your contributions (like storybook), this is recommended strategy to run the project locally:

  1. Create a new React Native from scratch, either Metro or create-react-native-app;
  2. Install the dependency to your root project: yarn add react-content-loader react-native-svg
  3. Open the project just created and clone this repository there;
  4. Create your loading component and point the react-content-loader to the project just cloned, like: import ContentLoader, { Rect, Circle } from './react-content-loader/native'

Commit messages

Commit messages should follow the commit message convention so, changelogs could be generated automatically by that. Commit messages are validated automatically upon commit. If you aren't familiar with the commit message convention, you can use yarn commit (or npm run commit) instead of git commit, which provides an interactive CLI for generating proper commit messages.

License

MIT