androkit

A reusable Android developer toolkit for Rust — the presentation-free plumbing that project-aware Android CLIs share.

androkit was extracted from dab so that tools like adev and dab don't each reimplement ADB wrangling, APK parsing, and Gradle project discovery.

• adev (crates.io) — a project-aware Android developer CLI that walks into any repo and knows its test, install, launch, and clean commands.
• dab (crates.io) — an Android device/ADB CLI for installing, inspecting, and managing apps and devices.

Building a tool on androkit? Open a PR to add it here.

The library never prints, colors, or prompts. Every function returns data ([serde]-serializable structs or plain values) or a Result; the calling CLI owns all rendering and interaction.

use androkit::project;

let project = project::discover(std::path::Path::new("."))?;
println!("app id: {:?}", project.application_id);
println!("variants: {:?}", project.variants.iter().map(|v| &v.name).collect::<Vec<_>>());

if let Some(variant) = &project.default_variant {
    println!("install task: {}", project.install_task(variant));     // installDevDebug
    println!("test task:    {}", project.unit_test_task(variant));   // testDevDebugUnitTest
}
# Ok::<(), anyhow::Error>(())

project::discover parses settings.gradle[.kts] and each module's build.gradle[.kts] statically (no JVM warmup) so the inner loop stays fast. It handles the conventional Groovy and Kotlin DSL shapes. Known limitations, surfaced rather than hidden:

• Build types debug and release are always assumed to exist.
• Product-flavor applicationId overrides/suffixes are not applied to the base id.
• Deeply dynamic Gradle (variables, buildSrc conventions) may need the gradle::Gradle::tasks introspection fallback.

• Rust 1.74+
• adb on PATH for the adb module; aapt/aapt2 for full APK metadata.

MIT