I Ditched Google ADK for LangGraph
The author shares their experience transitioning from Google ADK to LangGraph for creating AI Agents. They highlight the frustrations with Google ADK's dense documentation and telemetry data collection, which hindered their development process. In contrast, LangGraph offers more flexibility, easier state management, and a clearer programming flow, making it a preferred choice for the author.
- ▪The author built a prototype for a news aggregation website using Google ADK but faced challenges with its documentation and execution control.
- ▪LangGraph provides a more intuitive framework for creating AI Agents, allowing for easier reasoning about program flow and state changes.
- ▪The author appreciates LangGraph's flexibility and control, comparing the transition to moving from TensorFlow to PyTorch.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Maybe-Ray |
| Canonical URL | https://mayberay.bearblog.dev/i-ditched-google-adk-for-lang-graph/ |
| Publication time | Mon, 25 May 2026 07:19:15 +0000 |
| Retrieval time | 2026-05-25T07:37:36.533Z |
| Last seen | 2026-05-25T07:37:36.533Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | bElaJD9fWMHP |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
I Ditched Google ADK for LangGraph 25 May, 2026 LangGraph is by far the best framework I've used for creating AI Agents. The framework provides complete control over the execution of individual Agents and the state that flows through them, which you frankly don't get from the Google Agent Development Kit (ADK). Jumping off from the 5-Day AI Agents Intensive Course with Google on Kaggle, I built the prototype for Ikka, a Zimbabwean news aggregation website using the Google ADK. The trouble with the Google framework began when I needed to implement looping for my editor Agent. The documentation for the ADK is very dense and, at the time, did not provide a clear way of mixing sequential and looping execution.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Maybe-Ray.
Discussion
0 commentsMore from Maybe-Ray
