compose-views-interop

To fix jank in ComposeView RecyclerView ViewHolders, minimize Composition-phase work at interop boundaries by using lean update blocks and implementing proper release/reset handling for reused hybrid containers.

ViewCompositionStrategy ensures Compose disposes at the correct lifecycle moment when hosting ComposeView in Fragments or RecyclerView ViewHolders, preventing memory leaks and lifecycle bugs during incremental View to Compose migration.

Prevent recomposition loops when embedding Android Views in Compose by minimizing Composition-phase work at the interop boundary, using lean update blocks in AndroidView, and avoiding accidental high-cost state reads every frame.

ComposeView works with ViewPager2 pages without leaking memory when you select the correct ViewCompositionStrategy for disposal and apply performance-first phase thinking to state reads at the interop boundaries.

The best way to host SDK-only widgets inside Jetpack Compose is using AndroidView, ensuring you apply lean update blocks and performance-first phase thinking to prevent wasted recomposition work at the interop boundary.

ComposeView causes lifecycle bugs in Fragments when the ViewCompositionStrategy is not configured correctly for disposal, leading to Compose attempting to dispose at the wrong lifecycle moment during the incremental migration process.