While the WebView seems like an odd control to have in a mobile app, it continues to serve a variety of purposes, such as automating a login process in the background, viewing internal web pages, or even having an API based content management system providing HTML, and needing to be rendered on the mobile app. It’s a control I never like using, but one that seems to seep into many projects, due to API’s limitations on authentication or as a way to render easily changeable content.
In this series are several posts about many things you can configure, to make your life easier.
If you want to use Refresh or GoBack, you will need to extend the WebView control to make it accessible in your ViewModel.
Debugging the WebView
You can actually debug the WebView, via Chrome from your Desktop to an emulator or real device. This process is fantastic at debugging certain issues.
WebViews normally share cookies with your HTTPClient, with the exception of Android, which needs some extra help. This post goes through how it is shared and how to clear cookies from the shared Cookie Container.
Rendering Engine Configuration