I dare say that since it's related to Android Stud...
# composea
Alejandro Rios
07/20/2020, 6:11 PMI dare say that since it's related to Android Studio 4.2 then when that version is ready compose will be ready too
a
Adam Powell
07/20/2020, 6:13 PMI hate to burst this bubble but the first dev release of compose was related to Studio 4.0, and moved to 4.1 and now 4.2 as Studio releases have continued 🙂
😕 1
s
shikasd
07/20/2020, 6:15 PMI think it much more dependant on new Kotlin backend becoming stable :)
m
Mehdi Haghgoo
07/20/2020, 6:25 PMYes, as @Adam Powell said, I think it has more to do with Canary builds, not a specific version.
a
Adam Powell
07/20/2020, 6:27 PMRight, anything not ready to graduate to stable yet in an Android Studio release moves to the next canary and is removed from the beta track for that version
Adam Powell
07/20/2020, 6:27 PMSame process that was in effect for the navigation editor, for example
2 Views