“ ) noitagivaN fo selpicnirP eht rep sAhttps://developer.android.com/topic/libraries/architecture/navigation/navigation-principles ), you should structure your navigation graph and your app around having a fixed start destination that serves as a signpost for users that the next time they hit the system back button, they'll go back to the launcher. This, in many cases, precludes the need to remove the initial start destination from the back stack. ”
“ ) egap noitagivaN lanoitidnoC tnemelpmI ehThttps://developer.android.com/topic/libraries/architecture/navigation/navigation-conditional ) explains the suggested approach where navigation destinations such as onboarding, login, etc. are something that should be launched only as needed from the fixed start destination / elsewhere in your graph rather than be used as the start destination of your graph entirely. We're working on fleshing out the Conditional Navigation page with further examples and code on how to approach this common scenario. ”