Consider Building UI on ADK Web Instead of Rewriting Communication Code

[marvcks]

build-your-agent/agents/adk_ui_starter/websocket-server.py

Line 298 in 401798b

async def process_message(self, context: ConnectionContext, message: str):

The current frontend-backend communication code seems to have issues, particularly in handling artifact data from the backend ADK.
Completely rewriting the communication code from scratch feels like reinventing the wheel. Why not simply build upon the existing ADK Web framework? Their implementation already handles all the communication logic - we would only need to modify the frontend design.

[lhhhappy]

Thank you for the excellent suggestion! You're absolutely right that building on top of the ADK Web framework would be a more sensible approach.To be honest, when we initially built this, we thought the communication layer would be relatively straightforward, so we implemented it from scratch. Looking back, this was indeed reinventing the wheel. However, this approach did give us more flexibility to implement some custom features.

your suggestion is valuable, and we could consider extracting the core communication modules from ADK Web as a foundation and building our custom features on top of that in the future.

we now offer a more comprehensive UI deployment solution on the Bohrium platform that requires no manual
configuration. You can learn more from our documentation:

https://dptechnology.feishu.cn/wiki/ZSj9wbLJEiwdNek0Iu7cKsFanuW?from=from_copylink

We welcome continued discussion or PR submissions to improve this together!