Nestedscrollview — |verified|

</LinearLayout> </androidx.core.widget.NestedScrollView> For the magic to work, the inner scrollable view (e.g., RecyclerView ) must have nested scrolling enabled. In modern AndroidX versions, this is true by default, but you can explicitly set it:

Box(modifier = Modifier.nestedScroll(rememberNestedScrollInteropConnection())) // LazyColumn inside a vertical scroll nestedscrollview

<androidx.core.widget.NestedScrollView app:layout_behavior="@string/appbar_scrolling_view_behavior"> <!-- Content here --> </androidx.core.widget.NestedScrollView> </androidx.coordinatorlayout.widget.CoordinatorLayout> &lt;/LinearLayout&gt; &lt;/androidx

| Do | Don't | |----|-------| | Use NestedScrollView with CoordinatorLayout for collapsing toolbars. | Put a RecyclerView with wrap_content inside it for long lists. | | Enable fillViewport to fill the screen when content is short. | Nest NestedScrollView inside another NestedScrollView . | | Keep inner lists small (< 10 items) or use multiple view types in a single RecyclerView . | Assume NestedScrollView is a drop-in performance upgrade – it has overhead. | | Test scroll fling behavior – physics can feel different. | Forget to handle keyboard visibility if the view contains EditText fields. | Final Take NestedScrollView is not a magic bullet, but it is an indispensable tool for modern, material-design-compliant Android apps. Use it when you need coordination , avoid it when you simply need containment . Respect the recycling system, and your scrolling will be buttery smooth. | | Enable fillViewport to fill the screen

In the modern Android ecosystem, user interfaces are rarely simple. They often consist of complex hybrids: a collapsing toolbar, a tab layout, a view pager, and within each tab, a RecyclerView or ListView . When you put scrolling containers inside other scrolling containers, you encounter the infamous scroll conflict .