watermark logo

āĻĒāϰāĻŦāĻ°ā§āϤ⧀ āφāϏāϛ⧇

āĻ¸ā§āĻŦāϝāĻŧāĻ‚āĻ•ā§āϰāĻŋāϝāĻŧ āϚāĻžāϞ⧁

ViewModel Explained - Android Architecture Component | Tutorial

2 āĻ­āĻŋāω â€ĸ 10/12/24
āĻļ⧇āϝāĻŧāĻžāϰ āĻ•āϰ⧁āύ
āĻŦāϏāĻžāύ
121gamers
121gamers
14 āϏāĻžāĻŦāĻ¸ā§āĻ•ā§āϰāĻžāχāĻŦāĻžāϰ
14

🏆 My Online Courses
⭐Discount Coupon: LAUNCH-STEVDZA-SAN
https://stevdza-san.com

🐱‍👤 Wanna become a member? Join!
https://www.youtube.com/channe....l/UCYLAirIEMMXtWOECu

📸 Instagram
https://www.instagram.com/stevdza_san/


// ViewModel dependency
implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:2.2.0"

The ViewModel class is designed to store and manage UI-related data in a lifecycle conscious way. The ViewModel class allows data to survive configuration changes such as screen rotations. So when we are talking about Activity or Fragment we are actualy refering to UI Controllers. And ViewModel class should be created for each UI Controller in order to separate things like data and diferent calculations from UI Controler. In UI Controller there should only be necessary code for managing our UI, and everything else we could placed inside a ViewModel class.


Timestamps
0:00 - Introducing with ViewModel
1:30 - Practical example with ViewModel
6:30 - Conclusion

āφāϰ⧋ āĻĻ⧇āϖ⧁āύ
0 āĻŽāĻ¨ā§āϤāĻŦā§āϝ sort āĻ•ā§āϰāĻŽāĻžāύ⧁āϏāĻžāϰ
āĻĢ⧇āϏāĻŦ⧁āĻ• āĻŽāĻ¨ā§āϤāĻŦā§āϝ

āĻĒāϰāĻŦāĻ°ā§āϤ⧀ āφāϏāϛ⧇

āĻ¸ā§āĻŦāϝāĻŧāĻ‚āĻ•ā§āϰāĻŋāϝāĻŧ āϚāĻžāϞ⧁