Hi, the Compose library for GenUI was recently rel...

# compose

[Ghasem Shirdel]

Hi, the Compose library for GenUI was recently released:
developer.android.com/develop/ui/compose/agentic
My question is: is this project eventually going to use Remote Compose under the hood?
At KotlinConf this year, Remote Compose was introduced for widget and agent use cases, so I’m wondering whether this project is being developed in parallel with that implementation, or if there are plans to converge them in the future.
Also, as far as I understand, developer.android.com/jetpack/androidx/releases/compose-remote still hasn’t moved toward supporting custom component registration. I believe something like that was needed for components such as TextField, so that they wouldn’t have to be reimplemented from scratch.
On the other hand, Agentic Compose already seems to address this by allowing existing components and libraries such as Coil and Media3 to be used, as well as other pre-built components.
So I’m curious about the relationship between these two approaches and whether Agentic Compose is expected to build on top of Remote Compose in the future.

[blakelee]

These are completely different things. Notice that the a2ui spec has many renderers than just compose.

[yschimke]

On remote compose.

There are lower level apis for custom components, just not the composable ones. And there is player support, the view player predictably using a view for the custom component, while embedded compose player will use composables.

[yschimke]

but in general the public apis for players is probably starting next year. There are some end to end samples for text fields.

[yschimke]

But these two things are not linked in anyway. In theory you you build an a2ui library in remote compose. Or you could consider them alternatives.