One underrated thing that I miss from using Redux is the "action trace". You can literally sit down with the stakeholders [1] and explain the exact things that caused a screen to render. And these things are not cryptic function calls with stack-traces, but simple and chronologically ordered sets of human readable "actions" (I like to think of them as events) like UserFetched -> PlanFetched (<with this data>) -> FrozenUser. One can rewind the actions and iterate with the stakeholders why that screen appeared. This is huge and I miss this a lot.
1. Note that most of the time the stakeholder is yourself and/or another developer. But can also definitely be a non-coder.
1. Note that most of the time the stakeholder is yourself and/or another developer. But can also definitely be a non-coder.