Doodle VS kobweb

https://blog.jetbrains.com/kotlin/2023/08/compose-multiplatf...

They don't really mention Wasm there as this mostly focuses on the IOS support. They had a lot of presentations about that at kotlin conf and the compose web channel in the kotlin slack is very active.

Basically, anyone currently doing mobile development that is used to modern UI frameworks for that, will soon be able to target browsers effortlessly without compromising on their UI frameworks. Compose is one of the frameworks. But there are others. I've seen some nice kotlin-js frameworks targeting canvas and vector graphics. Doodle is a nice example: https://nacular.github.io/doodle/. I have not used that yet but it looks quite slick. A lot of kotlin-js stuff will transition to wasm once the compiler stabilizes.

Web developers seem to be mostly unable to see beyond their comfort zone of DOM/CSS/JS. There are alternative ways of doing UI/UX that are common outside of browsers. Applying that in a browser is transitioning from impossible (a few years ago) to being hard but very feasible (the last few years) to being easy, very common, and widely supported across different developer ecosystems (the next few years). Not a matter of if but when.

Doodle is a pure Kotlin UI framework for the Web (and Desktop), that lets you create rich applications without relying on Javascript, HTML or CSS. Check out the documentation and tutorials to learn more.

Doodle - A pure Kotlin UI framework for the Web (and Desktop).

Doodle is a pure Kotlin UI framework for the Web (and Desktop), that lets you create rich applications without relying on Javascript, HTML or CSS. Check out the documentation and tutorials to learn more.

Done, added "Other" and "None of the above" options. Thanks for the feedback! Btw, were you talking about this library: https://github.com/varabyte/kobweb?

Aaaaand sourcemap config done: https://github.com/varabyte/kobweb/commit/84e17b710d92332efdb37abb887e546a7f03c73d

(For people who don't know Kobweb, you can read more at https://github.com/varabyte/kobweb, but until I update it, please replace "Compose for Web" to "Compose HTML" in your head, thanks!)

I'm actively working on https://github.com/varabyte/kobweb, which builds on top of Compose for Web and adds some extra support to make it a little easier for Android developers to get into. (You will ultimately need to learn html / css but I believe Kobweb makes that a little easier to start getting used to it).

https://github.com/varabyte/kobweb is Compose for Web using DOM rendering instead of Canvas with a Jamstack like approach. Worth to try and if it later upgrade from Kotlin/JS to Kotlin/Wasm, it could really become something big …

I'm working on https://github.com/varabyte/kobweb which is not mature, but you might want to check it out anyway?

This is indeed a very important point, and I care deeply about that.

For Compose for Web, there has been I think a lot of debate to decide if the Web rendering should be Canvas or DOM based. At least for now, it seems the official support is focusing on Canvas rendering for pixel-perfect rendering, and it already works with Koltin/Wasm, see https://news.ycombinator.com/item?id=34779746. This choice is probably driven by Kotlin current mobile app main use case.

But via community-driven project like https://github.com/varabyte/kobweb or https://github.com/mpetuska/kmdc, Compose for Web can also be a good Web citizen and perform DOM based rendering.

I'm working on an opinionated framework on top of their framework called Kobweb, but depending on your goals it may be sightly too early to use it.

This may not help but I have a working ktor server in my project. Here's my Gradle config: https://github.com/varabyte/kobweb/blob/main/backend/server/build.gradle.kts