# jetpack-compose Published articles for jetpack-compose. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## jetc.dev Newsletter Issue #331 DevFeed: [jetc.dev Newsletter Issue #331]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-15T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [compose-for-desktop](), [servo](), [WebView]() Tags: [bug-fixes](), [chromium](), [compose-for-desktop](), [issue](), [jetpack](), [jetpack-compose](), [release-notes](), [webview]() ### AI overview This newsletter reviews recent Jetpack Compose release changes and highlights related developer content. It covers Compose BOM updates, Material3 and other Compose library versions, a keyboard focus bug and workaround, keyed composition, dialog background blurring, and Compose for Desktop libraries including a CEF-based option and window chrome controls. ### Source excerpt SideEffect keys! CEF-based WebView and window chrome controls for desktop apps! And... why does the keyboard flicker?!? ## The Thumb That Ran Ahead of the Finger: Anatomy of a Compose Slider Bug DevFeed: [The Thumb That Ran Ahead of the Finger: Anatomy of a Compose Slider Bug]() Original publisher: [Read original article]() Author: Vitaliy Gribko Published: 2026-09-14T04:19:34Z Content type: article Language: en Sources: [ProAndroidDev - Medium]() Topics: [bug](), [Compose](), [Android](), [Design system](), [Code]() Tags: [android](), [bug](), [code](), [compose](), [debugging](), [design-system](), [jetpack-compose](), [kotlin](), [qa](), [race-condition](), [ui]() ### AI overview This article examines a deterministic bug in a custom Compose slider where the thumb moves ahead of the user's finger during a drag. It traces the issue to a design-system slider forked from the AOSP Material implementation and discusses debugging and code simplification. ### Source excerpt A bug report sat in the backlog for seven months. The fix took a day, deleted a third of the slider's logic, and was almost shipped with a second bug inside -- until a machine read my diff better than I did. This is the whole story: the ported behavior that never made sense, the race nobody reported, and why the best fixes remove code. The report The bug report was seven months old when it reached me. A QA engineer had filed it in December, with a screen recording and three steps: Open the people search filters. Grab the right-hand thumb of the age range slider. Drag it slowly to the left. The recording showed the problem in two seconds. The thumb does not follow the finger. It sprints ahead -- you are still crossing the gap between two ticks, and the thumb is already standing on the next one, waiting for you, like a dog that runs to the park while you are still tying your shoes. Expected: the thumb moves with the finger. Actual: it escapes. On a budget phone, on two Android versions, every time. Not a race condition, not a flake -- a perfectly deterministic lie, filmed in December, assigned to a fix-day in July. Seven months is not negligence. It is the natural half-life of a visual glitch filed as minor against a screen nobody dies on. The age filter works. You tap a tick, the value applies. Only the drag -- the one gesture the slider exists for -- feels wrong in a way that is hard to screenshot and easy to deprioritize. When the ticket finally landed on my desk, a colleague glanced at it and asked whether it had already been fixed once. It had not. But I understood his confusion later, when I opened the slider's source and found a comment that explained everything -- including why this bug felt so old. The comment that confessed The slider is not the framework's slider. Our design system ships its own Compose slider, forked from the AOSP Material one, because design needed three knobs the framework does not expose: a custom thumb radius, a custom track height, a differ ## How Kotlin Flow Operator Fusion Works and When Ordinary Operators Break It DevFeed: [How Kotlin Flow Operator Fusion Works and When Ordinary Operators Break It]() Original publisher: [Read original article]() Author: Majidshahbaz Published: 2026-09-13T05:43:21Z Content type: article Language: en Sources: [ProAndroidDev - Medium]() Topics: [kotlin-flow](), [Coroutines](), [Code]() Tags: [android](), [code](), [coroutines](), [jetpack-compose](), [kotlin](), [kotlin-coroutines](), [kotlin-flow]() ### AI overview This article investigates Kotlin Flow operator fusion by instrumenting the runtime and comparing pipelines with adjacent fusible operators against pipelines interrupted by an ordinary map() call. It explains that adjacent channelFlow, flowOn, buffer, and produceIn calls can share one underlying channel through FusibleFlow, while an intervening non-fusible operator causes additional wrapper structure. ### Source excerpt Image Generated for the ArticleI Counted Every Hidden Channel Kotlin Flow Creates -- Most Devs Are Wrong About Which Operators Are Freebuffer() and flowOn() are supposed to fuse into one channel when chained. I wrote code to prove it -- and then found four "harmless" operators that quietly break it. Ask any experienced Kotlin developer what happens when you chain .buffer().flowOn(Dispatchers.IO).buffer(), and you'll usually get a confident answer: "it fuses into one channel." That's the folklore, repeated in talks, docs, and Stack Overflow answers. It's also only half true, and nobody seems to have actually checked the other half: which everyday operators quietly stop that fusion from happening. I decided to stop trusting folklore and instrument the actual runtime. Five separate experiments later, I had a very clear, very measurable answer -- and one of the results genuinely surprised me. The Myth, and the Mechanism Behind It Kotlin's coroutines library really does fuse adjacent channelFlow, flowOn, buffer, and produceIn calls into a single underlying channel instead of creating one per operator. This isn't a rumor -- it's real, deliberate behavior, implemented through an interface called FusibleFlow. Here's the actual check, straight from the source: https://medium.com/media/1cd3b407c1f2b2955b3df4be68ca18b5/href When flowOn() or buffer() is called, it checks whether the flow it's being called on already implements FusibleFlow. If it does, instead of wrapping it in a new object, it calls .fuse() -- which updates the existing object's settings (buffer size, dispatcher) in place. No new object. No new coroutine. No new channel. But that check only succeeds if the upstream is already a ChannelFlow. And that's where the folklore quietly stops being true. Building Something to Actually Measure This I wrote two nearly identical pipelines -- one where the fusible operators sit directly next to each other, and one where a completely ordinary map() sits in the middle: https://medi ## Android A2UI (AI to UI) Made Simple DevFeed: [Android A2UI (AI to UI) Made Simple]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-09T07:23:57Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Artificial Intelligence](), [Android](), [Jetpack Compose](), [Mobile](), [Protocol (disambiguation)](), [Google]() Tags: [a2ui](), [ai](), [android](), [android-app-development](), [api](), [artificial-intelligence](), [deprecated](), [google](), [jetpack-compose](), [mobile-app-development](), [software-development](), [user-interfaces]() ### AI overview This tutorial introduces A2UI, a protocol for rendering AI responses as user interfaces, and discusses trying it on Android with Jetpack Compose. It notes that an older Jetpack A2UI library is deprecated and that newer development is ongoing. ### Source excerpt Converting AI Prompt Output Into User Interface in Jetpack Compose Continue reading on Mobile App Development Publication " ## A Multi-Module Android Template with Kotlin Convention Plugins, Lint Rules, and Design System Tokens DevFeed: [A Multi-Module Android Template with Kotlin Convention Plugins, Lint Rules, and Design System Tokens]() Original publisher: [Read original article]() Author: Shamil Gulmetov Published: 2026-09-09T01:34:18Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Template](), [Android](), [Architecture & Design](), [Kotlin](), [Gradle](), [Jetpack Compose](), [Dependency injection](), [Automation](), [Refactoring](), [now-in-android]() Tags: [android](), [android-app-development](), [android-architecture](), [android-studio](), [architecture](), [automation](), [best-practices](), [build](), [compose](), [dependency-injection](), [gradle](), [how-to](), [jetpack-compose](), [kotlin](), [now-in-android](), [refactoring]() ### AI overview This tutorial presents an Android Architecture Template based on patterns from Google's Now in Android repository. It describes a multi-module structure with Gradle Version Catalogs, Kotlin Convention Plugins, Jetpack Compose design tokens and dark-theme support, dependency injection, custom Lint rules, and a terminal-based renaming tool. ### Source excerpt How to streamline your development workflow with pre-configured Kotlin Convention Plugins, custom Lint rules, and unified design system tokens. Creating a new Android application from scratch in modern engineering is rarely as simple as clicking File -> New -> New Project in Android Studio. Before writing a single line of business logic, developers face hours -- or even days -- of repetitive infrastructure setup: Configuring a scalable multi-module architecture. Setting up Gradle Version Catalogs and writing custom Kotlin Convention Plugins to eliminate build script duplication. Standardizing design tokens and dark theme support in Jetpack Compose. Wiring up Hilt Dependency Injection for Coroutine Dispatchers, network, and Application Scopes. Enforcing architectural boundaries and team coding standards using custom static analysis (Lint) rules. Google's official Now in Android (NiA) repository is the recognized gold standard for modern Android engineering. However, because NiA is a full-featured showcase app with domain logic (news feeds, authors, bookmarks, offline sync), using it as a starter kit is cumbersome: developers must strip out existing features while risking breaking build pipelines. This Android Architecture Template bridges that gap: a clean, production-ready starter kit that extracts NiA's best architectural patterns into an isolated foundation. To make it enterprise-ready with zero room for error, it includes a standalone automation tool. Instead of manual refactoring, run a single terminal command to rename and brand the entire architecture in seconds. Acknowledgments & Credits Core architectural decisions, build-logic convention plugins, and static analysis infrastructure in this template are directly inspired by Google's official Now in Android (NiA) repository. Rather than reinventing the wheel, this template focuses on developer ergonomics--making Google's best practices instantly usable out of the box. 1. Modular Project Architecture The repository ## From Permissions to Sessions: Rethinking Location Access in Android 17 DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-09-09T01:15:51Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Android](), [Jetpack Compose](), [android-development](), [implementation](), [ui]() Tags: [android](), [android-development](), [android-permissions](), [android17](), [androiddev](), [compose](), [development](), [feature](), [how-to](), [implementation](), [jetpack-compose](), [permission]() ### AI overview A tutorial on implementing Android 17's system-rendered Location Button in Jetpack Compose. The button uses the USE_LOCATION_BUTTON permission and grants precise location for the current session, with local rendering fallback on older Android versions or when remote rendering fails. ### Source excerpt Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th ## From Permissions to Sessions: Rethinking Location Access in Android 17 DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-09-03T18:18:32Z Content type: tutorial Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Android](), [Jetpack Compose](), [Mobile](), [ui]() Tags: [android](), [android-development](), [android-permissions](), [android17](), [androiddev](), [branding](), [consent](), [how-to](), [implementation](), [jetpack](), [jetpack-compose](), [layout](), [permissions]() ### AI overview A tutorial on implementing Android 17's system-rendered Location Button in Jetpack Compose applications. It explains session-only precise location access, the USE_LOCATION_BUTTON permission, the required Jetpack library, fallback rendering, and UI customization. ### Source excerpt Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th ## Animating between numbers in Jetpack Compose DevFeed: [Animating between numbers in Jetpack Compose]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-09-02T12:37:43Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Jetpack Compose](), [ui](), [API](), [Tooling]() Tags: [android](), [android-app-development](), [android-apps](), [android-development](), [androiddev](), [animation](), [api](), [app-development](), [apps](), [jetpack-compose](), [jetpackcompose](), [mobile-app-development](), [ui]() ### AI overview This tutorial explains how to animate changing numerical portfolio values in Jetpack Compose. It uses animateFloatAsState with a target value and a tween animation configured with a 500ms duration and FastOutSlowInEasing. ### Source excerpt When it comes to displaying portfolio data inside of Sleevd, users can change the selected filters which will adjust the portfolio values based on that selection. Alongside the main graph, we show the total portfolio value along with some small statistics for collection counts. When the user moves between the filter options, the values of... Continue reading -> ## jetc.dev Newsletter Issue #329 DevFeed: [jetc.dev Newsletter Issue #329]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-01T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [compose-multiplatform](), [Compose](), [cross-platform](), [Android](), [Streaming](), [HTML]() Tags: [android](), [compose](), [compose-multiplatform](), [cross-platform](), [dev](), [html](), [jetpack-compose](), [newsletter](), [streaming]() ### AI overview This newsletter issue reviews recent Jetpack Compose ecosystem updates, including the stable Compose Multiplatform release, new Remote Compose and Glance artifact groups, Compose Material3 changes, Navigation 3 beta updates, and related Android and Wear releases. It also covers cross-platform page curls, streaming Kotlinx HTML via Molecule, and screenshot prevention on Android and iOS. ### Source excerpt Compose Multiplatform `1.12.0`! New Remote Compose and Glance artifact groups! Cross-platform page curls! Streaming Kotlinx HTML via Molecule! Prevent screenshots! And... what does Material3 have against the rich?!? ## Using snapshot tests to prevent accessibility regressions in a Jetpack Compose Android app DevFeed: [Using snapshot tests to prevent accessibility regressions in a Jetpack Compose Android app]() Original publisher: [Read original article]() Author: ithersta (Яндекс) Published: 2026-08-27T07:05:12Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Compose](), [Android](), [яндекс]() Tags: [android](), [compose](), [jetpack](), [jetpack-compose](), [qa](), [tag-4004cf5948d3](), [tag-e69b694e3ce2](), [tag-f538878e20ff]() ### AI overview The article explains how the Yandex Mail Android team uses snapshot tests with Jetpack Compose to detect accessibility regressions. It describes Compose semantics, TalkBack, and why manual accessibility checks are insufficient as screens and shared components grow. ### Source excerpt Почта -- массовый продукт, которым пользуются самые разные люди, и поэтому он должен быть максимально доступен. Нам важно, чтобы приложение Яндекс Почты было удобно каждому, в том числе людям с особенностями зрения. На телефонах с Android за доступность для людей с особенностями зрения отвечает TalkBack -- функция озвучивания экрана, которая зачитывает текст, роль и состояние всех размеченных элементов на экране и позволяет с ними взаимодействовать. Если разметка сломается, приложением будет пользоваться сильно сложнее или вообще невозможно. Читать далее ## Mastering Jetpack Compose's New SelectionState API DevFeed: [Mastering Jetpack Compose's New SelectionState API]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-08-27T01:17:44Z Content type: tutorial Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Jetpack Compose](), [Compose](), [API](), [Code]() Tags: [android](), [androiddev](), [api](), [api-news](), [code](), [compose](), [jetpack-compose](), [reactive]() ### AI overview This tutorial introduces Jetpack Compose's SelectionState API, released in August 2026, for hoisted bidirectional selection control and reactive text observation. It demonstrates programmatic selection, clearing, range selection, word-based expansion, and access to selected text. ### Source excerpt Image generated using Gemini The Jetpack Compose August '26 release introduced a new API SelectionState for hoisted, bidirectional control and reactive text observation. Core ComponentsSelectionState An object that provides access to the selected text and methods for controlling it programmatically 🛑 We cannot use the same SelectionState with multiple SelectionContainersval selectionState = rememberSelectionState()SelectionContainer: A composable function that enables text selection of its content. SelectionContainer(state = selectionState) { Text( "Text content to be selected programmatically." ) }Programmatic Control Methods selectionState.selectAll(): Selects all the content in the container Button( onClick = { selectionState.selectAll() }) { Text("Select All") } selectionState.clear(): Clears the active selection Button(onClick = { selectionState.clear() }) { Text("Clear selection") } selectionState.select(TextRange): Selects a specific range of text Button( onClick = { selectionState.select(TextRange(0, 4)) }) { Text("Range selection") } selectionState.extendSelectionByWord(): Expands the selection of words This selects the first word in the container if there is no selection. The selection continues to the next Composable Text, if the next word is in a different Composable Text.Button( onClick = { selectionState.extendSelectionByWord()}) { Text("Extend selection") }Mutliple Text Components selectionSelected texts Provides access to the selected text. Returns List Backed by mutableStateOf -- Observable by Composablesprivate var _selectedTexts by mutableStateOf>Text(text = "Selected text: ${selectionState.selectedTexts}")Sample Code@Composable fun ProgrammaticSelectionExample() { val selectionState = rememberSelectionState() Column{ Row { Button( onClick = { selectionState.selectAll() }, ) { Text("Select All") } Button( onClick = { selectionState.clear() }, ) { Text("Clear selection") } } Row { Button( onClick = { selectionS ## jetc.dev Newsletter Issue #328 DevFeed: [jetc.dev Newsletter Issue #328]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-25T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [modules](), [API]() Tags: [api](), [batching](), [exceptions](), [images](), [jetpack-compose](), [modules](), [newsletter](), [published](), [videos]() ### AI overview Newsletter Issue #328 covers Jetpack Compose development topics, including API modules and composables, lazy-container lifecycle exceptions, recomposition and state-change batching, and selecting and copying text from images and videos. ### Source excerpt API modules and composables! LazyColumn() exceptions! 'Select and copy text' for images and videos! ## Building adaptive Android apps for foldable and expanded displays DevFeed: [Building adaptive Android apps for foldable and expanded displays]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-12T19:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Large Screen](), [Jetpack Compose](), [ui](), [Jetpack](), [Canvas]() Tags: [adaptive](), [android](), [jetpack](), [jetpack-compose](), [layout](), [multitasking](), [ui]() ### AI overview This Android developer article explains how to adapt apps for foldable devices and expanded displays. It covers window-based sizing, Jetpack Compose layout APIs, posture-aware interfaces, and preserving UI state across folding, rotation, multitasking, and resizing transitions, with examples from Notability and Flo Health. ### Source excerpt Posted by Fahd Imtiaz, Senior Product Manager, Loryn Hairston, Product Marketing Manager, and Tracy Agyemang, Product Marketing Manager, Android Developer Made by Google expands what's possible across the Android ecosystem. With the introduction of the Pixel 11 Pro Fold, Pixel Watch 5, and the entire Pixel family, users are moving seamlessly across diverse screen sizes, unique postures, and intelligent experiences. For you, the developer, this represents a massive opportunity: foldable users spend about 14x more than standard phone users. To help you elevate your existing experience without starting from scratch, we're sharing our latest platform guidance alongside real-world examples from developers already putting these features into production. Deliver adaptive experiences across foldables and expanded displays The Pixel 11 Pro Fold gives your app a chance to flex its capabilities with an expanded inner display and a standard size outer screen. Building for the foldable form factor requires dropping hardcoded layout rules and designing around available window space. Leveraging Jetpack Compose APIs like Navigation 3 with Scene strategies or our newest layout APIs like Grid and FlexBox allows your layout containers to automatically wrap, span, and reflow. You can also use the experimental MediaQuery API to dynamically adapt your UI to environmental signals like foldable posture, and keyboard states. Building adaptively requires tracking actual app dimensions rather than physical device size, especially during split-screen and multitasking flows. Using Window Size Classes from the WindowManager library allows your layout to respect folds and hinges as natural content separators. For instance, Notability leveraged Material 3 Window Size Classes to create a responsive two-pane layout that transitions smoothly between folded and expanded screens. As Ryan Shea, Android Engineering Manager at Notability, shared, tracking the window itself allows their layout and canvas z ## What's new in the Jetpack Compose August '26 release DevFeed: [What's new in the Jetpack Compose August '26 release]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-12T16:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Compose](), [Jetpack Compose](), [Android](), [API](), [upgrade](), [Documentation]() Tags: [2026](), [android](), [compose](), [graphics](), [jetpack-compose](), [layout](), [performance](), [release](), [sdk](), [shaders](), [update](), [upgrade]() ### AI overview The Jetpack Compose August 2026 release is stable and brings version 1.12 to core Compose modules. It adds Mesh Gradients, Wide Color Gamut and HDR rendering support, named areas in Grid, Credential Manager integration, and testing and performance improvements. The release also includes breaking changes, including a requirement for API 37 and AGP 9.1.1. ### Source excerpt Posted by Nick Butcher, Product Manager, Jetpack Compose Today, the Jetpack Compose August '26 release is stable! This release brings version 1.12 across core Compose modules (see the full BOM mapping), introducing rich visual APIs like Mesh Gradients and Wide Color Gamut (WCG) support, structural layout features like named areas in Grid, seamless integration with Android's Credential Manager, and significant testing and performance improvements. To update your project to today's release, upgrade your Compose BOM version to 2026.08.00: implementation(platform("androidx.compose:compose-bom:2026.08.00")) Breaking Changes AGP & Compile SDK: Compose 1.12 updates compileSdk to API 37, requiring a minimum AGP 9.1.1. As a reminder, Compose will always target the latest compileSdk. Learn more about this change here. Modifier.onFirstVisible() is deprecated: Migrate to Modifier.onVisibilityChanged(), which provides more precise visibility threshold tracking. Graphics Mesh Gradients Compose 1.12 introduces MeshGradientPainter to help you create multi-point, organic color gradients. val rows = 1 val columns = 1 val gradientPainter = remember { MeshGradientPainter(rows, columns) { // Parameters: row, column, position, color setVertex(0, 0, Offset(0f, 0f), Color.Red) // Top-Left setVertex(0, 1, Offset(1f, 0f), Color.Blue) // Top-Right setVertex(1, 0, Offset(0f, 1f), Color.Green) // Bottom-Left setVertex(1, 1, Offset(1f, 1f), Color.Yellow) // Bottom-Right } } Box( modifier = modifier .aspectRatio(16/9f) .fillMaxWidth() .paint(gradientPainter) ) For more information and examples, see the documentation. Wide Color Gamut & HDR Support Modern displays offer extended color fidelity and higher dynamic range. In Compose 1.12, full pipeline support for Wide Color Gamut (P3) and HDR rendering has been enabled across Compose graphics, paint, and shaders. Colors defined in non-sRGB color spaces (such as Display P3) are preserved through to platform rendering without color clamping. Colors wi ## Media3 1.11 adds customizable Compose player controls, gestures, and video preloading DevFeed: [Media3 1.11 adds customizable Compose player controls, gestures, and video preloading]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-11T16:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [media3](), [Compose](), [Jetpack Compose](), [Playback](), [Android](), [ExoPlayer](), [Ktor]() Tags: [android](), [audio](), [compose](), [compose-ui](), [exoplayer](), [jetpack](), [jetpack-compose](), [ktor](), [media](), [media3](), [playback](), [release](), [releases](), [video]() ### AI overview Android Media3 1.11 introduces customizable Jetpack Compose player layouts, gesture-based playback controls, player recycling and preloading for short-form video feeds, improved Cast integration, a Ktor HTTP client extension, and new Ogg and WAV muxing utilities. ### Source excerpt Posted by Toni Heidenreich, Software Engineer, Android Media3 1.11 is out. Powering the vast majority of top Android media apps, this release brings new features, bug fixes, and improvements across playback, editing, and UI components. We're expanding our Jetpack Compose UI modules with customizable Player slots and easy to use defaults, interactive gestures, state observers, and short-form video preloading using PlayerPool. We also modernized the Media3 Cast integration with SystemUI Output Switcher support, introduced a new Ktor HTTP client network extension, and added new muxing utilities for Ogg and WAV files. Read on for key highlights, and check out the full release notes for a comprehensive list of changes. Playback UI and Compose With Android becoming Compose-first, we are continuing to expand the media3-ui-compose and media3-ui-compose-material3 modules. This update introduces more granular control over your player layout, richer interaction patterns, and deeper integration with Material3. Customizable Player layout The Material 3 Player Composable now supports dedicated content slots for topControls, centerControls, bottomControls, and errorOverlay. You can drop in your own Composables or use the ready-made defaults published in PlayerDefaults: Player( player = player, topControls = { PlayerDefaults.TopControls(player) }, centerControls = { PlayerDefaults.CenterControls(player) }, bottomControls = { PlayerDefaults.BottomControls(player) }, ) The Player Composable also integrates FocusRequester support, enabling seamless D-pad and keyboard navigation on Android TV, foldables, and desktop environments. Example for a Composable Player with customized controls Gestures and playback speed control PlaybackSpeedState now provides a fast-forward/slow-motion API. The demo-compose app showcases this with a long-press gesture to fast-forward playback and seeking with double tap. Combined with the ProgressSlider introduced in 1.10, the Compose player UI now offers ric ## jetc.dev Newsletter Issue #326 DevFeed: [jetc.dev Newsletter Issue #326]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-11T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [compose-multiplatform](), [Android](), [compose-for-web](), [debug](), [Design system](), [Testing](), [AI-assisted coding]() Tags: [coding-agents](), [compose](), [compose-for-desktop](), [compose-for-web](), [debugger](), [design-system](), [jetpack-compose](), [testing]() ### AI overview Newsletter Issue #326 covers recent Compose developments, including Places UI Kit discussions, stability considerations, design-system testing, Compose Desktop and Web test bridges, and an Android debugger aimed at coding agents. It also highlights community projects and releases around Compose Multiplatform. ### Source excerpt Why we sometimes still need to think about stability! Compose Desktop/Web test bridge! Android debugger for coding agents! And... Places, everyone?!? ## How We Moved 1,500 Android Screenshot Tests to Roborazzi DevFeed: [How We Moved 1,500 Android Screenshot Tests to Roborazzi]() Original publisher: [Read original article]() Author: Zachary Wander Published: 2026-08-08T05:03:41Z Content type: tutorial Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [screenshot-testing](), [Android](), [Testing](), [Compose](), [Kotlin](), [Firebase](), [Git]() Tags: [android](), [compose](), [consistency](), [firebase](), [git](), [jetpack-compose](), [kotlin](), [mobile](), [robolectric](), [roborazzi](), [screenshot](), [screenshot-testing](), [software-testing](), [technology](), [testing](), [tests]() ### AI overview Thumbtack Engineering describes migrating 1,500 Android screenshot tests from Firebase Test Lab to Roborazzi, which runs locally on the JVM. The article covers porting existing suites, comparing screenshots in Git, and addressing rendering, test-data injection, and dependency-injection differences. ### Source excerpt How we moved 1,500 Android screenshot tests to Roborazzi.Introduction If you're a mobile developer you're probably no stranger to screenshot tests. Making sure that layouts remain consistent as time goes on and code changes is important for ensuring functionality and accessibility. Since Thumbtack uses Kotlin and Jetpack Compose for its Android apps, we had historically been using Firebase Test Lab to capture and compare layouts. However, using Firebase can be slow, tedious, and error-prone, so we decided it was time for a change. Instead of Firebase, we decided to migrate to using Roborazzi, a screenshot testing framework that runs fully locally inside the local JVM instead of relying on remote emulators and devices. For more details on why we migrated and the alternatives we evaluated, check out the previous blog post from Brian. This post is going to go into the details of how we migrated, and the challenges we faced along the way. Porting Loop Because the purpose of screenshot tests is ensuring consistency over time, we wanted to bring over our existing test suites into Roborazzi. Deleting the old ones and just creating new tests as we built new layouts was a potential option, but it would wipe out a lot of our automated verification. Instead, we ported our existing Firebase Test Lab screenshot test suites over to Roborazzi. In general, the porting process was pretty simple: Delete the old screenshots. Move the test suites over from androidTest to test. Adjust the code for any API differences. Record new screenshots. Compare the old and new screenshots in the git diff to make sure nothing is broken. Fix broken screenshots. Since Roborazzi uses Robolectric, and Robolectric implements the Android API, most of the test suites needed very few changes to work, with updating the main test rule and test annotations being enough to get them running. A few, like those that relied on permission granting rules or interacted directly with the test Activity, needed some more ## 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. ## Celebrating 5 years of Jetpack Compose DevFeed: [Celebrating 5 years of Jetpack Compose]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-28T16:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Compose](), [Jetpack Compose](), [Android](), [ui](), [Mobile](), [Kotlin](), [Compiler]() Tags: [android](), [compiler](), [compose](), [jetpack](), [jetpack-compose](), [kotlin](), [mobile](), [release](), [ui]() ### AI overview This retrospective marks five years since Jetpack Compose 1.0 was released on July 28, 2021. It describes Compose's evolution into a declarative UI toolkit using Kotlin, a compiler plugin, and a runtime; its expansion to additional form factors; and the community feedback that shaped the 1.0 release. The article also states that more than 68% of the top 1,000 apps use Compose in production and identifies Compose 1.11 as the latest version. ### Source excerpt 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 Too ## How R8 made Kotlin Coroutines on Android 2x faster DevFeed: [How R8 made Kotlin Coroutines on Android 2x faster]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-27T13:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Coroutines](), [Kotlin](), [R8](), [Android](), [Compose](), [Programming]() Tags: [android](), [android-gradle-plugin](), [app-performance](), [atomic](), [compose](), [coroutines](), [jetpack-compose](), [kotlin](), [perfetto](), [performance](), [programming](), [r8]() ### AI overview This article explains how R8 in AGP 9.2.0 optimizes Atomic*FieldUpdater calls into Unsafe variants, improving common operations by 2x to 4x. The optimization particularly benefits kotlinx.atomicfu and can make launching and cancelling Kotlin coroutines up to 2x faster. It also describes how coroutine overhead affected Jetpack Compose performance and how ART method traces helped identify bottlenecks. ### Source excerpt Posted by Andrei Shikov, Senior Software Engineer, Android Toolkit and Jonathan Starup, Software Engineer, R8 Team Starting from AGP 9.2.0, R8 optimizes most Atomic*FieldUpdater calls into Unsafe variants that perform 2x to 4x better on common operations. This has a particularly large impact on the kotlinx.atomicfu library that implements atomics for kotlinx.coroutines, making launching and cancelling coroutines up to 2x faster. In order to get the benefits, update your AGP to 9.2.0 or above. With the majority of Android apps adopting Kotlin as their main language of choice, kotlinx.coroutines has become a de-facto standard for asynchronous programming. The library offers a well-designed and structured way of managing concurrent flows that is native to Kotlin. Jetpack Compose was no exception, adopting coroutines for managing pointer events, animations and other interactions. At the time of writing, most concurrent APIs in Compose call suspend functions under the hood and are launching and/or cancelling coroutines to handle updates. As the Compose team started to investigate performance, coroutines were discovered to be a bottleneck for many operations that happen outside of composition. As an example, 80% of the time spent on creating and updating Modifier.clickable was consumed by launching and cancelling internal coroutines that handled InteractionSource updates. Based on those observations, much of early performance work was focused on removing coroutines from the default path and delaying initialization until necessary. The cost of a coroutine The easiest way to analyze a function's internal behavior on Android is to capture an Android Runtime (ART) method trace. An ART method trace is a tool that records the execution flow of an app, showing exactly which methods are called, their order, and how much time is spent in each, allowing developers to identify performance bottlenecks. For an empty LaunchedEffect { } call, it would look something like this: LaunchedE ## Practical Kotlin Multiplatform: Implementing the Firebase Sign-up Operation with Ktor DevFeed: [Practical Kotlin Multiplatform: Implementing the Firebase Sign-up Operation with Ktor]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-07-26T07:37:53Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Kotlin Multiplatform](), [Firebase](), [Ktor](), [Authentication](), [Android](), [interfaces](), [iOS](), [Exception]() Tags: [android](), [authentication](), [code](), [exception](), [firebase](), [interfaces](), [ios](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [ktor](), [multiplatform]() ### AI overview A tutorial on implementing a Firebase sign-up API request in a Kotlin Multiplatform application using Ktor. It defines an authentication repository interface and service implementation for Android and iOS clients, including API key, email, and password parameters and exception handling. ### Source excerpt This post is part four of a series adapted from Practical KMP, my book on building production Kotlin Multiplatform apps for Android and iOS. Part two built the authentication remote store and modelled its response. Implementing the Sign-up Endpoint Now that we've created the models for receiving back an authentication response, it's time for us... Continue reading -> ## Practical Kotlin Multiplatform: Creating the Firebase Auth Remote Store with Ktor DevFeed: [Practical Kotlin Multiplatform: Creating the Firebase Auth Remote Store with Ktor]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-07-18T15:17:19Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Kotlin Multiplatform](), [Authentication](), [Firebase](), [Ktor](), [Android](), [HTTP](), [iOS]() Tags: [android](), [api](), [authentication](), [firebase](), [ios](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [ktor](), [networking](), [tests]() ### AI overview This tutorial, part two of a Kotlin Multiplatform series, explains how to build a Firebase Authentication remote store with Ktor. It models Firebase Authentication's REST API behind a shared interface for Android and iOS, covering account operations, token refresh, dependency injection, and tests with a mocked client. ### Source excerpt This post is part two of a series adapted from Practical KMP, my book on building production Kotlin Multiplatform apps for Android and iOS. If you missed it, part one covered setting up the shared networking module. Introduction With our shared module now set up, we have the foundations that we need to start building... Continue reading -> ## jetc.dev Newsletter Issue #322 DevFeed: [jetc.dev Newsletter Issue #322]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-14T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [compose-for-desktop](), [multiplatform](), [Android](), [navigation]() Tags: [android](), [compose](), [compose-for-desktop](), [compose-multiplatform](), [dev](), [jetpack-compose](), [module](), [navigation]() ### AI overview This newsletter issue rounds up recent Jetpack Compose developments and related community content, including Compose updates, TV Compose performance, navigation, filter bars, settings-screen DSLs, Compose Multiplatform with SwiftUI, and Compose for Desktop performance. ### Source excerpt SubcomposeLayout! TV Compose! Nav3! Filter bars! Setting screens! And... can we make Compose for Desktop better?!? ## Practical Kotlin Multiplatform: Setting up the Kotlin Multiplatform Networking Module with Ktor DevFeed: [Practical Kotlin Multiplatform: Setting up the Kotlin Multiplatform Networking Module with Ktor]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-07-10T16:16:31Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Kotlin Multiplatform](), [Kotlin](), [Ktor](), [networking](), [REST API](), [Authentication](), [Firebase](), [Gradle](), [implementation](), [Android](), [iOS]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [app-development](), [authentication](), [firebase](), [gradle](), [implementation](), [ios](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [ktor](), [library](), [mobile-app-development](), [module](), [networking](), [rest-api]() ### AI overview A tutorial series installment that sets up a Kotlin Multiplatform networking module with Ktor for shared Android and iOS code. It describes building a portable Firebase Authentication and Firestore REST API layer without relying on platform-specific SDKs. ### Source excerpt This post is part one of a series adapted from Practical KMP, my book on building production Kotlin Multiplatform apps for Android and iOS. Part 1: Creating the Kotlin Multiplatform Module In this part of the book, we'll build the complete authentication remote store, defining a repository that handles every operation our app needs for... Continue reading -> [Next page]()