When possible, nav should move to Amper.
However, we have to wait until all build features that nav needs (like Kotlin C interop) are available (through Amper extensions) before migrating. We may also want to wait until Amper has reached the 1.0 release.
When possible, nav should move to Amper.
However, we have to wait until all build features that nav needs (like Kotlin C interop) are available (through Amper extensions) before migrating. We may also want to wait until Amper has reached the 1.0 release.