The Android Architecture

Slides for DroidYangon2019

Transcript

1. The Android Architecture @myolwin00
2. Why do we need this?
3. Separation of concerns(SoC) • Don’t write all your code in an Activity or a Fragment • Separate into sections • Encapsulate informations
4. Issues • Limited resource • UI controllers are not for business logic • You don't own implementations of Activity and Fragment • Destroyed after configuration changes • Potential memory leaks • Hard to test • Hard to maintain • And extending your app is more difficult
5. If you shouldn't use app components to store app data and state, how should you design your app?
6. Clean Architecture, Chapter 15 “A good software architecture allows the system to be easy to understand, to develop, to maintain and to implement.”
7. Common Architectures • MVC • MVP • MVVM • MVI, Clean Architecture and more…
8. Model-View-Controller(MVC)
9. • Describe business logic • Data operation • Define data manipulation Model • Represent UI components • Display the data from Controller View • Coordinate between View and Model Controller
10. MVP(Model-View-Presenter)
11. MVVM(Model-View-ViewModel)
12. Loaders • AsyncTaskLoader • CursorLoader
13. Loaders
14. MVVM with AAC Source: https://developer.android.com/jetpack/docs/guide
15. ViewModel From AAC • Replace loaders • Manage UI-related data in a lifecycle conscious way • Survive configuration changes
16. ViewModel Lifecycle
17. Useful links • https://github.com/googlesamples/android-architecture • https://github.com/googlesamples/android- architecture-components • https://developer.android.com/jetpack/docs/guide
18. Thank You ! It’s question time ! @myolwin00