I like this approach. He's essentially using selectors for most of the app logic, which are cached and are what the view components use to derive data. They're

I like this approach. He's essentially using selectors for most of the app logic, which are cached and are what the view components use to derive data. They're cool because they always give you a "fresh look" at what's in state. I find it interesting in his implementation that selectors can also dispatch other actions. If the author is reading: have you ever read about Behavioral Programming (BP) principles? I have written a bit about it here: - https://lmatteis.github.io/react-behavioral/ https://lmatteis.github.io/react-behavioral/ - https://medium.freecodecamp.org/an-intro-to-behavioral-programming-with-react-request-wait-and-block-ad876e2d235e https://medium.freecodecamp.org/an-intro-to-behavioral-progr... And also have given a talk about how UIs can better align with requirements: https://vimeo.com/298554103 https://vimeo.com/298554103 BP is still driven by trying to make change easier to implement in a large codebase, so I think there are some high-level similarities with your approach.