Android. Is using fragments in RecyclerView justified?

Question

Android

I have a card that, among other information, can contain an image, an image slider (3rd party library) or a video (YouTubeAPI). Previously, in the layout of the card, I simply indicated all three media elements (image, slider, video) and, depending on the needs, changed their visibility, hiding unnecessary elements and leaving only the necessary one visible.
Then I decided to try using fragments. I made three fragments, for each element (I note that the fragment class contains all the logic of the element, it only needs to pass parameters for initialization, and it will do the rest itself), and tried to use it in RecyclerView. If earlier I had three elements in the card, now I just wanted to put the fragment I needed in a special container in the card. But it was not there. In the onBindViewHolder of my RecyclerView adapter, this code replaces only the first element:

ImageSliderFragment fragment = ImageSliderFragment.newInstance(currentItem.images, mContext);
fragmentManager.beginTransaction().replace(R.id.card_media_container, fragment).commit();

I also read that using fragments in RecyclerView is highly undesirable. The question is whether it is worth using fragments in this case, for the sake of simplicity (these fragments are also used in another activity, besides, all the logic of media elements used to be in the RecyclerView adapter, and now it has been moved to their fragment classes). Or is it worth using the old scheme - the card immediately contains all the media elements that are made visible / invisible and filled in as needed? But then there is code duplication. the logic of the elements will again be in the RecyclerView adapter.
And if using fragments is justified - what is the right way to use them in RecyclerView? For some reason, only the first element is filled in.

Answer 1

There is no need to combine three Views into one fragment, since we RecyclerViewalready have the following methods for creating and binding a ViewHolder:
and
The viewType parameter is what you need. Override the method
so that for each element of the adapter it returns the desired type (video / slider / image), in onCreateViewHolder() inflate the desired view depending on the type of view, and create a ViewHolder, and in onBindViewHolder() bind the desired element to the viewholder, in depending on the type of the element.

Answer 2

The solution to filling only the first element is to specify not the usual container id, but assign a unique id to the container of each element and insert a fragment into it.
The question of the appropriateness of using the fragment in this particular case remains open.