Still maintained?

[quentin23soleil]

It seems issues are growing and we had no new release since June 5th, which makes me believe this library is not maintained anymore. If so, it might be good to disclose it on the readme and/or archive it.

[YoussefHachicha]

yap this is concerning

[nvkleban]

Agree, at least some level communication from maintainers on what are the plans, is it still maintained or not, would be very helpful.
I've asked in June in the discussion if any help needed with any specific part, still no answer.

[akardas16]

Even the basics are broken. There is still no one who cares about this library

[acmpo6ou]

I agree, I wanted to contribute to the docs, I wanted to improve the grammar. And, I saw there was an open discussion about it already, but there was no activity. It does seem like the devs are very busy with personal life stuff or something.

[Deorigami]

Time to move on guys, Use Official navigation from Jetbrains

[Deorigami]

me myself planning on migration

[quentin23soleil]

the devs are very busy with personal life stuff or something

and that'd be totally fine and understandable obviously. And they've helped the community so greatly I'm really grateful, I didn't mean this issue to sound anything near unpleasant.

[Syer10]

New beta is out 😄 https://github.com/adrielcafe/voyager/releases/tag/1.1.0-beta03

[nvkleban]

I received a response from the maintainer, and I hope he don’t mind me sharing it here.

Me: Hi! My name is Nick, I’m Android Developer and active user of the Voyager. I really appreciate you work on this library, but the question that I and other users have - is Voyager still supported, is there any plans on it?
It seems the original maintainer is no longer interested in this project, and you probably don’t have much spare time too.

DevSrSouza : Yeh, that is the case most of the time I don't have spare time to it, honestly my mind have not being very good this last months, but I still look for Voyager when the time comes. So it is still supported. But because I'm currently the only maintainer, I kinda shift what I would be focusing, so, in practice, what I have being focusing is the Core of the library, make sure is Extensible and work as expected. This means that, extensions that we have like TabNavigator, BottomSheetNavigator, etc, I don't have enough time to focus, so we let the community build their on implementations.
At the new docs, we move it to github, we appreciate every type of contribution, even docs. We have a page focus on community projects that is extending voyager and a FAQ that contains links to some snippets to try out, for example, Swipe Back on iOS. But this APIs, if I would put into the library, it come with a cost of maintaining and implementing very well, and honestly, because I don't have much spare time currently, I can't put this so asked APIs inside the library. But I guarantee to have enough API in Voyager Core Navigator to you be able to extend and implement it easily.

[acmpo6ou]

@nvkleban It's pretty sad there is only one guy working on this, I wish more people could help out maintain this. Otherwise the library is gonna be stagnating.