I was having a look at the blog posts and at the n...

# feed

[Edoardo Luppi]

I was having a look at the blog posts and at the new KMP wizard.
I think there is still a big problem: the Get Started documentation and the wizard are mobile/Compose-centric.

It doesn't come out the fact you can develop more than cross platform mobile apps.
The web target seem to focus on WebAssembly, which beside being the cool new kid at the moment, is still a second choice compared to JavaScript.

If I had to have a chat with my manager and go through that stuff I would probably be questioned on why I'm looking at mobile technology.

[Klitos Kyriacou]

Also, am I being nitpicky when I note that, if I just wanted a desktop application to run on Windows or Linux on the JVM, the wizard creates files containing import androidx.compose... even though my app will have nothing to do with Android whatsoever?

[Edoardo Luppi]

Because it's supposed you're creating a mobile app with Compose that also targets the desktop with Compose Desktop.
Not nitpicking, I totally agree with you.

[Todd]

It's just the package names for the library, which started off android only. Iirc, I remember hearing someone saying in retrospect they would not have chosen that to be the package name, but updating package names is not worth the payoff.

[Todd]

See this video starting at 32:45.

https://youtu.be/9MJPvsWQzP8?si=rCirOlX05yVgvxBE&t=1965▾

[CLOVIS]

> I remember hearing someone saying in retrospect they would not have chosen that to be the package name, but updating package names is not worth the payoff.
Well, a lot of people asked for this long before Compose was even 1.0. What I've heard is some managers at Google really wanted to keep it so it's clear that it was Android-first? Might just be a rumor, though.

kotlinx.compose.* would have been so much better for the KMP variant.

[Edoardo Luppi]

I've created https://youtrack.jetbrains.com/issue/KT-63167