Post

I like to understand why things work the way that they do. When I was writing my book on state management libraries in React Native I also made an effort to understand the reasoning behind the solutions. I reached out to library creators and was lucky to receive insightful answers.

31/12/25, 10:51 am0 reposts3 likes

ola 😎

@psyche.social

31 Dec 2025

I wrote this book in 2022-2023. Did it age well? I think so 😁 Thanks to the underlying knowledge of basic concepts, it still is a useful guide for choosing state management solutions for your apps. WDYT? You can find the book on amazon: www.amazon.pl/Simplifying-...

amazon.plSimplifying State Management in React Native: Master state management from hooks and context through to Redux, MobX, XState, Jotai and React Query : Desmurs-Linczewska, Aleksandra: Amazon.pl: KsiążkiSimplifying State Management in React Native: Master state management from hooks and context through to Redux, MobX, XState, Jotai and React Query : Desmurs-Linczewska, Aleksandra: Amazon.pl: Książki

Kræn Hansen 🇩🇰

@kraenhansen.dk

31 Dec 2025

While I totally accept my inherent bias (as a maintainer of such a library), I remember being curious that the book didn't seem to dive into local + reactive databases as a potential solution to state management.

ola 😎

@psyche.social

31 Dec 2025

To be honest, that path was totally off my radar! But I agree it has a place among other state management solutions. I'll need to write a blog post about reactive DBs as a follow up to the book. @kraenhansen.dk expect some questions 😁

🙈😅

Makes sense: That's a valuable data point too 🙂 One hypothesis of mine is that some of the libraries and mind share, which is thriving on the web are missing from the React Native ecosystem 🤔

Kræn Hansen 🇩🇰

@kraenhansen.dk

31 Dec 2025

At least not from the way it was presented back then, though I might be wrong on that understanding? If it's true - do you remember why you choose to keep that out of scope? Was that just not what people were using at the time?