voyager VS Appyx

If I were to start a project right now, I'd use https://github.com/adrielcafe/voyager although, it doesn't support Web Canvas or iOS yet I don't think.

Voyager has some bugs (apparently SavedStateHandle doesn't work and the PR is open since Nov 24), Appyx is nice but I hear it's laggy (but honestly, everything in Compose is laggy all the time, so if you use Compose, that's pretty standard tbh), I don't know enough about Navigation-Reimagined to tell you, Compose-Destinations is a codegenerator over Navigation-Compose so you drag in Accompanist-Navigation to have basic screen transitions which is pre-alpha tech.

Voyager

https://github.com/adrielcafe/voyager/issues/42 open since January

Yes, I've checked (it doesn't). I've also read AndroidScreenLifecycleOwner's source code, and I don't see a way for it to ever go to the ON_PAUSE state.

Using any of the 5 prominent community alternatives is a better approach (even though most people hoping to use the docs as if it was like, written for stable code, will muck around with their apps crashing if the user inputs a & symbol). I have this thing but I'd consider taking a look at https://github.com/adrielcafe/voyager or maybe https://github.com/olshevski/compose-navigation-reimagined

So it doesn't matter that I have a simpler one, for Navigation-Compose, I say "i don't care what you use as long as it's not Navigation-Compose", you could even use https://github.com/adrielcafe/voyager and it's a much more solid option.

Appyx https://github.com/bumble-tech/appyx

The idea was good, the execution had some issues. I hear bumble-tech/appyx wants to implement the same idea, but without the design oversights of RIBs.

Although technically you're not wrong. You can use Appyx which works as you said https://bumble-tech.github.io/appyx/