A modern programming language that makes developers happier.

kotlinlang

Hello! Now that Jetpack compose is in the stable state, is it fine to use jetpack compose in hybrid mode (combination of xml + jetpack ) on production in business critical apps? Has anyone done this already? Pardon me if this has already been discussed on this channel, I was not able to find the thread.

Based on <https://developer.android.com/jetpack/compose/adopt#what-developers-are-saying|this> I believe it is being used on production, I guess I am more curious about if anyone faced challenges wrt to hybrid approach (xml+ compose)

We've been doing the hybrid approach by a lot in our company and it is been working great for us. We can focus on writing new component on Compose while showing them in legacy screens (XML based) without having to refactor the whole feature.

My experience on a small app is that mixing navigation methods gets a bit hairy. Stick with classic navigation until ready to big bang the migration to Compose navigation.

apologies for sliding in here, and my ignorance, but what exactly is compose navigation? is that basically just jetpack navigation with some DSLs or something else?

Every significant app I know of that uses Compose is a "hybrid" of Compose + Views, since they were all started before Compose was stable.

This includes several apps, both internal and external, by a nationwide retailer.

&gt; what exactly is compose navigation? is that basically just jetpack navigation with some DSLs
Compose navigation is the `androidx.navigation:navigation-compose` artifact as explained here <https://developer.android.com/jetpack/compose/navigation>
I’m not using it personally so don’t know more details, but I think it uses a lot of the same internals under the hood as normal navigation, but it’s slightly different in some aspects.