[ac2u]

I don't think he/she meant that they used a flux pattern in addition to redux. Even though redux differs in many ways (self-admittedly) to canon Flux implementations, it's largely regarded to be in the flux family when folks are weighing up alternatives.

The problem detailed reared itself in my own efforts too, all the flux implementations promise elegance until a router comes along, which in many ways is another actor exerting control over what's on the user's screen.

You have to then make the choice on whether you want the router to handle what high level components are displayed, or if you want changes in the router to feed directly into changes in your state tree and then have it handled from there. That's where the complication comes in.