Priority of Compose Multiplatform and Communication of Roadmap #2220
-
|
Hello, I can tell that Google is interested in Jetpack Compose. They continuously update their roadmap and do great communication with the community. I can't find the same level of interest or communication from JetBrains concerning Compose Multiplatform. No updates on the progress of features development. No clear roadmap. No clear comment on iOS support or canvas-based web support although they have presence in the codebase. Jetpack Compose 1.2 Stable was released but I can't find any comment when to expect stable or beta Compose MP 1.2. Please don't misunderstand me. I'm just jealous about Compose MP and see it as a rival to current technologies like Flutter. So, I think better communication is essential for this success. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Silence is the answer |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for your feedback. Yes, unfortunately, we have issues with public communication (particularly, answering questions and issues in GitHub), and we plan to change things for the better. We are more active in Kotlin Slack channel than in GitHub Discussions (#compose-desktop, #compose-ios, #compose-web). Not active enough though. But if we have a definitive answer for a question, we usually answer on it.
Most of the features for Compose are developed here and here. But it will be more transparent if we would make changelogs more frequently.
We avoided roadmap so far because of a lot of uncertainties and to avoid false promises, but the roadmap is must-have for any mature product. So we'll figure out how we can provide it.
All we can say now that we actively develop iOS target (and not so active Web Canvas), and have big hopes. There is still a lot to do before we can definitely say "we officially support iOS" (or Web Canvas). And not only in technical, but also in managerial and legal aspects.
Our release cycle wasn't obvious from the beginning, but we described it in some places (1, 2, 3, 4). It obviously became lost, so we'll make a separate page about our release cycles and versioning. We can't release Compose Multiplatform straight away with Jetpack Compose, because Jetpack Compose is developed by Google, and they only test it for Android. We need time to adapt and stabilize it for the other platforms. What we can do though is to minimize the gap between our and Jetpack Compose releases. If we talk about a more concreate release that is based on Jetpack Compose 1.2, we plan to release it in October. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your detailed answers. I really appreciate that. I wish you success in every aspect of the project. |
Beta Was this translation helpful? Give feedback.
Thank you very much for your feedback. Yes, unfortunately, we have issues with public communication (particularly, answering questions and issues in GitHub), and we plan to change things for the better. We are more active in Kotlin Slack channel than in GitHub Discussions (#compose-desktop, #compose-ios, #compose-web). Not active enough though. But if we have a definitive answer for a question, we usually answer on it.
Most of the features for Compose are developed here and here. But it will be more transparent if we would make changelogs more frequently.
We avoided roadmap so far because of a lot of uncertainties and…