If I try to have a single module common-composables that are shared for desktop and android... am I "held back" by the version number that desktop supports? I know desktop is slightly behind and just curious if that basically means I'm always going to be a ~week+ behind on compose releases.

I'm confused. Desktop releases are always ahead of android, not behind.

Oh. I must've interpreted that wrong from a past thread then.

Yes but Compose for Android 1.0.0 beta is not compatible with the versions of Compose for Desktop or MP compose am i right? Is it planned in version 1.0 that it is possible to provide libraries which will work with both?

They are compatible in the sense that the APIs are stable and the same, but there are challenges around properly declaring your dependencies (you kinda need to choose either MPP dependencies or android dependencies). Solution not planned for version 1.0, but my tentative hope is that we will have a solution by end of the year.

Thanks. I have my main android app with a compose module as it stands today, and tonight I'm going to try integrating adding a desktop module again. 🤞