You can make few optimizations : 1. Optimize the layouts - decrease the layout nesting as much as possible to increase the performance. 2. Remove one dependency (circle image view) since Glide provides an options to transform an image into circular one. 3. Avoid non-static or anonymous instances of AsyncTask - leads to memory leak. 4. Instead of NotifyDataSetChanged that will refresh the whole collection. You can just notify an item position or range that you are updating (NotifyItemInserted or NotifyItemRangeChanged). This will cause less ui calculations and drawing. Cheers!

Each time when I'm thinking about learning some new good stuff - you just upload new great video about it. Keep doing your fantastic job man, your tutorials are great!

I absolutely love your tutorials. So easy to follow and understand. I love your clean and direct explanation of the topics. Great job! Thank you so much!

Wow, just wow, I can't even begin to explain how you've inspired me. Thank you. :)

I really like your idea to present complete examples. Many tutorials on the internet contains only fragments of the entire solution, and very often the code doesn't even compile. Very good job!

I'm a big fan of your tutorials man, keep up with the good work !! (Y)

CONGRATS ON 30K my man!

After trying for about months ,I think finally got this!Thank you~!

much appreciated i always love your work man! you are a legend.

Just applied your example to my app, and it works. Thank you!

your video is incredible, it's my first time to deal with mvvm and all problems that have faced me, you already have put the answer for them in this video. thanks much,

Hey Mitch, you’re doing a great job! I’m sure with time you’ll have a ton of subscribers and views.

Yet another high quality tutorial from you Mitch. I could not understand how MVVM works. The other tutorials go into details of databases and related topics. The result is MVVM basics are difficult to follow and implement. I did have to watch this tutorial five or six times to understand the MVVM concept. To test my understanding, the kotlin recyclerview tutorial (BlogPost) by you was used as a starting point. Following the instructions in this video and the source code for this tutorial, BlogPost source code was converted to the MVVM model used in this tutorial. Along the way I had to jump to google to solve problems when the intended kotlin code did not work as expected. The code I amended now works like this tutorial including adding new blogs by clicking the floating button. Many, many thanks for such a good tutorial. You are one of my go to channels for Android learning. Appreciate the time you take to post these tutorials.

Suggestion: enable "Show taps" on your emulator under developer options so the viewer can see exactly where you are pressing when you are demoing stuff.

Finally found an awesome Android teacher .

Look at that I implemented viewmodel into my app last night and this afternoon I see your video!

This helped a lot in my understanding of MVVM. Hopefully I can build my own viewmodel soon

watched a lots of videos for mvvm but finally this one really taught me something thank you sir awesome explanation.

So glad I stumbled upon your tutorials! Thanks man!

So far the only tutorial on MVVM i eventually got working... i understood it better after watching this tutorial... thank you...

Glad I stumbled upon this. Great explanation!

maaaan you just took a complicated subject and made it simple thank you!!

thank you, this is awesome. really eazy to follow and focus to the important point

Waiting so bad for your rest api + MVVM Project!!

Logically clear, and it helps me understand MVVM better (Also the English speech is relatively easy so I can get your point well). GOOD TUTORIAL.

Much appreciated. This tutorial video is much informative. You have beautifully explained all the terms in MVVM. Keep it up.

thanks for that video, it was exactly what I was looking for. Excited for MVVM now :)

Thanks for the tutorial, it was really helpful! One tiny detail you could change is that, when creating classes with the singleton pattern, the getInstance method should ideally be synchronized to avoid race conditions. Apart from that, excellent tutorial! :)

Thank you for your clear and step by step explanation !

Thanks for the demo of MVVM Liked it a lot

You are creating really awsome content. We can feel that you are really putting your heart into it. I really really thank you. best of luck

Thanks man. Very clear explanation.

Great video as always, and nice teaching keep it up!

Very good explanation and example, you used a simple problem to explain about live data with MVVM arch, congrats.

Most simple tutorial ever seen bro, Thank you very much. U helped me lot

The best video for the beginners to understand the MVVM. Thank you

I also learned that if you need the application context in your viewmodel, just extend Androidviewmodel instead of ViewModel

Thank you so much, this was more than helpful!

Great explanation. First minute watched and i know what its about. Havent seen any better explanation than that.

Thanks for tutorial , you have explained Android MVVM way easier than other tutorials on youtube.

Thanks again mitch!!

thank u for this tutorial. I have a question. If I want to update 'mIsUpdating' variable from the repository, what is the recommended way to do it?

dudee...Just excellent this is really what i want

Thank you for explaining difference mutablelivedata vs livedata. I am very confused when to used both of them because they are basically almost same.

Awesome. Using your vids for my bachelor thesis.!!! thank you

Yes I need this right now :) Please more

The best Viewmodel video you can find, end!

Hey Mitch, I am a fan of your tutorials! One question to you for this tutorial: is it a good way to make the repository as a singleton? If that is the way, the singleton instance will be always alive and the livedata inside won't ever be released. I know this makes sense to the demo scenario because it is pure a places app hence we expect the data to be alive for ever. however I think you can explain a little bit for the cases sometimes we don't want to make the repository as singleton, and it should be bind to the lifecycle owner? Just my 2 cents, I am a rookie to Android, especially to LiveData(Jetpack).

