# Android Android is a mobile operating system and app development platform whose SDK tools compile application code into APKs or Android App Bundles. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A unified view of Android security updates for enterprises and OEMs DevFeed: [A unified view of Android security updates for enterprises and OEMs]() Original publisher: [Read original article]() Author: Joseph Yong Published: 2026-09-17T20:00:00Z Content type: release Language: en Sources: [Security]() Topics: [Security](), [Library](), [Android Security](), [Android](), [Kernel](), [Operating system](), [Zero Trust](), [App]() Tags: [android](), [android-security](), [app](), [kernel](), [library](), [none](), [os](), [security](), [updates](), [zero-trust]() ### AI overview Google is launching the Security-State and Security-State-Provider libraries to give Android Enterprise partners, OEMs, and security-sensitive apps a unified view of security updates across the operating system, system modules, and kernel. The libraries support access decisions based on installed, published, and pending fixes. ### Source excerpt Security State Library ## Introducing the AndroidX Security State Libraries: A Unified View of Device Security DevFeed: [Introducing the AndroidX Security State Libraries: A Unified View of Device Security]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-09-17T19:00:00Z Content type: release Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Android Security](), [Library](), [Android](), [version](), [Google]() Tags: [android](), [android-security](), [libraries](), [release](), [security](), [version]() ### AI overview Android announces the stable release of AndroidX Security State 1.1.0 and Security State Provider 1.0.0. The libraries let developers and enterprises inspect component-level device security, compare installed, published, and available patch levels, expose update availability, and check whether selected vulnerabilities have been patched. ### Source excerpt Posted by Maunik Shah, Staff Software Engineer, Alec Garcia, Software Engineer, and Joseph Yong, Technical Program Manager At Android, we are constantly working to provide developers and enterprise partners with the data they need to keep devices protected. Today, we're thrilled to announce the stable release of the AndroidX Security State version 1.1.0 and Security State Provider version 1.0.0 libraries which provides a centralized mechanism designed to bring further transparency to the comprehensive security posture and pending updates across the Android ecosystem. Whether you develop security-critical, consumer-facing apps (such as banking, fintech, or healthcare) or Mobile Device Management (MDM) solutions, these libraries enable you to programmatically verify the security state of the device per component. Rather than relying on a coarse, monolithic Security Patch Level (SPL), you can evaluate true component-level protection and whether remediations are actively pending via the androidx.security.state library. For OEMs and Over-The-Air (OTA) client developers, the companion androidx.security.state.provider library allows you to expose update availability via standardized mechanisms. Understanding Security Patch Levels (SPL) As Android has evolved to deliver rapid, independent component updates through modular systems like Google Play system updates, relying on a single SPL build property is no longer the best way to determine a device's true security posture. To provide component level visibility, the Security State libraries provide APIs for three distinct patch levels: Device SPL (DSPL): The security patch level currently installed and running on the device for specific system components, queried from device properties and configs without network calls. Published SPL (PSPL): The latest patch level officially published in the Android Security Bulletin for those components. Available SPL (ASPL): The patch level ready to be downloaded and installed on the specif ## Introducing the AndroidX Security State Libraries: A Unified View of Device Security DevFeed: [Introducing the AndroidX Security State Libraries: A Unified View of Device Security]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-09-17T19:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Android Security](), [Library](), [Mobile](), [Security](), [Vulnerabilities](), [Google]() Tags: [android](), [android-security](), [apis](), [cves](), [developers](), [libraries](), [ota](), [release](), [version]() ### AI overview Google announces stable releases of the AndroidX Security State and Security State Provider libraries. The libraries let Android apps, MDM solutions, OEMs, and OTA client developers inspect component-level security patch status, pending remediations, update availability, and vulnerability coverage. ### Source excerpt Posted by Maunik Shah, Staff Software Engineer, Alec Garcia, Software Engineer, and Joseph Yong, Technical Program Manager At Android, we are constantly working to provide developers and enterprise partners with the data they need to keep devices protected. Today, we're thrilled to announce the stable release of the AndroidX Security State version 1.1.0 and Security State Provider version 1.0.0 libraries which provides a centralized mechanism designed to bring further transparency to the comprehensive security posture and pending updates across the Android ecosystem. Whether you develop security-critical, consumer-facing apps (such as banking, fintech, or healthcare) or Mobile Device Management (MDM) solutions, these libraries enable you to programmatically verify the security state of the device per component. Rather than relying on a coarse, monolithic Security Patch Level (SPL), you can evaluate true component-level protection and whether remediations are actively pending via the androidx.security.state library. For OEMs and Over-The-Air (OTA) client developers, the companion androidx.security.state.provider library allows you to expose update availability via standardized mechanisms. Understanding Security Patch Levels (SPL) As Android has evolved to deliver rapid, independent component updates through modular systems like Google Play system updates, relying on a single SPL build property is no longer the best way to determine a device's true security posture. To provide component level visibility, the Security State libraries provide APIs for three distinct patch levels: Device SPL (DSPL): The security patch level currently installed and running on the device for specific system components, queried from device properties and configs without network calls. Published SPL (PSPL): The latest patch level officially published in the Android Security Bulletin for those components. Available SPL (ASPL): The patch level ready to be downloaded and installed on the specif ## Android Studio Rabbit 2 Canary 1 now available DevFeed: [Android Studio Rabbit 2 Canary 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-09-17T17:07:57Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android](), [Android Gradle Plugin](), [Command-line interface](), [Compose]() Tags: [adb](), [android](), [android-gradle-plugin](), [android-studio](), [bug](), [cli](), [compose](), [gemini](), [release](), [release-notes]() ### AI overview Android Studio Rabbit 2 Canary 1 is available in the Canary channel, with general fixes and features across Android CLI, Android Gradle Plugin, code editing, Compose Preview, Gemini, and Gradle integration. ### Source excerpt Android Studio Rabbit 2 Canary 1 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Rabbit 2, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Rabbit 2 Canary 1 and Android Gradle Plugin 9.5.0-alpha06. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android CLI Issue #528094657 android studio find-usages: a bare symbol resolves to a single declaration with no caller control, causing both over-reporting (common names) and silent under-reporting (name collisions) Issue #559567813 android-cli leaves accumulating lib-downloader_jni-*.dll files in %TEMP% on Windows Android Gradle Plugin Issue #549072996 KMP AndroidX sources are not downloaded without a separate non-KMP module Issue #560282299 The Configuration.setVisible(boolean) method has been deprecated Issue #556343682 AGP 9.3.0's new optimization { enable = true } DSL does not set isMinifyEnabled in the ApplicationVariant object Code Editor Issue #553120510 Android Studio freezes every time Compose Preview Issue #295351352 Compose device previews don't work in studio Gemini Issue #555875043 An internal error has occurred in Agent Gradle Integration Issue #558766788 AGP 9.4.0: running a single method of a JUnit4 Parameterized instrumented test from Android Studio runs 0 tests (tests_regex "\[.*\]" loses backslashes in device shell) Issue #556780790 connectedAndroidTest always fails on `adb connect host:port` devices -- device id is percent-encoded before the per-device pass/fail lookup Preview Issue ## Obfuscation Fundamentals: Applying ProGuard and R8 Protections to Android Code DevFeed: [Obfuscation Fundamentals: Applying ProGuard and R8 Protections to Android Code]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: tutorial Language: en Sources: [Dustin Summers]() Topics: [obfuscation](), [Android](), [R8](), [Code]() Tags: [android](), [meetup](), [obfuscation](), [proguard](), [r8](), [video]() ### AI overview A presentation introducing obfuscation with ProGuard and R8, focused on applying protections to Android code. It explains how to diagnose the code entering and leaving these build tools. ### Source excerpt This presentation was given at a MeetUp in DC. It corresponds to this series of blog posts, which is the first in a series to teach about Obfuscation/ProGuard/R8, and will primarily be centered around applying protections to Android Code. Tools such as R8 and ProGuard are available, but to many they are a black box that code goes into and stuff comes out. The following will demystify the black box, and teach developers how to properly diagnose the code going into and coming out of these build tools. ## Udacity Android Basics Course Alumni Experience DevFeed: [Udacity Android Basics Course Alumni Experience]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: article Language: en Sources: [Dustin Summers]() Topics: [Android]() Tags: [android](), [course](), [experience]() ### AI overview The author describes providing input on life after completing Udacity's Android Basics course and on their experience working in Android. ### Source excerpt As an alumni of the Udacity Android Basics course, they reached out for my input in life after the course and my experience working in Android. ## Modern Android Hacking DevFeed: [Modern Android Hacking]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: article Language: en Sources: [Dustin Summers]() Topics: [Hacking](), [Android]() Tags: [android](), [hacking](), [modern](), [presentation](), [summit](), [video]() ### AI overview A presentation titled "Modern Android Hacking" was given at the 2020 Android Summit, which was hosted virtually due to the pandemic. The page provides a video of the presentation. ### Source excerpt This presentation was given at the 2020 Android Summit which was hosted virtually due to the pandemic Video of Presentation: ## A Simple MVI Architecture Approach Using LiveData DevFeed: [A Simple MVI Architecture Approach Using LiveData]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: opinion Language: en Sources: [Dustin Summers]() Topics: [Android](), [Dagger]() Tags: [architecture](), [architecture-pattern](), [error](), [livedata](), [loading](), [mvi]() ### AI overview A talk from Android Summit 2019 discusses a simple implementation of the MVI architecture pattern using LiveData and the Loading, Content, Error pattern. ### Source excerpt This was a talk provided by myself and Dan Lowe at Android Summit, 2019. In this we discuss a simple approach to the MVI (Model, View, Intent) Architecture Pattern using LiveData and the common Loading, Content, Error Pattern. Link to Dan's blog post is here which is what our talk was based around. ## PolyMO is a privacy-focused virtual pet built with an ESP32 and local AI DevFeed: [PolyMO is a privacy-focused virtual pet built with an ESP32 and local AI]() Original publisher: [Read original article]() Author: Ida Torres Published: 2026-09-17T00:30:05Z Content type: article Language: en Sources: [Yanko Design]() Topics: [ESP32](), [Hardware](), [Language models](), [Whisper](), [3D](), [voice ai](), [Android](), [Bluetooth]() Tags: [diy](), [gadgets](), [gadgets-technology-diy-virtual-virtual-pet](), [technology](), [virtual](), [virtual-pet]() ### AI overview PolyMO is a virtual pet designed to discourage excessive scrolling by becoming visibly ill when ignored. It combines an ESP32 device with an Android phone running local language, speech-recognition, and text-to-speech models, keeping conversations and pet behavior on the owner's hardware. ### Source excerpt Virtual Pet That Won't Let You Waste Your Life Scrolling Most of us know the feeling. You pick up your phone to check one notification, and forty-five minutes later you're three hundred posts deep into... ## Preparing Codename One for Android 17 and API 37 Migration DevFeed: [Preparing Codename One for Android 17 and API 37 Migration]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-17T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Android](), [migration](), [Security](), [format]() Tags: [android](), [apis](), [format](), [migration](), [security]() ### AI overview Codename One prepares for Android 17 and API 37 by adding platform compatibility checks, fixing API-level parsing and build-tool handling, and testing a new system-rendered location button. The article also describes moving PEM parsing and task removal into shared security-sensitive platform handling. ### Source excerpt API 37 checks and a system location button prepare Android migration. PEM parsing and task-clearing exit put more security-sensitive platform and format handling into Codename One. ## Artec выпустила 3D-сканер Neo с точностью до 0,025 мм и возможностью использовать меньше маркеров DevFeed: [Artec выпустила 3D-сканер Neo с точностью до 0,025 мм и возможностью использовать меньше маркеров]() Original publisher: [Read original article]() Author: daniilshat Published: 2026-09-16T20:38:18Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [3D](), [NEO](), [Wi-Fi](), [Android](), [iOS]() Tags: [3d](), [3d-3e5df75aae48](), [3d-808cb8ef1ed6](), [android](), [artec](), [artec-3d](), [ios](), [neo](), [tag-232a735f81ce](), [tag-37307bce20f9](), [tag-d14eb265d33e](), [wi-fi]() ### AI overview Artec has released Neo, a wireless 3D scanner for quality control and reverse engineering. It uses structured blue light, can capture up to 8 million points per second, and supports a hybrid mode that reduces the need for markers. Neo is available for $38,600. ### Source excerpt Artec представила Neo -- беспроводной 3D-сканер для контроля качества и реверс-инжиниринга. Одна из особенностей устройства заключается в гибридном режиме, в котором оператору не нужно покрывать всю деталь маркерами для позиционирования сканера. Читать далее ## Android Bench 2.0 Adds Long-Horizon Tasks and Agentic Evaluation for Android AI Coding DevFeed: [Android Bench 2.0 Adds Long-Horizon Tasks and Agentic Evaluation for Android AI Coding]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-09-16T15:58:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Benchmark](), [AI Models](), [LLM evaluation / benchmarking](), [AI-assisted coding](), [Large Screen](), [Jetpack Compose](), [Database]() Tags: [agentic-android-development](), [agents](), [ai](), [android](), [benchmark](), [benchmarks](), [coding](), [coding-agents](), [evaluation]() ### AI overview Android Bench 2.0 introduces long-horizon Android development tasks and agentic evaluation for assessing large language models and coding agents. Its continuous scoring considers functionality, visual fidelity, regressions, instruction adherence, and structural constraints. ### Source excerpt Posted by Matthew McCullough, VP, Product Management, Android Developer When we first launched Android Bench, we built a rigorous foundation for evaluating how large language models (LLMs) assist developers with real-world Android tasks. As AI models and agents rapidly evolve, we've been updating our methodology, such as aligning our benchmark framework with the Harbor framework. Today we're releasing the first set of long-horizon tasks (LHT), which are tasks of great complexity that take an engineer multiple days or even a week to complete. We are also introducing agentic evaluation, starting with agents from corresponding model providers. This addition brings us to Android Bench 2.0--a major upgrade designed to evaluate AI models and agents against the scale, ambiguity, and complex multi-step problem solving that you tackle every day. The Android Bench 2.0 leaderboard From incremental fixes to long-horizon tasks The first iteration of Android Bench, along with similar early AI coding benchmarks, focused on incremental changes to existing repositories, in many cases limited to bug fixes or smaller feature requests. This was a reflection of the capabilities of AI assistance at the time, as well as how you were using it. To continue helping you find the models and coding agents best suited to your development workflow, we have raised the bar of our evaluations to match the work you delegate to AI. Android Bench 2.0 mirrors these ambitious challenges with LHTs that include upgrading dependencies, adding new features, building apps from scratch, or converting a cross-platform app to Android. Complex tasks require a more nuanced evaluation and scoring On multi-day engineering tasks, binary pass or fail grading doesn't capture the full picture. For example, an agent might refactor 40 screens to Jetpack Compose, set up database tables, and pass 90% of requirements, but fail a single edge-case assertion. Binary scoring rates this run as 0%, obscuring the model's architectur ## Android Bench 2.0 introduces long-horizon tasks, agentic evaluation, and continuous scoring DevFeed: [Android Bench 2.0 introduces long-horizon tasks, agentic evaluation, and continuous scoring]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-09-16T15:58:00Z Content type: release Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Android](), [Benchmark](), [AI-assisted coding](), [LLM evaluation / benchmarking](), [upgrade](), [cross-platform]() Tags: [agent](), [agentic](), [agentic-android-development](), [ai-models](), [android](), [benchmark](), [evaluation]() ### AI overview Android Bench 2.0 updates Android developer benchmarking for large language models and agents. It introduces multi-day long-horizon tasks, agentic evaluation, and continuous scoring based on functionality, visual fidelity, regressions, and other objective criteria. ### Source excerpt Posted by Matthew McCullough, VP, Product Management, Android Developer When we first launched Android Bench, we built a rigorous foundation for evaluating how large language models (LLMs) assist developers with real-world Android tasks. As AI models and agents rapidly evolve, we've been updating our methodology, such as aligning our benchmark framework with the Harbor framework. Today we're releasing the first set of long-horizon tasks (LHT), which are tasks of great complexity that take an engineer multiple days or even a week to complete. We are also introducing agentic evaluation, starting with agents from corresponding model providers. This addition brings us to Android Bench 2.0--a major upgrade designed to evaluate AI models and agents against the scale, ambiguity, and complex multi-step problem solving that you tackle every day. The Android Bench 2.0 leaderboard From incremental fixes to long-horizon tasks The first iteration of Android Bench, along with similar early AI coding benchmarks, focused on incremental changes to existing repositories, in many cases limited to bug fixes or smaller feature requests. This was a reflection of the capabilities of AI assistance at the time, as well as how you were using it. To continue helping you find the models and coding agents best suited to your development workflow, we have raised the bar of our evaluations to match the work you delegate to AI. Android Bench 2.0 mirrors these ambitious challenges with LHTs that include upgrading dependencies, adding new features, building apps from scratch, or converting a cross-platform app to Android. Complex tasks require a more nuanced evaluation and scoring On multi-day engineering tasks, binary pass or fail grading doesn't capture the full picture. For example, an agent might refactor 40 screens to Jetpack Compose, set up database tables, and pass 90% of requirements, but fail a single edge-case assertion. Binary scoring rates this run as 0%, obscuring the model's architectur ## Our Transition to React Native DevFeed: [Our Transition to React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2020-07-09T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [React Native](), [Android](), [iOS](), [Mobile](), [React]() Tags: [android](), [android-apps](), [architectures](), [backend](), [bridge](), [business-logic](), [change](), [code](), [engineering](), [ios](), [mobile](), [news](), [react-native]() ### AI overview Khan Academy describes completing its transition to React Native for its iOS and Android apps. The article explains why the team moved away from separate platform codebases and outlines the transition's exploration, straddling, and extinction phases. ### Source excerpt In 2017, Khan Academy started using React Native in our iOS and Android apps. As of this year, we've reached a big milestone: our transition to React Native is complete! Every screen in the app is rendered in React Native. ## Building a Really, Really Small Android App DevFeed: [Building a Really, Really Small Android App]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-08-22T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [APK](), [Android Studio](), [App](), [Code]() Tags: [android](), [android-studio](), [apk](), [app](), [app-size](), [build](), [engineering](), [mobile](), [news]() ### AI overview This article describes building a minimally viable Khan Academy Android app focused on video playback. The resulting APK was 26 kilobytes to download, supported older Android versions, and offered limited offline navigation. ### Source excerpt By Charlie Marsh App size is important to us. As a team striving to deliver a free, world-class ... Read more ## Migrating to a Mobile Monorepo for React Native DevFeed: [Migrating to a Mobile Monorepo for React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-05-29T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [monorepo](), [React Native](), [Mobile](), [Submodules](), [Android](), [iOS](), [pull-requests](), [Jenkins]() Tags: [also](), [android](), [engineering](), [ios](), [jenkins](), [mobile](), [monorepo](), [news](), [react-native](), [submodules]() ### AI overview Khan Academy describes moving its React Native-related iOS and Android repositories from separate repositories and submodules into a single mobile monorepo. The change was intended to reduce synchronization problems, coordinate bridge changes across platforms, make pull requests and reviews more coherent, and simplify verification between codebases. The article also outlines repository-merging steps and anticipated trade-offs. ### Source excerpt By Jared Forsyth Over the past few months, we've been adding some React Native to our existing iOS ... Read more ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## Dev snapshot: Godot 4.8 dev 6 DevFeed: [Dev snapshot: Godot 4.8 dev 6]() Original publisher: [Read original article]() Author: Thaddeus Crews Published: 2026-09-15T20:00:00Z Content type: release Language: en Sources: [Godot Engine Official]() Topics: [Godot](), [releases](), [Release notes](), [Android](), [macOS]() Tags: [android](), [crash](), [dev](), [google-play](), [macos](), [pre-release](), [release](), [release-notes]() ### AI overview Godot 4.8 development snapshot 6 addresses startup crashes on macOS and a Google Play Store upload failure from the previous snapshot. It also introduces screen-space contact shadows for directional lights and includes other improvements available for testing. ### Source excerpt Hotfix for macOS and Android ## The Thumb That Ran Ahead of the Finger: Anatomy of a Compose Slider Bug DevFeed: [The Thumb That Ran Ahead of the Finger: Anatomy of a Compose Slider Bug]() Original publisher: [Read original article]() Author: Vitaliy Gribko Published: 2026-09-14T04:19:34Z Content type: article Language: en Sources: [ProAndroidDev - Medium]() Topics: [bug](), [Compose](), [Android](), [Design system](), [Code]() Tags: [android](), [bug](), [code](), [compose](), [debugging](), [design-system](), [jetpack-compose](), [kotlin](), [qa](), [race-condition](), [ui]() ### AI overview This article examines a deterministic bug in a custom Compose slider where the thumb moves ahead of the user's finger during a drag. It traces the issue to a design-system slider forked from the AOSP Material implementation and discusses debugging and code simplification. ### Source excerpt A bug report sat in the backlog for seven months. The fix took a day, deleted a third of the slider's logic, and was almost shipped with a second bug inside -- until a machine read my diff better than I did. This is the whole story: the ported behavior that never made sense, the race nobody reported, and why the best fixes remove code. The report The bug report was seven months old when it reached me. A QA engineer had filed it in December, with a screen recording and three steps: Open the people search filters. Grab the right-hand thumb of the age range slider. Drag it slowly to the left. The recording showed the problem in two seconds. The thumb does not follow the finger. It sprints ahead -- you are still crossing the gap between two ticks, and the thumb is already standing on the next one, waiting for you, like a dog that runs to the park while you are still tying your shoes. Expected: the thumb moves with the finger. Actual: it escapes. On a budget phone, on two Android versions, every time. Not a race condition, not a flake -- a perfectly deterministic lie, filmed in December, assigned to a fix-day in July. Seven months is not negligence. It is the natural half-life of a visual glitch filed as minor against a screen nobody dies on. The age filter works. You tap a tick, the value applies. Only the drag -- the one gesture the slider exists for -- feels wrong in a way that is hard to screenshot and easy to deprioritize. When the ticket finally landed on my desk, a colleague glanced at it and asked whether it had already been fixed once. It had not. But I understood his confusion later, when I opened the slider's source and found a comment that explained everything -- including why this bug felt so old. The comment that confessed The slider is not the framework's slider. Our design system ships its own Compose slider, forked from the AOSP Material one, because design needed three knobs the framework does not expose: a custom thumb radius, a custom track height, a differ ## Android Weekly Issue #744 DevFeed: [Android Weekly Issue #744]() Original publisher: [Read original article]() Published: 2026-09-13T16:28:25Z Content type: article Language: en Sources: [Android Weekly]() Topics: [Android](), [Development](), [Compose](), [Artificial Intelligence](), [Rive animation]() Tags: [android](), [android-development](), [compose](), [developers](), [lottie](), [net-11-preview-7](), [offline-speech-recognition](), [rive](), [speech](), [tutorials]() ### AI overview Android Weekly Issue #744 is a developer digest covering Android architecture and AI, annotation-based DSL APIs, animated paywalls, offline speech recognition in keyboards, Compose dialog blurring, and structural hot reload across Android, iOS, and desktop. ### Source excerpt Articles & Tutorials Sponsored Pushwoosh launches a new Push-only plan Stop overpaying for push notifications. Get powerful push infrastructure for $7 per 1,000 MAU, with high-speed delivery, 99.9% push-to-gateway delivery, migration support, and a 24-month price lock. Calculate your savings. Android's AI Era: Hype vs. Architecture Thomas Künneth examines Android's AppFunctions architecture and agent distribution claims behind Google's "intelligent system" framing. Two Racing Lines: Annotations and the DSL in NetFlow 0.7.0 KMP Bits explains adding an annotation-based API layer atop NetFlow's DSL, keeping compile-time-checked mapping and paging support intact. Sponsored How many app issues fell off your radar this week? Mobile teams deal with a firehose of incoming issues: regressions from QA, beta feedback, Play Store reviews, crashes, etc. AI code makes managing this even harder. Triage by Runway pulls every issue into one inbox, de-dupes, assigns, and tracks fixes so nothing is missed. See how it works. Adding Rive and Lottie Animations to Android Paywalls Jaewoong Eum explains building custom Rive and Lottie animated components for RevenueCat's server-driven Android paywalls. I Put Speech Recognition Inside an Android Keyboard. Here's What Broke. Farhad Ranjbar explores the architecture challenges of building an offline speech-recognition engine inside an Android keyboard. How to blur what's behind a Compose dialog, down to API 23 Timofey Krestyanov explains blurring content behind a Compose dialog across window boundaries, down to API 23. Compose HotSwan 2.0.0: The Future of Hot Reload on Android, iOS, and Desktop Jaewoong Eum introduces Compose HotSwan 2.0's own interpreter engine, enabling structural hot reload across Android, iOS, and Desktop. Place a sponsored post Advertise to more than 80k Android developers! Advertise your Android development related service or product! We reach out to more than 80k Android developers around the world, every week, through ## 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 ## Announcing ADK for Kotlin 1.0: Building Production-Ready AI Agents in Kotlin, Android, and Beyond DevFeed: [Announcing ADK for Kotlin 1.0: Building Production-Ready AI Agents in Kotlin, Android, and Beyond]() Original publisher: [Read original article]() Author: Guillaume Laforge Published: 2026-09-12T11:04:33.891311Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [Artificial Intelligence](), [Kotlin](), [AI Development](), [Android](), [Kotlin Multiplatform](), [multiplatform](), [Orchestration](), [Google](), [Persistence](), [Agent Skill](), [LiteRT](), [Cloud]() Tags: [agent-skill](), [agents](), [ai](), [ai-agent](), [ai-agents](), [android](), [building](), [database](), [development-kit](), [firebase](), [incident](), [kotlin](), [multiplatform](), [orchestration](), [persistence](), [production]() ### AI overview Google announces the 1.0 general availability release of the Agent Development Kit (ADK) for Kotlin, a production-ready toolkit for building multi-agent applications with Kotlin, Java, and Android. Built on Kotlin Multiplatform, it provides feature parity with the ADK 1.0 Core and adds Android-first extensions for on-device agents with LiteRT-LM and ML Kit, hybrid cloud workflows through Firebase AI Logic, and state persistence with Room and AppSearch. The release also includes type-safe, compile-time function calling through KSP and declarative agent skills. ### Source excerpt Google has officially released version 1.0 of the Agent Development Kit (ADK) for Kotlin, achieving full feature parity with the Python and Java ADK cores to enable idiomatic, multi-agent AI development. Built on Kotlin Multiplatform (KMP), the framework leverages Kotlin Symbol Processing (KSP) for zero-reflection, type-safe function calling, alongside advanced orchestration capabilities like human-in-the-loop workflows and context compaction. Additionally, the release introduces a robust suite of Android-first extensions, allowing mobile developers to integrate local models via LiteRT-LM, cloud reasoning through Firebase AI, session persistence using Room, and semantic memory powered by AppSearch. ## GTK 4.24 Released With Better Fractional Scaling, More Precise GDK Frame-Clock DevFeed: [GTK 4.24 Released With Better Fractional Scaling, More Precise GDK Frame-Clock]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T10:52:32Z Content type: news Language: en Sources: [Phoronix]() Topics: [GTK](), [Wayland](), [SVG](), [Android](), [bug]() Tags: [android](), [bug-fixes](), [desktop](), [desktop-linux](), [feature](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [svg](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview GTK 4.24 is a stable feature release that improves fractional scaling, frame timing, reduced-motion behavior, SVG support, and Wayland integration. It also includes Android frame-timing improvements and many bug fixes, while session save and restore has moved to GTK 4.26. ### Source excerpt GTK 4.24 released on Friday as the newest stable feature release to the GTK4 toolkit. It's quite a nice update to GTK4 for pairing with next week's GNOME 51 desktop release... ## Setup On Device Gemma 4 Android Development on Emulator DevFeed: [Setup On Device Gemma 4 Android Development on Emulator]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-11T14:27:55Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [gemma4](), [Android](), [Emulator](), [android-development]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [artificial-intelligence](), [emulator](), [gemma](), [gemma-4](), [google](), [mobile-app-development](), [on-device]() ### AI overview A tutorial explaining how to set up and run the Gemma 4 large language model locally on an Android Emulator, including downloading and testing the Google AI Edge Gallery sample app. It notes that emulator storage and memory may affect model use. ### Source excerpt Create Android Project with Downloadable Android On Device Gemma 4 Model Continue reading on Mobile App Development Publication " [Next page]()