How stupid is it to use `androidx.navigation:navigation-compose:1.0.0-SNAPSHOT` I do want to avoid ...

# compose

[jaqxues]

How stupid is it to use androidx.navigation:navigation-compose:1.0.0-SNAPSHOT

I do want to avoid Fragments, but I do not want to rewrite it every day because its a snapshot

[Afzal Najam]

Only use it if you're okay with the API changing really fast.

[Ian Lake]

You'll see API changes through each alpha too, just like with other Compose artifacts. It is always your choice to upgrade though (whether it is by updating the build ID for snapshots or your Compose alpha version for actual releases)

[jaqxues]

Lets hope there is an alpha soon enough for compose-navigation. Not entirely comfortable with using a snapshot and the snapshots repo

[Ian Lake]

It is the same bits of code either way - alpha builds are just locked in stone to a particular build ID 🙂

[Ian Lake]

But I get where you're coming from

[jaqxues]

Managing repositories with build ids is sth I only want to do for testing purposes, not the kind of fun I want to actually use lol

[Ash]

We don't mind the APIs changing as we get the app ready for the Play Store, as long as the long term API surface is getting better :-)

[Sam]

are there some non-trivial examples for navigation-compose yet?

[Ian Lake]

Generally that happens after the alpha comes out, not before 😛

[Ian Lake]

The demos are probably the closest you'll get to up to date examples of how to put the pieces together: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:navigation/navigation-compose/integration-tests/navigation-demos/src/main/java/androidx/navigation/compose/demos/