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!

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.

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.

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

Finally found an awesome Android teacher .

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!

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

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

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

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!

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

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

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,

All courses should teach using the best practices

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

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

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.

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

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

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

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

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

CONGRATS ON 30K my man!

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

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

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

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

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

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

So glad I stumbled upon your tutorials! Thanks man!

Thank you for your clear and step by step explanation !

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

Glad I stumbled upon this. Great explanation!

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

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

Thanks man. Very clear explanation.

Thanks for the demo of MVVM Liked it a lot

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?

The best Viewmodel video you can find, end!

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

Please continue this topic to adavance..🙏🖤

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

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

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

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

I dont understand how the list in the adapter automatically changed. We just call notifydatasetchanged(), but doesn't add the new value to the list in adapter. But somehow when the list in livedata is updated, the list in adapter is updated too. How that's work? The list in adapter is just normal list and we doesn't update it too..

Add imageview inside card view and give card view radius of half of it's height and it will be circular imageview

your video is very helpful and well thought out

Your style of teaching and the topic is very nice! But I have one issue: As far as I know the business logic doesn't belong to the viewmodels at all. In my opinion the viewmodels job is to prepare the data for the view and to route events between model and view so the view knows when the model changes and the view actions result in business logic calls on the model. That said - nice video! I did like it :)

Excellent explanation! Thanks

Really nice and well explained tutorial, notice that "ViewModelProviders" has been deprecated and now have to use "ViewModelProvider"only :)

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

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

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

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

Good video! But Android team didn’t come up with the name view model, Microsoft did lol

Yes I need this right now :) Please more

Google could have done far worse than to create an MVVM framework, but Google didn’t do anything for naming more grand than following naming as created by Microsoft for the ViewModel class, keeping in context MVVM is a Microsoft creation. Now, if only all the old Microsoft Windows GUI applications were self-consistent for how they were architected for the GUI code versus the rest, with keeping it separated...

If only the MutableLiveData objects can change and I understand you can "observe" those changes, why would the regular LiveData have the observe method, if it does not change. Are we always supposed to use the MutableLiveData?

Please use the dark theme for your IDE... very hard to watch the video during the night

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

Honestly speaking, this video is not for complete beginners.

I am still confuse with the adapter you have not used data binding in the xml of recyclerView item

Thank you so much, this was more than helpful!

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

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

Pretty awesome work.

Nicely explained, thanks!

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

Awesome video , great Job my friend. Thanks for your smooth English and great explanation, I was really frustrated by Indian videos out there.. glg lglgl gl

ViewModelProviders.of(context) is deprecated..what to use instead

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?

Thanks again mitch!!

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

Very good explanation

The way you describe mvvm, it sounds exactly like mvc. The model is the same, the view is the same, the repository/ DAO/ data layer is the same, and the controller in MVC is a wrapper for the application's business logic. You say that the viewmodel in mvvm has the same responsibility. I am struggling to see the difference.

Thank you.

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.

Anyone had a problem with items not showing until you rotate screen ?

thanks mitch, love it

Is mAdapter != null in 46 row inside your activity? U init mAdapter only in 50 row....

Well explained the concept.

I just done your demo example , it so simple i understood the concept cleanly . But when i tried to implement this with my Database related app its hard to handle , didn't work in my case. I have to minimize app and then reopen it then i see changes. Just waiting for you MVVM Retrofit tutorial to understood it clearly. Thanks for all.

That sounds so great. What are the differences between various Android architectures? What is the proper ways to use them?

I'm confused when you used Singleton Pattern, especially after reading this stackoverflow comment: "An Android Service (sub)class cannot be a singleton since the framework requires access to a default constructor for the class. The only reason I can think of for keeping a static reference to the (last) instance for which onStart was called is to simplify some internal code that may happen to reside in static methods. Considering that onStart was deprecated a long time ago (as of API level 5), this is most likely an example of bad coding style from early days of Android."

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

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 a lot, man, bro! ;)

I have found a bug. Each time the app is restarted the dataSet is duplicated. To avoid this I have added dataSet.clear(); in the method setNicePlaces() Do you noticed this also? Why the array is saved?

@CodingWithMitch got a new subscriber :)

Hi , I am unable to Register into your Official website I am registering for the very first time but still says "Account with this Username already exists".

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.

I just started learning MVVM so sorry if my question is stupid, at 23:49 you are making an example of what would be a server request, here you have a reference to `mIsUpdating` but is my understanding that I should have my api/db access code in the repository right? So If I make a server request on my Repository, how can I change `mIsUpdating`? I guess I could pass a reference of `mIsUpdating` to the repo but this is just me speculating I don't know if it's the best practice

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

cool explanation ... great...

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,

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.