--- title: One Tap, Three Machines: How Android Views, Flutter, and... description: A deep-dive comparison of how Android Views, Flutter, and Jetpack Compose each handle UI rendering when state changes. Android Views mutates a live object tree... canonical: https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UI | daily.dev og:description: A deep-dive comparison of how Android Views, Flutter, and Jetpack Compose each handle UI rendering when state changes. Android Views mutates a live object tree... og:url: https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz og:image: https://api.daily.dev/og/posts/2qGM1OxLz.png og:image:alt: One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UI og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UI **[Medium](https://daily.dev/sources/medium_js)** · 9 min read · 0 upvotes · 0 comments ## Summary A deep-dive comparison of how Android Views, Flutter, and Jetpack Compose each handle UI rendering when state changes. Android Views mutates a live object tree in place — efficient but prone to state-UI drift. Flutter rebuilds the entire widget tree on every state change, then diffs it against the previous tree to minimize expensive RenderObject updates. Compose tracks fine-grained subscriptions so only the exact composable scopes that read changed state are re-executed, avoiding both manual synchronization and optimistic rebuilds. Each approach has a hidden cost: Views requires manual sync, Flutter risks undisciplined rebuilds causing jank, and Compose silently degrades when stability contracts are violated. The article closes with a decision guide and previews the next installment on state management. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does Jetpack Compose decide which parts of the UI to re-render when state changes? Compose tracks precise subscriptions between observable state and the composable functions that read it, using an execution trace called the slot table. When a state value changes, only the specific composable scopes that read that value are re-executed; unchanged children are skipped by comparing cached inputs, so no rebuild or diff of the whole tree ever happens. _daily.dev surfaces deep dives like this for developers debugging unexpected recompositions in Compose._ ### Why does Flutter rebuild the entire widget tree on every state change instead of mutating it directly? Flutter treats widgets as cheap, immutable descriptions that are safe to recreate on every state change, avoiding the state-UI synchronization bugs common in mutable-tree systems like Android Views. The framework then diffs the new widget tree against the persistent Element tree, reusing existing Elements and RenderObjects when the type and key match, and only patching what actually differs. _track trade-offs like Flutter's rebuild-then-diff strategy with daily.dev when evaluating UI framework choices._ ### What causes Jetpack Compose to stop skipping recomposition for a function even when its inputs haven't changed? Compose relies on proving that a parameter cannot have changed behind its back to safely skip recomposition; a mutable var inside a data class or a bare List parameter breaks that guarantee. When this stability contract is violated, Compose silently stops skipping the function and re-runs it every time with identical data, causing invisible performance regressions that only show up later in a profiler. _developers chasing invisible Compose performance regressions can find this kind of analysis via daily.dev._ ## Similar posts on daily.dev - [One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UI](https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-ruoe8zjtc) · ProAndroidDev · 0 upvotes · 0 comments - [One Badge, Three Deliveries: How Android, Flutter, and Compose Keep Your UI in Sync](https://daily.dev/posts/one-badge-three-deliveries-how-android-flutter-and-compose-keep-your-ui-in-sync-fph6mmdcv) · Medium · 0 upvotes · 0 comments - [Why Jetpack Compose?](https://daily.dev/posts/why-jetpack-compose--uskvq7a4x) · Medium · 0 upvotes · 0 comments --- Tags: [#android](https://daily.dev/tags/android), [#flutter](https://daily.dev/tags/flutter), [#kotlin](https://daily.dev/tags/kotlin), [#jetpack-compose](https://daily.dev/tags/jetpack-compose) [View this post on daily.dev](https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UI","url":"https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz"},"datePublished":"2026-07-19T07:31:25.454Z","dateModified":"2026-09-13T19:03:16.925Z","description":"A deep-dive comparison of how Android Views, Flutter, and Jetpack Compose each handle UI rendering when state changes. Android Views mutates a live object tree...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/46f8c0b0e33ac41f3b517b8b0dde45e3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/46f8c0b0e33ac41f3b517b8b0dde45e3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"android,flutter,kotlin,jetpack-compose","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UI"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/one-tap-three-machines-how-android-views-flutter-and-compose-actually-render-your-ui-2qgm1oxlz#faq","mainEntity":[{"@type":"Question","name":"How does Jetpack Compose decide which parts of the UI to re-render when state changes?","acceptedAnswer":{"@type":"Answer","text":"Compose tracks precise subscriptions between observable state and the composable functions that read it, using an execution trace called the slot table. When a state value changes, only the specific composable scopes that read that value are re-executed; unchanged children are skipped by comparing cached inputs, so no rebuild or diff of the whole tree ever happens. daily.dev surfaces deep dives like this for developers debugging unexpected recompositions in Compose."}},{"@type":"Question","name":"Why does Flutter rebuild the entire widget tree on every state change instead of mutating it directly?","acceptedAnswer":{"@type":"Answer","text":"Flutter treats widgets as cheap, immutable descriptions that are safe to recreate on every state change, avoiding the state-UI synchronization bugs common in mutable-tree systems like Android Views. The framework then diffs the new widget tree against the persistent Element tree, reusing existing Elements and RenderObjects when the type and key match, and only patching what actually differs. track trade-offs like Flutter's rebuild-then-diff strategy with daily.dev when evaluating UI framework choices."}},{"@type":"Question","name":"What causes Jetpack Compose to stop skipping recomposition for a function even when its inputs haven't changed?","acceptedAnswer":{"@type":"Answer","text":"Compose relies on proving that a parameter cannot have changed behind its back to safely skip recomposition; a mutable var inside a data class or a bare List parameter breaks that guarantee. When this stability contract is violated, Compose silently stops skipping the function and re-runs it every time with identical data, causing invisible performance regressions that only show up later in a profiler. developers chasing invisible Compose performance regressions can find this kind of analysis via daily.dev."}}]} ```