It really is. And then the optional events if you need traceability and decoupling, the injectDispatch API for easy dispatching of events anywhere you need to do it, easy entity management if you need it. It’s awesome how something so simple is so easily extensible to serve virtually any use case no matter how big or small.

It works beautifully for both. You can provide a signal store in root for global state. In my experience, few things are truly global state: auth, preferences, user roles, RBAC, any global context like a customer switcher, etc. If you want traceability of actions or you just want to keep stores that impact others decoupled, you can define events and event groups, and then dispatch those from wherever you need, then you can add withReducers to the signal store to define events it should listen for and perform state transitions. Unless specified, signal store is local. You can provide it at the route config level so that all components on that route and any sub routes get the same instance. You can just provide it at the component level so that a particular component and its children gets access to the same instance. It’s just the golden standard of state management.

Thanks a lot!

Agreed. Signal Store is top notch 💪

completely agree, it stay simples when you want it simple, and can scale with custom features when you need it