MVVM Presentation
- 1. MVVM on Android Using Data Binding Library By: Javad Arjmandi Spring 2018 irLogcat Tehran, Iran
- 2. Architectural Pattern • Much like Design Patterns but in a broader scope • Also called Behavioral Patterns • Answers to the roles of each class/module • Helps maintain the software in a conventional way
- 3. Model-View-ViewModel Image courtesy of Microsoft Developer Network
- 4. The Model • It’s NOT a POJO • Holds the data • Is not necessarily the creator/provider of the data • Similar to Back-end of a Client-Server model Application
- 5. The View • Static and dynamic views provided in static files such as XML or XAML (for WPF) • Little or no logic code is contained by The View • Event handling, action and data manipulation logic code shouldn’t be in the code behind in View.
- 6. The ViewModel • Data provider for views. • Data interaction and manipulation • Most of the logic of the application • Is isolated from the view behavior wether static or dynamic
- 7. MVVM vs. MVC • ViewModel is identical to Controller, but they differ in nature • Full separation of UI and Logic • Models are more than just models; They have functionalities as well
- 8. What is Two-Way Binding?
- 9. Data Binding Library • Introduced in Google I/O 2015 • No longer need to glue • Views and layouts are first class java objects
- 10. Talk is cheap; Show me the code!
- 11. More Resources • Husayn Hakeem’s Articles in medium.com • Official developer guide for Data Binding Library on d.android.com • MSDN documents on MVVM • Google :)
- 12. Credits • Beeptunes Company • irLogcat team • Davud Hosseiny • Ashkan Taravati • You! Special Thanks to…