Document critical architecture decisions effortlessly. Stop debating the same topics and start building a technical compass for your team.
# ADR: Adopt Zustand for Global State
**Date:** 2026-08-11
**Status:** Accepted
## 1. Context
*Problem Type: State Management*
Our application state is becoming complex with deeply nested props. Prop drilling is causing performance bottlenecks and making components hard to test and maintain.
## 2. Decision
We will use Zustand for global state management. It provides a simple, un-opinionated, and hook-based API without the boilerplate of Redux.
## 3. Consequences
* Positive: Reduced boilerplate, better performance due to transient updates, easier learning curve for new developers.
* Negative: Less standardized architecture compared to Redux, might need careful structuring to prevent messy stores in large apps.
## 4. Alternatives Considered
* Redux Toolkit: Rejected due to boilerplate.
* Context API: Rejected due to performance issues with frequent updates.Steal our database of 20+ pre-written ADRs covering the most common frontend architecture decisions.
No spam. Unsubscribe anytime.
Discover more utility-driven tools designed to enhance your workflow and technical excellence.
Calculate error budgets and reliability targets. Know exactly when to freeze releases vs ship features.
Evaluate your repository's Developer Experience and spot friction points for new hires.
Detect heavy dependencies, deprecated packages, and bloat in your package.json.