Answers from the ADK Community Call: Strategy, Roadmap & Future Plans (Part 1)

[Shubhamsaboo]

Hello ADK users!

As a followup to our very first ADK community call on October 15th, we're releasing the answers to your great questions in a 6-part series. This first post covers our high-level strategy and roadmap.

We're including all questions, even those we're still working on, in the spirit of transparency.

Q: What is the ADK team's current strategy and roadmap?

A: Join the adk-community group to access details of the roadmap in the deck and a recording of the session.

Q: When is the ADK 2.0 release expected, and are there plans for time travel features?

A: We have no timeline for 2.0 at this time as we're continuing to focus on building the core features and improving the developer experience of ADK.

Regarding time travel: this has now just been introduced in ADK 1.17.0, which adds the ability to rewind a session to before a previous invocation (9dce06f). If you're looking for more ways to use time travel in your agents, please continue to create issues to help us drive prioritization.

Q: When will a MemoryStore-based session service be released as part of the official ADK?

A: We're working on the details for this and will share more when available.

Q: Are there plans to add Datastore/Firestore support to the SessionService?

A: This is a popular request! We're actively looking into it and will post updates as we have them.

Q: Will ADK add native retry mechanisms for model and tool invocations, especially for multi-agent workflows?

A: We agree this is a key area for robust agents. We're discussing the best way to implement this and will share updates. In the meantime, you can use the sample code and patterns shown in the ReflectAndRetryToolPlugin, which provides self-healing, concurrent-safe error recovery for tool failures.

Q: Are there plans for a native, integrated front-end for ADK for demos?

A: With protocols and app frameworks like AG-UI and Copilotkit now supporting ADK, you can create custom front-ends that can powered by agents built with ADK. We think this makes for the best of both worlds for now - enabling users to create their own custom front end apps, while we continue to refine and introduce more advanced features for ADK.

Q: We had many questions on language support (Kotlin, Go, Typescript).

A: Please stay tuned for more information on the release of new languages!

Q: How is the development of the ADK for Java progressing compared to the Python version?

A: We know many of you are waiting for this. We'll provide a more detailed comparison as soon as we can. In the meantime, let us know if there's a feature you'd like to see or contribute to in ADK Java!

We'll be back on Monday, Nov 3rd with Part 2, covering context caching and agentic design patterns. Thanks for being part of the awesome ADK community!

[achandrase-chwy]

Do I need to sign up for community calls? I attend the first one, didn't get any alert for Nov 3rd one.