---
title: "Do You Really Need a React State Management Library?"
url: https://daily.dev/posts/do-you-really-need-a-react-state-management-library--2wqp4losg
source_url: https://blog.bitsrc.io/react-do-you-really-need-an-external-library-for-state-management-28f67d03ebe5?source=rss----5c2fdf847f4a---4
type: article
source: "Bits and Pieces"
published: 2022-03-19T00:42:03.610Z
updated: 2022-03-19T00:42:03.610Z
tags: ["general-programming", "react", "webdev"]
reading_time: 7
upvotes: 26
comments: 2
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Do You Really Need a React State Management Library?

**[Bits and Pieces](https://daily.dev/sources/bit)** · 7 min read · 26 upvotes · 2 comments

## Summary

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.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.bitsrc.io/react-do-you-really-need-an-external-library-for-state-management-28f67d03ebe5?source=rss----5c2fdf847f4a---4>

## Community discussion

Top comments from developers on daily.dev.

**@kkurko** · 2 upvotes

> It all depends on a project needs, but the rules we are using on a big (around 500к lines of code) project are:
> - useState for UI states like show or hide modal, disable button, show error message and etc.
> - 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)
> - 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

**@irsooti** · 0 upvotes

> 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.

## Similar posts on daily.dev

- [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments
- [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments
- [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments

---

Tags: [#general-programming](https://daily.dev/tags/general-programming), [#react](https://daily.dev/tags/react), [#webdev](https://daily.dev/tags/webdev)

[View this post on daily.dev](https://daily.dev/posts/do-you-really-need-a-react-state-management-library--2wqp4losg)