Should I use Compose in production if I'm okay with maintaining the code with new releases? My use-case mainly involves dealing with Camera and videos. I went through compose-samples and found comments referencing to some of the issues being tracked; could someone brief me about the things (integrations with other jetpack components) that are not yet supported in Compose? I personally found jetpack compose opening up way more possibilities to do with the UI that I wouldn't have bothered to do had I using the legacy xml based layouts, but I'm getting bit confused about the architecture patterns to follow. Any recommendations in this regard would also make things clearer for me.

You might experience performance issues and bugs so if you're okay with that you can use it. Compose navigation will be released soon so keep an eye on that

@Se7eN may I know what kind of performance issues? I thought compose might be better in performance since it directly works on canvas

Like the

LazyColumn

's performance is still low compared to

RecyclerView

. It's still in it's first alpha phase, the performance will get better with each release

Another disadvantage of today's Compose (maybe just for me personally) that there are too few information. Ok, I can google something like

jetpack compose recycler view

and get info about

LazyColumnFor

. But google cannot get answer about questions that a little bit more complicated. That means my efficiency falls

True. I didn't find any tutorials/blogs on integrating camerax with jetpack compose, especially handling those seamless transitions on screen rotation

https://developer.android.com/jetpack/compose/state is a good read on the core of compose architecture patterns

It's also still missing some critical features, like comprehensive accessibility support.