Skija VS compose-multiplatform

So for some extra context, but Fleet is using Skija[1] and Compose[2] as a rendering an engine. Skija is a java wrapper for Skia and still does not support the full API. Compose is still relatively new and has not had nearly the amount of man hours devoted to it as Swing. This is just a technical preview, I'm sure there will be plenty of optimizations to come. I think it's pretty exciting to see Skija being used for a mainstream project!

[1] https://github.com/HumbleUI/Skija

So, to add file associations, we need to be able to pass both the .properties file and the --file-associations option. At the time of writing this article, the org.jetbrains.compose plugin doesn't provide such a mechanism. There is an open issue on GitHub that describes a possible workaround, which, unfortunately seems to not work on macOS.

JetBrains has a simplified example of a general-purpose Compose text viewer here: https://github.com/JetBrains/compose-multiplatform/blob/master/examples/codeviewer/shared/src/commonMain/kotlin/org/jetbrains/codeviewer/ui/editor/Editor.kt


Compose for desktop has a scrollbar component available. You probably can't use that directly on Android, but you could probably steal most of its code.

My company uses https://github.com/JetBrains/compose-multiplatform to make a desktop app in Kotlin. It's amazing and fantastic. It's basically as mature as using Kotlin in an Android app.

Kamel is an asynchronous media loading library for Compose Multiplatform.

Kotlin Compose Multiplatform is the way to do Desktop apps. https://github.com/JetBrains/compose-multiplatform

As for missing controls, a common one is a grid. They have built in grids, but again they are built for Android and don't make any sense in a desktop app. There is no simple way to create an Excel-like Data Grid like you might see in Windows Forms, although it can be done. https://github.com/JetBrains/compose-multiplatform/issues/344.