Is it really solved? :D

You had to create a library just to deal with basic params during navigation, and still, it doesn't support enums, parcelables and serializables. And probably never will.

It's stupid and funny at the same time that you have to write libraries to do simple stuff that already works with Fragments. I don't say Fragments are the best, I'm just complaining that navigation-compose is worthless, at least for now.

I use compose in production and lately I removed navigation-compose from the project and added fragments.

Example of things that crash or work shitty - Try to implement an AndroidView inside Composable, like CameraX or GoogleMaps. It works if you want some basic stuff, but considering you want custom views, behaviors, animations. etc. it's gonna be a pain in the ass. It's just simpler to implement it in xml or mix xml with compose.