Setup Circuit for Scalable Navigation: Seeking Insights

[shaharKeisarApps]

Hello everyone,

As we explore using Circuit for a scalable application, we're intrigued by the potential of extending its navigation capabilities to better support complex scenarios. Specifically, we're considering how incorporating navigation graphs or nested graphs, akin to what Jetpack Navigation offers, could enhance Circuit's utility for larger, more complex applications.

Given Circuit's emphasis on simplicity and effective state management, we're curious about the community's view on this evolution. Would integrating more advanced navigation concepts compromise the framework's straightforwardness, or could it enhance its scalability without significant complexity?

Furthermore, for those navigating the challenges of scaling with Circuit, what strategies or patterns have you employed to manage complex navigation flows? Are there adaptations within Circuit's model that you've found particularly useful for maintaining a clean and scalable architecture focused solely on navigation?

Your insights on balancing these complex navigation needs with Circuit's design philosophy would be invaluable as we aim to build a robust and adaptable application.

Looking forward to your thoughts and recommendations!

Thank you!

[ZacSweers]

Hey, there is a lot of wording here but it seems like you're just asking if nested navigation is possible in circuit. It is natively supported :).

Side note: in the future, I think it would be easier to help with your posts if you made them more concise. I suspect this one was (at least partially) generated by an AI tool, and the result is a lot of fluff that possibly obscures the point of your post.

[shaharKeisarApps]

First of all, thanks for being honest
Actually, I did try to explain the issue in a better way
The main question is:
Is it recommended to consider the navigation in Circuit, same as in Jetpack Navigation
so i can i graph for each flow of screens?

and if NavigableCircuitContent same as NavHost in Jetpack Navigation? (which might be one for the whole app)

[ZacSweers]

If you want to create a routing DSL, you can build that on top of Circuit. We don't currently offer a first party alternative for replicating that API.

If it's just for deeplinking, here's an example of an implementation I wrote in a personal project: ZacSweers/CatchUp#880.

For something like a bottom navigation bar with nested navigation, we have a sample of that in the STAR sample.

[shaharKeisarApps]

Yep, i have already went through Circuit examples, they are undoubtedly excellent
In addition, I also went through the Tivi project, and your personal project CatchUp, which both were very clear implementation to understand.
Right now I'm trying to understand if Circuit is meant to work in a simpler way and without graphs
or is it actually something I'm supposed to build myself ( build graphs with similar design as recommended in Jetpack Navigation)

In case it should work like graph,
i should have NavigableCircuitContent for each graph?, then both will be under CircuitCompositionLocals
Or should i build another "circuits" under that, as building graphs under NavHost in Jetpack Navigation?
because i want to be able to navigate to destinations between graphs..

In Addition, I would like to hear from the community, and creators of Circuit a recommendation for set up navigation for scaleable app, i'm pretty sure that in Slack you have already faced coupled of challenges when you design the library, and also implement it in the app.

Important to note that I really like to watch your episode with Jetbrains - Talking Kotlin

Thanks for your response:)

[shaharKeisarApps]

@ZacSweers I have looked for some examples for implementing navigation, and I have also watched the talk with Coding with the Italians—Circuit—Android App Architecture Masterclass with Zac and Josh from Slack(really like that you note the navigation part at the end.)

I have understood it much simpler than I thought,
Basically, for setting a new nested flow of screen, I should just set NavigableCircuitContent with backstack.

Currently, I'm starting that new flow like a regular screen.
Now I'm going to continue with understanding the benefits of setting a specific circuit for each flow.
and to check if there is another way to start a new flow (NavigableCircuitContent), unlike now, when I'm using a regular screen setup (presenter + UI) to host that flow.

The most important part is to say thanks to everyone who worked on that great framework. Our team decided to use that in our new app, and we hope to give it some "presents" back:)