A modern programming language that makes developers happier.

kotlinlang

I notice the JetNews sample uses it's own navigation ViewModel, instead of NavController and NavHost as documented here <https://developer.android.com/jetpack/compose/navigation>. The JetNews code looks easier to understand, and I'm wondering if there is a good reason to bother with NavController. I don't think it supports multiple back stacks (one per tab), which I want.

Probably just that JetNews was built before the navigation component was released for compose. I’d feel much better about the using the officially supported navigation component than a hand-rolled one.

I see the OwlApp sample uses the official nav component. I'll see if I can follow that.