1.) AndroidViewModel gets android.app.Application by design, so Jetpack's authors didn't intend to make it "android-independent"

2.) I've never seen an androidx.lifecycle.ViewModel re-used on a different platform, so while you can technically wrap the NavController in the Activity-scope with your own "Navigator" interface, it's not strictly necessary at all.