We have a view (screen 1) composable with an accom...

# compose

[bharath]

We have a view (screen 1) composable with an accompanist WebView in it. We have a use case where we need to navigate to another screen (screen 2), then come back to the screen 1 with the WebView in it. We’re running into an issue with screen 1 recomposing and instantiating a WebView again. we were looking for a way to avoid reloading the WebView. I know it’s expected that screen 1 will go out of composition when you navigate away from it, but wanted to see if there are options to avoid that in this case. Please put your thoughts in 🧵

[Liangjun Sha]

Hi bharath, did you find any solutions?