How to Shrink Your Compose Desktop App by 10x <gis...

# compose-web

[Konstantin Tskhovrebov]

How to Shrink Your Compose Desktop App by 10x
gist.github.com/terrakok/bb876b257adfdedffdd6fda98457c8ce

[bod]

Hahaha interesting approach 😅
But wouldn't it make more sense to have Compose target native?

[Konstantin Tskhovrebov]

not sure. there is no single native target + more libraries support wasm target

[Konstantin Tskhovrebov]

of cource as a general idea: native support is better 🙂

[Konstantin Tskhovrebov]

I don't argue

[bod]

Yeah I'm sure it would be a great challenge! But would also avoid kotlin to wasm to JS to Rust 😂

[Konstantin Tskhovrebov]

let's be realistic: most of apps don't need so direct access. usually what they need to parse jsons and to show lists 😆

[bod]

very true 😄

[Konstantin Tskhovrebov]

and I prefer for such apps installed PWA 😉

[bod]

hey maybe in the future OSes will have direct support for WASM/Canvas applications.

[Konstantin Tskhovrebov]

it is already possible. and we are experimenting with it too. but the thing is Browser APIs

[bod]

[hey in fact isn't Compose semi supported or almost supported or experimental, on MacOS? Or am I remembering wrong?]

[Konstantin Tskhovrebov]

experimental

[bod]

ah -> youtrack.jetbrains.com/issue/CMP-4580

[bod]

well maybe Wasm is the future for Desktop 🙂

[Frank Bouwens]

https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1782281738121479

[Frank Bouwens]

Might be related; Having a “native” Compose UI host could be what you meant.

[bod]

very cool

[bod]

(still JVM from what I can tell so not exactly what I meant)

[Frank Bouwens]

https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1783938008832499