android-template VS kotlin-android-template

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

This happened to me all the time when I wanted to create a new project on my own and it's something that should have a solution to improve the development speed. That's why I researched on the internet and found some examples about it like this. There were plenty of it but no one fit for me since most of them were oriented to use MVP and I'm more into MVVM. That's why I decided to create my own template on github