While as an idea this sounds very logical. I can’t imagine this channel having clear boundaries as to how people use it compared to the #compose channel. My intuition is that people will simply continue posting there, as it’s the channel with the most momentum (~8k members). And again, if I were to guess, >95% (probably more) of the people using compose only use it for Android. So if anything, I’d expect the “extra” channel (this) to somehow be the non-android channel, as opposed to having the original become the specialized case, and have this channel be the one that in reality the vast majority of people are interested in. I’m sure you’ve thought hard before making this decision, but what is your opinion in my thoughts here?

For me it's one more channel where to search. I know I can search in multiple channels at the same time but I am just so used to

Cmd + F

and start typing. But it seems like people don't search before asking anyway so I don't know if it's relevant 😅

It is relevant to me too. There’s a ton of very useful knowledge, for Android specifically too in the existing #compose channel, that’s for sure.

Why not rename the previous one to #compose-android and have the new one as #compose? 👀

This feels like a repeat of #android where people will go in expecting to ask android questions, but get :not-kotlin-but-kotlin-colored:'d to death because no one reads channel descriptions.

Why not rename the previous one to #compose-android and have the new one as #compose? 👀

This would make more sense. As long as renaming a channel does not suddenly break existing links, the archives in https://slack-chats.kotlinlang.org/ and so on. If there are no such implications I would say that this is a good solution. If not, I’d rather not break existing stuff.

maybe it would be more clear to follow KMP convention and call the general compose channel #compose-common?

I don’t think the idea is that the split is specifically for Compose for Android vs compose multiplatform. The message announcement there specifically says “The #compose channel is the main channel for discussing general Compose topics not related to any particular platform (for example, the common API, Compose design principles, etc.). I’ve updated the topic and description of the channel.“. So it’s more than just “common” which implies the connection with KMP. I don’t think this would be a better name for it.

yeah, it's kinda tough when you only have so many letters in a channel name to get that point across

Hi folks! Thank you for sharing your thoughts and feedback. These are all great questions to discuss. It’s true, we’ve thought hard before making this decision and even analyzed a sample of messages from the #compose channel (which still cannot provide us with the ultimate certainty it is the best structure ever possible 🙂 ). But we gonna keep an eye on the new structure and conversations in the channels to continue improvements if needed. Feel free to share your observations and thoughts too.

why was #compose-mp archived though? I think having a

compose-desktop

oriented channel was great to ask question related to desktop APIs/gotchas (not common compose questions)

Hey! There is #compose-desktop and other channels targeting platforms

Great - I actually haven’t check if it existed 🙈 Thank you!