Google Ships Agent Development Kit for Kotlin 1.0, Matching Python and Adding On-Device Android Agents

Google released version 1.0 of its Agent Development Kit for Kotlin, a production-ready framework for building AI agents that run across Kotlin, Android, and JVM server applications. The milestone brings the Kotlin implementation level with Google's existing ADK releases for Python and Java, closing a gap that had left Kotlin developers working from a partial toolkit. The release was reported by InfoQ, with Sergio De Simone covering the details.

Feature parity matters because ADK is Google's answer to a crowded field of agent frameworks, and language coverage determines which teams can adopt it without rewriting their stack. Python has carried ADK since its early releases, and Java followed; Kotlin's arrival means Android and backend Kotlin shops can now use the same abstractions, agent definitions, and tool-calling patterns as their Python counterparts. For teams already standardized on Kotlin for mobile and server work, that removes a reason to bolt on a second language just to ship an agent.

The Android-specific additions are the part that goes beyond parity. ADK for Kotlin includes support for on-device and hybrid AI, meaning an agent can execute some inference locally on the phone and defer heavier work to a remote model. That split is practical for latency, offline behavior, and privacy, since data that never leaves the handset cannot leak from a server. It also fits Google's broader push to run smaller models directly on Android hardware rather than routing every request through the cloud.

Google has been positioning ADK as the connective tissue for agents that call tools, chain steps, and hand off between models, and a 1.0 label signals the API is stable enough to build on. Reaching 1.0 in Kotlin also gives Google a stronger story against rivals courting the same developers, including LangChain and other open-source agent libraries that have leaned on Python and JavaScript. Kotlin's reach into Android gives Google a distribution channel those competitors do not control.

What to watch is how quickly the Android on-device path matures and whether Google keeps the three ADK implementations in lockstep or lets Kotlin drift. The 1.0 tag answers the stability question for now, but the harder test is adoption: whether Kotlin teams actually build agents on ADK instead of stitching together their own orchestration. Google has not detailed a roadmap for the Kotlin version beyond this release.