Jetpack-Navigation-Multistack-Example VS android-template

If you DON'T actually rely on the multi-stack behavior (1 stack / tab) then there is no need to use NavigationExtensions (personally I wouldn't use them even if I needed that, because the implementation is a bit wonky; you can do more reliable code manually.)

See this sample for auth / conditional navigation then pretend that "ProfileFragment" is the fragment in this sample

I am managing multiple backstacks with Jetpack Navigation just fine in this example https://github.com/Zhuinden/Jetpack-Navigation-Multistack-Example/tree/master/app/src/main/java/com/zhuinden/jetpacknavbottomnavfragmentexample 🤔

maybe this example will help you with understanding better. It does exactly what you want using listener which is invoked whenever fragment is changed, and arguments (passed from navigation graph unless conditions are needed)

Fragment based

Introducing - android template by u/skyyoo_

Wanted to share a template repository which I've been using extensively for past year or so. Who doesn't know how what's the benefit of a template project - you can find the description here. It's opinionated, but is very flexible I believe. It contains a bunch of branches for bottomNavigation, protoStore etc. It has CI setup using GitHub actions. Also there's some opinionated code style guides, and general code advices, mostly those which are really easy to miss unless you had recent experience with them, great memory or already have your checklist. Recently I've completely ditched the Groupie and started using compose inside fragments. Repository link: https://github.com/Skyyo/android-template

You might want to use templates. This will reduce the priject setup time drastically. This example covers typical combinations. Also some usefull code style (subjective) and general advices. https://github.com/Skyyo/android-template

you might find this example interesting