Do the contributors of Kotlin Multiplatform have any plan of writing a proper documentation site like flutter's?

Do you have specific recommendations for what could be added to the Kotlin docs to make it better? Also, do you perhaps mean Compose Multiplatform? KMP is just the language, and its docs are pretty thorough. Compose is more analogous to Flutter, since it is the cross platform UI framework built on top of KMP.

It's my bad. Yes, Compose Multiplatform. Thanks a lot for your understanding. A dedicated docs site with sections in the screenshot is what I think of. P.S. It would have been much better if beginners without any knowledge of Android development could start with Compose Multiplatform by just reading its detailed documentation.

+1 indeed. I have an old desktop app using Swing that I'd be interested in moving to Compose Multiplatform. So I don't even have a server-component. First I am for a pure desktop app, and if that works, maybe a web version as a next step. But I don't have any Jetpack Compose (or Android) experience. The Getting Started section currently clearly assumes a mobile-server setup. So more documentation on different setups would be nice. Last time I looked at it (Compose Multiplatform 1.4) I figured the basics out looking into the Jetpack Compose docs, but since I'm not targeting mobile there most be differences between the frameworks at some point!?!

The docs are a bit fractured, admittedly. The docs at the official Compose Multiplatform site are mainly focused on the platform-specific setup and don’t include docs on layout, widgets, state management, etc. because all that is already covered in the Android Compose docs. Most of what’s in the Android compose docs is not any different whether you’re running Compose on Android, Desktop, iOS, or other targets.

@Casey Brooks Thanks for the links, but these should really be on the website. A lot of people will not know where the can find this documentation. I know I was confused for a while. Having to go to the documentation of another framework for a platform one might not be interested in (Android) isn't intuitive. Many frameworks are based on other frameworks but that doesn't mean there API i identical. I'm still certain that there have to be differences somewhere. Desktop UI isn't Mobile UI, one uses fingers/swipes and is always fullscreen, the other one uses a mouse (left-, middle-, right click) and isn't always fullscreen. I'm sure Compose Multiplatform handles these differences somehow but the Jetpack Compose docs won't tell me anything about it.

Couldn't agree more with @Stephan Schröder. I guess, Compose Multiplatform is still in its early stage and so the contributors of Compose Multiplatform may not have the luxury of writing a full-fledged documentation at this moment. However, they can still pick the relevant information scattered here and there, organize them, and present them in a centralized docs so that beginners may find it easy to get started.