4 posts
Navigation Compose and the fragment navigator can coexist in one NavHost via the fragment interop artifact. That shared back stack is what makes an incremental screen-by-screen migration possible.
A RecyclerView migration removes most of its own machinery, because Compose's composition already does recycling and diffing. What survives is stable identity — getItemId becomes key — and knowing that makes the port mechanical.
AndroidView embeds a View inside Compose. Its factory lambda constructs, its update lambda binds, and conflating them causes either a View recreated per frame or one that never reflects new state.
Adding Compose to a View-based app is one class. The interesting decisions are which seam to cut at, and the ViewCompositionStrategy that governs when the composition is disposed.
