+1 for Zustand. Much quicker to get up and working. A good middle ground between Context and redux, project size wise at least.

More on reddit.com

Zustand, Recoil, and Jotai are all good, but are all very basic in comparison to Redux Toolkit. They're great if you don't need much global state or if you just want a replacement for useContext + useState + useReducer. TBH they're all worth learning on some level, just to better understand the strengths and weaknesses of them. If you're doing small-scale projects or just rolling a proof of concept, you might never need more than they offer. Knowing the line where each tool becomes a bottleneck is something you can only really get by messing with each in turn - or at least reading the docs and exploring the demos.

It's worth noting they solve a different problem than Redux Toolkit - they fit nicely between "react-only tools" and "Everything I need or might eventually need in one place". Redux Toolkit is a no-brainer if you've got a lot of global state, need easy CRUD-style managed entities, consume external API data (especially if you need fine control over caching and refetching), have complex data processing/manipulating for selectors, or want easy access to monitoring/debugging state changes.

More on reddit.com

state management behind custom hooks & having all the components agnostic about underlying state management You just described Zustand exactly. Zustand is really simple, basically a custom hook library. You define the hook, it’s getters and setters, then start using it throughout the application. Redux is a little more feature rich. If you plan on fetching data through your state management, then redux is probably the way to go. You can fetch data in Zustand also, but Redux seems to be built around fetching data. It seems like you want something that doesn’t become a bear to deal with. Something that, if needed, can be removed without too much headache. Even though their mascot is a bear, I’d say Zustand is your pick. Redux is built to “be” your application. I’ve seen many junior devs, myself included, struggle to wrap their heads around Redux and create some terrible patterns with it. Zustand seems to be an attempt to solve those issues. More on reddit.com

There are types of state in react. All of these do different things.

Local app/component state: useState should do.

Global app state: Zustand or useContex(if it doesn't change too often).

Server state: React-query.

More on reddit.com