Jetpack Compose — two years in production
Compose hit stable 1.0 in 2021. By 2026 it's the default for new Android apps. What worked, what hurt.
Jetpack Compose is Android's modern UI toolkit: declarative, written in Kotlin, with a mental model close to SwiftUI. It reached stable 1.0 in 2021, and Google now recommends it for new Android UI. After a couple of years of running Compose in production apps, the picture is clear: it's the right default, but it has its own failure modes, and teams that ignore them pay in scroll performance and debugging time.
What works well
- Less code, fewer files. No XML layouts, view binding or adapter boilerplate. A list with a custom item is a function, not several classes plus a layout file.
- State-driven UI. The screen reflects state: you change the state, Compose updates what changed. Together with a ViewModel and Kotlin flows, the data path is easy to follow.
- Animations. The animation APIs cover most needs, from visibility and content changes to shared element transitions, with little code.
- Material 3 components are mature enough for production, including theming and dynamic color.
- Previews and tests. Previews with different themes and font scales, and UI tests that find elements by semantics instead of view IDs.
- Beyond Android. JetBrains' Compose Multiplatform lets teams share UI with other platforms, including iOS and desktop. Check how mature each target is for your use case before committing.
What hurts
- Recomposition performance. If a composable reads state it doesn't need, or gets parameters the compiler can't treat as stable, it recomposes more often than necessary. On low-end devices this shows up as janky scrolling in lists.
- Misleading debug builds. Compose runs noticeably slower in debug builds. Judge performance only on release builds with R8 enabled, on real mid-range and low-end devices.
- A new mental model for debugging. Bugs come from when and why things recompose, side effects running at the wrong time or state kept in the wrong place. A team used to Views needs time to think this way.
- Mixed codebases. Compose inside Views and Views inside Compose both work, but navigation, theming, window insets and focus handling across the boundary cause subtle bugs.
- Fast-moving libraries. Compose, Material and related libraries change quickly. Plan regular dependency updates instead of one big jump a year.
Practices that pay off
- Hoist state and pass only what a composable needs. Give reusable components values and lambdas, not whole ViewModels.
- Use keys in lazy lists. Stable keys for
LazyColumnitems keep scroll position and animations correct when the data changes. - Defer frequent reads. For values that change every frame, such as scroll offset, read them in lambda-based modifiers or through
derivedStateOf, so only layout or drawing reruns instead of the whole composition. - Ship Baseline Profiles. They improve startup and first-scroll performance by precompiling hot code paths.
- Watch recomposition counts. The Layout Inspector in Android Studio shows how often each composable recomposes. Check your heaviest screens regularly.
- Keep side effects explicit. Use
LaunchedEffect,DisposableEffectand related APIs deliberately, and never start work directly in a composable body.
Migrating a legacy app
For an existing View-based app, don't plan a big-bang rewrite. Start with leaf screens or new features through ComposeView, set up a shared theme that maps your existing colors and type styles to Material 3, and move larger flows when you have to change them anyway. Navigation is usually the last piece to migrate. The app stays shippable the whole time.
Bottom line
For new Android projects in 2026, Compose is the default. For legacy apps, migrate screen by screen rather than all at once. iOS has gone through the same transition; see SwiftUI vs UIKit in 2026.
We build Android apps with Compose and modernize existing ones: see Android app development and mobile app support.
Planning a new Android app or a migration to Compose? Reach us on Telegram or MAX.
Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.
Message on Telegram → Message on MAX