# Android Gradle Plugin

A Gradle plugin that adds features specific to building Android apps.

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

## Android 17 AppFunction Walkthrough First Experience

DevFeed: [Android 17 AppFunction Walkthrough First Experience](<https://devfeed.tech/articles/android-17-appfunction-walkthrough-first-experience-29454.md>)

Original publisher: [Read original article](<https://medium.com/mobile-app-development-publication/android-17-appfunction-walkthrough-first-experience-d27b261b84d1?source=rss----f9c208bdbb09---4>)

Author: Elye - A Dev By Grace

Published: 2026-09-07T12:51:23Z

Content type: tutorial

Language: en

Sources: [Mobile App Development Publication](<https://devfeed.tech/sources/mobile-app-development-publication-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [App](<https://devfeed.tech/topics/app.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Emulator](<https://devfeed.tech/topics/emulator.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [app-development](<https://devfeed.tech/tags/app-development.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [development](<https://devfeed.tech/tags/development.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

A first-hand walkthrough of Android 17 AppFunction, which lets Gemini discover an app's functionality. The article covers the required Android Studio version, Android 17 emulator, Android SDK API 37.0 target, and Android Gradle Plugin requirements.

### Source excerpt

Enabling Gemini to Find Your App Functionalities Continue reading on Mobile App Development Publication "

## Android Studio Rabbit 1 Canary 2 now available

DevFeed: [Android Studio Rabbit 1 Canary 2 now available](<https://devfeed.tech/articles/android-studio-rabbit-1-canary-2-now-available-26335.md>)

Original publisher: [Read original article](<https://androidstudio.googleblog.com/2026/08/android-studio-rabbit-1-canary-2-now.html>)

Author: Android Studio Releaser (noreply@blogger.com)

Published: 2026-08-20T13:34:55Z

Content type: release

Language: en

Sources: [Android Studio Release Updates](<https://devfeed.tech/sources/android-studio-release-updates.md>)

Topics: [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [bug](<https://devfeed.tech/topics/bug.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [bug](<https://devfeed.tech/tags/bug.md>), [compose](<https://devfeed.tech/tags/compose.md>), [json](<https://devfeed.tech/tags/json.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [preview](<https://devfeed.tech/tags/preview.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>)

### AI overview

Android Studio Rabbit 1 Canary 2 is available in the Canary channel. The release includes general fixes in Android Studio and Android Gradle Plugin 9.5.0-alpha02, including fixes related to Baseline Profiles, Lint JSON generation, Compose Preview, and connected devices.

### Source excerpt

Android Studio Rabbit 1 Canary 2 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 1, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Rabbit 1, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Rabbit 1 Canary 2 and Android Gradle Plugin 9.5.0-alpha02. 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 Baseline Profiles & ProfileInstaller Issue #543799367 Baseline profile is pulled off the device but never registered in test-result.pb, so collectBaselineProfile finds nothing and copyBaselineProfileIntoSrc deletes the committed profile Lint Issue #546124524 AGP's SarifReporter generates invalid JSON when LintFix has an ending alternative that produces no edits Preview Issue #545671285 [Compose Preview] Code/Split/Design tabs missing in Kotlin files with @Preview annotation in Android Studio Quail 3 Patch 1 Running Devices Issue #546841017 Bug: IDE has various issues with connected device, including installation and mirroring, despite all signs showing otherwise

## Android Studio Rabbit 1 Canary 1 now available

DevFeed: [Android Studio Rabbit 1 Canary 1 now available](<https://devfeed.tech/articles/android-studio-rabbit-1-canary-1-now-available-26334.md>)

Original publisher: [Read original article](<https://androidstudio.googleblog.com/2026/08/android-studio-rabbit-1-canary-1-now.html>)

Author: Android Studio Releaser (noreply@blogger.com)

Published: 2026-08-17T14:06:36Z

Content type: release

Language: en

Sources: [Android Studio Release Updates](<https://devfeed.tech/sources/android-studio-release-updates.md>)

Topics: [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [bug](<https://devfeed.tech/tags/bug.md>), [channel](<https://devfeed.tech/tags/channel.md>), [compose](<https://devfeed.tech/tags/compose.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [screenshot-testing](<https://devfeed.tech/tags/screenshot-testing.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

Android Studio Rabbit 1 Canary 1 is available in the Canary channel. The release includes general fixes for Android Studio, Android Gradle Plugin 9.5.0-alpha01, baseline profiles, Compose Preview Screenshot Testing, profilers, and other components.

### Source excerpt

Android Studio Rabbit 1 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 1, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Rabbit 1 Canary 1 and Android Gradle Plugin 9.5.0-alpha01. 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 Gradle Plugin Issue #533547933 Add a test that validate relocation does not affect task execution Baseline Profiles & ProfileInstaller Issue #543799367 Baseline profile is pulled off the device but never registered in test-result.pb, so collectBaselineProfile finds nothing and copyBaselineProfileIntoSrc deletes the committed profile Compose Preview Screenshot Testing Issue #538484834 Compose Preview Screenshot Testing (alpha15): renderer fails on all previews with IncompatibleClassChangeError: <pkg>.R and <pkg>.R$attr disagree on InnerClasses attribute Gemini Issue #540709807 S0 CRITICAL: Data Loss - AI Agent executed malformed shell command deleting drive contents Profilers Issue #347764600 TabbedToolbarTest.noCloseButtonWhenNoListener() broken

## React Native 0.87 - Strict TypeScript API, Metro Update, Swift Package Manager, AGP 9 Support

DevFeed: [React Native 0.87 - Strict TypeScript API, Metro Update, Swift Package Manager, AGP 9 Support](<https://devfeed.tech/articles/react-native-0-87-strict-typescript-api-metro-update-swift-package-manager-agp-9-support-48136.md>)

Original publisher: [Read original article](<https://reactnative.dev/blog/2026/08/11/react-native-0.87>)

Author: Zeya Peng; Fabrizio Cucci; Gabriel Donadel Dall'Agnol; Christian Falch

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

Content type: release

Language: en

Sources: [React Native Blog](<https://devfeed.tech/sources/react-native-blog.md>)

Topics: [React Native](<https://devfeed.tech/topics/react-native.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [migration](<https://devfeed.tech/topics/migration.md>), [swift-package-manager](<https://devfeed.tech/topics/swift-package-manager.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>)

Tags: [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [announcement-release](<https://devfeed.tech/tags/announcement-release.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [migration](<https://devfeed.tech/tags/migration.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [release](<https://devfeed.tech/tags/release.md>), [swift-package-manager](<https://devfeed.tech/tags/swift-package-manager.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

React Native 0.87 makes the Strict TypeScript API the default JavaScript API, updates Metro to 0.87, adds experimental Swift Package Manager support for iOS, and raises minimum toolchain requirements to Node.js 22, Android Gradle Plugin 9, and Kotlin 2.0 or newer. The release also introduces breaking changes and provides migration guidance plus a temporary opt-out for legacy TypeScript types.

### Source excerpt

Today we are excited to release React Native 0.87!

## Android Studio Quail 4 Canary 4 now available

DevFeed: [Android Studio Quail 4 Canary 4 now available](<https://devfeed.tech/articles/android-studio-quail-4-canary-4-now-available-26331.md>)

Original publisher: [Read original article](<https://androidstudio.googleblog.com/2026/08/android-studio-quail-4-canary-4-now.html>)

Author: Android Studio Releaser (noreply@blogger.com)

Published: 2026-08-06T14:55:00Z

Content type: release

Language: en

Sources: [Android Studio Release Updates](<https://devfeed.tech/sources/android-studio-release-updates.md>)

Topics: [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>)

### AI overview

Android Studio Quail 4 Canary 4 is available in the Canary channel, with general fixes in Android Studio and Android Gradle Plugin 9.4.0-alpha08.

### Source excerpt

Android Studio Quail 4 Canary 4 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 Quail 4, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Quail 4, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Quail 4 Canary 4 and Android Gradle Plugin 9.4.0-alpha08. 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 CPU Issue #157084391 tools/base/common/.../SparseArray.java has memory leak Gemini Issue #538645014 Android Studio AI grep toolCall keeps failing to execute. Issue #500338962 Shell command is not available in Sandbox of GIAS Issue #540709807 S0 CRITICAL: Data Loss - AI Agent executed malformed shell command deleting drive contents Hangouts Issue #41325047 Regression: Chrome crashes on screen sharing through hangouts Profilers Issue #183419293 Tiny fonts in the Profiler (CPU and native memory charts)

## Android Studio Quail 4 Canary 1 now available

DevFeed: [Android Studio Quail 4 Canary 1 now available](<https://devfeed.tech/articles/android-studio-quail-4-canary-1-now-available-26327.md>)

Original publisher: [Read original article](<https://androidstudio.googleblog.com/2026/07/android-studio-quail-4-canary-1-now.html>)

Author: Android Studio Releaser (noreply@blogger.com)

Published: 2026-07-16T13:28:23Z

Content type: release

Language: en

Sources: [Android Studio Release Updates](<https://devfeed.tech/sources/android-studio-release-updates.md>)

Topics: [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Emulator](<https://devfeed.tech/topics/emulator.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [macOS](<https://devfeed.tech/topics/macos.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [preview](<https://devfeed.tech/tags/preview.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>)

### AI overview

Android Studio Quail 4 Canary 1 is available in the Canary channel. The release includes general fixes and changes involving Android Studio, Android Gradle Plugin, Gradle integration, lint, navigation, and emulator-related behavior.

### Source excerpt

Android Studio Quail 4 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 Quail 4, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Quail 4 Canary 1 and Android Gradle Plugin 9.4.0-alpha05. 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 Studio Issue #533146818 ExtractAnnotations task does not share build cache entries between mac and linux Gradle Integration Issue #491718901 AGP 9.1.0 Circular dependency error between :app:l8DexDesugarLibUiTest and :app:minifyAndroidTestWithR8 Lint Issue #526716181 Disable DalvikOverride by default Issue #533527424 Lint tasks do not share build cache entries between mac and linux Navigation Editor Issue #271424916 nested navigation graph as starting destination breaks Android Studio Preview Running Devices Issue #532163938 "Hardware Input" emulator option is not persisted across Android Studio restarts

## A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage

DevFeed: [A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage](<https://devfeed.tech/articles/a-great-gradle-module-structure-30613.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2026/07/a-great-gradle-module-structure/>)

Author: Jesse Wilson

Published: 2026-07-15T13:38:11Z

Content type: article

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [build times](<https://devfeed.tech/topics/build-times.md>), [modules](<https://devfeed.tech/topics/modules.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>)

Tags: [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [build](<https://devfeed.tech/tags/build.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [modules](<https://devfeed.tech/tags/modules.md>), [test-coverage](<https://devfeed.tech/tags/test-coverage.md>)

### AI overview

The article describes a Gradle module convention that separates each feature's public API from its implementation. The author says this structure reduced build times and coupling between features while helping enforce test coverage, with Android Gradle Plugin support making a separate test-fixtures module unnecessary.

### Source excerpt

Flattening my Dependency Graph Jesse Wilson Jesse explores a Gradle module structure that he likes. Read now ➡ I liked this not-so-recent post from Jesse Wilson, which outlines a Gradle module convention that prioritizes clear public/private boundaries to support encapsulation and build speed. The approach, adapted from one presented by Ralf Wondratschek, also happens to closely resemble one that I helped institute at Dropbox shortly after I joined four and a half years ago.

## Android Studio Quail 3 Canary 1 now available

DevFeed: [Android Studio Quail 3 Canary 1 now available](<https://devfeed.tech/articles/android-studio-quail-3-canary-1-now-available-26317.md>)

Original publisher: [Read original article](<https://androidstudio.googleblog.com/2026/06/android-studio-quail-3-canary-1-now.html>)

Author: Android Studio Releaser (noreply@blogger.com)

Published: 2026-06-18T15:07:37Z

Content type: release

Language: en

Sources: [Android Studio Release Updates](<https://devfeed.tech/sources/android-studio-release-updates.md>)

Topics: [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [releases](<https://devfeed.tech/topics/releases.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [bug](<https://devfeed.tech/tags/bug.md>), [compose](<https://devfeed.tech/tags/compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [preview](<https://devfeed.tech/tags/preview.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

Android Studio Quail 3 Canary 1 is available in the Canary channel, alongside Android Gradle Plugin 9.4.0-alpha01. The release includes general fixes and features, including fixes for signing configuration, Compose editing, import and sync, Kotlin Multiplatform compilation, running devices, and Cyrillic keyboard input during device mirroring.

### Source excerpt

Android Studio Quail 3 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 Quail 3, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Quail 3 Canary 1 and Android Gradle Plugin 9.4.0-alpha01. 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 Gradle Plugin Issue #499166350 AGP SigningConfig is too eager Compose Editing Issue #522127451 Android Studio Quail Surround With Widget Option not working Import/Sync Issue #457204879 The Kotlin main() function fails to run with Android Studio Otter (works fine with Narwhal 4) Multiplatform Issue #496002555 androidMain.kotlin.exclude(...) is ignored by compileAndroidMain with com.android.kotlin.multiplatform.library Running Devices Issue #269961652 When using Device Mirroring, Cyrillic keyboard input does not work

## Declarative Gradle EAP2 - November 2024 Update

DevFeed: [Declarative Gradle EAP2 - November 2024 Update](<https://devfeed.tech/articles/declarative-gradle-eap2-november-2024-update-24608.md>)

Original publisher: [Read original article](<https://blog.gradle.org/declarative-gradle-november-2024-update>)

Author: Paul Merlin

Published: 2024-11-18T05:00:00Z

Content type: release

Language: en

Sources: [Gradle](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [ide](<https://devfeed.tech/topics/ide.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>)

Tags: [experimental](<https://devfeed.tech/tags/experimental.md>), [features](<https://devfeed.tech/tags/features.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [here](<https://devfeed.tech/tags/here.md>), [ide](<https://devfeed.tech/tags/ide.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [preview](<https://devfeed.tech/tags/preview.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

This update announces Declarative Gradle EAP2, an experimental second Early Access Preview of Gradle's declarative model. It describes the Declarative Configuration Language, Software Types, improved IDE and tooling support, starter-project generation, and direct exposure of Android Gradle Plugin models through the new AGP ecosystem plugin. The release is intended for community feedback and is not ready for production use.

### Source excerpt

Introduction A year ago, we announced a new experimental project called Declarative Gradle. That blog post presented our vision for a declarative model for Gradle. It also introduced our concept of a developer-centric software definition. This was followed by the first Early Access Preview release in July 2024, accompanied by the First Look at Declarative Gradle blog post. The first EAP introduced a configuration model called Software Types, a new Declarative Configuration Language (DCL), and demonstrated the potential for tooling improvements and better IDE support. It is now easier to try Declarative Gradle. The first EAP was based on separate Declarative Gradle prototype plugins. These prototype plugins implement Software Types wrapping existing plugins like Android Gradle Plugin (AGP) and Kotlin Multiplatform (KMP), making them usable from DCL. Since then, we've worked with the Android Studio team to expose their existing model of the Android Gradle Plugin as a Software Type directly in DCL to demonstrate Declarative Gradle on a real-world plugin with elaborate DSL. We also experimented with other IDEs and enhanced gradle init to generate starter projects that use DCL. With those efforts concluded, we are happy to announce the second EAP release! This blog post provides an update on the project's progress and outlines how you can provide feedback and influence our next steps. Declarative Gradle is still in an experimental stage and is not ready for production use. We are providing a second early access preview to gather more feedback from the community. We invite you to try out the samples and the demo applications and to share your feedback. Official Android Software Type Preview We worked with the Android Studio team to enable the Android Gradle Plugin (AGP) to expose its existing models, aka. Project extensions, directly as Software Types, to make them available in DCL. The new AGP ecosystem plugin now exposes androidApp and androidLibrary Software Types, whi

## Stop Repeating Yourself 2: Using Test Fixtures with AGP

DevFeed: [Stop Repeating Yourself 2: Using Test Fixtures with AGP](<https://devfeed.tech/articles/stop-repeating-yourself-2-using-test-fixtures-with-agp-25115.md>)

Original publisher: [Read original article](<http://michaelevans.org/blog/2024/07/29/stop-repeating-yourself-2-using-test-fixtures-with-agp/>)

Author: Michael Evans

Published: 2024-07-29T23:43:27Z

Content type: tutorial

Language: en

Sources: [Gadget Habit](<https://devfeed.tech/sources/gadget-habit.md>)

Topics: [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [build performance](<https://devfeed.tech/topics/build-performance.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [android-development](<https://devfeed.tech/tags/android-development.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [build](<https://devfeed.tech/tags/build.md>), [build-performance](<https://devfeed.tech/tags/build-performance.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

This tutorial explains how Android Gradle Plugin 8.5.0 adds native support for reusable test fixtures in modularized Android projects. It covers defining shared test utilities such as mocks, fakes, and test data, then consuming them from other modules.

### Source excerpt

Modern Android development often involves modularization to enhance build performance and maintainability. As you break down your app into multiple modules, sharing test utilities such as fixtures, mocks, or fakes between modules can become challenging. A few years ago I wrote about the concept of test fixtures, but at the time they weren't supported for Android modules. Thankfully, with Android Gradle Plugin (AGP) 8.5.0, Google introduced native support for test fixtures, streamlining this process significantly. What Are Test Fixtures? Test fixtures are reusable components such as test data, helper classes, or mocks that you can use to support your tests. Prior to AGP 8.5.0, sharing these utilities across modules often required workarounds like creating dedicated "test" modules or manually wiring dependencies. With AGP 8.5.0, the testFixtures feature makes it easier to declare and consume test fixtures directly from your modules. Setting Up Test Fixtures To enable test fixtures for a module, you need to include the testFixtures feature in your module's build.gradle.kts file. Here's how you can set it up: 1 2 3 4 5 6 7 8 9 android { // Enable test fixtures for the module testFixtures.enable = true } dependencies { // Declare dependencies for your test fixtures testFixturesImplementation("com.example:some-library:1.0.0") } The testFixtures source set is automatically created under the src directory: 1 2 3 4 5 6 7 8 9 module-name/ src/ main/ java/ testFixtures/ java/ kotlin/ test/ java/ You can now place reusable test utilities, such as mock data generators or fake implementations, inside the testFixtures directory. Consuming Test Fixtures Modules can consume test fixtures by declaring a dependency on the testFixtures configuration of another module. For example, if module-b needs to use the test fixtures from module-a, add the following dependency: 1 2 3 dependencies { testImplementation(testFixtures(project(":module-a"))) } Once this dependency is added, the test co

## Get current flavor in Android Gradle

DevFeed: [Get current flavor in Android Gradle](<https://devfeed.tech/articles/get-current-flavor-in-android-gradle-25847.md>)

Original publisher: [Read original article](<https://medium.com/@banmarkovic/get-current-flavor-in-android-gradle-6d23d27259e3?source=rss-8aced922ece------2>)

Author: Ban Markovic

Published: 2023-08-07T12:20:20Z

Content type: tutorial

Language: en

Sources: [Ban Markovic](<https://devfeed.tech/sources/stories-by-ban-markovic-on-medium.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Groovy](<https://devfeed.tech/topics/groovy.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [flavors](<https://devfeed.tech/tags/flavors.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [groovy](<https://devfeed.tech/tags/groovy.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

The article's approach reads `gradle.startParameter.taskRequests` and extracts the flavor from a task name matching `assemble<Flavor><Debug|Release>` or `bundle<Flavor><Debug|Release>`. Its Kotlin DSL and Groovy versions choose the `assemble` pattern when the task request text contains `assemble`, otherwise the `bundle` pattern; both lowercase the captured flavor and return an empty string after printing `NO FLAVOR FOUND` if no match is found. The supplied text presents this as a way to conditionally include or exclude plugins or libraries based on the selected flavor.

### Source excerpt

Gradle is a topic that most Android developers postpone to learn as much as they can. This happens until we realize that it is a crucial part when it comes to packaging our apps or SDKs (here is my article that can help you out with understanding Gradle better). Since the diversity of Android devices is huge, we always need to strive not to package unnecessary things. Product flavors Sometimes it is required from us to publish different versions of our app, depending on the different requirements of our clients. This leads us to having one codebase that can support multiple configuration changes (enabling or disabling particular features) depending on our clients. To avoid changing our code each time we want to publish a different version of our app, we use product flavors. They enable us to set up different app variants at project level, and then we can reference them in our code, in order to enable or disable something. Problem Enabling or disabling particular features inside our Kotlin code is not that complex, but in order to follow those toggles, sometimes we would also like to include or exclude some plugins or libraries. Since this type of work is done in Gradle, there is a need for us to know which product flavor is selected in our Gradle file. Solution Writing Gradle scripts can be done with Kotlin DSL or Groovy, and since we already know Kotlin, I will focus on explaining the Kotlin DSL solution and later on I will also provide the full Groovy version of our getCurrentFlavor function. By using Kotlin DSL in our Gradle scripts, we can add any function at the bottom of our app/build.gradle.kts file, so let's create our getCurrentFlavor() function that returns an empty String. fun getCurrentFlavor(): String { return "" } Since we are inside our build.gradle.kts file, we have a reference to a Gradle object that belongs to our project. Inside it, we have the information of the parameters that the Gradle object uses for starting the build. By having that informa

## The Importance of Validating the Gradle Wrapper

DevFeed: [The Importance of Validating the Gradle Wrapper](<https://devfeed.tech/articles/the-importance-of-validating-the-gradle-wrapper-27434.md>)

Original publisher: [Read original article](<https://jdvp.me/articles/Gradle-Wrapper-Validation>)

Author: JD Porterfield (jd.porterfield@alumni.rice.edu)

Published: 2022-04-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [JD Porterfield | Articles](<https://devfeed.tech/sources/jd-porterfield-articles.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Batch file](<https://devfeed.tech/topics/batch-file.md>), [Shell](<https://devfeed.tech/topics/shell.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [apk](<https://devfeed.tech/tags/apk.md>), [article](<https://devfeed.tech/tags/article.md>), [batch](<https://devfeed.tech/tags/batch.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [shell](<https://devfeed.tech/tags/shell.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

This tutorial explains how the Gradle Wrapper standardizes Gradle versions across Android projects and CI/CD environments, then focuses on validating wrapper files to reduce the risk of malicious tooling attacks.

### Source excerpt

Protecting your projects from malicious gradle wrappers can be straight-forward, find out how in this article!

## Fairly evaluating the impact of different Android UI libraries on Gradle build

DevFeed: [Fairly evaluating the impact of different Android UI libraries on Gradle build](<https://devfeed.tech/articles/fairly-evaluating-the-impact-of-different-android-ui-libraries-on-gradle-build-25905.md>)

Original publisher: [Read original article](<https://chao2zhang.medium.com/fairly-evaluating-the-impact-of-different-android-ui-libraries-on-gradle-build-6301de5e0e60?source=rss-d19045640fe------2>)

Author: Chao Zhang

Published: 2021-11-09T16:24:37Z

Content type: article

Language: en

Sources: [Chao Zhang](<https://devfeed.tech/sources/stories-by-chao-zhang-on-medium.md>)

Topics: [build times](<https://devfeed.tech/topics/build-times.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [application](<https://devfeed.tech/tags/application.md>), [build](<https://devfeed.tech/tags/build.md>), [choice](<https://devfeed.tech/tags/choice.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [compose](<https://devfeed.tech/tags/compose.md>), [control](<https://devfeed.tech/tags/control.md>), [data](<https://devfeed.tech/tags/data.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [developer](<https://devfeed.tech/tags/developer.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [ergonomics](<https://devfeed.tech/tags/ergonomics.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [impact](<https://devfeed.tech/tags/impact.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

The excerpt proposes controlling for project and tooling differences when comparing Jetpack Compose, Data Binding, View Binding, and plain Views' effects on Gradle builds. It treats UI library choice as the independent variable and build measures such as clean and incremental build time and task timelines as outcomes. To keep comparisons fair, it recommends holding machine specifications, Gradle and Android Gradle Plugin versions, module dependencies, and UI appearance constant. Since production migrations often span commits alongside dependency and module changes, the article suggests using Android Studio poet to generate synthetic projects with configurable tooling, module structure, and code complexity. The excerpt provides setup rationale but no comparative build results.

### Source excerpt

Photo: Tsvetoslav Hristov from Unsplash For an Android application maintained by a large group of developers, build time is one of the most critical developer ergonomic metrics. This is particularly true when we evaluate to adopt new technology. Jetpack Compose is the new exciting modern UI library to build Android applications. Its official documentation already covers developer ergonomics on two of their sample applications. Although the comparison narrated in Jetpack Compose: Before and after were valuable, we would like to apply scientific control to our experiments, in order to fairly evaluate Compose against the existing UI layer technologies, such as Data Binding and View Binding. Fairness In a scientific experiment study, we use variables to test our hypothesis. There are basically three groups of variables: Independent variable as the input of our evaluation. Since we are evaluating the different Android UI libraries in this study, the particular type of UI library becomes our independent variable. Namely, Jetpack Compose, Data Binding, View Binding, and plain View. Dependent variable as the output of our evaluation. We would like to see how the choice of UI library impacts Gradle build, so the dependent variable could be any metric from our Gradle build. For instance, clean build time, incremental build time, and the timeline of the task execution. Control variable as the constants in our evaluation. We want to ensure the comparison to be performed with the same context. This means we need to ensure the same machine spec, same Gradle version, same Android Gradle Plugin version, same module dependencies, and same UI appearance. However, for large-scale applications, we are very unlikely to complete the full UI layer migration with a single atomic commit. Oftentimes, we are doing migrations over multiple commits spread over a time span, mixed with other commits to upgrading dependencies and altering module structures. With multiple commits, we become less co

## Herding Elephants

DevFeed: [Herding Elephants](<https://devfeed.tech/articles/herding-elephants-15673.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/herding-elephants>)

Author: Tony Robalik

Published: 2021-11-04T11:00:00Z

Content type: article

Language: en

Sources: [Square Corner](<https://devfeed.tech/sources/square-corner-blog-medium.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [gradle-plugin](<https://devfeed.tech/topics/gradle-plugin.md>), [composite-build](<https://devfeed.tech/topics/composite-build.md>), [experience report](<https://devfeed.tech/topics/experience-report.md>), [Code Modularity](<https://devfeed.tech/topics/code-modularity.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Android Library](<https://devfeed.tech/topics/android-library.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-library](<https://devfeed.tech/tags/android-library.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [applications](<https://devfeed.tech/tags/applications.md>), [apps](<https://devfeed.tech/tags/apps.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [ast](<https://devfeed.tech/tags/ast.md>), [bash](<https://devfeed.tech/tags/bash.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [block](<https://devfeed.tech/tags/block.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [build](<https://devfeed.tech/tags/build.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [module](<https://devfeed.tech/tags/module.md>), [project](<https://devfeed.tech/tags/project.md>)

### AI overview

Square's MDXA team reorganized build logic across a 3,500-plus-module Gradle repository around convention plugins that encode the company's module model. Module scripts were reduced to concise plugin, dependency, and optional configuration declarations; common settings moved into tested plugins. The team added unit and Gradle TestKit integration tests, including a Gradle and Android Gradle Plugin version matrix. Moving logic from buildSrc to an included build avoided buildSrc's per-build checks and broad configuration invalidation, but plugin resolution from the included build added about 30 seconds (roughly 33%) to configuration. Publishing binary plugins to Artifactory removed that regression for feature engineers, while retaining the included build for rapid prototyping. The migration also used an AST-based tool to rewrite scripts. The article reports lower script complexity, reduced memory pressure, and faster builds, while acknowledging that complexity was relocated into a separate, tested build domain.

### Source excerpt

Wrangling a 3,500-module Gradle project

## A Bit of Gradle Housekeeping

DevFeed: [A Bit of Gradle Housekeeping](<https://devfeed.tech/articles/a-bit-of-gradle-housekeeping-27046.md>)

Original publisher: [Read original article](<https://zsmb.co/a-bit-of-gradle-housekeeping/>)

Author: Márton Braun

Published: 2021-09-01T20:00:00Z

Content type: tutorial

Language: en

Sources: [zsmb.co](<https://devfeed.tech/sources/zsmb-co.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [build](<https://devfeed.tech/tags/build.md>), [build-tools](<https://devfeed.tech/tags/build-tools.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [groovy](<https://devfeed.tech/tags/groovy.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [marton-braun](<https://devfeed.tech/tags/marton-braun.md>), [properties](<https://devfeed.tech/tags/properties.md>), [zsmb](<https://devfeed.tech/tags/zsmb.md>), [zsmb-co](<https://devfeed.tech/tags/zsmb-co.md>), [zsmb13](<https://devfeed.tech/tags/zsmb13.md>), [zsmbco](<https://devfeed.tech/tags/zsmbco.md>)

### AI overview

This tutorial explains how to simplify Android Gradle project configuration by removing obsolete build-tool, Java, and Kotlin JVM target settings and replacing deprecated SDK version properties. It also discusses keeping project source-set configuration simple.

### Source excerpt

While cleaning is traditionally a spring activity, let me invite you to do it at the end of summer this time around. In this article, we'll take a look at some Gradle configuration that you can probably clean up in your Android project.

## Pick lint version

DevFeed: [Pick lint version](<https://devfeed.tech/articles/pick-lint-version-26134.md>)

Original publisher: [Read original article](<https://vadzimv.dev/2021/07/28/calculate-lint-version.html>)

Author: Vadzimv Dev Blog

Published: 2021-07-28T15:00:00Z

Content type: tutorial

Language: en

Sources: [Vadzimv Dev](<https://devfeed.tech/sources/vadzimv-dev-blog.md>)

Topics: [lint](<https://devfeed.tech/topics/lint.md>), [version](<https://devfeed.tech/topics/version.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automation](<https://devfeed.tech/tags/automation.md>), [code](<https://devfeed.tech/tags/code.md>), [custom](<https://devfeed.tech/tags/custom.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [google](<https://devfeed.tech/tags/google.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [lint](<https://devfeed.tech/tags/lint.md>), [project](<https://devfeed.tech/tags/project.md>), [properties](<https://devfeed.tech/tags/properties.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

For a custom Android lint rule, the excerpt says the lint dependency version must match the Android Gradle Plugin (AGP) version using the stated convention: add 23 to AGP's major version while keeping the remaining version parts (for example, AGP 4.2.2 gives lint 27.2.2). To avoid recalculating manually after AGP updates, it proposes storing the AGP version in the root project's `ext` properties, parsing it in the lint project, adding 23 to the major version, and using the calculated value in dependencies. The excerpt does not show the code or explain compatibility beyond this convention.

### Source excerpt

How to pick lint dependency version when you implement a custom lint rule for Android project.

## Targeting Android in a Kotlin/Multiplatform Mobile library

DevFeed: [Targeting Android in a Kotlin/Multiplatform Mobile library](<https://devfeed.tech/articles/targeting-android-in-a-kotlin-multiplatform-mobile-library-22866.md>)

Original publisher: [Read original article](<https://medium.com/kodein-koders/targeting-android-in-a-kotlin-multiplatform-mobile-library-b6ab75469287?source=rss----f311f45ef54---4>)

Author: Salomon BRYS

Published: 2021-04-26T14:32:30Z

Content type: tutorial

Language: en

Sources: [Kodein Koders](<https://devfeed.tech/sources/kodein-koders-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Android Library](<https://devfeed.tech/topics/android-library.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Library](<https://devfeed.tech/topics/library.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [build](<https://devfeed.tech/tags/build.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-multiplatform-mobile](<https://devfeed.tech/tags/kotlin-multiplatform-mobile.md>), [library](<https://devfeed.tech/tags/library.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [plugin](<https://devfeed.tech/tags/plugin.md>)

### AI overview

This tutorial explains how to target Android APIs from a Kotlin Multiplatform Mobile library. It advises developers to distinguish Android APIs from JVM APIs, then outlines an official approach using the Android Gradle plugin and Kotlin's Android target, as well as a lighter but more restrictive alternative. The official approach publishes an AAR instead of a JAR and supports Android resources such as images, XML files, and JNI native libraries.

### Source excerpt

https://medium.com/media/6c54678f49c79a047a73b582f72c478e/href So far, we've seen how to create a Kotlin/Multiplatform Mobile library, how to access iOS Swift APIs in it, and how to push it to Maven Central. We haven't discussed how to access Android APIs. Kotlin is the main Android programming language, so how difficult can it be ? Well, it turns out that the Android platform is not as simple as the JVM, so there are multiple strategies you can use to access Android APIs in your KMM libraries. Let's discuss them! First and foremost, you need to make sure that you actually need an Android API, and not a JVM API. You should not have your library target Android if the API you want to access is actually provided by the JVM. Most of the file access, date time, cryptography, and many more APIs are JVM APIs, and even if your library is supposed to be used especially on mobile targets, it is way simpler to target the JVM rather than adding the entire Android toolchain to your build. OK, so you're positive you need Android APIs? The way I see it, there are two ways you can add the Android APIs to the classpath of your library: There's the official way, which enables all Android capabilities to your library. There's the lighter way, a hack, really, which is more restrictive, but a lot simpler, which we'll discuss at the end of this video. The official way consists in adding the Android Gradle plugin to your build, as well as its corresponding Kotlin target & Android configuration. https://medium.com/media/b40d2cd887b34d8002fb3861463fd19b/href Adding the com.android.library plugins and defining an Android target, rather than a regular JVM target, has a notable effect: what will be published is an AAR (for Android ARchive) rather than a JAR (for Jvm ARchive). This means that the library can package Android resources, such as images, XMLs, or JNI native libraries. As you can see, most of the Android configuration is not happening in the kotlin block, but in the android block. T

## How to break your Android App with proguard / R8

DevFeed: [How to break your Android App with proguard / R8](<https://devfeed.tech/articles/how-to-break-your-android-app-with-proguard-r8-24744.md>)

Original publisher: [Read original article](<https://medium.com/yazio-engineering/how-to-break-your-android-app-with-proguard-r8-6566bc387b63?source=rss----65bd178b00af---4>)

Author: Paul Woitaschek

Published: 2021-03-02T15:19:22Z

Content type: article

Language: en

Sources: [YAZIO](<https://devfeed.tech/sources/yazio-engineering-medium.md>)

Topics: [R8](<https://devfeed.tech/topics/r8.md>), [proguard](<https://devfeed.tech/topics/proguard.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [app](<https://devfeed.tech/tags/app.md>), [proguard](<https://devfeed.tech/tags/proguard.md>), [r8](<https://devfeed.tech/tags/r8.md>)

### AI overview

A broad R8/ProGuard rule, `-assumenosideeffects class android.util.Log { public *; }`, can affect inherited public methods as well as logging calls. The article reports that this includes synchronization methods on `Object`, such as `notify`, potentially breaking app synchronization and causing hangs. It recommends avoiding `*` wildcards with `-assumenosideeffects` and specifying the logging signatures explicitly (`v`, `d`, `i`, `w`, `e`, and `println`) when removing production log calls. The author also warns that the issue can enter an app through a library's consumer ProGuard rules.

### Source excerpt

I recently updated the android gradle plugin to 4.0.0. While developing, everything went smoothly and at some point I was ready to cut a release. The very last manual testing of the release app bundle was also fine so no Proguard / R8 issues on the first sight either. Then I thought: Let me check the CI results again. Everything was fine, but: The instrumentation tests. Almost all of them were timing out. After inspecting the logs, they all hang at the end of the on-boarding. Strangely the loading spinner was loading for way longer than the timeout should be. So I tested it on my phone and faced the same results. At that time I had no idea it was caused by updating AGP, so I did a 2 hours long git bisect. Okay, now lets create a minimal self reproducible bug report because I found a huge bug in AGP, everyone should know about immediately. I created a Hello World project that was making a single network call and printed it results into a TextView. Strangely here it did not reproduce. After experimenting with the OkHttp configuration and testing if it was related to some gradle plugin, I finally had the idea that it might be related to R8. So I added my proguard configuration and now the network call hang! Let's locate the issue further. I was step by step removing lines from my proguard configuration until only a single line was left: -assumenosideeffects class android.util.Log { public * ; } Now what is this? How is that even slightly related to anything? It should remove the log spam of some third party libraries we're using. So I was asking Mads Ager. (he works on D8/R8) you have to be very careful with -assumenosideeffects The problem is that in order for -assumenosideeffects to have the effect of actually removing calls, it matches up the class hierarchy. Therefore, this rule says that anything public in android.util.Log and its superclasses has no side-effects. That include the synchronization methods defined on Object. So, please don't use * wildcards in conne

## Migrating old artifacts from JCenter to MavenCentral

DevFeed: [Migrating old artifacts from JCenter to MavenCentral](<https://devfeed.tech/articles/migrating-old-artifacts-from-jcenter-to-mavencentral-25563.md>)

Original publisher: [Read original article](<https://www.marcogomiero.com/posts/2021/move-libray-jcenter-to-maven/>)

Author: Marco Gomiero

Published: 2021-02-11T00:00:00Z

Content type: tutorial

Language: en

Sources: [Posts on Marco Gomiero](<https://devfeed.tech/sources/posts-on-marco-gomiero.md>)

Topics: [Library](<https://devfeed.tech/topics/library.md>), [Jfrog](<https://devfeed.tech/topics/jfrog.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [article](<https://devfeed.tech/tags/article.md>), [download](<https://devfeed.tech/tags/download.md>), [files](<https://devfeed.tech/tags/files.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [jfrog](<https://devfeed.tech/tags/jfrog.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [signing](<https://devfeed.tech/tags/signing.md>), [sonatype](<https://devfeed.tech/tags/sonatype.md>)

### AI overview

This tutorial explains how to manually migrate existing Android library artifacts from JCenter to Maven Central after JCenter's shutdown. It covers downloading artifacts from Bintray, signing the AAR, POM, JAR, and signature files, and uploading them through Sonatype without recompiling the library.

### Source excerpt

As you may have heard, JCenter is shutting down in May 2021. Into the Sunset on May 1st: Bintray, JCenter, GoCenter, and ChartCenter https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So, if you are using JCenter as the repository for your libraries (as me), it's time to migrate. In this article, I will not go through the publishing process of a library to MavenCentral, because there are already plenty of resources available. For example, I followed the one written by Márton Braun.

## Presenting data efficiently in emails

DevFeed: [Presenting data efficiently in emails](<https://devfeed.tech/articles/presenting-data-efficiently-in-emails-25908.md>)

Original publisher: [Read original article](<https://chao2zhang.medium.com/presenting-data-efficiently-in-emails-f27cb5f9119e?source=rss-d19045640fe------2>)

Author: Chao Zhang

Published: 2021-01-29T01:25:52Z

Content type: article

Language: en

Sources: [Chao Zhang](<https://devfeed.tech/sources/stories-by-chao-zhang-on-medium.md>)

Topics: [email](<https://devfeed.tech/topics/email.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [apk](<https://devfeed.tech/tags/apk.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [company](<https://devfeed.tech/tags/company.md>), [compare](<https://devfeed.tech/tags/compare.md>), [data](<https://devfeed.tech/tags/data.md>), [data-visualization](<https://devfeed.tech/tags/data-visualization.md>), [easier](<https://devfeed.tech/tags/easier.md>), [efficiently](<https://devfeed.tech/tags/efficiently.md>), [email](<https://devfeed.tech/tags/email.md>), [executive](<https://devfeed.tech/tags/executive.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [gradle-plugin](<https://devfeed.tech/tags/gradle-plugin.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [leadership-team](<https://devfeed.tech/tags/leadership-team.md>), [less](<https://devfeed.tech/tags/less.md>), [numbers](<https://devfeed.tech/tags/numbers.md>), [reading](<https://devfeed.tech/tags/reading.md>)

### AI overview

For an email report, Chao Zhang recommends replacing prose-heavy results with less text and larger, more prominent numbers to make key findings easier to scan. The example describes an Android Gradle Plugin upgrade from 4.0 to 4.1, with CI build time reduced by 50% at the 50th percentile and 32% at the 90th percentile, and APK size reduced by 17%. Zhang says the more visual version drew positive reactions from readers across company levels. The excerpt does not show the redesigned report itself.

### Source excerpt

A simple trick to write an email report for your readers Image by Hermann Traub from Pixabay Recently my team wrote an email report to the leadership team on the executive summary of Android Gradle Plugin upgrades. Below is the initial version of the reports in the exec summary section: - We have migrated to Android Gradle Plugin from 4.0 to 4.1. -We have observed a reduction in CI build by 50% at 50th percentile and 32% at 90th percentile. - Our APK size is also reduced by -17% The above looks pretty ordinary. But let's compare it to the following: Less text, larger numbers, much easier for readers to get interested in reading them 🎉 Testimony: I have received more than 5 "wow"s from readers across the company hierarchy for the bottom version. The inspiration is actually from the COVID-19 dashboard of where I live. I came to realize how often it is used in public versus how rare it is used in company emails.

## Switching AspectJ Plugins in Android

DevFeed: [Switching AspectJ Plugins in Android](<https://devfeed.tech/articles/switching-aspectj-plugins-in-android-27437.md>)

Original publisher: [Read original article](<https://jdvp.me/articles/Switching-AspectJ-Plugins-Android>)

Author: JD Porterfield (jd.porterfield@alumni.rice.edu)

Published: 2021-01-18T00:00:00Z

Content type: article

Language: en

Sources: [JD Porterfield | Articles](<https://devfeed.tech/sources/jd-porterfield-articles.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [aspect-oriented-programming](<https://devfeed.tech/tags/aspect-oriented-programming.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [switching](<https://devfeed.tech/tags/switching.md>)

### AI overview

This article explains why the author replaced the android-gradle-aspectj plugin while updating an Android sample project. Frequent breakage across Android Gradle Plugin releases and recurring regressions made the plugin difficult to maintain. The author evaluates alternative AspectJ plugins and focuses on compatibility through the shared aspectjrt library.

### Source excerpt

The previous AOP Plugins I have used in Android have had various issues with maintainability. Discover why I switched and which plugin I switched to

## Android library development - Modularization

DevFeed: [Android library development - Modularization](<https://devfeed.tech/articles/android-library-development-modularization-28691.md>)

Original publisher: [Read original article](<https://jeroenmols.com/blog/2020/11/04/library-modularization/>)

Author: info@jeroenmols.com (Jeroen Mols)

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

Content type: tutorial

Language: en

Sources: [Jeroen Mols](<https://devfeed.tech/sources/jeroen-mols.md>)

Topics: [Android Library](<https://devfeed.tech/topics/android-library.md>), [Library](<https://devfeed.tech/topics/library.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-jetpack](<https://devfeed.tech/tags/android-jetpack.md>), [android-library](<https://devfeed.tech/tags/android-library.md>), [blogs](<https://devfeed.tech/tags/blogs.md>), [development](<https://devfeed.tech/tags/development.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [library](<https://devfeed.tech/tags/library.md>), [maven](<https://devfeed.tech/tags/maven.md>), [modularization](<https://devfeed.tech/tags/modularization.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

This article explains modularization challenges in Android libraries and SDKs, including missing submodule dependencies and unintended exposure of submodule APIs. It presents three approaches: publishing submodules to Maven, bundling them into a fat AAR, or creating a single-module SDK.

### Source excerpt

With modularization being all the hype, should you also modularize an SDK? Are fat aar files really needed? And how do you prevent internal APIs from being exposed on your public interface?

## It's Time to Upgrade to the New Firebase Crashlytics SDK!

DevFeed: [It's Time to Upgrade to the New Firebase Crashlytics SDK!](<https://devfeed.tech/articles/it-s-time-to-upgrade-to-the-new-firebase-crashlytics-sdk-16363.md>)

Original publisher: [Read original article](<https://firebase.blog/posts/2020/10/its-time-to-upgrade-to-new-firebase>)

Author: Oleg Kodysh

Published: 2020-10-22T00:00:00Z

Content type: release

Language: en

Sources: [Firebase Blog](<https://devfeed.tech/sources/firebase-blog.md>)

Topics: [Crashlytics](<https://devfeed.tech/topics/crashlytics.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [tvOS](<https://devfeed.tech/topics/tvos.md>), [watchOS](<https://devfeed.tech/topics/watchos.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [build](<https://devfeed.tech/tags/build.md>), [crashlytics](<https://devfeed.tech/tags/crashlytics.md>), [fabric](<https://devfeed.tech/tags/fabric.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [ios](<https://devfeed.tech/tags/ios.md>), [macos](<https://devfeed.tech/tags/macos.md>), [news](<https://devfeed.tech/tags/news.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [updates](<https://devfeed.tech/tags/updates.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [watchos](<https://devfeed.tech/tags/watchos.md>)

### AI overview

Firebase encourages developers to migrate from the deprecated Fabric SDK to the Firebase Crashlytics SDK before the legacy SDK is sunset. The article describes crash-reporting, build-plugin, symbol-upload, and multi-platform improvements.

### Source excerpt

News, tutorials, and updates from the Firebase team.

## Smaller APKs with resource optimization

DevFeed: [Smaller APKs with resource optimization](<https://devfeed.tech/articles/smaller-apks-with-resource-optimization-20973.md>)

Original publisher: [Read original article](<https://jakewharton.com/smaller-apks-with-resource-optimization/>)

Published: 2020-09-01T00:00:00Z

Content type: tutorial

Language: en

Sources: [Jake Wharton](<https://devfeed.tech/sources/jake-wharton.md>)

Topics: [Optimization](<https://devfeed.tech/topics/optimization.md>), [APK](<https://devfeed.tech/topics/apk.md>), [Android Gradle Plugin](<https://devfeed.tech/topics/android-gradle-plugin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-apk](<https://devfeed.tech/tags/android-apk.md>), [android-gradle-plugin](<https://devfeed.tech/tags/android-gradle-plugin.md>), [apk](<https://devfeed.tech/tags/apk.md>), [build](<https://devfeed.tech/tags/build.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

This article explains how resource names and paths are stored multiple times in an Android APK and shows how Android Gradle Plugin 4.2 resource optimization can reduce APK size. It uses a minimal Gradle-built app and APK inspection to compare the effects.

### Source excerpt

How many times does the name of a layout file appear in an Android APK? We can build a minimal APK with a single layout file to count the occurrences empirically. Building an Android app with Gradle requires only one thing: an AndroidManifest.xml file with a package. From there we can add a dummy layout whose contents are just <merge/> since we only care about its name. . ├── build.gradle └── src └── main ├── AndroidManifest.xml └── res └── layout └── home_view.xml Running gradle assembleRelease will produce a release APK measuring a paltry 2,118 bytes. We can dump its contents using xxd and look for home_view byte sequences. $ xxd build/outputs/apk/release/app-release-unsigned.apk ⋮ 000004c0: 0000 0074 0000 0018 0000 0072 6573 2f6c ...t.......res/l 000004d0: 6179 6f75 742f 686f 6d65 5f76 6965 772e ayout/home_view. 000004e0: 786d 6c63 66e0 6028 6160 6060 6490 61d0 xmlcf.`(a```d.a. ⋮ 00000570: 0000 0000 0000 0000 1818 7265 732f 6c61 ..........res/la 00000580: 796f 7574 2f68 6f6d 655f 7669 6577 2e78 yout/home_view.x 00000590: 6d6c 0000 0002 2001 f801 0000 7f00 0000 ml.... ......... ⋮ 00000700: 0000 0000 0909 686f 6d65 5f76 6965 7700 ......home_view. 00000710: 0202 1000 1400 0000 0100 0000 0100 0000 ................ ⋮ 00000870: 0000 ad04 0000 7265 732f 6c61 796f 7574 ......res/layout 00000880: 2f68 6f6d 655f 7669 6577 2e78 6d6c 504b /home_view.xmlPK ⋮ There are three uncompressed occurrences of the path and one uncompressed occurrence of only the name in the APK based on this output. If you have not read my post on calculating zip entry size or are not familiar with the structure of a zip file, a zip file is a list of file entries followed by a directory of all available entries. Each entry contains the file path and so does the directory. This accounts for the first occurrence (the entry header) and the last occurrence (the directory record) in the output. The middle two occurrences in the output are from inside the resources.arsc file which is a database of sorts for

[Next page](<https://devfeed.tech/topics/android-gradle-plugin.md?cursor=WyIyMDIwLTA5LTAxVDAwOjAwOjAwKzAwOjAwIiwgImY5MTU0OGNlLWYxN2ItNGNjYi05NDUxLWU0OTY1OTkxZDZhZCJd>)