I have navigation graph like this: - A ◦ B ...

# compose

[Marko Novaković]

I have navigation graph like this:
• A
◦ B
◦ C
B, C are inside of a nested graph.
C should always pop to B.
from A user can navigate to both B and C.
how to achieve A -> C -> B -> A?

point me to a right place to ask this question if this is not right channel

[Stylianos Gakis]

By "A -> C -> B -> A?" you mean "A -> C (press back button ->) B (press back button ->) A?" here right?

Have you tried when you navigate to C to also just navigate to B at the same time? What does that look like?
So going from:

onClick {
 navController.navigate(C())
}

to this:

onClick {
 navController.navigate(B())
 navController.navigate(C())
}

[Marko Novaković]

yes but that seemed weird, so I thought there is maybe some other way

[Stylianos Gakis]

Weird as in the animation looks wrong, or just that the code looks odd?

[Marko Novaković]

code

[Ian Lake]

Multiple calls to navigate is exactly how you add multiple things to the back stack, so that code is correct (you'll note our processing of deep links does the same thing to build up its synthetic back stack)

[Ian Lake]

What is weird is injecting a screen that users haven't seen in the back stack as part of your normal app user flow, so I'd look into doing some user research to understand if what you are proposing is expected by users at all or if the whole UX needs to be rethought.

[Marko Novaković]

thank you very much.
I also think that it’s weird but that is what our UX came up with 🤷‍♂️.

[Stylianos Gakis]

You can always argue against what your UX people say if things feel too weird from your perspective as an experienced developer. Sometimes you'll notice that they don't have a good reason for what they do, and when questioned take back such odd decisions 😄

[Marko Novaković]

yes, sure. I think that they made the best decision for this flow.
it doesn’t make 100% sense in theory but when using it it feels good