# Introducing Concurrent Mode (Experimental)

.scary > blockquote { background-color: rgba(237, 51, 21, 0.2); border-left-color: #ed3315; }

> Caution:
>
> This page was about experimental features that aren't yet available in a stable release. It was aimed at early adopters and people who are curious.
>
> Much of the information on this page is now outdated and exists only for archival purposes. **Please refer to the React 18 Alpha announcement post for the up-to-date information.**
>
> Before React 18 is released, we will replace this page with stable documentation.

This page provides a theoretical overview of Concurrent Mode. **For a more practical introduction, you might want to check out the next sections:**

* Suspense for Data Fetching describes a new mechanism for fetching data in React components.
* Concurrent UI Patterns shows some UI patterns made possible by Concurrent Mode and Suspense.
* Adopting Concurrent Mode explains how you can try Concurrent Mode in your project.
* Concurrent Mode API Reference documents the new APIs available in experimental builds.

### What Is Concurrent Mode? <a href="#what-is-concurrent-mode" id="what-is-concurrent-mode"></a>

Concurrent Mode is a set of new features that help React apps stay responsive and gracefully adjust to the user's device capabilities and network speed.

These features are still experimental and are subject to change. They are not yet a part of a stable React release, but you can try them in an experimental build.

### Blocking vs Interruptible Rendering <a href="#blocking-vs-interruptible-rendering" id="blocking-vs-interruptible-rendering"></a>

**To explain Concurrent Mode, we'll use version control as a metaphor.** If you work on a team, you probably use a version control system like Git and work on branches. When a branch is ready, you can merge your work into main so that other people can pull it.

Before version control existed, the development workflow was very different. There was no concept of branches. If you wanted to edit some files, you had to tell everyone not to touch those files until you've finished your work. You couldn't even start working on them concurrently with that person — you were literally _blocked_ by them.

This illustrates how UI libraries, including React, typically work today. Once they start rendering an update, including creating new DOM nodes and running the code inside components, they can't interrupt this work. We'll call this approach "blocking rendering".

In Concurrent Mode, rendering is not blocking. It is interruptible. This improves the user experience. It also unlocks new features that weren't possible before. Before we look at concrete examples in the next chapters, we'll do a high-level overview of new features.

#### Interruptible Rendering <a href="#interruptible-rendering" id="interruptible-rendering"></a>

Consider a filterable product list. Have you ever typed into a list filter and felt that it stutters on every key press? Some of the work to update the product list might be unavoidable, such as creating new DOM nodes or the browser performing layout. However, _when_ and _how_ we perform that work plays a big role.

A common way to work around the stutter is to "debounce" the input. When debouncing, we only update the list _after_ the user stops typing. However, it can be frustrating that the UI doesn't update while we're typing. As an alternative, we could "throttle" the input, and update the list with a certain maximum frequency. But then on lower-powered devices we'd still end up with stutter. Both debouncing and throttling create a suboptimal user experience.

The reason for the stutter is simple: once rendering begins, it can't be interrupted. So the browser can't update the text input right after the key press. No matter how good a UI library (such as React) might look on a benchmark, if it uses blocking rendering, a certain amount of work in your components will always cause stutter. And, often, there is no easy fix.

**Concurrent Mode fixes this fundamental limitation by making rendering interruptible.** This means when the user presses another key, React doesn't need to block the browser from updating the text input. Instead, it can let the browser paint an update to the input, and then continue rendering the updated list _in memory_. When the rendering is finished, React updates the DOM, and changes are reflected on the screen.

Conceptually, you can think of this as React preparing every update "on a branch". Just like you can abandon work in branches or switch between them, React in Concurrent Mode can interrupt an ongoing update to do something more important, and then come back to what it was doing earlier. This technique might also remind you of [double buffering](https://wiki.osdev.org/Double_Buffering) in video games.

Concurrent Mode techniques reduce the need for debouncing and throttling in UI. Because rendering is interruptible, React doesn't need to artificially _delay_ work to avoid stutter. It can start rendering right away, but interrupt this work when needed to keep the app responsive.

#### Intentional Loading Sequences <a href="#intentional-loading-sequences" id="intentional-loading-sequences"></a>

We've said before that Concurrent Mode is like React working "on a branch". Branches are useful not only for short-term fixes, but also for long-running features. Sometimes you might work on a feature, but it could take weeks before it's in a "good enough state" to merge into main. This side of our version control metaphor applies to rendering too.

Imagine we're navigating between two screens in an app. Sometimes, we might not have enough code and data loaded to show a "good enough" loading state to the user on the new screen. Transitioning to an empty screen or a large spinner can be a jarring experience. However, it's also common that the necessary code and data doesn't take too long to fetch. **Wouldn't it be nicer if React could stay on the old screen for a little longer, and "skip" the "bad loading state" before showing the new screen?**

While this is possible today, it can be difficult to orchestrate. In Concurrent Mode, this feature is built-in. React starts preparing the new screen in memory first — or, as our metaphor goes, "on a different branch". So React can wait before updating the DOM so that more content can load. In Concurrent Mode, we can tell React to keep showing the old screen, fully interactive, with an inline loading indicator. And when the new screen is ready, React can take us to it.

#### Concurrency <a href="#concurrency" id="concurrency"></a>

Let's recap the two examples above and see how Concurrent Mode unifies them. **In Concurrent Mode, React can work on several state updates&#x20;**_**concurrently**_ — just like branches let different team members work independently:

* For CPU-bound updates (such as creating DOM nodes and running component code), concurrency means that a more urgent update can "interrupt" rendering that has already started.
* For IO-bound updates (such as fetching code or data from the network), concurrency means that React can start rendering in memory even before all the data arrives, and skip showing jarring empty loading states.

Importantly, the way you _use_ React is the same. Concepts like components, props, and state fundamentally work the same way. When you want to update the screen, you set the state.

React uses a heuristic to decide how "urgent" an update is, and lets you adjust it with a few lines of code so that you can achieve the desired user experience for every interaction.

### Putting Research into Production <a href="#putting-research-into-production" id="putting-research-into-production"></a>

There is a common theme around Concurrent Mode features. **Its mission is to help integrate the findings from the Human-Computer Interaction research into real UIs.**

For example, research shows that displaying too many intermediate loading states when transitioning between screens makes a transition feel _slower_. This is why Concurrent Mode shows new loading states on a fixed "schedule" to avoid jarring and too frequent updates.

Similarly, we know from research that interactions like hover and text input need to be handled within a very short period of time, while clicks and page transitions can wait a little longer without feeling laggy. The different "priorities" that Concurrent Mode uses internally roughly correspond to the interaction categories in the human perception research.

Teams with a strong focus on user experience sometimes solve similar problems with one-off solutions. However, those solutions rarely survive for a long time, as they're hard to maintain. With Concurrent Mode, our goal is to bake the UI research findings into the abstraction itself, and provide idiomatic ways to use them. As a UI library, React is well-positioned to do that.

### Next Steps <a href="#next-steps" id="next-steps"></a>

Now you know what Concurrent Mode is all about!

On the next pages, you'll learn more details about specific topics:

* Suspense for Data Fetching describes a new mechanism for fetching data in React components.
* Concurrent UI Patterns shows some UI patterns made possible by Concurrent Mode and Suspense.
* Adopting Concurrent Mode explains how you can try Concurrent Mode in your project.
* Concurrent Mode API Reference documents the new APIs available in experimental builds.
