# 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. ## 16 September 2026 Artifact Wave DevFeed: [16 September 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-16T19:33:36Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [Jetpack]() Tags: [2026](), [blog](), [jetpack](), [sdk](), [september-2026]() ### 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! ## The Android Startup Pattern: A Lifecycle-Aware, Multi-Module Approach DevFeed: [The Android Startup Pattern: A Lifecycle-Aware, Multi-Module Approach]() Original publisher: [Read original article]() Author: Ehab Elwan Published: 2026-09-13T05:31:09Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Android](), [modules](), [Jetpack](), [Framework]() Tags: [android](), [android-development](), [app-startup](), [architecture](), [framework](), [jetpack](), [kotlin](), [mobile-architecture](), [module](), [privacy](), [software-architecture]() ### AI overview This tutorial presents a lifecycle-aware, dependency-injection-driven startup pattern for modular Android applications. It contrasts a centralized startup anti-pattern with Jetpack App Startup and discusses process lifecycles, testability, and delaying tracking SDK initialization until privacy consent is evaluated. ### Source excerpt A Clean, DI-Driven Architecture for Managing Cold Starts, Background Wakeups, and Privacy Compliance in Modern Android Apps Image generated by AIDisclosure: This article was drafted by me and refined with the help of AI tools. Every growing Android project eventually spawns a two-headed "God Class." On one side, your Application class becomes a dumping ground for global infrastructure--third-party SDKs, crash reporters, and tracking tools. On the other side, your main entry point (typically the MainViewModel) gets choked with UI-blocking startup logic. It usually looks something like this: The Anti-Pattern: The Two-Headed God Class class MyApplication : Application() { override fun onCreate() { super.onCreate() // The framework dumping ground CrashReportingSDK.getInstance().setCollectionEnabled(true) HeavyUiSDK.initialize(context = this, ...) AnalyticsSDK.initialize(this, "API_KEY") // ... 50 more lines of spaghetti } }class MainViewModel : ViewModel() { init { // The UI-blocking dumping ground updateRemoteConfigs() checkUserSessionToken() processPendingDeepLinks() prefetchHomeFeedData() // ... UI cannot render until this finishes } } Splitting initialization across these two files creates major problems: It breaks the Single Responsibility Principle: The app's entry points are forced to orchestrate the inner workings of every single feature, tightly coupling your modules. It ignores process lifecycles: Application tasks run indiscriminately on every silent background wakeup, while MainViewModel tasks fail to re-trigger when the app returns to the foreground. It destroys testability: Hardcoding SDK initializations directly into your entry points makes it incredibly difficult to write isolated unit tests without complicated mocking setups. It complicates privacy compliance: A centralized dumping ground makes it extremely difficult to dynamically suspend tracking SDKs until user consent under global privacy regulations (such as GDPR, CCPA, and CPRA) is explicitly grant ## 9 September 2026 Artifact Wave DevFeed: [9 September 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-09T20:32:28Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [Jetpack](), [iOS]() Tags: [2026](), [blog](), [ios](), [jetpack](), [sdk](), [september-2026]() ### 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]() Original publisher: [Read original article]() Published: 2026-09-09T17:00:00Z Content type: release Language: en Sources: [AndroidX Release Notes]() Topics: [Jetpack](), [releases](), [Release notes](), [Compose](), [Library]() Tags: [benchmark](), [compose](), [jetpack](), [latest-release](), [libraries](), [lifecycle](), [navigation](), [release-notes](), [room](), [security](), [sqlite](), [tracing](), [ui]() ### 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 ## 26 August 2026 Artifact Wave DevFeed: [26 August 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-26T20:14:49Z Content type: news Language: en Sources: [The CommonsBlog]() Topics: [Jetpack]() Tags: [2026](), [blog](), [jetpack](), [sdk]() ### AI overview This weekly update reports two new Jetpack artifact groups and nearly 750 new artifact versions. The artifact group names and individual artifact details are not included in the supplied text. ### Source excerpt Here is what we got as new Jetpack artifacts this week! ## Jetpack XR SDK core libraries reach beta: The next milestone for Android XR DevFeed: [Jetpack XR SDK core libraries reach beta: The next milestone for Android XR]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-18T17:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Jetpack XR SDK](), [Android XR](), [Jetpack](), [Compose](), [releases]() Tags: [android-xr](), [beta-announcement](), [compose](), [jetpack](), [jetpack-xr-sdk](), [preview](), [releases](), [sdk]() ### AI overview Google announces that Jetpack SceneCore, ARCore for Jetpack XR, and XR Runtime have reached beta as part of the Jetpack XR SDK. The release stabilizes APIs for Android XR development, while Jetpack Compose for XR is expected to reach beta soon. ### Source excerpt Posted by Amy Zeppenfeld, Developer Relations Engineer, Greg Underwood, Software Engineering Manager, Yasmine Evjen, Senior Product Manager, Android XR Since introducing the Android XR SDK, developers have transformed their ideas into innovative, immersive experiences for XR headsets and wired XR glasses. As the ecosystem expands, you can more easily take those experiences from preview to production and reach users wherever they are. Today, we're excited to announce that Jetpack SceneCore, ARCore for Jetpack XR, and XR Runtime have reached beta with Jetpack Compose for XR to follow soon! This means the APIs are stabilizing, making it a great time to start integrating them into your production workflows and creating for Android XR. Why the Jetpack XR SDK? The Jetpack XR SDK includes all the tools and libraries you need to build immersive and augmented experiences for Android XR. Whether you're porting an existing 2D app or creating a new 3D XR app from scratch, you can do so using the familiar Android development tools you already know and love. To support your development, this release focuses on providing the fundamental building blocks across the SDK: Jetpack SceneCore: Build and manipulate the Android XR scene graph with 3D content. You can arrange 3D models, play spatial audio, and use the robust entity-component system to create, control, and manage entities. ARCore for Jetpack XR: Bring digital content into the real world with perception capabilities. This library powers depth estimation, persistent anchors, hit testing, and plane identification. XR Runtime: Provides the essential runtime foundation of the SDK, handling device lifecycles, session creation, and system configurations that enable the API surface. Jetpack Compose for XR: Create spatial UI layouts that take advantage of Android XR's spatial capabilities. This library lets you use familiar Compose concepts to create spatial UIs and will be reaching Beta soon. What's new in Beta? Direct feedback from ## 12 August 2026 Artifact Wave DevFeed: [12 August 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-12T23:48:49Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [Jetpack](), [Compose]() Tags: [2026](), [blog](), [compose](), [jetpack](), [sdk]() ### AI overview This week's Jetpack artifact wave added more than 900 artifact versions, including stable versions of Compose, but no new artifact groups or artifacts. ### Source excerpt Here is what we got as new Jetpack artifacts this week! ## 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 ## 29 July 2026 Artifact Wave DevFeed: [29 July 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-29T20:04:22Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [Jetpack]() Tags: [blog](), [jetpack](), [sdk]() ### AI overview The post announces new Jetpack artifacts for the week. ### Source excerpt Here is what we got as new Jetpack artifacts this week! ## AppFunctions, revisited DevFeed: [AppFunctions, revisited]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2026-07-25T11:36:27Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [Jetpack](), [Android](), [Library](), [implementation](), [Maven]() Tags: [ai](), [android](), [androiddev](), [article](), [code](), [coding](), [community](), [development](), [engineering](), [implementation](), [inclusive](), [jetpack](), [library](), [maven](), [programming](), [software](), [update]() ### AI overview This tutorial revisits Android Jetpack AppFunctions after alpha10 stopped publishing appfunctions-service. It explains the new service entry-point model, generated subclasses and XML, manual service declaration, the removal of AppFunctionContext, and a correction about using installed-app display names instead of package names. ### Source excerpt In Agentic interaction using AppFunctions I showed how Be nice publishes createAppPair for agents, using Jetpack appfunctions 1.0.0-alpha08. That setup leaned on a library-merged PlatformAppFunctionService, an AppFunctionContext parameter, and aggregate XML named app_functions.xml / app_functions_v2.xml. When I bumped toward what Android Studio was suggesting as of mid July, Sync failed: Could not find androidx.appfunctions:appfunctions-service:1.0.0-alpha10. On 1 July 2026, alpha10 stopped publishing appfunctions-service (Maven still lists it through alpha09). The Add the AppFunctions API guide now expects you to host an @AppFunctionServiceEntryPoint AppFunctionService. Spoiler: that is the real change. The rest of this post is how that landed in Be nice, plus an important update to the earlier article that is easy to miss if you only chase compile errors. Correction first In the earlier post I wrote that agents would pass package names for app1 and app2. That was wrong for Be nice. The implementation matches display names, case-insensitively, against installed apps. Package names are a convenient engineer habit; they are a poor agent habit when the user said "Clock" and "Contacts". KDoc and app-level metadata have to say what the code accepts -- agents lean on that text harder than on your mental model of the APK. What changed in the model Before alpha10 you annotated a helper class and let the service AAR merge a stock entry point into the manifest. Starting with alpha10: @AppFunction lives in androidx.appfunctions (not androidx.appfunctions.service) It is only legal on methods of an abstract AppFunctionService marked @AppFunctionServiceEntryPoint KSP generates the concrete subclass named in serviceName and the XML named in appFunctionXmlFileName You declare that generated service yourself; nothing merges a stock one anymore There is no AppFunctionContext parameter; the service is a Context Drop appfunctions:aggregateAppFunctions. Grepping for empty app_functions. ## 22 July 2026 Artifact Wave DevFeed: [22 July 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-22T23:08:52Z Content type: news Language: en Sources: [The CommonsBlog]() Topics: [Jetpack]() Tags: [2026](), [blog](), [jetpack](), [sdk]() ### AI overview A weekly update about new Jetpack artifacts released on 22 July 2026. ### Source excerpt Here is what we got as new Jetpack artifacts this week! ## 15 July 2026 Artifact Wave DevFeed: [15 July 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-15T21:39:38Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [Jetpack](), [multiplatform]() Tags: [2026](), [blog](), [jetpack](), [material3](), [multiplatform](), [release](), [sdk](), [updates]() ### AI overview This release update covers five newly observed Jetpack artifacts, including Material3 Ripple receiving multiplatform support, alongside nearly 200 artifact updates overall. ### Source excerpt Here is what we got as new Jetpack artifacts this week! ## Google I/O 2026: The Sessions Worth Your Time DevFeed: [Google I/O 2026: The Sessions Worth Your Time]() Original publisher: [Read original article]() Author: blundell Published: 2026-06-02T17:22:00Z Content type: opinion Language: en Sources: [Blundell]() Topics: [Google](), [Artificial Intelligence](), [Android](), [Model Context Protocol](), [Jetpack](), [App]() Tags: [2026](), [agent](), [agentic](), [ai](), [android](), [androiddev](), [antigravity](), [generative-ui](), [google](), [google-i-o](), [google-io](), [intermediate](), [jetpack](), [mcp](), [reference](), [reference-androiddev-google-io]() ### AI overview An opinionated guide to the Google I/O 2026 sessions most relevant to developers. It highlights Gemini updates, agent transaction protocols, generative UI in Google Search, and Android App Functions, which are presented as being in preview and enabling assistants to call app capabilities. ### Source excerpt Like every year, I binge-watched I/O. And like every year I came out the other side with more links than time. A fire-hose of announcements, most of which you'll never touch, a handful of which will change how you work next week. Here I filter for you. Links to the sessions are inline so you [...] The post Google I/O 2026: The Sessions Worth Your Time first appeared on Blundell. ## The Future of Android Apps with AppFunctions DevFeed: [The Future of Android Apps with AppFunctions]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2026-03-30T04:30:00Z Content type: article Language: en Sources: [Shreyas Patil's Blog]() Topics: [Android](), [AI Agent](), [Jetpack](), [SDKs]() Tags: [agentic-ai](), [ai](), [ai-agent](), [ai-agents](), [aidl](), [android](), [android-app-development](), [android-apps](), [app-development](), [gemini](), [jetpack](), [kotlin](), [sdk]() ### AI overview This article explains Android AppFunctions, which let apps expose self-describing data and functionality that AI agents and assistants can discover and execute using natural language. It discusses their optional nature, current device availability, Gemini access, and integration through the Android 16 SDK or Jetpack library. ### Source excerpt Explore the potential of Android AppFunctions for AI agents. Learn how apps can share functionality with intelligent assistants using self-describing functions. ## Jetpack's evolution, ecosystem complexity, and a curated Android development stack DevFeed: [Jetpack's evolution, ecosystem complexity, and a curated Android development stack]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2026-03-08T11:36:03Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [Jetpack](), [Android](), [android-development](), [Library](), [Architecture & Design](), [migration]() Tags: [android](), [android-architecture](), [android-development](), [architecture-components](), [coding](), [community](), [compatibility](), [dependency](), [deprecated](), [development](), [ecosystem](), [engineering](), [inclusive](), [jetpack](), [jetpackcompose](), [kmp](), [kotlin](), [library](), [migration](), [software]() ### AI overview This article traces Jetpack's evolution from Android Architecture Components and the Support Library to Jetpack and the androidx namespace. It argues that Jetpack's growth to more than 130 artifacts, along with deprecated libraries and multiple solutions for common tasks, has created an ecosystem that developers need to navigate using a curated recommended stack. ### Source excerpt If you are an Android developer, you know Jetpack. It changed how we build Android apps. But that was long ago. Today, the ecosystem is shifting again. We aren't just building for one platform anymore. We are building for the world. Let me show you how to take the Jetpack libraries you know and use them to fuel a new generation of applications that run everywhere. From Jetpack to a unified architecture First, let's ground ourselves. What exactly is Jetpack? It's more than just a bag of libraries. It is Google's opinionated answer to Android development. It unbundled features from the OS, so we could update our apps without waiting for Android system updates. It gave us backward compatibility. Most importantly, it gave us guidance. It stopped the wild west of Android development and brought us a standard way to build. Before Jetpack, we lived in an era of fragmentation. New features were tied to the OS. If you wanted the latest UI on an older phone, you were out of luck. Eventually, Google introduced the Support Library to fix this. It sort of worked, but it was a mess. We had v4 support, v7 appcompat, v13... it was dependency hell. We needed a reboot. That reboot came in two steps. In 2017, Google announced Android Architecture Components at I/O--ViewModel, Room, Lifecycle, LiveData--and they went 1.0 stable that November. That was the how to architect piece. Then, at I/O 2018, came Jetpack: the umbrella name and the migration to androidx.*. Eventually, everything moved to the new namespace. Libraries were strictly unbundled--own versions, own cycles, semantic versioning so we could reason about compatibility. So: Architecture Components in 2017, Jetpack and androidx in 2018. Today, we have solved one problem but created another: The Jetpack Jungle. There are now over 130 artifacts in the suite. We have historical baggage. Deprecated libraries still sit next to modern ones--for example lifecycle-extensions, which Google deprecated and replaced with separate lifecycle-ru ## Android development updates include Android XR SDK Developer Preview 3 and new tools for AI glasses DevFeed: [Android development updates include Android XR SDK Developer Preview 3 and new tools for AI glasses]() Original publisher: [Read original article]() Author: Daniel Galpin Published: 2025-12-19T23:33:51Z Content type: article Language: en Sources: [Android Developers - Medium]() Topics: [Android XR](), [android-development](), [Android Studio](), [Jetpack](), [Compose](), [OpenXR](), [Godot](), [Unreal Engine]() Tags: [android-development](), [android-studio](), [android-xr](), [featured](), [jetpack](), [jetpack-compose](), [now-in-android](), [openxr](), [release](), [unreal](), [unreal-engine]() ### AI overview This edition of Now in Android reviews Android development updates, with emphasis on Android XR SDK Developer Preview 3 and tools for AI glasses. It covers Jetpack libraries, ARCore geospatial capabilities, adaptive field-of-view APIs, Android Studio emulator support, and OpenXR integrations for Unreal Engine and Godot. ### Source excerpt Android XR, Android Studio Otter 2 feature drop; Android 16 QPR2, compose updates, Jetpack Navigation 3, performance and much, much, much more. Welcome to Now in Android, your ongoing guide to what's new and notable in the world of Android development. You can catch a short subset of what's in this gigantified update on YouTube, but read on for the full story. https://medium.com/media/406ea21381b605792c1cb5f40715bc89/href Start building for glasses, new devices for Android XR and more in The Android Show | XR Edition 👓 The Android Show | XR Edition introduced updates to the Android XR platform, focusing on new devices and developer tools. The platform is expanding to include lightweight AI and Display AI glasses from Samsung, Gentle Monster, and Warby Parker, integrating Gemini for features like live translation and visual search. Uber is exploring AI Glasses for contextual directions. Wired XR glasses, such as XREAL's Project Aura, are scheduled for release next year. Android XR SDK Developer Preview 3 offers increased stability for headset APIs and opens development for AI Glasses. This includes new libraries like Jetpack Compose Glimmer for transparent display UI and Jetpack Projected for extending your mobile apps to glasses. ARCore for Jetpack XR gains Geospatial capabilities, and new APIs enable detection of device field-of-view for adaptive UIs. The platform, built on OpenXR, supports Unreal Engine development with a Google vendor plugin for hand tracking coming next year, and Godot Engine now includes Android XR support via its OpenXR vendor plugin v4.2.2 stable. Start building for glasses, new devices for Android XR and more in The Android Show | XR Edition Check out #TheAndroidShow in 60 seconds for a quick video overview of what we covered. Build for AI Glasses with the Android XR SDK Developer Preview 3 and unlock new features for immersive experiences 🚀 Android XR SDK Developer Preview 3 is now available, enabling you to build augmented experiences for ## Inside Jetpack ViewModel: Internal Mechanisms and Multiplatform Design DevFeed: [Inside Jetpack ViewModel: Internal Mechanisms and Multiplatform Design]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2025-12-07T02:29:08Z Content type: tutorial Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Jetpack](), [Android](), [android-development](), [Mobile]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [caching](), [change](), [coroutines](), [interface](), [jetpack](), [jetpack-compose](), [key-value-store](), [kotlin-multiplatform](), [lifecycle](), [multiplatform](), [viewmodel]() ### AI overview A technical tutorial explaining Jetpack ViewModel's internal mechanisms, including retention across configuration changes, ViewModelStore key-value caching, ViewModelProvider creation, factory-based instantiation, resource cleanup, and coroutine integration. ### Source excerpt Unsplash@davidvig Jetpack's ViewModel has become an essential component of modern Android development, providing a lifecycle-aware container for UI-related data that survives configuration changes. While the API appears simple on the surface, the internal machinery reveals design decisions around lifecycle management, multiplatform abstraction, resource cleanup, and thread-safe caching. Understanding how ViewModel works under the hood helps you make better architectural decisions and avoid subtle bugs. In this article, you'll dive deep into how Jetpack ViewModel works internally, exploring how the ViewModelStore retains instances across configuration changes, how ViewModelProvider orchestrates creation and caching, how the factory pattern enables flexible instantiation, how CreationExtras enables stateless factories, how resource cleanup is managed through the Closeable pattern, and how viewModelScope integrates coroutines with the ViewModel lifecycle. The fundamental problem: Surviving configuration changes Configuration changes present a fundamental challenge for Android development. When a user rotates their device, changes language settings, or triggers any configuration change, the system destroys and recreates the Activity. Any data stored in the Activity is lost: https://medium.com/media/82ee86f042e31a1ede3f551f919b4429/href The naive approach is to use onSaveInstanceState(): https://medium.com/media/74f2c1da669e831b1488b3f297d55997/href This works for small, serializable data. But what about large datasets, network connections, or objects that can't be serialized? What about ongoing operations like network requests? The Bundle approach fails for these cases, both because of size limitations and because serialization/deserialization is expensive. ViewModel solves this by providing a lifecycle-aware container that survives configuration changes through a retained object pattern, not serialization. The ViewModelStore: The retention mechanism At the heart of Vie ## Now in Android #116 DevFeed: [Now in Android #116]() Original publisher: [Read original article]() Author: Meghan Mehta Published: 2025-05-09T15:58:03Z Content type: article Language: en Sources: [Android Developers - Medium]() Topics: [now-in-android](), [Compose](), [android-development](), [Jetpack](), [Google](), [Google AI]() Tags: [android](), [android-16](), [bug-fixes](), [compose](), [featured](), [google](), [google-ai](), [google-io-2025](), [google-play](), [jetpack](), [jetpack-compose](), [now-in-android](), [release](), [upgrade]() ### AI overview Now in Android #116 covers the Google I/O program, Jetpack Compose 1.8, the redesigned Play Console app dashboard, new Android Vitals metrics, the Testing at Scale series, Android 16 Beta 4, and recent AndroidX updates. ### Source excerpt Google IO program lineup, Jetpack Compose 1.8, Play Console insights Android Vitals Metrics, Testing at Scale blog series and AndroidX! Welcome to Now in Android, your ongoing guide to what's new and notable in the world of Android development. In this edition, we'll cover the Google IO program lineup, what's new in Jetpack Compose 1.8, the redesigned Play Console app dashboard, new Android Vitals Metrics, the launch of the Testing at Scale blog series, and the latest in AndroidX. https://medium.com/media/f791874912c70580592d3dc0ac12e0fa/hrefhttps://medium.com/media/514683104227eecfef6dcedea0d6ddb4/href Most of the content of this post is available in the form of a video or podcast, so feel free to watch or listen rather than read on. (Or do all three to help you remember! There won't be a quiz.) Articles 📚Get ready for Google I/O: Program lineup revealed 🗓 The Google I/O agenda is now available, and you can register to explore sessions on AI, Android, Web, and Cloud, taking place May 20-21. The Google Keynote will be on May 20th at 10:00 AM PT, with the Developer Keynote at 1:30 PM PT. You can join online for livestreams May 20-21, with on-demand sessions and codelabs on May 22. Sessions will cover AI advancements using Gemini models, building apps for multiple devices using Google AI, and new features for web development. Get ready for Google I/O: Program lineup revealed What's new in the Jetpack Compose April '25 release 🚀 Jetpack Compose 1.8 is out with new features, API updates, and bug fixes. You can upgrade your Compose BOM version to 2025.04.01 to use the new release. Here are some of the key updates: You can now integrate Autofill functionality into your Compose applications. The new autoSize parameter lets the text size adapt to the container size The onLayoutRectChanged modifier solves many use cases that the existing onGloballyPositioned modifier does; however, it does so with much less overhead. LookaheadScope is stable and includes numerous performanc ## Simplify ViewBinding in Android with ViewBindingPropertyDelegate 2.0 DevFeed: [Simplify ViewBinding in Android with ViewBindingPropertyDelegate 2.0]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2025-02-04T13:30:45Z Content type: release Language: en Sources: [Stories by Kirill Rozov on Medium]() Topics: [Android](), [Library](), [Jetpack](), [Refactoring](), [Memory Leaks](), [recyclerview]() Tags: [android](), [android-jetpack](), [fragments](), [jetpack](), [library](), [memory-leaks](), [open-source](), [performance](), [recyclerview](), [refactoring](), [release](), [ui](), [view-binding]() ### AI overview This article announces ViewBindingPropertyDelegate 2.0, a release that refactors how the Android library manages ViewBinding lifecycles. It replaces Jetpack Lifecycle-based detection with component lifecycle callbacks for Fragments and Activities, improving the timing of reference clearing and addressing issues related to Fragment animations. The release also supports lazy ViewBinding creation and aims to prevent memory leaks. ### Source excerpt I'm excited to announce the release of ViewBindingPropertyDelegate 2.0, which introduces significant under-the-hood refactoring to enhance the library's stability and performance. In this article, I'll highlight the most important changes and explain how they improve the library's functionality. Brief Introduction ViewBindingPropertyDelegate(VBPD) is a lightweight library designed to simplify the use of Android's ViewBinding by: Managing the ViewBinding lifecycle and clearing references to prevent memory leaks. Eliminating the need to maintain nullable references to Views or ViewBindings. Creating ViewBindings lazily. The library supports usage in various components, including Activities, Fragments, ViewGroups, and RecyclerView.ViewHolders. class ProfileFragment : Fragment(R.layout.profile) { private val profileBinding: ProfileBinding by viewBinding(ProfileBinding::bind) override fun onViewCreated(view: View, savedInstanceState: Bundle?) { super.onViewCreated(view, savedInstanceState) // ProfileBinding instance will be created lazily on first access profileBinding.name.text = ... } override fun onDestroyView() { super.onDestroyView() // profileBinding reference will be cleared after onDestroyView() } }Changes in 2.0Transition from Lifecycle to Component Callbacks In previous versions (1.x), VBPD relied on Jetpack's Lifecycle to detect when a View was being destroyed. This approach had a limitation: the Lifecycle callback methods could be invoked before Fragment.onDestroyView(), while the ViewBinding reference was still needed. To address this, VBPD postponed clearing the ViewBinding reference using an Android Handler after onDestroyView(), when the Fragment's View LifecycleOwner transitioned to the DESTROYED state. In version 2.0, VBPD now utilizes FragmentManager.FragmentLifecycleCallbacks to detect when a Fragment's view is destroyed. The key difference lies in the timing of these callbacks, allowing for more precise management of the ViewBinding lifecycle. // Sou ## Why are we so afraid of code as a commodity? DevFeed: [Why are we so afraid of code as a commodity?]() Original publisher: [Read original article]() Author: Kris Rasmussen Published: 2024-06-26T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Artificial Intelligence](), [Generative AI](), [Figma](), [Code](), [Programming](), [React](), [TypeScript](), [Kotlin](), [Jetpack](), [Complex Systems]() Tags: [ai](), [code](), [figma](), [frameworks](), [generative-ai](), [jetpack](), [kotlin](), [programming](), [react](), [software](), [systems](), [typescript]() ### AI overview The article argues that AI-assisted development may automate code translation and parts of the design-to-code workflow, but engineering remains more than producing code. Engineers continue to add value by identifying the right problems, reasoning from first principles, designing abstractions, and creating elegant, maintainable systems that address user needs. Framework-specific expertise may decline in relative value, while broader engineering judgment remains difficult to commoditize. ### Source excerpt Instead of asking how AI will automate our jobs, we should be focusing on what we, as engineers, uniquely do well. What problems can AI currently solve, and where is the whitespace to go beyond that? ## Google announces expanded Kotlin Multiplatform support and adoption at Google I/O 2024 DevFeed: [Google announces expanded Kotlin Multiplatform support and adoption at Google I/O 2024]() Original publisher: [Read original article]() Published: 2024-05-14T00:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Kotlin](), [Android](), [Google](), [cross-platform](), [kotlin-multiplatform-libraries](), [Jetpack](), [Library]() Tags: [android](), [cross-platform](), [developer-experience](), [google](), [google-i-o](), [kmp](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [skie](), [tooling]() ### AI overview The article discusses Google I/O 2024 announcements about Kotlin Multiplatform. It highlights Android support, recommendations to share business logic, KMP support in Jetpack libraries, Google Docs' use of KMP, and Google's mention of SKIE. ### Source excerpt Big News from Google I/O! Android is officially supporting Kotlin Multiplatform. The announcement includes a shout out to SKIE, first-class tooling and library support, and official recommendations for using KMP. ## Android Jetpack ViewModel has KMP Support! - Kevin Schildhorn DevFeed: [Android Jetpack ViewModel has KMP Support! - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2024-03-22T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [Kotlin Multiplatform](), [Jetpack](), [Library](), [version](), [Jetpack Compose](), [Coroutines]() Tags: [android](), [android-jetpack](), [coroutines](), [ios](), [jetpack](), [jetpack-compose](), [kmp](), [kotlin-multiplatform](), [library](), [version](), [viewmodel]() ### AI overview The lifecycle-viewmodel artifact, part of Android Jetpack, adds Kotlin Multiplatform support in version 2.8.0-alpha03. ViewModel and related classes can be used from common code, with guidance on adding the dependency and handling possible duplicate-class conflicts with Jetpack Compose. ### Source excerpt This article discusses the newest version of the lifecycle-viewmodel artifact, part of the official Android Jetpack library, and how it adds support for KMP projects. ## What's new in Android 14 for developers DevFeed: [What's new in Android 14 for developers]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2023-10-04T18:06:41Z Content type: article Language: en Sources: [Stories by Kirill Rozov on Medium]() Topics: [Android](), [navigation](), [Jetpack](), [Library]() Tags: [android](), [android-14](), [android-app-development](), [androiddev](), [deprecated](), [developers](), [jetpack](), [navigation](), [new-features](), [permissions](), [pixel8](), [sdk](), [vulnerabilities]() ### AI overview This article reviews Android 14 changes affecting application developers, including background execution and foreground service restrictions, Intent and BroadcastReceiver changes, Predictive Back Gesture animations, and restrictions on installing applications targeting SDK versions below 23. ### Source excerpt Android 14 is already here, so I took the documentation, experts' reviews, and other available resources to sort out all the important changes that will affect most application developers. Let's examine new restrictions on background mode, changes in Foreground Service, new restrictions on the work of Intent and BroadcastReceiver. In this release, we have many restrictions, but we've also got new features. Thanks for Mishaal Rahman for his articles about Android 14. I based the articles on them.Predictive Back Gesture in actionDemonstration of animation of using back navigation. Source Already in Android 13, we were warned that in the next version of Android, we should expect updates of the Back Gesture and Predictive Back Gesture with animation in the form of a preview screen where we will move. Animation for that preview is still not working. If you want it to work, you should activate it in the developer's settings. Demonstration of animation of using back navigation An example of your personal animation when doing the Back gesture Also, the ability to create personal transition animations inside the application was added. For that, a method handleOnBackProgressed() was added in OnBackPressedCallback. This method is called with the progress of the Back Gesture, as well as the handleOnBackPressed() and handleOnBackCancelled() methods, which are called at the end of the Back Gesture's animation and its cancellation, respectively. On the screen, you can see an example of implementing your custom animation using the Jetpack AppCompat 1.8.0 library. class MainActivity : AppCompatActivity() { override fun onCreate(savedInstanceState: Bundle?) { ... val box = findViewById(R.id.box) val screenWidth = Resources.getSystem().displayMetrics.widthPixels val maxXShift = (screenWidth / 20) val callback = object : OnBackPressedCallback( enabled = true ) { override fun handleOnBackProgressed( backEvent: BackEvent ) { when (backEvent.swipeEdge) { BackEvent.EDGE_LEFT -> box.t ## A script to compare two Macrobenchmarks runs DevFeed: [A script to compare two Macrobenchmarks runs]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2023-09-07T16:36:32Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Android](), [Jetpack](), [Script](), [Kotlin]() Tags: [android](), [article](), [benchmark](), [developers](), [download](), [improvements](), [install](), [jetpack](), [kotlin](), [performance](), [run](), [script]() ### AI overview This article presents a Kotlin script for comparing the results of two Jetpack Macrobenchmark runs. It builds on a methodology using normalized distributions and confidence intervals, and explains how to install, download, make executable, and run the script. ### Source excerpt In Statistically Rigorous Android Macrobenchmarks, I laid out a methodology for rigorously comparing the outcome of two Jetpack Macrobenchmark runs. To summarize the article: Remove sources of variations until the distribution fits a normal distribu... [Next page]()