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

Ouverte
  • Quelque chose ne va pas ?
#70 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
android, kotlin
Domaine
mobile-dev, testing-qa

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Kotlin
Étoiles
216
Forks
49
Merge moyen
1 j 14 h
PR mergées (30 j)
6

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de android/appfunctions

Toutes les issues de android/appfunctions

Issues similaires

Plus d'issues Kotlin

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.