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

Aperta
  • Qualcosa non va?
#70 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
mobile-dev, testing-qa

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Kotlin
Stelle
216
Fork
49
Merge medio
1g 14h
PR unite (30g)
6

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di android/appfunctions

Tutte le issue di android/appfunctions

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.