We use Google Analytics to see which pages help people. No ads, no profiles. Privacy Policy
@Preview renders a composable without running the app. Its real value is the pressure it applies: a component that can't be previewed is a component that can't be tested, and both point at the same design problem.
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.
A useful Compose suite is mostly unit tests, a layer of state-driven component tests, screenshot tests for visual regressions, and a handful of journeys. The shape matters more than the count.
Compose's test framework auto-syncs with the composition, so most tests need no waiting at all. The failures come from things that never go idle, and from work the framework cannot see.
Listing what I shipped is not the review. Listing what changed for other people is.
Compose testing is finders, actions and assertions over the semantics tree. The API is small; the judgment is choosing between a unit test, a Compose test with a fake, and a full instrumented test.
Decisions need synchronous time; proposals need written artifacts.
Most of a toolchain is habit rather than measured benefit.
Compose UI tests match against the semantics tree, not the layout. Selecting by text and content description tests what users perceive; selecting by testTag tests an implementation detail you invented for the test.