It was great. 🙏 and, so helpful. 🙏 Thanks, Dear Mitch

Excellent explanation! Thanks

Nicely explained, thanks!

your video is very helpful and well thought out

Nice explanation!

Thank you.

Nice job man keep going

Thank you for the movie. One important comment: new nicePlace is added in MainActivityViewModel (and not in NicePlaceRepository). I would like to see how to run postValue from the NivePlaceRepository. Thank you.

Thats good info u are give to the world for free ... big love

5:57 The user is a datasource,too. Activity/Fragment editText.getText.toString is data.The user of the app is ALWAYS a Datasource

Well explained the concept.

Nice job man. I have a question though. I am working with data from an API, and every time the fragment refreshes, the recyclerview is repopulated and thus the items are all @t can I solve that?

Pretty awesome work.

These are interesting tutorials. The Java is a little odd to follow, though. Are you going to make versions of these videos in Kotlin?

Hey friend, greetings from Brazil, do you know if there's any project with this MVVM architecture where i can use as template to build up any app in it? Your video is teaching me a lot about this issue, thank you in advance !

thanks mitch, love it

finally I understand, Thanks alot

Thanks a lot, man, bro! ;)

setNicePlaces(); function means a action to get data from webservice, right? it's usually asynchronous, so how data can set in livedata sir? using interface to pass data instead?

Hello i am from India, You are Amazing brother, Thank you...

The hardest part in implementing MVVM is dealing with different data source like cache and local database and network, so your app can be useful even in situations like poor internet. I hope you use these different data sources in your upcoming tutorial

Hey Mitch, i ve a question, why did you used different packages for classes in it. They could have been in one package. How does it help ? Thanks in advance

Thanks so much!

Great video. I'm gonna have to rewatch it a few times though. As someone new to design patterns it was hard to follow.

What other things that I need to understand before learning MVVM other than Room,retrofit ?

whaaaaaaaaaaat !!!! i made the right decision subscribing you man !!!!

Hey Mitch, with repositories, am I supposed to make a single repository for all network operations on my app or multiple repositories with network operations that are relevant to each other?

thanks a lot!!

Mitch, why do we need to use postValue(), Instead you should have used setValue() itself, Since onpostexecute runs on the Main thread, setValue should be good enough right? please correct me if my understanding as wrong.

Do we have to use live data if we are using viewmodel and mvvm ? Like I have some values of user name, address, age etc.. so how to store and retrieve them using viewmodel and mvvm ?

thanks! nice tutorial

you should also make the default constructor of NicePlaceRepository class private. in order to implement the proper singleton method.

Please continue this topic to adavance..🙏🖤

hello mitch i was trying to fetch the data from firebase database using MVVM and following this lecture but it is not working,at the end mutableLivedata showing null,

I have modified the code by moving the function to add data to repository class. The viewmodel has links to live data in repository. The code compiles without error and runs. Can you confirm one query on update.

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?

Great work Mitch. But i have one doubt as per understanding ViewModel data should clear when we click back button in the mobile and activity is destoryed Right. Iam trying to reopen the app then recycler view Items going on increase. Is there any leak the program.

Does data get automatically updated in the app when its updated on the server or we have to call api again to get the latest data from server?

Thank u for the tutorial...

Where do we write the business logic in mvvm? In some articles it says Model and in some other articles it says Viewmodel.

Excellent

I really love your videos and you've been helping me a lot... But on your repository, the method is synchronous and on a real example, it would be asynchronous and I'm not sure how I'd do that. Should I create an interface for every method of my repository that has a method for when my request goes ok (a 200, for example) and another method for when there's an error (e.g a 500)?

Beautiful.

Brilliant video

Sometimes the live data tends to emit old values. I use SingleLiveEvent() as a replacement. Any other solutions?

Wow Man..Thanks a lot

Hey Mitch! There's a problem. If I actually call an online API in setNicePlaces() method in Repository class, and set the value of dataset in the onResponse(), the LiveData doesn't update the UI with the received data. How should that be implemented? Please help !!!!

Great Video! One Question: In your Repo in setNicePlaces(): Let's assume you wouldn't statically add all values but fetch them asynchronously (e.g. make a JSONObjectRequest), how would you implement this? In my case my fragment which observes changes for some reason only gets an update when a configuration change occurs.

cool explanation ... great...

Very good explanation

Hey Mitch, I thoroughly enjoyed the tutorial. I want to build a Scientific Calculator app to apply what I learnt here. Can I simply make the calculations in the ViewModel ? Where do I need a repository here unless I want to add a history feature by saving the previous calculations to SQLite? Can we use MVVM for any app no matter the size of the app? I'm not using a specific architecture at my workplace yet. So I'm working on some simple side apps to get started. I have some confusion on the role of viewmodel and the repository - especially for the apps that don't require much SQLite or Network operations. Please clarify.

Line 46 (28:24) - you are getting back the new list from the viewmodel everytime the observer knows about a change but you do nothing with the new list that you receive - so why bother notifying the adapter for any changes as you do nothing with these changes anyway?