simple-stack-ftue-sample VS android-template

A simplified variation can be seen in this repo, a LiveData variant with Jetpack stuff can be seen in this repo, my issue with this sample is that as there is no input + debounce + filter + async data load example in it, there is no switchMap (and even for combineTuple, I can use my other helper validateBy here), and those would be key to understanding the difference in terms of expressibility and power...

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

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