<https://developer.android.com/jetpack/androidx/re...
# feedo
Ohiorenua Aigboje
03/08/2026, 1:23 PMhttps://developer.android.com/jetpack/androidx/releases/compose-remote
I just came across this new compose library. I think it's best use will be for compose wasm, if it is supported. It will greatly reduce the binary size. I am not using yet because it is still in alpha not yet stable and the documentation is not clear enough.
m
Michael Paus
03/08/2026, 1:43 PMWhich documentation? Is there any documentation at all for this beyond this sole sentence "Remote Compose is a framework to create UI for remote surfaces"? Even the API link is broken.
t
Tanish Azad
03/08/2026, 1:56 PMIt won't decrease the WASM binary size by much, most of the size is for the skiko wasm which is ~8.5MB, and then theres a smaller app wasm, it can probably reduce the size of app wasm most of that is coming from external libraries, the actual UI code is fairly slim.
o
Ohiorenua Aigboje
03/08/2026, 2:02 PM@S. It doesn't state were it breaks your UI. @Tanish Azad Most UI framework has this feature eg React
s
streetsofboston
03/08/2026, 3:03 PMIt does NOT support true server side rendering yet... (at least when i tried it out 2 months ago). It supports on-device cross process rendering only so far (your Android app or service being the "server" rendering a widget on your home screen). This is why:
The "server" (remote-creation) part of the remote rendering library depends on Android libraries/code!
Not until they pull the server side rendering library away from its Android dependencies, only then will true server side rendering be possible.
Maybe this has changed since last month, since Philipp doesn't mention this.
👍 2
e
ephemient
03/11/2026, 12:51 PMephemient
03/12/2026, 10:57 AMIt does NOT support true server side rendering yet...https://issuetracker.google.com/issues/482343980
24 Views