State only travels in one direction • State is immutable • State is modified by pure functions Source: redux.js.org/docs/introduction/ThreePrinciples.html @karlbowden
is divided into: • Input and Output ~ State and Actions • Side effects ~ pushed to the edges • into Action Creators, Middleware and Services • State mutation: performed by Reducers @karlbowden
of state are used or changed in multiple components. • Ie, Battleships. One set of rules. Multiple different views of the same state. Multiple inputs. • Side effect handling • Dealing with one or more API's • External sources of actions • Push API's & WebSockets @karlbowden
and tested • Large state. Ie, don't store images in the state tree, just use references • High performance gesture interactions • Don't create unthrottled actions for every touch event @karlbowden
sorting arrays • Reducer should not cause side effects • I've got 99 problems, but globals ain't one of them • Globals / Singletons / Shared Instances still cause Coupling • Use coordinator + presenters @karlbowden
Swift / Realm presentation Redux Dan Abramov: Getting Started with Redux on Egghead Special Thank You to: Aleksander Rendtslev - @ARendtslev Benjamin Encz - @benjaminencz @karlbowden