[Needs investigation] Shared ViewPool for Nested RecyclerView

[anandwana001]

Is your feature request related to a problem? Please describe. This issue is a suggestion for optimizing and improving recycler view performance.

Describe the solution you'd like One of the approaches using which we can improve the scrolling/loading of our nested RecyclerView is to use a shared view pool with all our nested recycler views as well apparent recycler view.

Additional context This issue is a conversation point in the team meetings. This is more of an investigation if we require this or not. Also, if doing this will help us to increase the performance by 25% or more, if not it's worth to do.

[BenHenning]

At first glance this seems potentially really difficult to solve generically, but it probably depends on the context. @anandwana001 can you point out the cases where we're using nested recycler views to better help contextualize the problem space?

[BenHenning]

Next steps: we need to dig into this with a specific nested recycler view example to get a sense of:

• Will this introduce any performance benefits? If so, what are these benefits (in quantified metrics)?
• How complex is integrating view pool with our existing bindable adapter pattern?