Hi Andrey!
I think on an API level, the biggest difference you’ll see is you don’t need to callback into the Activity to setup state restoration with onSaveInstanceState or onCreate, it comes for free.
You may also notice that the API is Kotlin first, and it’s very easy to grab an instance of the navigator in a Fragment with activityNavigatorController extension method.
Fundamentally, this library and FragNav use the same APIs under the hood, attaching and detaching the root fragment for each tab. It’s less opinionated however, it provides no switchTab method, and it also exposes the FragmentTransaction API should you want to perform shared element transitions and the like.
