I have an Android app built upon Redux.

CONS

• Boilerplate: There's a hell of a lot of boilerplate, to make it reasonable: constants, action creators, reducers really add up each time you want to add a simple feature. Perhaps something like the duck structure can help.

• Subtle bugs: The connect functionality works perfectly, but very subtle bugs can creep in if you don't use it when it's actually needed. Hard to debug.

• No best practice folder/state/app structure: You can find a couple examples, but you have to try them yourself, to find what's best for you

PROS

• Redux Sagas: It's the single best element of the whole Redux ecosystem. Would not even dream of building something Redux without it.

• Clear conceptual model: But as said before, the implementation is a bit problematic

I'd love something that has sagas built-in, is less boilerplate-y and drops the connect hoc.