We are trying to understand how viewmodels and recyclerviews can work together. In our case we have a custom view, used in an activity, with its own viewmodel. Now this custom view need to be part of the layout of items in a recyclerview. That means each ViewHolder will have a ViewModel attached to it. We think it’s not a good solution but we’re wondering what would it be a way to structure this type of situation. ViewModel attached to the adapter (we think it’s bad)? use DataBinding to connect VH and VM? we don’t have databinding set up in the project though. What do you guys think?

In the sunflower app (https://github.com/googlesamples/android-sunflower) , the Adapter ViewHolder has a viewModel and this ViewModel sets the data. You can check it out and see if that works for you 😄.

uh thanks. I always forget about the sunflower project 🙂

Don’t worry, I hope that can help you or give you an idea at least.

I think the big difference we have compared with this example is that we need livedata to change the VH UI after an API call

Oh my. There is some kind of design flaw. Try to read this article https://proandroiddev.com/adapting-your-recyclerview-the-2019-approach-e47edf2fc4f3 Maybe it will help you resolve your problem

I’ve never mentioned fragment inside a RecyclerView. This is not what we have and this is definitely not what we want. Thanks anyway for the link 🙂

Yes yes. I has in my mind analogy for complex view with viewmodel and wrote it as example

I would recommend having your Activity ViewModel expose the data source (ex; livedata of list of stuff) which your Activity observes and updates an Adapter the activity manages.