Until Compose for Native Desktop (such as the curr...

# compose-ios

[Landry Norris]

Until Compose for Native Desktop (such as the current macOS prototype) is stable, is this a good place for discussion (Compose for Native macos is very similar to Compose for iOS in the codebase)? Or is #compose better?

[Alina Dolgikh [JB]]

I’d rather say #compose-desktop

[Michael Paus]

But compose-desktop implies Java and its tool-chain which is quite different from compose-native for macOS.

[Landry Norris]

I’d imagine one day, it’ll be helpful to have a separate compose-native channel. The whole Desktop via K/JVM or desktop via K/N is already a bit confusing.

[jim]

I suppose it depends on the specifics of the question. I think #compose-desktop would be the right long-term place, especially if you are talking about anything desktop-specific. I'd see this channel as more of "how do I interoperate with iOS APIs/widgets". But it depends on the question, if it's more of a discussion about a particular function of native builds that reproduces on iOS also, then this channel might be a good place with more people who are familiar with the native/iOS toolchains. That said, many of the same people will likely hang out in both channels, so might not super matter where you ask, just use your best judgement.

[jim]

Maybe as a rule of thumb, if the issue does not reproduce on iOS, then it should not be in the iOS channel. If you're mentioning desktop APIs, then desktop is the right channel. If you're mentioning iOS APIs, then iOS is the right channel.

If it reproduces on both iOS and Desktop (purely an issue with native compiling), then you can choose at your discretion which channel would be most appropriate.

The idea is to put the conversations in a place where they will be most discoverable to the audience who is most likely to want to see them. That's a judgement call you'll need to make when formulating your question.