Swift, do you even Flux?

In 2014, Facebook brought us Flux and with it, the idea of unidirectional data flow. Allied with React, Flux and its variations took the Web World by storm. Today's mobile apps also rely heavily on data handling so why not apply the same principles to it? This talk is aimed at the mobile community, specifically the iOS community. It is supposed to be an intro to the unidirectional data flow pattern, cover the basics of how to use Flux and Redux on iOS and share my experience in applying it to existing code, its benefits and pitfalls.

Transcript

1. Swift, do you even Flux? Afonso Graça @AfonsoGraca
2. This is not about which architecture is the best.
3. MVC MVVM MVP Ŏ
4. Too broad?
5. Present day Apps › UI-Driven › Connected › Persistent 
6. Why is UI Code such a pain? Complex
9. What is Flux really? Action Dispatcher Store View
10. But how can I use it in iOS? › Dispatcher › State › Actions › Stores › View Controllers
11. What about Redux? Reducer #1 Reducer #2 Store View Action
12. Benefits › Clear State Propagation › Incremental adoption › Testability & Debuggability › Predictability
13. Drawbacks › Lack Reactive UIKit › Multiple Store Dependency
14. ? Alternatives › Elm › React Native
15. It’s a wrap! › Strive for simplicity › Increase familiarity › Be a breaker of conventions
16. Afonso Graça ² afonsograca @AfonsoGraca Thank You!