Skip to content
Discussion options

You must be logged in to vote

The app manages navigation as state, using a soft fork of Navigation 3 bc Navigation 3 is not KMP compatible yet. This should be resolved with compose 1.9.

A high level overview of the navigation semantics are explained in this video.

Ultimately, it makes it easy to build out navigation for multiple screen sizes at once.

The root navigation type is a MultistackNav, managed by the NavigationStateHolder typealias. The NavigationStateHolder holds an instance of a MultiStackNav in memory, and every time it changes, it's persisted to disk in the SavedStateDataStore.

To navigate in the app, a navigation action is sent from the a ViewModel, and the ViewModel sends a navigation mutation to the Na…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by tunjid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants