Dev
September 29, 2026
0 views
2 min read

Celebrating 5 years of Jetpack Compose

Curated by Patrick
Source: Android Developers
Celebrating 5 years of Jetpack Compose
Tech Daily Byte Analysis

The Android team, led by Developer Relations Engineer Rebecca Franks, Product Manager Nick Butcher, and Product Marketing Manager Loryn Hairston, used a blog post and a live birthday stream to celebrate the milestone. Since the July 28 2021 launch of Compose 1.0, the toolkit has progressed through eleven minor releases, with 1.11 available today and 1.12 on the horizon. Google’s announcement at I/O 2026 that Views will enter maintenance mode and that Material Design will be delivered exclusively through Compose underscores a strategic pivot: the legacy XML‑based UI stack is being retired in favor of a fully declarative, Kotlin‑driven approach. The post also highlights that more than two‑thirds of the most popular Android applications have already adopted Compose in production, a figure that validates the shift and signals that developers are moving away from the old imperative model.

The celebration fits into a broader industry trend toward declarative UI frameworks. Apple’s SwiftUI, Meta’s React Native, and Google’s own Flutter all champion a “write once, render everywhere” philosophy, and Compose’s expansion into TV, Wear OS, Glance widgets, and even experimental display‑glass support (Compose Glimmer) mirrors that cross‑device ambition. The partnership with JetBrains to power Compose Multiplatform further blurs the line between Android‑only and truly multi‑platform development, positioning Compose as a potential competitor to Flutter for desktop, iOS, and web targets. Community contributions—libraries such as Haze, Touch Robot, and the Mosaic terminal UI—have accelerated feature adoption and kept the ecosystem vibrant, a model that mirrors the open‑source success of React and SwiftUI.

Looking ahead, the mandatory migration from Views to Compose will create short‑term friction for legacy codebases, especially for large enterprises with entrenched XML layouts. However, Google’s “Compose‑first” stance promises sustained investment, including new adaptive layout primitives like FlexBox, Grid, MediaQuery, and Styles that aim to simplify responsive design across form factors. Watch for the 1.12 release, which will likely deepen integration with Material 3 Expressive and refine tooling for performance testing (e.g., Paparazzi). The success of the community‑driven libraries suggests that third‑party innovation will continue to shape Compose’s capabilities, but Google must ensure that the maintenance mode for Views does not leave critical bugs unaddressed, lest developers hesitate to fully commit.

Key Takeaways

Over 68 % of the top 1,000 Android apps have already migrated to Jetpack Compose, confirming rapid ecosystem adoption.

Google has officially placed Compose as the sole UI development path for Android, relegating the classic Views toolkit to maintenance‑only status.

The introduction of adaptive APIs and the upcoming 1.12 release expand Compose’s ability to handle complex, responsive layouts across phones, tablets, TV, Wear OS, and emerging devices.

Collaboration with JetBrains and a thriving open‑source community extend Compose beyond Android, positioning it as a genuine multi‑platform UI solution.

About the Source

This analysis is based on reporting by Android Developers. Here is a short excerpt for context:

