Circuit in an older app with fragments containing Compose views and ViewModels?

[Shusek]

I'm wondering if anyone has experience using circuit in an older application that relies on fragments containing Compose views along with ViewModels. I would like to gradually refactor the codebase, but I haven't found any samples that cover this specific scenario.

Currently, I'm using Jetpack Navigation (non-Compose) for navigation, which I plan to migrate away from in the final step of the refactoring process.

I tried creating a Circuit object inside a fragment, but there doesn't seem to be a way to retain it across navigation steps. As a result, the entire state is lost and recreated each time.

#Edit
I just checked that the circuit works on a similar principle to the molecule library, switching from that to circuit seems to be a much better for incremental refactoring. Am I thinking correctly?

[ZacSweers]

I tried creating a Circuit object inside a fragment, but there doesn't seem to be a way to retain it across navigation steps. As a result, the entire state is lost and recreated each time.

Can you be more specific? For example, what is "a Circuit object" in this context? Circuit's SaveableBackStack participates in saved instance state, and with that any saved values within that. A simple CircuitContent is just a fancy composable like any other, and any uses of rememberSaveable should work accordingly there.

In general it would be easier to help you can be more specific about your issue.