Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalI think the problem is not multiple layouts, but the image processing you are doing in the different layouts.
If you set large bitmap to smaller imageView it would take too much memory. So it is better to put image tasks on different thread, for that you can use some good image library like "Picasso" or "Universal Image Loader".
For More optimization tips about recycler view, you can find hereClick here
I think the problem is not multiple layouts, but the image processing you are doing in the different layouts.
If you set large bitmap to smaller imageView it would take too much memory. So it is better to put image tasks on different thread, for that you can use some good image library like "Picasso" or "Universal Image Loader".
More optimization tips about recycler view, you can find here
I think the problem is not multiple layouts, but the image processing you are doing in the different layouts.
If you set large bitmap to smaller imageView it would take too much memory. So it is better to put image tasks on different thread, for that you can use some good image library like "Picasso" or "Universal Image Loader".
For More optimization tips about recycler view, Click here
I think the problem is not multiple layouts, but the image processing you are doing in the different layouts.
If you set large bitmap to smaller imageView it would take too much memory. So it is better to put image tasks on different thread, for that you can use some good image library like "Picasso" or "Universal Image Loader".
More optimization tips about recycler view, you can find here
