:wave: Hi everyone! The Compose community has gro...

# compose

[Alina Dolgikh [JB]]

👋 Hi everyone!

The Compose community has grown a lot in recent years. We’re looking to improve the community policies and structure to make it easier to find information that interests you and to ensure that the channels remain useful for the fantastic discussions this group is known for. Here are the changes we’ve made and the new overall channel structure:

1. ✏️ 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.
2. 👋 We created the #compose-android channel for discussing anything related to Android-specific Compose APIs, topics like integration with android.*, and Android Studio tooling.
3. stackoverflow We encourage you to post StackOverflow-style questions on StackOverflow. If you think that your question fits well there, please consider moving it. This makes questions more discoverable for other people and makes Compose channels more unique and interesting to follow. Please use relevant tags [compose], [android-jetpack-compose]
🗣️ We encourage you to share your thoughts about these changes here 🧵

[Daniele B]

That is a great idea! so that people who have questions about using Compose with AAC ViewModel, Jetpack Navigation and Hilt don’t need to “infest” this channel, and can just use the #compose-android