# Jetpack

Android Jetpack is a suite of libraries that helps developers follow best practices, reduce boilerplate code, and write consistent code across Android versions, devices, and form factors.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## 18 November 2026 Artifact Wave

DevFeed: [18 November 2026 Artifact Wave](<https://devfeed.tech/articles/18-november-2026-artifact-wave-144207.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/11/18/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-11-18T23:01:08Z

Content type: news

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [cameraX](<https://devfeed.tech/topics/camerax.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bom](<https://devfeed.tech/tags/bom.md>), [camera](<https://devfeed.tech/tags/camera.md>), [compose](<https://devfeed.tech/tags/compose.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [google](<https://devfeed.tech/tags/google.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [maven](<https://devfeed.tech/tags/maven.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [stable](<https://devfeed.tech/tags/stable.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Google announced the `2026.11.01` BOM with stable Jetpack Compose `1.13.0`, but several hours later neither had appeared on `maven.google.com`. At the time of writing, the latest listed Compose Foundation was `1.13.0-rc01` and the latest stable BOM was `2026.09.00`; the author expected the publishing gap to be fixed in the coming days. Meanwhile, over 300 artifact updates were available, including stable Jetpack Camera `1.7.0`.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## Android UI thread vs. RenderThread: what actually happens when a frame is drawn

DevFeed: [Android UI thread vs. RenderThread: what actually happens when a frame is drawn](<https://devfeed.tech/articles/android-ui-thread-vs-renderthread-what-actually-happens-when-a-frame-is-drawn-140454.md>)

Original publisher: [Read original article](<https://proandroiddev.com/android-ui-thread-vs-renderthread-3f54bb74340f?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-11-17T19:50:28Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [jank](<https://devfeed.tech/topics/jank.md>), [real-time rendering](<https://devfeed.tech/topics/real-time-rendering.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>)

Tags: [accelerated](<https://devfeed.tech/tags/accelerated.md>), [acceleration](<https://devfeed.tech/tags/acceleration.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [animation](<https://devfeed.tech/tags/animation.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [background](<https://devfeed.tech/tags/background.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [canvas](<https://devfeed.tech/tags/canvas.md>), [cause](<https://devfeed.tech/tags/cause.md>), [changes](<https://devfeed.tech/tags/changes.md>), [frame](<https://devfeed.tech/tags/frame.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [performance](<https://devfeed.tech/tags/performance.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [thread](<https://devfeed.tech/tags/thread.md>), [ui](<https://devfeed.tech/tags/ui.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

Frame drops can persist even when app code is off the main thread because frame preparation, command rendering, GPU execution, and display composition are separate stages. The UI thread handles callbacks, layout and drawing; with hardware acceleration, onDraw() records commands into display lists rather than rasterizing them. RenderThread replays those lists and submits graphics work, the GPU executes it, and SurfaceFlinger composes the app buffer. Diagnose the slow stage with a system trace: inspect main-thread Choreographer work, RenderThread DrawFrame, GPU completion, and presentation timing. Heavy onDraw() calculations can delay submission; costly paths or clips can make RenderThread slow; textures, overdraw, or shaders can saturate the GPU. Cache geometry or simplify commands according to the bottleneck. Compose uses the same graphics pipeline, though state reads can be placed in different stages to limit which work reruns. The supplied text is an excerpt and does not establish full-document coverage.

### Source excerpt

An Android app with a non-blocking main thread in your application can still get frame drops. This seems odd as we know that drawing a frame involves several components. Our code will only run in the first component. The UI thread will handle the app-side of things and records the drawing commands. A Native thread (RenderThread) will take these recordings and do the actual rendering. The GPU will then execute the graphics commands and SurfaceFlinger will compose your apps buffer with everything else on screen. This can be confusing when trying to solve dropped frames. Slowness in your onDraw() and an overloaded GPU will look the same to your users, but need different solutions. Moving your code to a background thread will only help with one of these issues. To find out which issue you have, follow your frame through the pipeline. What the UI thread does Every app has a main thread, usually called the UI thread. It owns the main message queue and runs lifecycle callbacks, input events and anything posted to the main looper. For the View system it also applies property changes, measures and lays out the hierarchy, runs animation callbacks, calls View.draw() and your onDraw(), and records drawing operations for hardware-accelerated rendering. The last job is easy to overlook. With hardware acceleration, onDraw() does not rasterize anything. Your Canvas calls are recorded into a display list, and each View keeps its own (a RenderNode). Here is a simple custom View: class ProgressView(context: Context) : View(context) { private val paint = Paint(Paint.ANTI_ALIAS_FLAG) private var progress = 0.5f override fun onDraw(canvas: Canvas) { super.onDraw(canvas) canvas.drawCircle(width / 2f, height / 2f, width * progress / 2f, paint) } } When invalidate() schedules a redraw, the framework calls onDraw() during the next frame traversal, on the UI thread, and the circle is recorded rather than painted. That is why a custom View can cause jank while the GPU is almost idle. If onDraw

## Kotlin Multiplatform Networking with Native Android and iOS ViewModels

DevFeed: [Kotlin Multiplatform Networking with Native Android and iOS ViewModels](<https://devfeed.tech/articles/kotlin-multiplatform-networking-with-native-android-and-ios-viewmodels-134271.md>)

Original publisher: [Read original article](<https://proandroiddev.com/kmp-networking-native-viewmodels-cf6fb357b012?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-11-14T14:49:33Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Ktor](<https://devfeed.tech/topics/ktor.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [coroutine-testing](<https://devfeed.tech/topics/coroutine-testing.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [cancellation](<https://devfeed.tech/tags/cancellation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [coroutine](<https://devfeed.tech/tags/coroutine.md>), [domain](<https://devfeed.tech/tags/domain.md>), [error](<https://devfeed.tech/tags/error.md>), [http](<https://devfeed.tech/tags/http.md>), [http-client](<https://devfeed.tech/tags/http-client.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [native](<https://devfeed.tech/tags/native.md>), [networking](<https://devfeed.tech/tags/networking.md>), [published](<https://devfeed.tech/tags/published.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>)

### AI overview

The article recommends sharing Ktor networking, serialization, repositories, domain models, and meaningful use cases in Kotlin Multiplatform while Android and iOS retain native ViewModels and presentation state. Callers own coroutine or task lifecycles: Android can launch through `viewModelScope`; iOS can bridge Kotlin suspend functions to Swift `async`/`await` with KMP-NativeCoroutines or SKIE and cancel its Swift `Task`. Ktor requests are suspending and need no automatic dispatcher switch when they are main-safe; truly blocking or CPU-heavy work should use an appropriate injected dispatcher. Preserve cancellation, reuse the HTTP client, and keep DTO-to-domain and domain-to-UI mapping at their respective boundaries. The article notes that Swift interop adds generated types and conversions, and shared unit tests do not verify platform HTTP engines or the Kotlin-to-Swift bridge.

### Source excerpt

Share Ktor networking, repositories, and use cases while Android and iOS keep control of their native ViewModels, UI state, threading, and cancellation. Kotlin Multiplatform allows us to share networking and business logic between Android and iOS. When an API call is made from the shared Kotlin module to the native app there are a number of things we need to make a decision on. Who creates the coroutine? Who handles where the work is executed? Will the ViewModel be the same for Android and iOS? How do we get the use cases from the shared module onto each platform? The decisions here are more important than the actual HTTP client. A good KMP architecture will not have all the layers shared between both platforms. We can leave the repositories and use cases in Kotlin, have Android use its Jetpack ViewModels and iOS use SwiftUI with its native Swift ViewModels. Both platforms will call the same business functions but each will have control over their own presentation lifecycle. It's important to make sure the work that needs to be consistent is shared. Let's look at how we can create this architecture using a simple example of fetching articles from a REST API. 1. Decide what belongs in shared code Lets start with two native applications and one shared KMP module. The Android and iOS applications will not need or have identical ViewModels. But they should access to the same business operation. The shared module can own: HTTP client configuration and API requests. DTOs and serialization. Repository implementations and data-to-domain mapping. Use cases that represent application operations. Shared validation, business rules, and error classification. Android can use using Jetpack ViewModel, viewModelScope, and StateFlow. iOS may use SwiftUI, ObservableObject, @Published, and Swift concurrency. This is one of the architecture options described in the Kotlin Multiplatform ViewModel documentation: sharing the repository and data layers while keeping platform-specific ViewMo

## 11 November 2026 Artifact Wave

DevFeed: [11 November 2026 Artifact Wave](<https://devfeed.tech/articles/11-november-2026-artifact-wave-130797.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/11/11/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-11-11T23:45:35Z

Content type: release

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Maven Central](<https://devfeed.tech/topics/maven-central.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [beta](<https://devfeed.tech/tags/beta.md>), [blog](<https://devfeed.tech/tags/blog.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [compose](<https://devfeed.tech/tags/compose.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [container](<https://devfeed.tech/tags/container.md>), [cronet](<https://devfeed.tech/tags/cronet.md>), [dash](<https://devfeed.tech/tags/dash.md>), [database](<https://devfeed.tech/tags/database.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [device](<https://devfeed.tech/tags/device.md>), [effect](<https://devfeed.tech/tags/effect.md>), [espresso](<https://devfeed.tech/tags/espresso.md>), [exoplayer](<https://devfeed.tech/tags/exoplayer.md>), [frame](<https://devfeed.tech/tags/frame.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

The 11 November 2026 artifact wave lists Media3 components at version 1.12.0-beta01, spanning playback, data sources, UI, session, testing, and transformation modules. It also lists new AndroidX Test alpha releases: core and related components at 1.8.0-alpha04, monitor at 1.9.0-alpha05, orchestrator at 1.7.0-alpha04, Espresso and extensions mostly at 3.8.0-alpha04 and 1.4.0-alpha04 respectively, plus Gradle version catalog releases at 2026.11.00.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## 4 November 2026 Artifact Wave

DevFeed: [4 November 2026 Artifact Wave](<https://devfeed.tech/articles/4-november-2026-artifact-wave-118920.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/11/04/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-11-04T22:51:19Z

Content type: news

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [blog](<https://devfeed.tech/tags/blog.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [web](<https://devfeed.tech/tags/web.md>), [webkit](<https://devfeed.tech/tags/webkit.md>)

### AI overview

The 4 November 2026 artifact wave added one new group, `androidx.web`, with a single artifact, `androidx.web:web`. It is not listed in the documentation; its description says it provides modern APIs for use with `android.webkit` and `androidx.webkit`. The wave also included just shy of 400 artifact updates.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## Build for every screen with the latest Jetpack Compose updates from Android Developer Summit

DevFeed: [Build for every screen with the latest Jetpack Compose updates from Android Developer Summit](<https://devfeed.tech/articles/build-for-every-screen-with-the-latest-jetpack-compose-updates-from-android-developer-summit-118936.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/build-for-every-screen-jetpack-compose-updates>)

Author: Rebecca Gutteridge

Published: 2026-11-04T00:00:00Z

Content type: release

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Android](<https://devfeed.tech/topics/android.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [jetpack-navigation](<https://devfeed.tech/topics/jetpack-navigation.md>), [deeplinks](<https://devfeed.tech/topics/deeplinks.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [cameraX](<https://devfeed.tech/topics/camerax.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [adaptive-development](<https://devfeed.tech/tags/adaptive-development.md>), [android](<https://devfeed.tech/tags/android.md>), [build](<https://devfeed.tech/tags/build.md>), [car](<https://devfeed.tech/tags/car.md>), [compose](<https://devfeed.tech/tags/compose.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [device](<https://devfeed.tech/tags/device.md>), [displays](<https://devfeed.tech/tags/displays.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [events-programs](<https://devfeed.tech/tags/events-programs.md>), [foldables](<https://devfeed.tech/tags/foldables.md>), [googlebook](<https://devfeed.tech/tags/googlebook.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [latest](<https://devfeed.tech/tags/latest.md>), [screen](<https://devfeed.tech/tags/screen.md>), [summit](<https://devfeed.tech/tags/summit.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The Compose 1.13 stable release is planned to add adaptive Grid and Flexbox layouts, Progressive Blur, and Formatted Text; the excerpt also describes a rewritten BasicTextField using TextFieldState and a buffer-driven architecture to avoid IME race conditions and support rich-text editing. Jetpack AppState, in alpha, extends Compose snapshot state into app architecture: Transform derives reactive state from State and Flow inputs, while StateStore shares observable keyed state across app surfaces and can persist it with DataStore. Navigation 3 version 1.2 adds type-safe deep links using Kotlin Serialization and supports custom argument parsing and synthetic back stacks. The excerpt also highlights Compose input support for trackpads, mice, and physical controls, adaptive multi-pane layouts using Navigation 3 and WindowManager, and Android skills for agent-assisted adaptive work, performance, XML migration, and Ink. These are summit highlights from the supplied excerpt, not a complete account of all sessions or announcements.

### Source excerpt

The Android ecosystem is a multi-device reality that spans phones, foldables, tablets, wearables, in-car displays, XR, and Googlebook. In this landscape, adaptive development is foundational to reaching users wherever they are.

## 28 October 2026 Artifact Wave

DevFeed: [28 October 2026 Artifact Wave](<https://devfeed.tech/articles/28-october-2026-artifact-wave-105705.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/10/28/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-10-28T22:11:23Z

Content type: news

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [blog](<https://devfeed.tech/tags/blog.md>), [can](<https://devfeed.tech/tags/can.md>), [comes](<https://devfeed.tech/tags/comes.md>), [compose](<https://devfeed.tech/tags/compose.md>), [composition](<https://devfeed.tech/tags/composition.md>), [custom](<https://devfeed.tech/tags/custom.md>), [developers](<https://devfeed.tech/tags/developers.md>), [effect](<https://devfeed.tech/tags/effect.md>), [here](<https://devfeed.tech/tags/here.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [this](<https://devfeed.tech/tags/this.md>)

### AI overview

The update describes two new AppState library groups. StateStore, built on the Compose runtime, provides APIs for hoisting snapshot state into the application layer; its multiplatform `statestore` artifact is paired with an Android-only `statestore-datastore` artifact for persistence. Transform, also built on the Compose runtime, lets apps run and manage a composition outside the UI; its `transform` and `transform-testing` artifacts both support multiplatform. The text also lists `androidx.media3:media3-effect-play-services` as a new artifact but gives no further details about it.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## What's new in Android developer tools and performance at Android Dev Summit

DevFeed: [What's new in Android developer tools and performance at Android Dev Summit](<https://devfeed.tech/articles/what-s-new-in-android-developer-tools-and-performance-at-android-dev-summit-105739.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/android-dev-summit-26-developer-tools-performance>)

Author: Adarsh Fernando

Published: 2026-10-28T00:00:00Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [google-antigravity](<https://devfeed.tech/topics/google-antigravity.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Android XR](<https://devfeed.tech/topics/android-xr.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Google AI](<https://devfeed.tech/topics/google-ai.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [perfetto](<https://devfeed.tech/topics/perfetto.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [acp](<https://devfeed.tech/tags/acp.md>), [adb](<https://devfeed.tech/tags/adb.md>), [added](<https://devfeed.tech/tags/added.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [agent-harnesses](<https://devfeed.tech/tags/agent-harnesses.md>), [agents](<https://devfeed.tech/tags/agents.md>), [android](<https://devfeed.tech/tags/android.md>), [dev](<https://devfeed.tech/tags/dev.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [events-programs](<https://devfeed.tech/tags/events-programs.md>), [help](<https://devfeed.tech/tags/help.md>), [performance](<https://devfeed.tech/tags/performance.md>), [summit](<https://devfeed.tech/tags/summit.md>), [this](<https://devfeed.tech/tags/this.md>), [tools](<https://devfeed.tech/tags/tools.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Android Dev Summit announcements cover three connected workflows: using agents within Android Studio, building and testing through Android CLI, and improving app performance from production signals. Android Studio's stable Bring Your Own Agent supports over 40 ACP-compatible agents with project context and tools such as Compose Preview and Logcat; other updates include agent change reviews and an XML-to-Compose migration assistant in Canary. Android CLI extends builds, profiling, previews, and device access to terminals and CI, with plugins for Google Antigravity, Claude Code, and Codex. Performance updates include LeakCanary analysis, Android Performance Analyzer tracing, Crashlytics and Android vitals signals, and tools for R8 optimization and Compose recomposition analysis. Lightbuild is an early preview recommended for experimental projects, while production apps should continue using Gradle and AGP. Availability varies by feature across stable, Canary, early access, and forthcoming releases.

### Source excerpt

This year at Android Dev Summit we shared how Android's developer tools are evolving to help you be more productive alongside your agents.

## Agentic and Flexible: A next era of Android development

DevFeed: [Agentic and Flexible: A next era of Android development](<https://devfeed.tech/articles/agentic-and-flexible-a-next-era-of-android-development-105740.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/build-it-your-way-a-next-era-of-android-development>)

Author: Matthew McCullough

Published: 2026-10-28T00:00:00Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Android XR](<https://devfeed.tech/topics/android-xr.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Jetpack XR SDK](<https://devfeed.tech/topics/jetpack-xr-sdk.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [ML Kit](<https://devfeed.tech/topics/ml-kit.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [google-antigravity](<https://devfeed.tech/topics/google-antigravity.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apps](<https://devfeed.tech/tags/apps.md>), [availability](<https://devfeed.tech/tags/availability.md>), [build](<https://devfeed.tech/tags/build.md>), [dev](<https://devfeed.tech/tags/dev.md>), [development](<https://devfeed.tech/tags/development.md>), [era](<https://devfeed.tech/tags/era.md>), [everyday](<https://devfeed.tech/tags/everyday.md>), [flexibility](<https://devfeed.tech/tags/flexibility.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [great](<https://devfeed.tech/tags/great.md>), [next](<https://devfeed.tech/tags/next.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [summit](<https://devfeed.tech/tags/summit.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Android's announced tools aim to reduce development friction through agent choice, agent-ready workflows, new APIs, and broader form-factor support. Android Studio Rabbit 2 is stable and supports Claude Agent, Codex, Antigravity, and 40+ ACP-compliant agents. Android CLI adds Firebase-powered remote device testing, Compose previews, Perfetto profiling, bundle and library analysis, and 30+ Android skills; official plugins are also available for Antigravity, Claude Code, and Codex. For agentic apps, AppFunctions is in beta, while A2UI for Compose and ML Kit's Gemini Nano 4 Agentic API are in alpha. Connected Apps can be prototyped before applying for the production preview. Adaptive development updates include alpha AppState, stable Navigation 3 1.2, and adaptive layout features planned for Compose 1.13. The excerpt also announces stable Jetpack XR libraries, Android Studio XR emulators, XR Engine Hub, and geospatial APIs. Google Play foldable requirements are to be detailed later.

### Source excerpt

Today, at the Android Dev Summit, we are announcing the broad availability of many tools and APIs designed to remove everyday friction and give you more flexibility to build great Android apps.

## 21 October 2026 Artifact Wave

DevFeed: [21 October 2026 Artifact Wave](<https://devfeed.tech/articles/21-october-2026-artifact-wave-94015.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/10/21/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-10-21T23:43:09Z

Content type: release

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [blog](<https://devfeed.tech/tags/blog.md>), [compose](<https://devfeed.tech/tags/compose.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [expression](<https://devfeed.tech/tags/expression.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [remote](<https://devfeed.tech/tags/remote.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [testing](<https://devfeed.tech/tags/testing.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

The 21 October 2026 artifact wave includes one new Compose Remote artifact, `androidx.compose.remote:remote-creation-expression`, and four Photo Picker artifacts: `photopicker-activity`, `photopicker-embedded`, `photopicker-embedded-compose`, and `photopicker-embedded-testing`. The source says these are among more than 800 artifact updates; it gives no details about their functionality.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## AI, Meet App: Android AppFunctions

DevFeed: [AI, Meet App: Android AppFunctions](<https://devfeed.tech/articles/ai-meet-app-android-appfunctions-91130.md>)

Original publisher: [Read original article](<https://proandroiddev.com/ai-meet-app-android-appfunctions-30bb845a4787?source=rss----c72404660798---4>)

Author: Katie Barnett

Published: 2026-10-20T16:45:04Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-apps](<https://devfeed.tech/tags/ai-apps.md>), [ai-on-device](<https://devfeed.tech/tags/ai-on-device.md>), [android](<https://devfeed.tech/tags/android.md>), [android-16](<https://devfeed.tech/tags/android-16.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [data](<https://devfeed.tech/tags/data.md>), [device](<https://devfeed.tech/tags/device.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [google](<https://devfeed.tech/tags/google.md>), [internet](<https://devfeed.tech/tags/internet.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>)

### AI overview

Android AppFunctions lets authorized on-device AI agents call tools exposed by Android apps through the OS; the API supports Android 16 and above and was in private preview with trusted testers as of October 2026. Apps describe functions and their inputs and outputs in KDoc-backed metadata generated by the Jetpack library; agents use that metadata to select a function and pass parameters. The article's Game Night Guru example exposes local board-game queries and play logging. It recommends choosing focused, low-risk functions, limiting access, requiring clear confirmation for destructive actions, and disabling functions when authentication or subscription conditions are unmet. Nullable inputs let agents omit information, though the author says requests for the agent to ask users for required details did not always work in testing. The described testing agent can exercise functions, and Gemini supplemented locally returned game names with web searches. The excerpt also points to a dedicated Android skill for generating Kotlin code and metadata.

### Source excerpt

Implement the brand new API which allows your Android apps to behave just like an on-device MCP server. Your apps and AI have been side by side on your device for a while. It's time to introduce them! Android AppFunctions is a new Android platform API and a Jetpack library which allows on device AI apps like the Gemini app to interact directly with apps that implement it. Generated with Gemini Nano Banana. As of writing this article (October 2026), the AppFunctions API is in a private preview with trusted testers, so you are not able to test it out immediately with the consumer version Gemini or any other AI apps on your device or emulator. But if, like me, you want to stay ahead of the AI curve, you can prepare your app right now. That way, when it does roll out to users, your app will be ready to meet Gemini! (And never fear, there are other ways to test it!) What is an AppFunction? AppFunctions allows your app to provide tools for the on device AI agents (e.g. the Google Gemini app) to use to answer user's questions and complete tasks. It behaves just like an on device MCP server, exposing this functionality via the Android OS itself so that any authorised agent (not just Gemini) can request access and interact with your app. AppFunctions are available for Android 16 and above. Why implement AppFunctions?Local app data By now, we have all used AI to fetch data from the internet and other sources and use it to create cool new things and help us with our daily lives. But what if the data we want to use is not on the internet or some other cloud source and only exists within an app? There are many reasons why you might only want your data to stay local to your app: Privacy: Personal information, financial information, health information, all things that a user may not want to be shared in its entirety on a server or the internet. Authentication: Data that requires the user to authenticate to see first, and we might not be able to verify that the AI app is authorised

## Your Design System Is a Contract. Enforce It with Konsist and Android Lint

DevFeed: [Your Design System Is a Contract. Enforce It with Konsist and Android Lint](<https://devfeed.tech/articles/your-design-system-is-a-contract-enforce-it-with-konsist-and-android-lint-91135.md>)

Original publisher: [Read original article](<https://proandroiddev.com/konsist-design-system-validator-jetpack-compose-d5c3814fe462?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-10-20T16:36:52Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Design system](<https://devfeed.tech/topics/design-system.md>), [lint](<https://devfeed.tech/topics/lint.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [automated](<https://devfeed.tech/tags/automated.md>), [color](<https://devfeed.tech/tags/color.md>), [colors](<https://devfeed.tech/tags/colors.md>), [component](<https://devfeed.tech/tags/component.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-ui](<https://devfeed.tech/tags/compose-ui.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [custom](<https://devfeed.tech/tags/custom.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [design-systems](<https://devfeed.tech/tags/design-systems.md>), [dimensions](<https://devfeed.tech/tags/dimensions.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [feature](<https://devfeed.tech/tags/feature.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [lint](<https://devfeed.tech/tags/lint.md>), [padding](<https://devfeed.tech/tags/padding.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [rules](<https://devfeed.tech/tags/rules.md>), [screen](<https://devfeed.tech/tags/screen.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

Treat the design system as an enforceable engineering contract: centralize approved tokens and reusable components, then place each rule in the layer suited to check it. Konsist can test package structure and architectural boundaries; custom Android Lint detectors can flag prohibited source patterns, such as numeric Compose Color literals outside approved packages; Compose UI tests can check rendered behavior like accessibility, font scaling, touch targets, and state transitions. The sample Lint rule is deliberately limited: it may miss colors expressed through constants, helpers, resources, aliases, or other forms, and it cannot judge whether a named token is semantically appropriate. The article recommends testing both violations and allowed exceptions, keeping rules narrow to reduce false positives, verifying APIs against the project's pinned versions, and rolling checks out gradually before making them blocking in CI.

### Source excerpt

A practical guide to enforcing colors, spacing, typography, shapes, and component conventions in Jetpack Compose -- with a custom Android Lint rule. A design system is only as reliable as the rules that prevent teams from bypassing it. Most Android teams have a design system. They define typography, colors, spacing, shapes, dimensions, and reusable Compose components. They document usage guidelines, publish component libraries, and ask developers to follow the established conventions. Yet a few months into development, the same problems start appearing. One screen uses 16.dp for horizontal padding; another uses 18.dp. A developer creates a custom TextStyle because the existing typography does not look quite right. A feature introduces a hardcoded hex color. A button uses a different corner radius from the rest of the application. Someone builds another card component because the existing one seems inconvenient to reuse. None of these decisions looks particularly dangerous in isolation. Together, they undermine the consistency the design system was supposed to provide. Code reviews can catch some of these violations, but they are not a reliable enforcement mechanism. Reviewers have limited time, conventions are easy to overlook, and the same feedback gets repeated across pull requests. The better approach is to treat the design system as an engineering contract and enforce that contract through automated checks. For Android teams using Jetpack Compose, Konsist and custom Android Lint rules solve complementary parts of this problem. Konsist can enforce architectural and structural conventions. Android Lint can inspect source code for prohibited patterns. Compose UI tests can verify how the resulting interface behaves at runtime. Together, they turn design-system conventions from documentation into executable rules. Start by defining what the contract actually means Before writing a test or a lint detector, identify the rules your team expects every feature to follow. N

## Finally The Official Way of Secure DataStore is Here!

DevFeed: [Finally The Official Way of Secure DataStore is Here!](<https://devfeed.tech/articles/finally-the-official-way-of-secure-datastore-is-here-91132.md>)

Original publisher: [Read original article](<https://proandroiddev.com/finally-the-official-way-of-secure-datastore-is-here-ae878f5eb457?source=rss----c72404660798---4>)

Author: Burak Karaduman

Published: 2026-10-20T16:18:09Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Android Security](<https://devfeed.tech/topics/android-security.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [coroutines-flow](<https://devfeed.tech/topics/coroutines-flow.md>), [Coroutines](<https://devfeed.tech/topics/coroutines.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [backup](<https://devfeed.tech/tags/backup.md>), [coroutines](<https://devfeed.tech/tags/coroutines.md>), [data](<https://devfeed.tech/tags/data.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [flow](<https://devfeed.tech/tags/flow.md>), [jetpack-datastore](<https://devfeed.tech/tags/jetpack-datastore.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [mobile-app-security](<https://devfeed.tech/tags/mobile-app-security.md>)

### AI overview

The excerpt shows how `androidx.datastore:datastore-tink` can encrypt a typed DataStore through an `AeadSerializer` backed by Tink and an Android Keystore master key, replacing custom AES/GCM storage code. It explains that encryption protects copied files but not data read by the app itself. Decryption or deserialization failures become DataStore corruption; a handler can reset a session, while irreplaceable data needs another recovery plan. Because Android backups can restore the encrypted file and keyset without the device-bound master key, the excerpt advises excluding both from cloud and device-transfer backups. It also outlines migration from legacy encrypted preferences and notes that the library is alpha, key rotation is manual, and migration was unit-tested but not tested on an install retaining real legacy data.

### Source excerpt

Securing data has always been a concern since the early days of app development. Platforms do their best to protect user data, but there are always edge cases. Attackers may still reach sensitive data, even in encrypted form, and if they get the key, the protection is meaningless. So yes, encryption helps, but it is not magic. On Android we started with SharedPreferences. It was simple, widely used, and even had built in encryption through EncryptedSharedPreferences. Then Kotlin Flow and Coroutines arrived, apps reached a global audience, and codebases grew. We now needed async operations, thread safety, type safety, custom objects, proper error handling and reactive streams. SharedPreferences was not designed for that, and DataStore was introduced to solve it. But Google deprecated the Jetpack Security (security-crypto) library, and DataStore had no built in encryption, so most of us wrote our own. Now there is androidx.datastore:datastore-tink, added in DataStore 1.3.0-alpha07. In this post we build a small encrypted session store: a login screen that saves an email and a token, and a home screen that reads them. We also show what happens when decryption fails. The full sample project (with Hilt) is on GitHub: burkido/official-datastore-encryption-sample What encryption protects, and what it does not Encrypting a file protects it when someone gets the file but not your app, for example from a rooted phone, a raw copy of the device storage or a copied backup. It does not protect against code inside your own app, because that code can simply read the decrypted value from DataStore. Encryption is one layer of security. It is not the whole solution.How we did it before Our old setup was similar to the one in this article. A security class created an AES/GCM key in the Android Keystore and managed the IV manually: fun encryptData(keyAlias: String, text: String): Pair<ByteArray, ByteArray> { val secretKey = generateSecretKey(keyAlias) cipher.init(Cipher.ENCRYPT_MODE, se

## The Evolution of Flow Collection in Jetpack Compose

DevFeed: [The Evolution of Flow Collection in Jetpack Compose](<https://devfeed.tech/articles/the-evolution-of-flow-collection-in-jetpack-compose-85772.md>)

Original publisher: [Read original article](<https://proandroiddev.com/the-evolution-of-flow-collection-in-jetpack-compose-e93416a9d52d?source=rss----c72404660798---4>)

Author: chanzmao

Published: 2026-10-13T00:04:28Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [coroutines-flow](<https://devfeed.tech/topics/coroutines-flow.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-architecture](<https://devfeed.tech/tags/android-architecture.md>), [android-compose](<https://devfeed.tech/tags/android-compose.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [api](<https://devfeed.tech/tags/api.md>), [app-architecture](<https://devfeed.tech/tags/app-architecture.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [background](<https://devfeed.tech/tags/background.md>), [collection](<https://devfeed.tech/tags/collection.md>), [compose](<https://devfeed.tech/tags/compose.md>), [composition](<https://devfeed.tech/tags/composition.md>), [coroutine](<https://devfeed.tech/tags/coroutine.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [flow](<https://devfeed.tech/tags/flow.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [state](<https://devfeed.tech/tags/state.md>), [ui](<https://devfeed.tech/tags/ui.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [viewmodel](<https://devfeed.tech/tags/viewmodel.md>)

### AI overview

`collectAsStateWithLifecycle()` packages lifecycle-aware Flow collection into a concise Compose API: collection runs while the lifecycle is active and stops below the chosen state. Earlier options have tradeoffs: `collectAsState()` may keep collecting while the composition remains active; `launchWhenStarted()` can suspend collection while upstream work continues; `repeatOnLifecycle()` cancels and restarts its block but requires more code; and `flowWithLifecycle()` still needs Compose state conversion and an initial value for a regular Flow. Stopping UI collection does not necessarily stop upstream work or refresh data. For example, `stateIn` with `SharingStarted.WhileSubscribed(5_000)` can keep upstream active for five seconds after the last subscriber; later restart behavior depends on the source Flow. A cold HTTP Flow may fetch again, while a Room Flow resuming observation does not necessarily make a network request.

### Source excerpt

From basic state collection to lifecycle-aware UI updates Image created by AI When collecting a Flow in Jetpack Compose, the code can be as simple as this: val uiState by viewModel.uiState.collectAsState() But Android applications have a lifecycle. When an app moves to the background, should the UI continue collecting updates? What happens when the user returns? Over the years, Android developers have used several approaches to handle these questions. Understanding how they evolved helps us choose the right API without adding unnecessary code. Let's walk through the key changes, from collectAsState()to collectAsStateWithLifecycle(). 1. Compose 1.0: collectAsState()July 2021 Jetpack Compose 1.0 introduced collectAsState() as a straightforward way to convert a Flow into Compose State. val uiState by viewModel.uiState.collectAsState() Whenever the Flow emits a new value, Compose updates the state and recomposes the relevant UI. The code is simple, but there is an important distinction: collectAsState() does not automatically stop collection when the Android lifecycle falls below STARTED. For example, when an Activity moves to the background, collection can continue as long as the composition remains active. This isn't necessarily a problem for every Flow. However, if the upstream Flow performs expensive work or maintains an active connection, continuing to collect while the UI is not visible may be undesirable. 2. Lifecycle 2.4.0: launchWhenStarted() and repeatOnLifecycle()October 2021 Before lifecycle-aware collection became a simple Compose API, developers often managed the lifecycle manually. One approach was launchWhenStarted(): lifecycleOwner.lifecycleScope.launch { lifecycleOwner.lifecycle.launchWhenStarted { viewModel.uiState.collect { state -> // Handle state } } } This approach tied execution to the lifecycle, but it had a significant drawback: when the lifecycle stopped, the coroutine could be suspended rather than cancelled. Upstream work could continue unne

## Google brings Gemini 4 Argon to Android development tools

DevFeed: [Google brings Gemini 4 Argon to Android development tools](<https://devfeed.tech/articles/bringing-our-latest-frontier-model-to-android-developers-88689.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/bringing-gemini-4-argon-to-android-agentic-engineering-antigravity-cli>)

Author: Jason Buchel

Published: 2026-10-13T00:00:00Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [product-news](<https://devfeed.tech/tags/product-news.md>)

### AI overview

Google is making Gemini 4 Argon available to Android developers through Antigravity, Android Studio, Google AI Studio, and Firebase AI Logic. The article describes agentic workflows for multi-step development tasks, build-error diagnosis using Gradle and Kotlin logs, and generating Jetpack Compose interfaces and shaders.

### Source excerpt

As agentic development accelerates, Android engineering is reaching an exciting new frontier: moving from assistive code completion to agents executing end-to-end under your direction. You have total choice and flexibility in the models and agents you use.

## Moving Local Storage to Jetpack DataStore Without Paying a Cent in Performance

DevFeed: [Moving Local Storage to Jetpack DataStore Without Paying a Cent in Performance](<https://devfeed.tech/articles/moving-local-storage-to-jetpack-datastore-without-paying-a-cent-in-performance-84567.md>)

Original publisher: [Read original article](<https://proandroiddev.com/moving-local-storage-to-jetpack-datastore-without-paying-a-cent-in-performance-e709b28719de?source=rss----c72404660798---4>)

Author: Taufik Amaryansyah

Published: 2026-10-10T17:14:49Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [async](<https://devfeed.tech/topics/async.md>), [coroutines-flow](<https://devfeed.tech/topics/coroutines-flow.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [all](<https://devfeed.tech/tags/all.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [anr](<https://devfeed.tech/tags/anr.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [apply](<https://devfeed.tech/tags/apply.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [background](<https://devfeed.tech/tags/background.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-datastore](<https://devfeed.tech/tags/jetpack-datastore.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [local](<https://devfeed.tech/tags/local.md>), [mobile-performance](<https://devfeed.tech/tags/mobile-performance.md>), [moving](<https://devfeed.tech/tags/moving.md>), [performance](<https://devfeed.tech/tags/performance.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

The app replaced SharedPreferences with Jetpack DataStore and found no measurable runtime cost in an isolated comparison: startup, CPU, and memory differences stayed within run-to-run variation. On a Samsung Galaxy A15, all measured cold and warm starts after updating were faster, including the first launch that ran the migration; because the APKs differed in other ways, this shows the migration did not delay users, not that DataStore caused the speedup. The migration runs on a background thread and reportedly takes tens of milliseconds. The release as a whole showed its first screen 0.7 seconds faster on a Samsung Galaxy A55. The authors stress measuring builds in one session, reporting ranges, and adding telemetry for migration duration and write failures. Findings come from internal tests on physical devices and may vary on other hardware.

### Source excerpt

How we replaced the storage foundation of a large-scale app, then proved it with numbers.Illustration Generated by GeminiTL;DR The most important local data in our app now lives in Jetpack DataStore, replacing SharedPreferences. We measured the impact with an isolated benchmark: no measurable runtime cost. Cold start, hot start, CPU, and memory all stay within normal run-to-run variation. Migrating existing users' data to DataStore runs once and finishes in tens of milliseconds, on a background thread. In the same release, the app as a whole shows its first screen 0.7 seconds faster than the previous release on a Samsung Galaxy A55. DataStore did not stand in the way of that. Why we left SharedPreferences SharedPreferences has been part of Android since API 1. It is simple and good enough for many cases. But in an app as large as ours, its limits started to show. 1. The API is synchronous, and it is often called from the main thread. The first read of a SharedPreferences file blocks the calling thread until the whole file is loaded from disk. If that thread is the main thread, the UI waits too. 2. apply() is not fully asynchronous. apply() looks like a background write. But Android waits for every pending apply() to finish when an Activity stops or a Service finishes. On a device with slow storage, that wait can turn into an ANR. commit() is worse, because it blocks explicitly. 3. Write failures are invisible. apply() never tells you whether the data was actually saved. If it fails, the app never finds out. 4. There is no convenient reactive way to observe changes. All you get is a listener, which leaks easily and does not fit with coroutines or Flow. 5. Types are not enforced. Storing an Int and reading it back as a Long only surfaces at runtime, as a ClassCastException. Jetpack DataStore was designed to address all of this: SharedPreferences vs Jetpack DataStoreBenchmark results The question we heard most before the release: "If the storage moves to DataStore, won

## Tracking execution events for your WorkManager Workers

DevFeed: [Tracking execution events for your WorkManager Workers](<https://devfeed.tech/articles/tracking-execution-events-for-your-workmanager-workers-60130.md>)

Original publisher: [Read original article](<https://msfjarvis.dev/posts/tracking-execution-events-for-your-workmanager-workers/>)

Author: Harsh Shandilya

Published: 2026-09-25T11:05:00Z

Content type: tutorial

Language: en

Sources: [Posts on Harsh Shandilya](<https://devfeed.tech/sources/posts-on-harsh-shandilya.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [execution](<https://devfeed.tech/topics/execution.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Sentry](<https://devfeed.tech/topics/sentry.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [android](<https://devfeed.tech/tags/android.md>), [android-jetpack](<https://devfeed.tech/tags/android-jetpack.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [execution](<https://devfeed.tech/tags/execution.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [lint](<https://devfeed.tech/tags/lint.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [sentry](<https://devfeed.tech/tags/sentry.md>), [workmanager](<https://devfeed.tech/tags/workmanager.md>)

### AI overview

A tutorial on using new experimental WorkManager APIs in Android Jetpack to inspect worker executions, collect execution metrics, and send events to Sentry dashboards. It also discusses limitations involving result subtypes, Lint, and Kotlin parameters.

### Source excerpt

WorkManager 2.12.0 introduces brand new APIs for deep introspection of Worker executions

## New Jetpack artifacts include Google's first official A2UI implementation for Compose

DevFeed: [New Jetpack artifacts include Google's first official A2UI implementation for Compose](<https://devfeed.tech/articles/23-september-2026-artifact-wave-58891.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/09/23/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-09-23T20:01:08Z

Content type: release

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [a2ui](<https://devfeed.tech/topics/a2ui.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [a2ui](<https://devfeed.tech/tags/a2ui.md>), [blog](<https://devfeed.tech/tags/blog.md>), [compose](<https://devfeed.tech/tags/compose.md>), [google](<https://devfeed.tech/tags/google.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [release](<https://devfeed.tech/tags/release.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>)

### AI overview

This release update covers a new wave of Jetpack artifacts, including Google's first official implementation of A2UI for Compose. It also notes more than 500 new artifact versions and an incomplete artifact release with a missing POM file.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## 16 September 2026 Artifact Wave

DevFeed: [16 September 2026 Artifact Wave](<https://devfeed.tech/articles/16-september-2026-artifact-wave-31463.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/09/16/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-09-16T19:33:36Z

Content type: release

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [blog](<https://devfeed.tech/tags/blog.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>)

### AI overview

A brief update on the new Jetpack artifacts released during the week of September 16, 2026.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## Build, Audit, and Ship on Jetson with NVIDIA Skills + JetPack 7.2: BSP and Device Skills, Signing, and Trustworthy Jetson Production

DevFeed: [Build, Audit, and Ship on Jetson with NVIDIA Skills + JetPack 7.2: BSP and Device Skills, Signing, and Trustworthy Jetson Production](<https://devfeed.tech/articles/build-audit-and-ship-on-jetson-with-nvidia-skills-jetpack-7-2-bsp-and-device-skills-signing-and-trustworthy-jetson-production-49262.md>)

Original publisher: [Read original article](<https://www.seeedstudio.com/blog/2026/09/14/build-audit-and-ship-on-jetson-with-nvidia-skills-jetpack-7-2-bsp-and-device-skills-signing-and-trustworthy-jetson-production-2/>)

Author: silvia

Published: 2026-09-14T03:51:49Z

Content type: article

Language: en

Sources: [Seeed Studio](<https://devfeed.tech/sources/latest-news-from-seeed-studio.md>)

Topics: [Jetson](<https://devfeed.tech/topics/jetson.md>), [Embedded Software Dev](<https://devfeed.tech/topics/embedded-software-dev.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [Risk](<https://devfeed.tech/topics/risk.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>), [pcie](<https://devfeed.tech/topics/pcie.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [DeepStream](<https://devfeed.tech/topics/deepstream.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [customization](<https://devfeed.tech/tags/customization.md>), [deepstream](<https://devfeed.tech/tags/deepstream.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [flashing](<https://devfeed.tech/tags/flashing.md>), [inference](<https://devfeed.tech/tags/inference.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetson](<https://devfeed.tech/tags/jetson.md>), [llm](<https://devfeed.tech/tags/llm.md>), [news](<https://devfeed.tech/tags/news.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [risk](<https://devfeed.tech/tags/risk.md>), [signing](<https://devfeed.tech/tags/signing.md>)

### AI overview

This article explains how NVIDIA BSP-side and device-side skills support Jetson production workflows. It covers carrier-board and boot configuration, memory optimization, flashing and validation, headless inference operations, DeepStream pipelines, and skill signing and governance.

### Source excerpt

Embedded projects have two very different risk zones: before flashing and after booting. NVIDIA separates The post Build, Audit, and Ship on Jetson with NVIDIA Skills + JetPack 7.2: BSP and Device Skills, Signing, and Trustworthy Jetson Production appeared first on Latest News from Seeed Studio.

## 9 September 2026 Artifact Wave

DevFeed: [9 September 2026 Artifact Wave](<https://devfeed.tech/articles/9-september-2026-artifact-wave-28108.md>)

Original publisher: [Read original article](<https://commonsware.com/blog/2026/09/09/jetpack-artifact-wave.html>)

Author: CommonsWare

Published: 2026-09-09T20:32:28Z

Content type: release

Language: en

Sources: [The CommonsBlog](<https://devfeed.tech/sources/the-commonsblog.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [blog](<https://devfeed.tech/tags/blog.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>)

### AI overview

This release update covers a new Jetpack artifact wave, including Ink Rendering support for iOS and more than 1,300 new artifact versions.

### Source excerpt

Here is what we got as new Jetpack artifacts this week!

## September 09, 2026

DevFeed: [September 09, 2026](<https://devfeed.tech/articles/september-09-2026-22736.md>)

Original publisher: [Read original article](<https://developer.android.com/jetpack/androidx/versions/all-channel>)

Published: 2026-09-09T17:00:00Z

Content type: release

Language: en

Sources: [AndroidX Release Notes](<https://devfeed.tech/sources/androidx-release-notes.md>)

Topics: [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [compose](<https://devfeed.tech/tags/compose.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [latest-release](<https://devfeed.tech/tags/latest-release.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [room](<https://devfeed.tech/tags/room.md>), [security](<https://devfeed.tech/tags/security.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

This Android developer page lists AndroidX library components across four release channels and provides recent release dates and version information. It also links to component release histories, archived release notes, and the current versions page.

### Source excerpt

Activity Version 1.14.0-alpha02 Annotation Version 1.11.0-rc01 Benchmark Version 1.5.0 Car App Version 1.9.0-alpha02 Collection Version 1.7.0-alpha01 Compose Animation Version 1.12.1 Compose Animation Version 1.13.0-alpha03 Compose Foundation Version 1.12.1 Compose Foundation Version 1.13.0-alpha03 Compose Material Version 1.12.1 Compose Material Version 1.13.0-alpha03 Compose Material3 Version 1.5.0-alpha28 Compose Material3 Adaptive Version 1.4.0-alpha02 Compose Remote Version 1.0.0-alpha19 Compose Remote Foundation Version 1.0.0-alpha02 Compose Runtime Version 1.12.1 Compose Runtime Version 1.13.0-alpha03 Compose Ui Version 1.12.1 Compose Ui Version 1.13.0-alpha03 Core Uwb Version 1.1.0-alpha02 Credentials Providerevents Version 1.0.0-beta01 Datastore Version 1.3.0-alpha11 Emoji2 Version 1.7.0-rc01 Glance Adaptive Version 1.0.0-alpha02 Glance Wear Version 1.0.0-alpha18 Heifwriter Version 1.2.0-alpha02 Ink Version 1.1.0-alpha08 Lifecycle Version 2.12.0-alpha03 Mediarouter Version 1.9.0-alpha02 Navigation Version 2.10.1 Navigation3 Version 1.2.0-rc01 Room Version 2.8.5 Room3 Version 3.0.3 Room3 Version 3.1.0-alpha01 Savedstate Version 1.6.0-alpha03 Security Version 1.0.0 Security Version 1.1.0 Sqlite Version 2.7.1 Sqlite Version 2.8.0-alpha01 Tracing Version 2.0.2 Wear Compose Version 1.7.0-rc01 Wear Compose Remote Version 1.0.0-alpha11 Webkit Version 1.18.0-alpha01 Xr Arcore Version 1.0.0-rc01 Xr Glimmer Version 1.0.0-alpha19 Xr Projected Version 1.0.0-alpha12 Xr Runtime Version 1.0.0-rc01 Xr Runtime Version 1.1.0-alpha01 Xr Scenecore Version 1.0.0-rc01

## From Permissions to Sessions: Rethinking Location Access in Android 17

DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17](<https://devfeed.tech/articles/from-permissions-to-sessions-rethinking-location-access-in-android-17-22946.md>)

Original publisher: [Read original article](<https://proandroiddev.com/from-permissions-to-sessions-rethinking-location-access-in-android-17-5a13124b777d?source=rss----c72404660798---4>)

Author: Nav Singh

Published: 2026-09-09T01:15:51Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-permissions](<https://devfeed.tech/tags/android-permissions.md>), [android17](<https://devfeed.tech/tags/android17.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [button](<https://devfeed.tech/tags/button.md>), [compose](<https://devfeed.tech/tags/compose.md>), [consent](<https://devfeed.tech/tags/consent.md>), [feature](<https://devfeed.tech/tags/feature.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implement](<https://devfeed.tech/tags/implement.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [layout](<https://devfeed.tech/tags/layout.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [library](<https://devfeed.tech/tags/library.md>), [location](<https://devfeed.tech/tags/location.md>), [permission](<https://devfeed.tech/tags/permission.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [sessions](<https://devfeed.tech/tags/sessions.md>)

### AI overview

Android 17's system-rendered LocationButton is presented as a way to request precise location for the current session through system-managed consent. The excerpt's setup declares USE_LOCATION_BUTTON and coarse/fine location permissions, marks ACCESS_FINE_LOCATION with onlyForLocationButton, adds the androidx.core.locationbutton:locationbutton-compose library (shown as 1.0.0-alpha01), and uses its LocationButton composable to handle grant or denial callbacks. The library uses remote system rendering on Android Cinnamon Bun (API 37) and later, with a local Compose fallback on older versions or if remote rendering fails. The excerpt also shows optional styling for colors, outlines, size, and corner radii.

### 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. <!-- Standard Coarse and Fine Location Permissions + onlyForLocationButton --> <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" android:usesPermissionFlags="onlyForLocationButton"/> <!-- Required system permission for rendering the LocationButton --> <uses-permission android:name="android.permission.USE_LOCATION_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](<https://devfeed.tech/articles/from-permissions-to-sessions-rethinking-location-access-in-android-17-25982.md>)

Original publisher: [Read original article](<https://proandroiddev.com/from-permissions-to-sessions-rethinking-location-access-in-android-17-5a13124b777d?source=rss-711ab22c5c77------2>)

Author: Nav Singh

Published: 2026-09-03T18:18:32Z

Content type: tutorial

Language: en

Sources: [Nav Singh](<https://devfeed.tech/sources/stories-by-nav-singh-on-medium.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-permissions](<https://devfeed.tech/tags/android-permissions.md>), [android17](<https://devfeed.tech/tags/android17.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [compose](<https://devfeed.tech/tags/compose.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [location](<https://devfeed.tech/tags/location.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [sessions](<https://devfeed.tech/tags/sessions.md>)

### AI overview

Android 17's Jetpack Compose LocationButton lets users grant precise location for the current session through a system-handled consent flow. The excerpt says to declare USE_LOCATION_BUTTON and ACCESS_COARSE_LOCATION, and to mark ACCESS_FINE_LOCATION with onlyForLocationButton, then add the androidx.core.locationbutton:locationbutton-compose dependency (shown as version 1.0.0-alpha01) and use the LocationButton composable to handle grant or denial. On Android Cinnamon Bun (API 37) and later it uses system remote rendering; on older versions or if that fails, it falls back to local Compose rendering. The button's colors, outline, size, shape, and pressed corner radius can be customized. The excerpt presents this as reducing custom permission-flow work and making session-only access clearer, but supplies no comparison or further limitations.

### 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. <!-- Standard Coarse and Fine Location Permissions + onlyForLocationButton --> <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" android:usesPermissionFlags="onlyForLocationButton"/> <!-- Required system permission for rendering the LocationButton --> <uses-permission android:name="android.permission.USE_LOCATION_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

[Next page](<https://devfeed.tech/topics/jetpack.md?cursor=WyIyMDI2LTA5LTAzVDE4OjE4OjMyKzAwOjAwIiwgImM3NjBlYTVjLTEwY2MtNGI4YS04MGQyLTVhYzMxNzJmNmUxOCJd>)