What you need to know before using React libraries like Redux

Bit's platform is a collaborative development platform, offering insights into component-driven development, code sharing, and version control for modern software projects. Through articles, tutorials, and documentation, Bit offers insights into creating and managing reusable components across projects and teams. Developers can learn about component design, versioning strategies, and integration with popular frameworks to streamline development workflows and improve code quality.

Bits and Pieces

The State is not a specific concept of React but a generic one of JavaScript. It is a core concept because it keeps track of the status of our application and describes it over time. React is composed of several components, each of which may have a state. With the introduction of hooks, we can use state also inside functional components.

Do You Really Need a React State Management Library?

A possible solution: a third-party library

How to use it in your application: my consideration

It all depends on a project needs, but the rules we are using on a big (around 500к lines of code) project are:
<ul>
<li>useState for UI states like show or hide modal, disable button, show error message and etc.</li>
<li>Context for the thing between UI state and kinda data state - filters (filters state will affect the UI e.g. selected checkbox, but it will be also passed to the query, so we will have different response)</li>
<li>State management libraries - back-end data, local cache or you can call it whatever you want, but it’s not related to the look of the UI</li>
</ul>

I’d say no, because when your application grow soon or later you end to create a context/provider component and you have to optimize it. So why reinvent the wheel? Using an easy and debuggable state manager can helps.
But it’s not always true.
Sometime UIs are very simple, then using Context API just to avoid prop drilling is enough.