Jetpack Compose has a swiftly-changing API. We used to use the unary plus operator a lot (+memo), but no more. We used to use the binary plus operator (for combining modifiers), but that is gone too. Fundamental constructs like Container get deprecated and replaced (with Box in this case). And so on.
This is to be expected.
So long as we are in “dev” releases, anything could change in the API surface. That’s the point of “dev” releases – get early API feedback before that API starts to solidify. When we get to alpha releases, while the API may still change, those changes will be less drastic.
Certainly, you are welcome to use Compose for whatever you want, so long as you do not mind re-re-re-re-re-writing it as the API undergoes these substantial shifts. Hopefully, part of your objective of using Compose is to provide feedback on what you like and what you do not, such as through the kotlinlang Slack #compose channel.
On the flip side, if all you are doing is experimenting with Compose to get a sense of how it works… do not feel that you have to take on every dev release. The more releases you skip, the farther behind you fall, and the more difficult it may be to update your code… but you may not be planning on updating that experimental code anyway.
We may be in the “dev” release phase for quite some time. Plan accordingly!