You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing app navigation was not designed to have the nested nav graph as default. So, it requires more effort to implement a new navigation for the authentication flow, such as Splash, Login, or Sign Up. Normally, we should have 2 nested graphs: onboarding & main; then, we can easily navigate to the main graph after authenticating.
Solution
Define a "MainNavGraph" (and also "OnboardingNavGraph" later) nested graph between AppNavGraph (AppNavigation) and the app screens as default to improve the app navigation logic. The final app navigation structure will look like this:
Why
The existing app navigation was not designed to have the nested nav graph as default. So, it requires more effort to implement a new navigation for the authentication flow, such as Splash, Login, or Sign Up. Normally, we should have 2 nested graphs:
onboarding
&main
; then, we can easily navigate to themain
graph after authenticating.Solution
Define a "MainNavGraph" (and also "OnboardingNavGraph" later) nested graph between
AppNavGraph
(AppNavigation) and the app screens as default to improve the app navigation logic. The final app navigation structure will look like this:Who Benefits?
Developers
The text was updated successfully, but these errors were encountered: