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!

After trying for about months ,I think finally got this!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,

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.

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

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

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

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

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

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

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

CONGRATS ON 30K my man!

So glad I stumbled upon your tutorials! Thanks man!

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

Finally found an awesome Android teacher .

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.

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

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

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

Glad I stumbled upon this. Great explanation!

Thank you for your clear and step by step explanation !

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.

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! :)

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

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

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

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

Thanks for the demo of MVVM Liked it a lot

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

Thanks man. Very clear explanation.

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

Thanks again mitch!!

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

Thank you so much, this was more than helpful!

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

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

Excellent explanation! Thanks

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

The best Viewmodel video you can find, end!

Yes I need this right now :) Please more

Nicely explained, thanks!

your video is very helpful and well thought out

Thank you.

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

Pretty awesome work.

Nice job man keep going

Well explained the concept.

Nice explanation!

Thanks so much!

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

thanks mitch, love it

finally I understand, Thanks alot

Please continue this topic to adavance..🙏🖤

thanks a lot!!

Thanks a lot, man, bro! ;)

Brilliant video

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

Wow Man..Thanks a lot

Beautiful.

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).

Excellent

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?

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

thanks! nice tutorial

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

Thanks!

Very good explanation

Thank man, it's helpful!! thank you so much

cool explanation ... great...

Thank u for the tutorial...

thank you mitch

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

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

thank you so much......

All courses should teach using the best practices

Awesome.

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

Great video

I'm more of a MCVMPICVVM guy? It basically takes 2 years to write a simple app, but, it's worth the wait!

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.

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.

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?

great !

Loved the tutorial but I couldn't stop looking at the misspelling of Australia in the recycler app 😂

This one is awesome tutorial........ Please add local cache and retrofit both in your next tutorial..

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

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 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

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?

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 ?

good job

Is possible to share the same instance of view model between activities similar to share the same view model between fragments? Please Help

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.