I agree, reloading the webview (thus most probably loosing the current navigation state) wouldn’t be great. Displaying an error message would at the very least give some useful feedback to the user, as opposed to a plain white view.
Of course this is not enough, we need to understand where the app consumes so much memory that it gets killed by the system, and if that can be avoided.
I agree, reloading the webview (thus most probably loosing the current navigation state) wouldn’t be great. Displaying an error message would at the very least give some useful feedback to the user, as opposed to a plain white view.
Of course this is not enough, we need to understand where the app consumes so much memory that it gets killed by the system, and if that can be avoided.