Is this project abandoned? about flow HOT 4 OPEN

Probably because they went over to use reactive workflow + state machine bindings, which replace the key manager in this thing. Also if state machines manage the current state, then backstack logic moves there.

It's just a hunch. But you can check out https://github.com/Zhuinden/simple-stack which is created from Flow and therefore has a very similar API, and does the same thing (without the service reference counting thing).

from flow.

it's a pretty simple project, we've been using it for years as-is. Probably worth a "real" release though I can't speak to future maintenance.

from flow.

Thanks for the info. The source does seem pretty straightforward and our needs are pretty simple. @Zhuinden I took a quick look at your simple stack, more robust but the source seems more complicated at first glance - I'll take a longer look. At this point I'm evaluating based "what if I need to extend this lib myself"

from flow.

@rzmudzin that's odd, I am probably biased but the core functionality is the Backstack + BackstackDelegate (and the StateChanger interface), most other things are default behaviors, helpers and fluff.

The BackstackManager does the actual state persistence, that's true, so that's where some internal magic happens. Namely, what InternalLifecycleIntegration does in Flow.

from flow.