react-content-loader vs react-lazy-load-image-component vs react-loading vs react-loading-skeleton vs react-placeholder
React Loading and Placeholder Libraries
react-content-loaderreact-lazy-load-image-componentreact-loadingreact-loading-skeletonreact-placeholderSimilar Packages:

React Loading and Placeholder Libraries

These libraries provide various methods to enhance user experience during loading states in React applications. They help to create visually appealing loading indicators and placeholders that can improve perceived performance by giving users feedback while content is being fetched or processed. Each library has its unique approach, offering different styles and functionalities for loading states, making it easier for developers to implement loading indicators that fit their application's design.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
react-content-loader014,000164 kB212 months agoMIT
react-lazy-load-image-component01,55395.4 kB57a year agoMIT
react-loading0817-198 years agoMIT
react-loading-skeleton04,18526.7 kB7a year agoMIT
react-placeholder01,613-235 years agoISC

Feature Comparison: react-content-loader vs react-lazy-load-image-component vs react-loading vs react-loading-skeleton vs react-placeholder

Customization

  • react-content-loader:

    react-content-loader allows for extensive customization of the skeleton screens, enabling developers to define shapes and sizes that match the actual content layout. This flexibility helps create a seamless transition from loading to loaded states, enhancing user experience.

  • react-lazy-load-image-component:

    react-lazy-load-image-component offers customization options for lazy loading images, including the ability to define placeholder images or effects while the main image loads. This ensures that the user sees a relevant placeholder, improving the visual experience during loading.

  • react-loading:

    react-loading provides a variety of loading spinner styles and sizes, allowing developers to choose or customize the spinner that best fits their application's design. However, it has limited customization compared to other libraries focused on skeleton screens.

  • react-loading-skeleton:

    react-loading-skeleton is highly customizable, allowing developers to adjust the width, height, and shape of the skeleton components. This makes it easy to create loading states that closely resemble the final content layout, improving user experience.

  • react-placeholder:

    react-placeholder supports customization of loading placeholders, including the ability to define the number of lines, width, and height of text placeholders. This flexibility allows developers to create visually appealing loading states that fit their application's design.

Performance Optimization

  • react-content-loader:

    react-content-loader is optimized for performance, as it generates SVGs that are lightweight and efficient. This ensures that loading screens do not significantly impact the overall performance of the application, making it suitable for high-performance applications.

  • react-lazy-load-image-component:

    react-lazy-load-image-component significantly improves performance by loading images only when they are in the viewport. This reduces the initial load time and bandwidth usage, making it ideal for image-heavy applications.

  • react-loading:

    react-loading is lightweight and has minimal impact on performance, making it suitable for applications that require simple loading indicators without complex animations or heavy resources.

  • react-loading-skeleton:

    react-loading-skeleton is designed to be lightweight and efficient, ensuring that skeleton screens do not hinder the performance of the application. It helps maintain a smooth user experience during content loading.

  • react-placeholder:

    react-placeholder is optimized for performance, allowing developers to create loading states without adding significant overhead to the application. It supports various loading types while maintaining efficient rendering.

Ease of Use

  • react-content-loader:

    react-content-loader is easy to use, requiring minimal setup to create skeleton screens. Its straightforward API allows developers to quickly implement loading states without extensive configuration.

  • react-lazy-load-image-component:

    react-lazy-load-image-component is user-friendly, providing a simple API for lazy loading images. Developers can easily integrate it into their applications with minimal effort, making it accessible for beginners.

  • react-loading:

    react-loading is designed for simplicity, allowing developers to quickly add loading spinners to their applications with just a few lines of code. Its ease of use makes it a popular choice for quick implementations.

  • react-loading-skeleton:

    react-loading-skeleton is easy to implement, providing a simple API that allows developers to create skeleton screens with minimal configuration. This makes it a great choice for projects that need quick loading indicators.

  • react-placeholder:

    react-placeholder is straightforward to use, offering a simple API for creating various loading placeholders. Developers can quickly implement loading states without complex setup, making it beginner-friendly.

Visual Appeal

  • react-content-loader:

    react-content-loader excels in creating visually appealing skeleton screens that closely mimic the layout of the actual content. This enhances the user experience by providing a smooth transition from loading to loaded states.

  • react-lazy-load-image-component:

    react-lazy-load-image-component allows for the use of placeholder images, which can be visually appealing and relevant to the content being loaded. This helps maintain user engagement during image loading.

  • react-loading:

    react-loading offers a variety of spinner designs that can be visually appealing, but it may not match the content layout as effectively as skeleton screens. It is best used for simple loading indicators rather than complex content.

  • react-loading-skeleton:

    react-loading-skeleton provides visually appealing skeleton screens that enhance the user experience by mimicking the structure of the content. This helps users understand what to expect while the content loads.

  • react-placeholder:

    react-placeholder supports various loading types, allowing developers to create visually appealing placeholders that fit different content types. This versatility helps maintain user engagement during loading.

Community and Support

  • react-content-loader:

    react-content-loader has a strong community and good documentation, making it easy for developers to find support and examples. This helps in quickly resolving issues and implementing features effectively.

  • react-lazy-load-image-component:

    react-lazy-load-image-component benefits from an active community and comprehensive documentation, providing developers with resources and support for implementation and troubleshooting.

  • react-loading:

    react-loading has a decent community and sufficient documentation, but it may not be as extensive as other libraries. Developers can still find support and examples to assist with implementation.

  • react-loading-skeleton:

    react-loading-skeleton has a growing community and good documentation, offering developers the resources needed to implement and customize skeleton screens effectively.

  • react-placeholder:

    react-placeholder has a supportive community and adequate documentation, making it easy for developers to find help and examples for creating loading placeholders.

How to Choose: react-content-loader vs react-lazy-load-image-component vs react-loading vs react-loading-skeleton vs react-placeholder

  • react-content-loader:

    Choose react-content-loader if you need customizable SVG-based skeleton screens that mimic the layout of your content. It is ideal for creating visually appealing loading states that match your application's design, especially when you want to provide a smooth transition from loading to loaded content.

  • react-lazy-load-image-component:

    Select react-lazy-load-image-component when you want to optimize image loading by lazy loading images as they enter the viewport. This package is perfect for applications with many images, as it helps improve performance and reduce initial load times by loading images only when necessary.

  • react-loading:

    Use react-loading if you need a simple and customizable loading spinner or indicator. This package is great for applications that require a straightforward loading animation without the need for complex configurations or styles, making it easy to implement and use.

  • react-loading-skeleton:

    Opt for react-loading-skeleton when you want to create skeleton screens that are easy to implement and highly customizable. This library is particularly useful for providing a smooth user experience by displaying placeholders that resemble the structure of your content while it loads.

  • react-placeholder:

    Choose react-placeholder if you need a versatile library that supports various loading types, including text and image placeholders. It is suitable for applications that require a quick and flexible solution for loading states, allowing you to easily create placeholders that fit different content types.

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