ProTalk #1 | Android Architecture Component

Dalam Talks ini kita akan membahas design pattern dan arsitektur yang dapat membantu pengembangan aplikasi android yang digunakan di industry-grade android apps.

Transcript

1. Android Architecture Pattern Setyo Nugroho
2. Let’s know the problem
3. My activity is so big! Need to change UI? Where do i put the logic for this action? How to test this function? A new team member! A new wild bug appear!
4. Why you should do it?
5. • Separation of Concern • Easier unit testing • Easier to manage big project • Make your code understandable • Avoid GOD activity
6. Some Common Architecture Pattern
7. MVP Model-View-Presenter https://github.com/setyongr/SimpleMVPDemo
8. • Model — the data layer. Responsible for handling the business logic and communication with the network and database layers. • View — the UI layer. Displays the data and notifies the Presenter about user actions. • Presenter — retrieves the data from the Model, applies the UI logic and manages the state of the View, decides what to display and reacts to user input notifications from the View.
10. Show me the code!
11. MVVM Model - View - View Model https://github.com/setyongr/SimpleMVVMDemo
13. • Model: abstracts the data source. The ViewModel works with the DataModel to get and save the data. • View: that informs the ViewModel about the user’s actions • View Model: exposes streams of data relevant to the View • Recommended by Google
14. Lets meet Android Architecture Component
15. Lifecycle
16. Add to your application
17. ViewModel
18. Lets talk about the problem • State loss on orientation change. handling it with onSaveInstanceState() and onCreate() is tedious especially when the data is large
19. ViewModel Scope
20. Implementing ViewModel
21. ViewModel in Activity
22. LiveData
23. LiveData is an observable data holder class. Unlike a regular observable, LiveData is lifecycle-aware, meaning it respects the lifecycle of other app components, such as activities, fragments, or services. This awareness ensures LiveData only updates app component observers that are in an active lifecycle state.
24. Advantage of LiveData • Ensures your UI matches your data state • No memory leaks • No crashes due to stopped activities • No more manual lifecycle handling • Always up to date data • Proper configuration changes • Sharing resources
27. Navigation
28. Advantages • Single Activity for entire application • Graphical navigation flow editor • Shared ViewModel • Currently still beta
29. Adding navigation to your application • More at: https://developer.android.com/jetpack/androidx/releases/navigation
32. In your Activity
33. Navigating • findNavController().navigate(R.id.action_id) • findNavController().navigateUp()
34. Another Architecture Pattern
35. MVI Model-View-Intent • Unidirectional data flow • Reactive • Take inspiration from JavaScript framework like React.js and Redux • Use functional principle • Used by Bukalapak but simplified Reference: http://hannesdorfmann.com/android/model-view-intent
36. Mobius by Spotify
37. MVICore by Badoo
38. MvRx by AirBnb Currently this is my favourite architecture
39. Learn More: Example by Google: https://github.com/ googlesamples/android-architecture
40. What the best architecture?
41. Thank you