If I understand correctly, the android related dependencies are also pulled in as part of Compose Desktop build? If so, what's general approach used then to only depend on those for both?

Just apply the JetBrains plugin and use built in deps under

compose

accessor

Thanks @Javier, I'll try that

the only problem is where you want to add libraries which doesn't match with JetBrains one

In beta API is stable so as long as there's no ABI change (such as that introduced in beta07) compatibility shouldn't be a problem.

But I think it is a forced error

I hope compose web will also get Android dependencies soon

@Javier I haven't seen that. How does the plugin know what version the dependency uses?

I don't know how it does, but for example, if I add the jetbrains dependencies in the app module, and I add there the google ui tooling dependency to use

Preview

, if google/jetbrains are not pointing to the same version, it fails

So your "dependency" means compose itself right? That is understandable, since that's essentially different versions of the same library. This shouldn't prevent you from using other libraries that use compose.

Tried this as a test, with a number of dependencies etc commented out (like tooling one), and was able to run Android app using that plugin and then adding these

implementation(compose.foundation)
    implementation(compose.material)
    implementation(compose.ui)

Interesting 👀