compose-navigationlisted

# Navigation 3 Sources of truth: [Navigation 3 guide](https://developer.android.com/guide/navigation/navigation-3) and its pages on [basics](https://developer.android.com/guide/navigation/navigation-3/basics), [saving state](https://developer.android.com/guide/navigation/navigation-3/save-state), [decorators](https://developer.android.com/guide/navigation/navigation-3/naventrydecorators), [scenes](https://developer.android.com/guide/navigation/navigation-3/scenes), [metadata](https://developer.android.com/guide/navigation/navigation-3/metadata), [animations](https://developer.android.com/guide/navigation/navigation-3/animate-destinations), [results](https://developer.android.com/guide/navigation/navigation-3/return-results), [deep links](https://developer.android.com/guide/navigation/navigation-3/deep-links), [modularization](https://developer.android.com/guide/navigation/navigation-3/modularize) and [migration](https://developer.android.com/guide/navigation/navigation-3/migration-guide); the [release notes](https://developer.android.com/jetpack/androidx/releases/navigation3); the official [nav3-recipes](https://github.com/android/nav3-recipes). Google strongly recommends a **single-activity app using Navigation 3**. In Navigation 3 you own the back stack: it is an observable list of **keys**, and `NavDisplay` renders the entries for those keys. There is no `NavController`, no navigation graph and no route strings. Core APIs are stable since **1.1**. `ResultEventBus` and t