Omg it's amazing that you're covering this topic & not only in theory!!! When can we expect the next upload can't wait looking very much forward to it!!! Thank you soooo much for making these amazing videos 😍😍😍😍
Single source of truth ... data from a toaster ... This is the type of lingo that anyone can understand, and now that I know what mvvm is, its never too late to split my 4000 line fragment views. I should have seen this earlier but your video was and is the ultimate motivation
Hey Reso, Hello from Novo Mesto. I got an idea of a project you might start. Make like an e-commerce app with MVVM, retrofit, coroutines, I think it would cover a lot of things. I think those series would be amazing.
Other than ViewModel advantage,configuration change, what's the real benefit of using MVVM considering all the hassle and fuss involved in MVVM along with Retrofit? Assume I was to create a simple app that just makes network request using Volley without the need of worrying screen rotation, and DAO, what's the advantage we are getting for banging head learning complex architecture that can be achieved in just 10 liner code? It's no doubt good for complex projects though since it's well structured and Unit testing friendly. But what for a simple app?
Downvoted because this video like most of them completely ignores the part about business objects. Apps are not just about grabbing data and displaying it, like this video and so many show. Most apps have classes that have nothing to do with retrieving data or displaying it but manipulating the data, making business logic decisions and deciding what the user gets to see. Those blocks need to be integrated into the hierarchy. Believe me, I've been building software for 3 decades and it really amazes me how so many young developers just can't get this.
Thank you for your valuable input. I tend to put business logic into classes which are contained as objects of a some general IO class, like repository. I pass data to them, wait for an output and return the output from a repository. The client code from the UI only calls simple methods on the ViewModel which calls the repository and thus the UI code doesn't know about the intricacies of the business logic.
@@ResoCoder The problem with your illustration is that you imply that the viewmodel communicates with the repository. A repository is always associated with data storage. In most cases, business logic classes are what are used to communicate to data access components such as a repository. So a proper hierarchy would show the viewmodel communicating to business object components and not a repository component. The business objects in turn communicate with the repository.
You speak so clearly that i do not have to turn on subs
exactly
This is the best video on MVVM. Explains the concept on detail level.
. ruclips.net/video/Y5ys6chK_wI/видео.html
Only video that actually made me understand MVVM.. thanks😊
. ruclips.net/video/Y5ys6chK_wI/видео.html
This is the best tutorial about MVVM so far.. Very easy to follow and understand
. ruclips.net/video/Y5ys6chK_wI/видео.html
The best video that abstract the idea in a simple way for me!
thank you !
I'm late to this party, but this is the best explanation I've gotten to date! Thanks a million!
Omg it's amazing that you're covering this topic & not only in theory!!! When can we expect the next upload can't wait looking very much forward to it!!! Thank you soooo much for making these amazing videos 😍😍😍😍
I'm happy to help 😉 The next tutorial about using MVVM in a real app will be out next Friday!
@@ResoCoder can i have the link please ?
I just made a video about that topic too 👍
Wow! Android Architecture Components is so awesome that we're all excited about it 😃
Yea they are and it's a lot of fun to work with them. Especially when it comes to configuration changes.
yea ... hello my teacher , your tutorial really amazing
And thank you both for your work :)
Its hard
Single source of truth ... data from a toaster ... This is the type of lingo that anyone can understand, and now that I know what mvvm is, its never too late to split my 4000 line fragment views. I should have seen this earlier but your video was and is the ultimate motivation
it's the best explained in MVVM so far
You've just gained one subscriber. Great Tutorial
One of the best explanations on youtube on MVVM Cheers Mate! Thnks for sharing :)
The best MVVM explanation I've seen. Thank you.
Very informative video, understood everything from beggining to the end, keep up the good work ;)
I so loved it.Was struggling from days to grasp this.Even though android it really applies to all framewworks.
. ruclips.net/video/Y5ys6chK_wI/видео.html
Hey Reso, Hello from Novo Mesto. I got an idea of a project you might start. Make like an e-commerce app with MVVM, retrofit, coroutines, I think it would cover a lot of things. I think those series would be amazing.
9:02 actually, safety is number one priority
Thank you. This concept explanation truly helped me.
watching this in 2021 mmm this is good stuff man
Really Good Explanation about MVVM Architecture. Thank you
.. ruclips.net/video/Y5ys6chK_wI/видео.html
LOVE IT! THANKS FOR THE CLEAR INFO
Great and simple explanation of the MVVM pattern. Thank you! 😊
Thanks. This is a good tutorial. I recommend others to follow. Happy Coding.
The explanation was clear and objective. Thank you
Thank you for the video! Keep making such understandable videos! :)
please make a video, difference between MVP and MVVM and why we should use MVVM
I didn't get what is MvvM , liveData but your video tutorial give me a lot of info thx
Thank you! Very clear explanation.
Wow this helped so much thank you.
i will share this video to my friend without doubt!
Very nice explanation
I sense potential in this channel. Subbing.
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Simple and clear! thx
Thanks for this explanation. It helps me a lot.
Hello sir i am big fan of yours i love your videos.can you please make new video on appodeal ads integration in unity thanks😊
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Thanks for the tutorials, they are well done!
Really helpful
Thank you!
very nice video man, props!
Thanks reso!
phenomenal
its one of the best
Great intro thanks!
Thanks! Your videos are amazing
Outstanding 👍
.. ruclips.net/video/Y5ys6chK_wI/видео.html
thank you! I think it's a important basic pattern
@ 5:22 so do you suggest this marks the end of RxJava ??
Live data is the new kid around the block?
Thank You!
crystal clear
Very informative video.. thanks
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Can I get the next video link, please? This video is really helpful. Looking forward more to learn about MVVM structure.....
He also made this video ruclips.net/video/d7UxPYxgBoA/видео.html
You should make a full course on Android development. Please do it.
I will in the near future!
Such a great explanation!
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Awesome!
You are great. 🇧🇩
Does the 'DB' on the diagram refer to 'database' or its something else. thanks
Other than ViewModel advantage,configuration change, what's the real benefit of using MVVM considering all the hassle and fuss involved in MVVM along with Retrofit?
Assume I was to create a simple app that just makes network request using Volley without the need of worrying screen rotation, and DAO, what's the advantage we are getting for banging head learning complex architecture that can be achieved in just 10 liner code? It's no doubt good for complex projects though since it's well structured and Unit testing friendly. But what for a simple app?
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Thank you, I have been looking implementing mvvm in Android, I know how to do that on Xamarin, but on Android I don't.
Nicely explained ❤
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Very well explained.
.. ruclips.net/video/Y5ys6chK_wI/видео.html
very nice video
Good explanation,Thx.
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Great explanation
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Nice Tutorial thanks
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Thanks.
Thanks man
.. ruclips.net/video/Y5ys6chK_wI/видео.html
great. thank you
.. ruclips.net/video/Y5ys6chK_wI/видео.html
hey are you paulo from udemy?
Thanks. It very useful. You always use this pattern?
In the past, no. In the future? Hell yeah 😄
good google
very good
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Hi there, I have a doubt, can a screen have multiple viewmodels?
.. ruclips.net/video/Y5ys6chK_wI/видео.html
awesome! a lot of thanks! (боже даже я понял)
plz, teach us anko from begin to end:)
Plz make a small game in android studio.😃😃
I will try but it might not be appropriately good for a video 😂
It's not clear, its always better to show a real example
You will read your code many more times than you write it
What's this all about sir?😉
.. ruclips.net/video/Y5ys6chK_wI/видео.html
Downvoted because this video like most of them completely ignores the part about business objects. Apps are not just about grabbing data and displaying it, like this video and so many show. Most apps have classes that have nothing to do with retrieving data or displaying it but manipulating the data, making business logic decisions and deciding what the user gets to see. Those blocks need to be integrated into the hierarchy. Believe me, I've been building software for 3 decades and it really amazes me how so many young developers just can't get this.
Thank you for your valuable input. I tend to put business logic into classes which are contained as objects of a some general IO class, like repository. I pass data to them, wait for an output and return the output from a repository. The client code from the UI only calls simple methods on the ViewModel which calls the repository and thus the UI code doesn't know about the intricacies of the business logic.
@@ResoCoder The problem with your illustration is that you imply that the viewmodel communicates with the repository. A repository is always associated with data storage. In most cases, business logic classes are what are used to communicate to data access components such as a repository. So a proper hierarchy would show the viewmodel communicating to business object components and not a repository component. The business objects in turn communicate with the repository.
Oh, thanks. I've actually never seen a class hierarchy like you describe. Not even in tbe official Android docs. It makes sense though.
.. ruclips.net/video/Y5ys6chK_wI/видео.html
thank you