A modern programming language that makes developers happier.

kotlinlang

The navigation-compose new typed route feature is cool :cool::sunglasses:. However, I found the API is not friendly for `dinamyc` routing. By dynamic I mean, I don't know the number and the types of my routes upfront the App starts. It will be provided from an `app-config.json` file at build time or from Firebase configuration, launchdarkly etc.
How are others dealing with dynamic routes setup?

Have them all there, and dynamically not use some of them if that version of the app doesn't want to.

Keep in mind that the graph is meant to be all possible routes - whether you actually use them all as part of your business logic (choosing a v1 route vs v2 route based on an A/B test) is up to you

But yes, the reason the string route APIs aren't deprecated is because they are still exactly what you need for a runtime, server side generated navigation graph if you really want to go down that direction - in that world, everything is runtime anyways

Ah great, I kinda guessed that was the API approach but wanted some community confirmation. 
I am pretty glad to hear the String routes API remains untouched :pray::+1: