<@UJNJP518C> I've been following the development o...

# compose

[Seri]

@Nicolas Roard I've been following the development on Remote Compose and am very excited to see where it goes!

I'm interested in writing a KMP/Native player and integrating an LLM with remote-creation-core in order to create my own Compose-based design iteration tool. I saw an earlier post of yours that roughly estimated a native player around H2/2026. How has this been going along, or is there a public roadmap?

thank you and the team for all your work! 🎉

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1764567153221429?thread_ts=1757443379.992539&amp;cid=CJLTWPH7S

[Nicolas Roard]

You can take a look at some ongoing experiments: https://github.com/camaelon/remotecompose-experiments (see https://camaelon.github.io/remotecompose-experiments/RemoteComposeIntroduction/ too)

[Pablichjenkov]

Wouldn't this solve the "system notification can't execute compose" issue.

[Seri]

@Pablichjenkov This project doesn't have much to do with notifications. "remote compose" in this sense means an architectural shift in Compose towards something like a server/client. The server execute Compose code to produce a streamable layout binary, then a client renders that layout binary to actually create the live screen

[Pablichjenkov]

Oh 😓 I see, I thought it was behind that. Since is a similar principle but more capable than the current Live update notifications API which is very limited per say

[Nicolas Roard]

Technically you can send it to a notification (the implementation in platform is at the RemoteView layer), but we are focusing more on the widgets use case at the moment