breaking it up in a large app for sure, based around some logical units (screen or feature, etc.). In @Elliott’s talk at droidcon he had some great examples of the actions doing the reduction by implementing a
Reducible
interface. Then your reducer is just really small and calls the reduce function on the action. I like that alot, but haven't tried it in a large project yet