# Recomposition Published articles for Recomposition. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Stop Ignoring Compose Stability (Yes, Even with Strong Skipping Mode) DevFeed: [Stop Ignoring Compose Stability (Yes, Even with Strong Skipping Mode)]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2026-08-03T04:30:00Z Content type: article Language: en Sources: [Shreyas Patil's Blog]() Topics: [Compose](), [Jetpack Compose](), [Android](), [Kotlin](), [Optimization]() Tags: [android](), [compiler](), [compose](), [compose-compiler](), [compose-stability](), [jetpack-compose](), [kotlin](), [optimization](), [performance](), [recomposition]() ### AI overview This article explains why Compose stability still matters when Strong Skipping Mode is enabled. It describes how unstable parameters are compared by instance equality, which can prevent composables from skipping and lead to unnecessary recompositions, and discusses automatic lambda memoization. ### Source excerpt Strong Skipping Mode doesn't make Compose stability obsolete. Discover the hidden referential equality trap causing silent recompositions in your app. ## How Jetpack Compose builds and updates UI with modifiers DevFeed: [How Jetpack Compose builds and updates UI with modifiers]() Original publisher: [Read original article]() Published: 2026-06-29T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Compose](), [ui](), [layout](), [interfaces]() Tags: [compose](), [declarative](), [interfaces](), [modifiers](), [recomposition](), [stateful](), [workshop-learning-programming]() ### AI overview This tutorial explains how Jetpack Compose builds and updates user interfaces. It focuses on modifiers, layout measurement, drawing, semantics, user interactions, recomposition, and modifier node interfaces. ### Source excerpt How Compose actually works? How it works under the hood and why it's so powerful. ## Introducing Dejavu: Recomposition Testing for Jetpack Compose DevFeed: [Introducing Dejavu: Recomposition Testing for Jetpack Compose]() Original publisher: [Read original article]() Author: Matt McKenna Published: 2026-03-09T19:26:54Z Content type: release Language: en Sources: [Matt McKenna]() Topics: [Jetpack Compose](), [Testing](), [AI Agent]() Tags: [ai-agent](), [android](), [compose](), [diagnostics](), [error-messages](), [jetpack](), [jetpack-compose](), [kotlin](), [recomposition](), [testing](), [ui]() ### AI overview The article introduces Dejavu, a testing tool for Jetpack Compose that turns recomposition behavior into test assertions. It describes asserting expected recomposition counts, receiving diagnostic information on failures, and using CompositionTracer without production-code instrumentation, a compiler plugin, bytecode manipulation, or a Gradle plugin. ### Source excerpt Where This Idea Came From At Square, most of the app is built on Workflow. There is an internal testing framework that lets you assert exactly how many render passes are triggered for a given interact ## How Composition and Recomposition Work in Jetpack Compose DevFeed: [How Composition and Recomposition Work in Jetpack Compose]() Original publisher: [Read original article]() Published: 2026-02-16T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Compose](), [Jetpack Compose]() Tags: [compose](), [jetpack-compose](), [recomposition](), [state](), [ui](), [workshop-learning-programming]() ### AI overview This tutorial explains composition and recomposition in Jetpack Compose, including how composables build a UI tree and how snapshot state triggers updates to the parts of the UI that read changed state. ### Source excerpt Clear explanation of how composition and recomposition work in Jetpack Compose. ## Compose Stability Analyzer 0.7.0: Recomposition Cascade and Live Heatmap DevFeed: [Compose Stability Analyzer 0.7.0: Recomposition Cascade and Live Heatmap]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-02-15T00:08:14Z Content type: tutorial Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Jetpack Compose](), [Android Studio](), [Gradle](), [Code]() Tags: [adb](), [android](), [android-studio](), [compose](), [compose-stability](), [gradle](), [gradle-plugin](), [jetpack-compose](), [kotlin-multiplatform](), [monitoring](), [recomposition]() ### AI overview This article introduces Compose Stability Analyzer 0.7.0, focusing on its Recomposition Cascade Visualizer and Live Recomposition Heatmap. It explains how the heatmap uses ADB-connected device events to display runtime recomposition counts in Android Studio. ### Source excerpt Jetpack Compose's stability system determines whether a composable function can be skipped during recomposition. When all parameters are stable, Compose can compare them and skip the function entirely if nothing changed. When even one parameter is unstable, the composable must re-execute every time its parent recomposes. Understanding which composables are stable and which are not is the first step toward optimizing Compose performance, but it's not the whole picture. Compose Stability Analyzer has been providing real-time stability analysis directly in Android Studio through gutter icons, hover tooltips, inline hints, and code inspections. These features answer the question "is this composable stable?" at a glance. Version 0.7.0 goes further by answering two additional questions that static analysis alone cannot address: "what happens downstream when this composable recomposes?" and "which composables are actually recomposing the most on a real device?" In this article, you'll explore the two new features introduced in version 0.7.0: the Recomposition Cascade Visualizer and the Live Recomposition Heatmap. Live Recomposition Heatmap Static analysis tells you which composables could recompose unnecessarily. The Live Recomposition Heatmap tells you which ones actually are. It bridges runtime behavior with your IDE by reading @TraceRecomposition events from a connected device via ADB and displaying live recomposition counts directly above composable functions in the editor. To use the heatmap, you need the Compose Stability Analyzer Gradle plugin applied to your project, composable functions annotated with @TraceRecomposition, and logging enabled via ComposeStabilityAnalyzer.setEnabled(true) in your Application class. With those in place, open the Compose Stability Analyzer tool window and click the Start/Stop button in the title bar. If one device is connected, monitoring begins immediately. If multiple devices are connected, a picker popup lets you choose which one t ## How Compose Stability Affects Recomposition and Passing Types DevFeed: [How Compose Stability Affects Recomposition and Passing Types]() Original publisher: [Read original article]() Published: 2026-02-02T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Compose](), [Jetpack Compose]() Tags: [compose](), [declarative](), [deep-dive](), [developers](), [recomposition](), [state](), [ui](), [workshop-learning-programming]() ### AI overview This article explains how Compose stability affects recomposition and the safety of passing types through the UI tree. It distinguishes immutable, stable, and unstable types, emphasizing that some mutable types remain safe because Compose can observe their changes. ### Source excerpt Deep dive into how Compose handles stability and why it's crucial for developers. ## Deep dive into annotations in Jetpack Compose DevFeed: [Deep dive into annotations in Jetpack Compose]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2025-05-19T05:16:29Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Compose](), [Jetpack Compose](), [ui]() Tags: [android](), [android-app-development](), [app-development](), [compose](), [deep](), [deep-dive](), [examples](), [jetpack](), [jetpack-compose](), [kotlin](), [optimization](), [performance](), [recomposition](), [state](), [ui]() ### AI overview This tutorial explains how Jetpack Compose uses compiler annotations and runtime mechanisms such as recomposition, skipping, and restartability. It describes how these mechanisms affect composable execution and performance, with practical examples. ### Source excerpt An extensive deep dive into annotations in Jetpack Compose. Understand how @Composable, @Stable, @ReadOnlyComposable, and others work under the hood. ## How Jetpack Compose Measuring Works DevFeed: [How Jetpack Compose Measuring Works]() Original publisher: [Read original article]() Author: Helios Alonso Published: 2023-09-28T15:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Jetpack Compose](), [Compose](), [ui](), [Android](), [Code]() Tags: [android](), [canvas](), [compose](), [debug](), [engineering](), [jetpack-compose](), [lambda](), [layout](), [performance](), [recomposition](), [structure](), [typography](), [ui]() ### AI overview This tutorial explains how Jetpack Compose measures and lays out UI. It presents Compose UI as an internally generated tree of nodes, describes the Layout method and its content lambda, measure policy, and modifiers, and outlines how measuring and drawing work. ### Source excerpt A high level overview on producing custom rich UI in Compose ## Profiling and Optimization Techniques for Jetpack Compose Apps DevFeed: [Profiling and Optimization Techniques for Jetpack Compose Apps]() Original publisher: [Read original article]() Author: IceRock Development Published: 2023-04-28T03:14:45Z Content type: tutorial Language: en Sources: [IceRock Development - Medium]() Topics: [Jetpack Compose](), [Optimization](), [Android Studio](), [Android](), [cpu](), [GPU]() Tags: [android](), [android-app-development](), [android-studio](), [compose-compiler](), [cpu](), [emulator](), [gpu](), [jetpack-compose](), [mobile-app-development](), [optimization](), [performance](), [profiling](), [recomposition]() ### AI overview This tutorial uses the Campus student schedule app to explain profiling and optimization techniques for Jetpack Compose. It covers excessive recompositions, Compose Compiler Metrics, CPU and GPU profiling, and Android Studio's Recomposition Counts tool. ### Source excerpt Your brand-new app gets bombarded with user complaints on Google Play about it hanging or slowing down? Follow the tips in this article to fix it. Hello! My name is Sergey Panov, and I am a mobile developer at IceRock. Today, I will be using our Campus app as an example to demonstrate profiling and optimization techniques for Jetpack Compose. Campus is an app that allows students to view their class schedule. Its main feature is the schedule screen consisting of two pagers for weeks and days. When users tried to swipe them, it caused the app to hang, but we managed to fix it. Here are the topics discussed in the article: Recomposition Counts. Pinpointing Excessive Recompositions. Compose Compiler Metrics. Identifying the Root Causes of Excessive Recompositions. CPU Profiling. Finding "Hot" Methods and Freeing up the CPU. GPU Profiling. Learning Which Components Take a Long Time to Draw. More Tips on Fixing Bugs Identified with Profiling Tools. Recomposition Counts. Pinpointing Excessive Recompositions Issue. The first concept we need to highlight is that of recomposition. Rendering a screen in Compose consists of traversing the graph of composable functions. If a graph node changes its state (i.e. arguments of a composable method, values of MutableState or animations change), the subgraph is updated, that is, the functions are called again. Such an update is called a recomposition. Recompositions are fast and should not present any issues, but frequent recompositions can cause an app to slow down. This is a distinctive feature and a pitfall of Compose. After all, a developer can make some mistakes leading to excessive recompositions, for instance, recreate an object instead of reusing it. This results in unnecessary computations and performance issues. Solution. In large projects, these mistakes might be tricky to detect by the unaided eye, so Android Studio provides our eyes with an aid -- a tool called Recomposition Counts. It can be enabled in Layout Inspector to ## Leveraging the Snapshot Mutation Policies of Jetpack Compose DevFeed: [Leveraging the Snapshot Mutation Policies of Jetpack Compose]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2023-01-30T13:30:39Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Jetpack Compose](), [Compose](), [ui](), [Code]() Tags: [android](), [android-app-development](), [compose](), [data-class](), [jetpack-compose](), [kotlin](), [library](), [mutation](), [recompose](), [recomposition](), [standard-library](), [state](), [state-management](), [ui]() ### AI overview A tutorial on SnapshotMutationPolicy in Jetpack Compose, explaining how structural, referential, and never-equal policies determine whether state changes trigger UI recomposition. ### Source excerpt Understand Snapshot Mutation Policies in Jetpack Compose. Learn how to control when and how your UI recomposes based on state changes. ## Profiling and Optimizing Jetpack Compose Apps with Recomposition, CPU, and GPU Analysis DevFeed: [Profiling and Optimizing Jetpack Compose Apps with Recomposition, CPU, and GPU Analysis]() Original publisher: [Read original article]() Author: IceRock Development Published: 2023-01-25T06:55:43Z Content type: tutorial Language: en Sources: [Stories by IceRock Development on Medium]() Topics: [Jetpack Compose](), [Compose](), [Optimization](), [Android Studio](), [Compiler](), [cpu](), [GPU](), [Mobile](), [Emulator]() Tags: [android](), [android-app-development](), [android-studio](), [compose](), [compose-compiler](), [cpu](), [emulator](), [gpu](), [jetpack-compose](), [mobile-app-development](), [optimization](), [performance](), [profiling](), [recomposition]() ### AI overview This tutorial demonstrates profiling and optimization techniques for Jetpack Compose using the Campus student-schedule app. It explains how to detect excessive recompositions with Recomposition Counts and Compose Compiler Metrics, then use CPU and GPU profiling to identify performance problems and slow-to-draw components. ### Source excerpt Your brand-new app gets bombarded with user complaints on Google Play about it hanging or slowing down? Follow the tips in this article to fix it. Hello! My name is Sergey Panov, and I am a mobile developer at IceRock. Today, I will be using our Campus app as an example to demonstrate profiling and optimization techniques for Jetpack Compose. Campus is an app that allows students to view their class schedule. Its main feature is the schedule screen consisting of two pagers for weeks and days. When users tried to swipe them, it caused the app to hang, but we managed to fix it. Here are the topics discussed in the article: Recomposition Counts. Pinpointing Excessive Recompositions. Compose Compiler Metrics. Identifying the Root Causes of Excessive Recompositions. CPU Profiling. Finding "Hot" Methods and Freeing up the CPU. GPU Profiling. Learning Which Components Take a Long Time to Draw. More Tips on Fixing Bugs Identified with Profiling Tools. Recomposition Counts. Pinpointing Excessive Recompositions Issue. The first concept we need to highlight is that of recomposition. Rendering a screen in Compose consists of traversing the graph of composable functions. If a graph node changes its state (i.e. arguments of a composable method, values of MutableState or animations change), the subgraph is updated, that is, the functions are called again. Such an update is called a recomposition. Recompositions are fast and should not present any issues, but frequent recompositions can cause an app to slow down. This is a distinctive feature and a pitfall of Compose. After all, a developer can make some mistakes leading to excessive recompositions, for instance, recreate an object instead of reusing it. This results in unnecessary computations and performance issues. Solution. In large projects, these mistakes might be tricky to detect by the unaided eye, so Android Studio provides our eyes with an aid -- a tool called Recomposition Counts. It can be enabled in Layout Inspector to ## Performance in Jetpack Compose DevFeed: [Performance in Jetpack Compose]() Original publisher: [Read original article]() Author: Denys Rudenko Published: 2022-10-03T16:41:03Z Content type: tutorial Language: en Sources: [Stories by Denis Rudenko on Medium]() Topics: [Jetpack Compose](), [ui](), [Code]() Tags: [android](), [android-app-development](), [article](), [compiler](), [compose](), [false-positive](), [jetpack-compose](), [lambda](), [modifiers](), [performance](), [recomposition](), [scopes](), [skip](), [ui](), [val](), [var](), [variables]() ### AI overview A practical guide to improving Jetpack Compose performance through stable parameters, skippable composables, optimized recompositions, remembered lambdas, and compiler and layout-inspector metrics. ### Source excerpt Article tells about my research on how to write efficient Compose code. It consists of 6 sections and a TL;DR/Summary in the end. We will cover: Optimising recompositions When should you use @Immutable and @Stable annotations; Unstable classes, variables, lambdas; Non-restartable & skippable composables; Lambda modifiers; Passing lambdas providing required fields instead of fields in composables; Inlined composables; When you should use remember { }. We'll be using Compose Compiler Metrics and layout inspector tools to know: - If a class is stable or not; - If the composable function is skippable/restartable; - Amount of skipped recompositions. 1. Unstable objects on UI layer. To understand why we should care about stability, let us peek into a very important metric called skippability. It allows compose runtime to skip recomposition of a composable when all the parameters it uses are considered stable. What is considered stable by the compiler? - All primitive value types: Boolean, Int, Long, Float, Char, etc. - Strings - Lambdas (not always, we will get to it later) We want composable functions to use stable params to become skippable. 1) Don't use var when seeking stability. Fields declared as var are considered unstable: https://medium.com/media/724da23ba38eaa9d3312318e7e8038b9/hrefhttps://medium.com/media/f8dd8a39bce60e48b5ff8bdd4a02b9ef/href UserDetails composable will be recomposed even if the user never gets modified. Using val instead of var in User class will fix this issue. 2) Not all lambdas are considered stable. Let's look at the following examples: https://medium.com/media/fbbff417d165a501b21a3e5d2c6f087f/hrefhttps://medium.com/media/c6aaae01fda67c633edcdf7bb351e620/href Since the lambdas capture outside scopes, they won't be automatically inferred as stable and reused as expected. If the lambda requires access to external variables, the compiler will add those variables as fields, which are passed into the constructor of the lambda. We go a 2 ways of ## When Compose remember cannot forget DevFeed: [When Compose remember cannot forget]() Original publisher: [Read original article]() Published: 2022-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Compose](), [compose-for-web](), [ui](), [color]() Tags: [change](), [compose](), [compose-for-web](), [recomposition](), [state](), [ui](), [update]() ### AI overview This tutorial explains why a Compose composable continued displaying an old value after recomposition in a Compose for Web color utility app. The issue occurred because remember preserves values across recompositions; supplying the changing color value as a key caused the remembered value to update. ### Source excerpt Чытаць на беларускай мове Introduction When developing color-utils app using Compose for Web I faced an issue that remember didn't want to forget the state. It was quite annoying experience as it felt stupid: composable function is recomposed with the new value provided but remember still kept old value. As usual, there is no magic there and the answer is quite simple therefore this article won't be that long. Compose is all about state. In the app I had two levels of state: ## How to change system bar colors using Jetpack Compose DevFeed: [How to change system bar colors using Jetpack Compose]() Original publisher: [Read original article]() Published: 2022-07-20T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [Compose](), [Jetpack Compose](), [Dark Mode](), [XML](), [Code]() Tags: [changes](), [code](), [compose](), [jetpack-compose](), [recomposition](), [xml]() ### AI overview This tutorial explains how to change Android status bar and navigation bar colors directly with Jetpack Compose, without modifying XML files. It shows how to use the activity's system bar properties and update icon appearance according to the dark theme. ### Source excerpt System bar colors can be changed directly with Compose, without a need to modify any XML files. ## Keep your Tabs and List in sync using Jetpack Compose DevFeed: [Keep your Tabs and List in sync using Jetpack Compose]() Original publisher: [Read original article]() Author: Vaios Tsitsonis Published: 2022-06-20T12:15:00Z Content type: tutorial Language: en Sources: [Blueground Engineering blog]() Topics: [Jetpack Compose](), [Compose](), [ui](), [Kotlin](), [Development](), [Code]() Tags: [android](), [code](), [compose](), [development](), [jetpack-compose](), [kotlin](), [list](), [recomposition](), [state](), [ui]() ### AI overview This tutorial introduces Jetpack Compose and explains how to build a UI with grouped list items, synchronized tabs, scrolling behavior, and automatic navigation to corresponding groups. It also discusses Compose's Kotlin-based UI model, state handling, recomposition, and interoperability with the older UI system. ### Source excerpt Jetpack Compose In May 2019, Google announced a new UI toolkit for Kotlin developers. In July 2021 the first stable version of this toolkit was made available. So, it is a fresh but I believe very promising toolkit. Some of the benefits of using the Jetpack Compose will be mentioned ## Exploring MovableContentOf in Jetpack Compose DevFeed: [Exploring MovableContentOf in Jetpack Compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2022-03-14T04:49:00Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [Compose](), [Android](), [Code]() Tags: [android](), [article](), [code](), [compose](), [how-to](), [jetpack-compose](), [performance](), [recomposition]() ### AI overview This tutorial explains Jetpack Compose's movableContentOf function, introduced in version 1.2.0-alpha03. It shows how moving composable content can avoid unnecessary recomposition, preserve state when items change position, and potentially improve performance. ### Source excerpt Jetpack Compose recently introduced a new function named movableContentOfin version 1.2.0-alpha03. As the name suggests, this enables us to move around content without the need for recomposition. This could save time and increase performance if the recompositions are expensive and or numerous. Jetpack compose already has some ## How Compose Compiler Stability Annotations Affect Recomposition and UI Performance DevFeed: [How Compose Compiler Stability Annotations Affect Recomposition and UI Performance]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2022-03-10T12:42:38Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Compose](), [ui](), [Compiler]() Tags: [android](), [android-app-development](), [compatibility](), [compose](), [compose-compiler](), [kotlin](), [kotlin-beginner](), [performance](), [recomposition](), [ui]() ### AI overview This tutorial explains how Compose Compiler stability annotations, including @Stable and @Immutable, communicate guarantees about models and functions. These guarantees can help the compiler optimize recomposition and may improve UI performance, but violating them can cause undefined behavior. ### Source excerpt Understand the Compose compiler's stability promises. Learn how @Stable and @Immutable impact recomposition and how to help the compiler optimize your UI. ## Fun with Compose: Bad UI in a Great Framework - Touchlab DevFeed: [Fun with Compose: Bad UI in a Great Framework - Touchlab]() Original publisher: [Read original article]() Published: 2021-08-04T03:23:44Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Compose](), [Jetpack Compose](), [ui](), [Kotlin](), [Boilerplate]() Tags: [android](), [animations](), [boilerplate](), [compose](), [jetpack-compose](), [kotlin](), [livedata](), [recomposition](), [state](), [ui]() ### AI overview An exploration of Jetpack Compose that builds deliberately poor volume-control interfaces and reflects on the framework's development experience. The article highlights concise UI code, custom animations, reduced boilerplate, and lessons about state, mutation, and recomposition. ### Source excerpt To celebrate Jetpack Compose finally hitting 1.0, I decided to bring back an old reddit trend of creating the absolute worst volume control UI possible.