Why are there so many Compose artifacts? It's a bi...

# compose

[Mehdi Haghgoo]

Why are there so many Compose artifacts? It's a bit confusing. Is it not possible to put the whole Jetpack Compose library in one artifact?

[allan.conda]

that’s going full circle with AppCompat all over again 😄
I personally like the separation, I have modules where I only need the runtime artifact for example.

[gildor]

agree, keep it separate, it’s very nice to have good modularisation to make it as slim as possible for different projects

[gildor]

@Mehdi Haghgoo if you just try to play with it, add all dependencies to your project from https://maven.google.com/web/index.html?q=compose#androidx.compose

[caelum19]

It can be less confusing if there is a gradle snippet maintained with each package and a comment with what the package includes, which I imagine there will be later on 🙂

[gildor]

Yeah, true

[Mark Murphy]

FWIW, at least in the current artifact organization, androidx.compose.material:material will pull in a lot of the other ones via transitive dependencies. So, if you are aiming for a Material Design look, start with that one dependency, then add others only if needed.

[Ricardo C.]

It's better if everything is separated. What is hard is figuring out which dependency you need. It would be cool if you could write the name of the composable and alt enter would give you the dependency you need plus latest version

[gildor]

There is a such feature for some androidx dependencies