New navigation system

[michaem]

Our sample uses Jetpack Navigation. It brought some strong dependencies through whole project, such as

HomeFragment.kt
...
val navController = viewBinding.bottomNavigation.setupWithNavController(
 navGraphIds = navGraphIds,
 fragmentManager = childFragmentManager,
 containerId = R.id.nav_host_container,
 intent = requireActivity().intent
 )

or codegen into

CharactersListFragment.kt
...
is CharactersListViewEvent.OpenCharacterDetail ->
 findNavController().navigate(
 CharactersListFragmentDirections
 .actionCharactersListFragmentToCharacterDetailFragment(viewEvent.id))

It's not good decision without scalable points for projects "under Forma". And we think that will be good have some abstraction navigation layer, which will protect project structure, architecture from navigation tools dependencies, especially codegen from Navigation component.

That's why need to create own navigation system, which will be use by app presentation layer. May be after, we will think about additional navigation targets for Forma.
See here, some mind ideas how it may be look

[b1n0m13]

It's better to BackTo have field Class<Destination> instead of Destination. In that case you have no need to create such Destination with it's explicit params when you just want to go back.

[ikarenkov]

Maybe we can use cicerone? In our project we use cicerone and one more navigation abstraction for controlling screens flow

[stepango]

Done on v2 via the navigation abstraction lane:

• F-102 design: docs/NAVIGATION-ABSTRACTION.md (Layer A ports vs Layer B navigationRes)
• F-111 sample: core/navigation/api + root Jetpack adapter; feature impl/VM Nav-free
• F-112 progressive example: examples/android/12-navigation-ports

Closing as completed product work. Reopen only if a new nav engine/target is desired beyond the ports model.