OkMVP

An internal talk I gave at work on MVP.

Transcript

1. OK MVP Aaron He
2. OK MAP WHAT’S THE PROBLEM? ▸ We want to deliver features fast ▸ At same time we need it reliable, scalable and maintainable ▸ We also need a pattern that is consistent
3. OK MVP DECOUPLE BUSINESS LOGIC ▸ Activity/Fragment is difficult to test ▸ Yes, Espresso/UI Automater but with sloppy design Integration tests are a scam: https://vimeo.com/80533536
4. OK MVP WHAT IS MVP? ▸ Model-View-Presenter https://github.com/rallat/EffectiveAndroid
5. OK MVP MODEL-VIEW-PRESENTER ▸ Start by defining interfaces. Pop Config as an example. ▸ Model ▸ View ▸ Presenter ▸ The interface is the contract ▸ Can be mocked
6. OK MVP EASY TO INTEGRATE WITH LEGACY CODE ▸ Flexible ▸ Example: Confirm dialog when vehicle is deleted
7. OK MVP WHAT COULD GO WRONG ▸ The View ▸ Android fragmentation ▸ Interface is the contract ▸ But does the implementation actually do what you expect? Integration tests are a scam: https://vimeo.com/80533536
8. OK MVP OTHER CHOICES ▸ MVC ▸ MVVM ▸ U2020
9. OK MVP OK MVP ▸ An Ok architecture but simple, scalable, maintainable A few Ok libraries: https://www.youtube.com/watch?v=WvyScM_S88c