Posted by Rebecca Franks, Developer Relations Engineer, Nick Butcher, Product Manager, Loryn Hairston, Product Marketing Manager, Android Today, we officially celebrate five years since the release of Jetpack Compose 1.0. From version 1.0, announced on July 28th, 2021, to our latest 1.11 release, we’ve seen the APIs evolve significantly over the years, and we’re taking a moment to celebrate. When we officially announced the 1.0 release, we promised a simpler, faster, and more intuitive way to build native interfaces on Android. Looking back, it's safe to say that Compose didn’t just deliver on that promise, but also completely changed the Android ecosystem, with more than 68% of the top 1,000 apps using it in production today. History Over the last five years, Compose has grown steadily. In the early days, we explored showing you how to build layouts with the basic Box, Row, and Column. Today, we’ve expanded Compose to work not just on mobile devices, but to other form factors such as Compose for TV, WearOS, Glance for Widgets, and even display glasses with Jetpack Compose Glimmer. We recorded an Android Developers Backstage episode with Clara Bayarri, Engineering Lead for Jetpack, and two former leads of the team, Romain Guy and Chet Haase, along with Tor Norbye, Senior Engineering Director. In this episode, they discuss the history of Compose and the early days of development. Compose highlights over the years Looking back The beginnings of Compose were very different from what you know today. Two projects were happening in parallel inside the Android team. At the time, the Views toolkit team was thinking of unbundling the UI Toolkit into a library to help with development speed, and make it easier for developers to adopt and control updates. Meanwhile, a team was working on a novel idea to build declarative layouts by embedding XML inside Kotlin, which looked something like this: Those two efforts merged to produce what you know today - a fully declarative UI Toolkit that utilizes the power of a compiler plugin, runtime, and Kotlin: @Composable fun Newsfeed(stories: List) { LazyColumn { items(stories) { story -> Card { val author = story.author Image(painterResource(author.profilePhoto), contentDescription = author.name) Text(author.name) Text(story.content) if (story.hasCommentsEnabled()) { for(comment in story.comments) { Text(comment.mainContent) } } } } } } And you, the community, helped us very early on! Before 2021, Compose had a pre-alpha phase, which helped ensure Compose was fit to solve the problems of our developers. One of our favorite memories is the Android Dev Challenge. We challenged the community to build four different tasks with Compose, filling our feeds with Puppy apps, clocks, and weather apps, and giving us a ton of direct feedback that helped shape the 1.0 release. Compose has continued to evolve, from launching with a set of Material 2 components to now supporting Material 3 Expressive. Material 2 in Compose Material 3 Expressive in Compose Looking ahead As of today, Compose 1.11 is the latest version with 1.12 coming soon, offering so much more than 1.0, 5 years ago. This year, we introduced more adaptive APIs, such as FlexBox, Grid, MediaQuery, and Styles. These APIs let you advance to the next level of premium, adaptive UI development with Compose. At Google I/O 2026, we announced that we are now Compose-first, meaning that all future UI development will happen only in Compose, while the Views toolkit enters maintenance mode. Material Design is also shifting focus entirely to Compose, signaling an end to the findViewById era. Community is at the heart of Compose Over the years, you’ve inspired us with creative examples of how you’ve used Compose, and we’d love to highlight a few more examples of where we’ve seen exciting work. JetBrains has been a great partner for Google with Compose, expanding Compose to work across platforms with Compose Multiplatform and enabling desktop, iOS, and web developers to also enjoy the benefits of Compose. We’ve really enjoyed following our most beloved newsletters from JetpackCompose.app’s Dispatch, AndroidWeekly, to jetc - helping Android Developers stay up-to-date with the latest in the world of Compose and Android. Another standout contributor is sinasamaki. They’ve created many delightful experiences using Compose, such as this fun ribbon modifier and the glitchy effect: Saket Narayan has also always been an inspiration when it comes to creating useful tools for Compose, such as telephoto, a library featuring support for pan and zoom gestures and automatic sub-sampling of large images, or the latest library, Touch Robot, which allows you to easily test interaction animations: paparazzi.gif(end = 3_000) { DebitCard( Modifier.testTag("card") ) val touchRobot = rememberTouchRobot() LaunchedEffect(Unit) { touchRobot.onNode(hasTestTag("card")).performGesture { draw( path = createAndroidHeadPath(), duration = 3.seconds, ) } } } /** A path drawing the Android head. */ fun createAndroidHeadPath(bounds: Rect): Path = TODO() Jake Wharton, who has used Compose in innovative ways (like molecule, and even building UI with Compose for the terminal with mosaic). Chris Banes, who has built many Compose libraries over the years, with our most recent favourite - Haze for background blurring, and many of the Android Google Developer Experts like Akshay Chordiya, Huyen Tue Dao, and Katie Barnett, who’ve contributed to the success of Compose. But this is not about selecting individuals - there have been so many great contributors to the Compose codebase, and many of you continue to inspire us with your fun examples, libraries, and in-depth talks. Without the community, Jetpack Compose wouldn’t be as successful as it is today. Cheers to the next 5 years, and more! Jetpack Compose has grown from an experimental idea into the standard for Android UI Development. Thank you to the entire Toolkit team at Google, and to the incredible global developer community that wrote libraries, filed bugs, and pushed the boundaries of what declarative UI can do. This week, we’ll be celebrating with some in-person birthday parties across the globe, and a live “Birthday party” on the Android Developers YouTube channel on July 30th at 13:00 UTC. During this time, we’ll hang out and discuss Compose and answer your questions! Cheers to the next 5 years, and happy composing!
Read the original at Android Developers

More in Dev