FLUX based clean architecure

Presented on Droidcon IT 2016

demo code: https://github.com/unsign3d/cleancodeapp/
html version: https://s3-eu-west-1.amazonaws.com/yolobruzzy/dcit2016finale.html#/step-1

REDDIT THREAD (there are good info on that topic): https://www.reddit.com/r/androiddev/comments/4e5dcb/bring_facebooks_flux_architecture_on_android/

YOUTUBE VIDEO (IT): https://www.youtube.com/watch?v=yOmv2OfpZ4c

Transcript

1. FLUX based clean architecture Luca Bruzzone @unsign3d Android developer @ Tandù Notes: Why u no just MVP/MVC? No real rules on events No real rules on business rules Limited modularity for use cases Notes:
2. Notes: WHY FLUX Strict rules on events Models has their own states Better support for use cases Single flow of data Notes:
3. Notes: WHY FLUX Events are detached from data Events are empty classes Data are detached from views Dispatcher just work It's nothing new, is just pub/sub agent messaging Notes:
4. Notes: USE CASES, NOT LAYERS Write modules that do one thing and do it well Modules are indipendents from each others Notes:
5. Notes: unsign3d/cleancodeapp data_layer module handles retriving of data res divided by use cases modules for use cases Notes:
6. unsign3d/cleancodeapp Each app module contains Activities Adapters and ViewHolders Controllers Stores Notes: Notes:
7. Bonus tips Use RxJava and RxAndroid Don't use setters on models Use resource separation Unit test everything Avoid AsyncTasks Avoid singletons, register obj on Application class Notes: Thanks Tandù Scale.ws lgvalle/android-flux-todo-app fernandocejas.com Notes: