Another great video. Thank you

@MaximumDevelopment

Ай бұрын

Thanks for the support!

Great content. While watching and implementing can understand how the compose navigation library written for android.

@MaximumDevelopment

22 күн бұрын

Thank you! I’m glad you found it helpful.

Wow! Great video. I use Avenger for common navigation. I didn't know what you shared is supported.

@MaximumDevelopment

Ай бұрын

Thank you! It's a great time to be a multiplatform developer. There's so many excellent options available to us.

@frank4pickerson

Ай бұрын

@@MaximumDevelopment yes, love how clear you are in your explanation. So crystal clear!

what happens when you got 50 screens? we list them all in the App component?

@MaximumDevelopment

2 күн бұрын

Great question! This could warrant its own video but here are my thoughts. For starters, we could implement our custom nav graph in its own composable, and pass our state into it. This would clean up our App component, but we would still have to deal with a large, unwieldy list of screens elsewhere. We actually have this same problem with most navigation libraries. Going beyond this, we could implement a series of nested nav graphs, breaking up our monolithic graph into smaller chunks (where navigation from certain screens would branch into different graphs). This is just one possible solution. If it were my project, I would also consider how many standalone screens could be reduced to sub-screens (removing them from the graph, and handling their visibility within their parent composable). As always, there could be many solutions to this, with differing pros and cons. I’m curious how you would approach solving this. Thank you for watching, and for your thought provoking question!