[FR]: Render A2UI returned by AppFunctions in the Testing Agent

Abierto
  • ¿Algo no está bien?
#70 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, kotlin
Área
mobile-dev, testing-qa

Línea de trabajo

Start with the open questions: whether A2UI returned from an AppFunction is the intended approach, which catalog to target, and the updateComponents.components string-versus-array mismatch in fetchSendMessageDetails (ChatApp). Compare the feature/a2ui-contact-picker branch with main and the androidx.a2ui parser before any design work. Done means a maintainer has confirmed the approach and catalog, with a design agreed for rendering A2UI in the Testing Agent.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Is there an existing issue for this?
  • I have searched the existing issues
Describe the problem

The Android Dev Summit keynote shows what looks like a custom app widget inside Gemini. I want to test that kind of flow locally: an app returns UI from an AppFunction, and a host renders it, as Gemini would.

The Testing Agent can't do this today because it doesn't render A2UI on main. I also couldn't find a way to use Gemini Developer Mode with on-device AppFunctions.

Describe the solution

I plan to build this in my fork of the Testing Agent, and I'd be glad to contribute it upstream if it's useful.

@JolandaVerhoef I'm mentioning you because you authored feature/a2ui-contact-picker, which adds an A2UI renderer to the Testing Agent.

First, I'd like to confirm my assumption. The keynote is outside this repo, but do you know how that widget was rendered? Was it A2UI returned from an AppFunction, like fetchSendMessageDetails in ChatApp, or an iframe from a remote MCP server?

If it was A2UI, or A2UI is otherwise the intended approach for AppFunctions, I have two follow-up questions:

  1. Which catalog should the Testing Agent support? I plan to start with the Basic Catalog. ChatApp uses comms_catalog_preview, but its URL returns 404. Is a schema available?
  2. Would you accept a PR that adds A2UI rendering to the Testing Agent? feature/a2ui-contact-picker is close, but it predates the resources format and uses a hand-written renderer. I'd start from main with androidx.a2ui, which requires compileSdk 37.1 and alpha versions of Compose and Material3.
Additional context

I also noticed that fetchSendMessageDetails sets updateComponents.components to a JSON string, while the androidx.a2ui parser expects an array. Is that intentional?

Code of Conduct
  • I agree to follow this project's Code of Conduct
Lenguaje dominante
Kotlin
Estrellas
216
Forks
49
Merge medio
1 d 14 h
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de android/appfunctions

Todos los issues de android/appfunctions

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.