CommonsWare reported that JetBrains is already wor...

# javascript

[Daniele B]

CommonsWare reported that JetBrains is already working at a Kotlin/JS version of JetpackCompose, but he doesn’t mention any source. Do you have any extra information?
https://commonsware.com/blog/2020/11/07/where-compose-could-go.html

[Casey Brooks]

Nothing public yet, but they did share a prototype they had managed to put together so far https://kotlinlang.slack.com/archives/C01D6HTPATV/p1604602564128500?thread_ts=1604443719.027900&cid=C01D6HTPATV

[Svyatoslav Kuzmich [JB]]

https://zal.im/h8/ is an old demo that uses Compose manipulating DOM tree without a Web canvas Skia wrapper.

[Svyatoslav Kuzmich [JB]]

https://twitter.com/bashorov/status/1324329633458913280

[Casey Brooks]

Is Compose on web going to be only a Skia canvas, or will HTML DOM trees also be supported?

[gaetan]

@Svyatoslav Kuzmich [JB] Manipulating DOM tree seems to be the “normal” way of implementing UI inside the browser. Compose for the web shouldn’t do it that way?

[Svyatoslav Kuzmich [JB]]

I don’t know much about this project direction.

If it would draw pixels on canvas on all platforms the same way (Flutter approach), it would be very easy to share UI across platforms, but you would likely miss on a lot of built-in HTML5 features.

Another very easy approach would be to expose DOM as Composable functions. This is what we did in the demo from a hackathon. This way you can’t share any UI code with Android and other platforms, unless you “expect-actual” a bunch of code.

[Svyatoslav Kuzmich [JB]]

An approach that would implement common Compose UI elements using DOM in an efficient way, would be perfect, but I don’t know how hard it is or is it even possible.

[gaetan]

Thanks for the answers.

[Daniele B]

@Svyatoslav Kuzmich [JB] Either DOM-based or Canvas-based, the most important thing is that it’s SEO-friendly.