So what parts of compose desktop are lacking compared to compose android?

You tell us! Try it out, tell us what's missing / needed most.

So it’s expected that Android and desktop have the same features?

Icons.Filled.Visibility

and

Icons.Filled.VisibilityOff

is missing.

Desktop is newer so things are a little more experimental, and the platforms are different so some features make sense for one platform but not the other, but largely the goal is to keep them more aligned than divergent.

There are things missing in Android compose, e.g scrollbars. But they make sense only in Desktop. 😀

Scrollbars make sense on Android : to know where you are, in case you have a mouse, in case you need to fast scroll long lists (e.g. contacts list or whatever)

We intend to lift scrollbars into more common code, just hasn't happened yet. But yes, scrollbars were implemented on Desktop first because they were more critical to the desktop experience.

Yeah, I had to say "*much* sense". In Android they are indicators only, but in desktop they are interactive.

Overridable platform dependent defaults is the way to go IMHO

Image loading library

image manipulations are covered in https://github.com/JetBrains/compose-jb/tree/master/tutorials/Image_And_Icons_Manipulations, could you clarify what is missing

@olonho just checked the doc,

imageFromFile

synchronously loads images from disk? Also what about loading from network?

but why one cannot use

javax.imageio.ImageIO

for example? Or you mean something MPP-aware?

I'm not sure. You just pointed on that Readme, but async image loading from disk/web is not covered there. Some example of image loading from network in a shared Android/Desktop code would be great.

Time to contribute to Coil and decouple it from Android 😏

What is CEF support?

oh wow cool.