Decompose VS kotlinx.html

I use Decompose, although I also have a kmp project which that supports. I find the compose extensions providing a very easy API when integrating with compose.

For one of our apps we used https://arkivanov.github.io/Decompose/ for navigation. It is mentioned in the Compose Multiplatform repo, but we found it pretty obscure to use and it has some confusing concepts built in.

View model is Googles recommended approach, but there are other approaches out their you can use like decompose

When you are building your app in KMM, sometimes you need to pack some libraries along with project files in the shared module. For example if you are using Decompose you need to access it's Value class in Swift.

I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.

I personally like decompose for its testability, clear separation of concerns, and apis for compose animations. Plus it's multiplatform so you can use it for other kmp targets.

Full discretion, all my new apps are built using mvi with MVIKotlin and decompose for the compose extensions for navigation animations. A sample project I have built with that architecture can be found here.

Check out Decompose, it's multiplatform - https://github.com/arkivanov/Decompose

Decompose

1 Clone this repo https://github.com/tom-delalande/html-to-kotlin-converter and open in intellij 2 In the root of that project folder, create input.txt and add the component/html that you want to convert (feel free to pick a component from tailwind), run main in that project and it'll be converted to kotlin ktor html DSL in output.txt (basically, that's the readme of that project lol) 3 in your ktor project (make sure you already added ktor-html from kotlin team), respond to a route like so

As for the strange infix syntax, you're correct - it's not important (for Dart anyway). Kotlin supports writing code that have DSL like syntax making things like typesafe HTML or Jetpack Compose possible.

I'm not familiar with JavaEE/JSP so I cannot really answer that, why do these technologies need a special IDE? Does JSP even make sense with Kotlin? If I was stuck with JSP I'd probably use Java since that's what JSP was made for. Kotlin has other solutions like https://github.com/Kotlin/kotlinx.html

Html DSL in Kotlin. See it on Github.

If so, and if they don't provide an easy way to set a font family list, you may have to escape into a raw block: https://github.com/Kotlin/kotlinx.html/wiki/Style-and-script-tags

You might like to leave a comment here, someone requested svg support in the Kotlin HTML dsl https://github.com/Kotlin/kotlinx.html/issues/144

Thanks for sharing, I really like projects like this. And the website is really informative.

I find it less of a new language and more of a JS preprocessor, removing lots of the cruft and integrating XML-tags and CSS in a very neat way.

What I miss:

1) I feel the web is shifting to more type checking. TS, Elm, Kotlin.js... I personally also prefer more typesafety, especially if the project grows in LOC/team size.

2) Compared to JSX, Imba does a much better job in integrating adjacent technologies. Though I much prefer these to be integrated in an eDSL fashion. For example how Elm does HTML templating (in Elm) or Kotlinx.html[1].

Just taste i guess. Good luck with yr project!

[1]: https://github.com/Kotlin/kotlinx.html

I do use kotlinx.html and while there is a lack of the documentation about the tags, most of them are already implemented (as far as I know they are automatically generated) and the ones that aren't automatically generated can be implemented manually in your own project.