Architecture Blueprints and Testing in Android - Introduction

Introductory slides for the Architecture Blueprints and Testing in Android event organised by GDG Ibadan on September 24th, 2016. It contains details about the schedule of the event nad the basics of the MVP architecture on Android

Transcript

1. Architecture Blueprints and Testing in Android Hamza Fetuga Adegeye Mayowa Efeturi Money
2. What we’ll be talking about  Architecture blueprints in Android?  MVP  CodeLabs  Clean Architecture  CodeLabs  Testing  CodeLabs
3. Architecture Blueprints in Android
4. What is the status quo?
5. Why is any of this necessary?
6. Architecture Blueprints in Android The Android framework offers a lot of flexibility when it comes to defining how to organize and architect an Android app. This freedom, whilst very valuable, can also result in apps with large classes, inconsistent naming and architectures (or lack of) that can make testing, maintaining and extending difficult.
7. Architecture Blueprints in Android  Helps solves these common problems  Structure, testing and maintainability
8. Types of architecture blueprints  MVP (Model View Presenter)  Clean Architecture  MVVM (Model View-View Model)
9. MVP The model is the data that will be displayed in the view (user interface).
10. MVP The view is an interface that displays data (the model) and routes user commands (events) to the Presenter to act upon that data. The view usually has a reference to its Presenter.
11. MVP The Presenter is the “middle- man” (played by the controller in MVC) and has references to both, view and model
12. MVP
13. MVP
14. MVP (Gmail Android app)