@Stylianos Gakis
Hi there.
• yes, it reteint nav history by storing it in the
rememberSaveable
via own saver. !WARNING! backstack stored via savable yet DATA-store logic base on storeMode and might be lost during process death, see doc, it is explaind in there
• predictive back - cant say for 100%, it uses default back handler for android, custom for jvm and nothing for iOS. We may take a look into this direction, just create featureRequest.
• all savestates rememberSavable are restored, using
storeageMode = Savable
will also retain all nav args/results - see doc
• deeplink itself is about to alterate backstack, we just letting you alterate it as you want, so you free to use any kind of deeplinks logic. EG: deeplinkg smth/catalog=1&item=2. You can parese is as you want and just alterate backstack smth like
pseudocode:
navController.alterateBackStack{
clear()
add(CatalogScreen, CatalogData(id=1))
}
navController.replace(DetailScreen, DetailData(id=2))