Best Practice for Keeping Search Filter After Back, but Clearing on Bottom Navigation Tab Switch

[Egi10]

I currently have a Screen inside a Bottom Navigation. In this screen, there is a List of Data along with a Search feature. Here’s the behavior I want to achieve:

• When the user performs a search, the list should be filtered based on the query.
• If the user taps on one of the items to open the Detail screen, then navigates back to the list, the search result (filtered data) should still be preserved.
• However, if the user switches to another screen within the Bottom Navigation, then comes back to this screen, the search query should be cleared (reset).
  This is my current implementation:

private var cacheQuerySearch by mutableStateOf("")
private var isDetail by mutableStateOf(false)

init {
    lifecycle.doOnPause {
        if (!isDetail) {
            cacheQuerySearch = ""
        } else {
            isDetail = false
        }
    }
}

My Question
Is this the correct approach? Or is there a better way to preserve the search query when returning from the detail screen, but clear it when switching to a different screen within the Bottom Navigation?

[arkivanov]

I'd recommend hoisting your state in the list component, e.g. via StateFlow or BehaviorObservable, whatever you prefer. The state will be there if you navigate to another screen in the stack and then go back. You can also use InstanceKeeper to retain the state over configuration changes on Android, and StateKeeper to preserve the state over process death if you need that.

To clear the state on tab navigation you can use replaceCurrent instead of bringToFront for tab navigation, but this will be destroying all tab components, not just the list component. If this is not what you want, then you can keep using brongToFront and clear the state manually on tab navigation by calling a function on your list component.