But overall, I’ve done a lot with SSR and I’ve generally found that it doesn’t make for a very great or polished front-end UX. It works, and for fast development, internal projects, or mostly-static content, it’s probably good enough. But to really get a snappy, responsive experience on the frontend, having some kind of decoupled client-rendered UI does feel better from a user’s perspective. Also makes it easier to integrate into a mobile app if you ever need to add that, as it would be talking to the same APIs that the web client uses

In particular, the workaround in this issue (https://github.com/Kotlin/kotlinx.html/issues/88) makes it possible to get the underlying HTMLElement from any point in the kotlinx HTML DSL, so you can mount dynamic content to that one element and update it later with new content from a Flow, and not necessarily replace the entire screen on every small data change