IssueTracker

Component used: Navigation Version used: 2.7.6 Devices/Android versions reproduced on: Emulator API 34

The overall issue is that a standard Material design bottom navigation is very difficult to implement with the Navigation library in Compose. At minimum I would expect documentation or a sample showing how to implement it. At best it would be nice to have an additional API to easily implement it.

Specifically, since Compose navigation uses deep link logic under the hood, when navigating to a destination that can be reached from multiple tabs, the route that navigation library uses to get to that destination is based on which route was added to the graph first (basically indeterminate), rather than searching within the current graph.

See this link for another description of the problem: https://stackoverflow.com/questions/77307862/jetpack-compose-how-to-navigate-from-many-bottom-tabs-to-one-screen.

The workaround is to manually keep track of the parent graph context by constructing unique routes including the parent destinations in the route string. I call this a workaround because:

• documentation doesn't mention this strategy
• it seems to me this is something better handled by the library
• not tracking this information as the default means a large refactor as soon as you have one destination you want to reach from multiple graphs.
• for developers who are used to navigating by destination id, this is an unexpected new limitation of the navigation library.

Here is a sample app describing the issue: https://github.com/Chozzle/sample-compose-tab-nav