Integration with AAC Navigator

[AlexisQapa]

Hi, as part of the new JetPack along with android architecture components Google released a navigation component (https://developer.android.com/topic/libraries/architecture/navigation/). While the java part seems quite close to what Alligator does, there is a XML/UI integration with features like deep links. (I don't care much about the XML thing but the way it's allow you to build flows with deep links is convenient)

So I'm wondering :

• is there is something to do to make this new component works great with alligator ?
• will you maintain alligator while google will push people to its navigator ?

[aartikov]

Hi. Thank you for these topical questions.

In my opinion Alligator and AAC Navigation have too different conceptions to mix it together. Alligator operates with screens, AAC Navigation - with destinations and actions. AAC Navigation has a navigation graph, Alligator does not. Even fragment management is different. I don't use standard back stack of fragments.

I don't want to stop maintaining of Alligator. I use it in my projects, and it fits my needs perfectly. If other developers find my library useful, it is an additional motivation for me. AAC Navigation is in alpha stage now, there are plenty of bugs and missing features. Of course Google has enough resources to polish it. So we will have one more option to choose soon.