views:

13

answers:

0

Hi,

I have an application that uses quite a bit of WebView. This can be triggered from a lot entry points in the application that brings up a generic browser activity with a WebView in it.

By doing this, i find that there is a high chance that this browser activity will be removed from the activity stack and destroyed when a user presses Back. When a user interacts with the application to invoke the generic browser activity again, it gets recreated. From this common scenario for the application lifecycle, i can see that i will lose all Javascript caches and posible image caches (i don't care about browse history).

My question is, how do i retain a copy of the WebView for reuse? What are the common ways to design an application like this? Is there a way to "hide" an activity and put it back to the top of the stack when needed?

Any pointers are much appreciated.