Re:Let's crash the integrated browser in Facebook
by saagarjha on Tuesday March 14, 2017 @10:28AM
(#13867714)
Actually, it's not that simple. There are a couple ways to load websites on iOS:
* UIWebView: Old, slow, but dead simple.
* WKWebView: The new "WebKit" drop-in replacement for UIWebView. It uses Safari's Nitro engine, and allows for full customization for the chrome, but does not allow for content blocking. Most new apps use this.
* SFSafariViewController: A "Safari view"; you have no control over the UI chrome (or browsing history, etc.), but it uses Nitro and loads content blockers.
* Safari app: The actual app. Loads content blockers.
Re:Let's crash the integrated browser in Facebook
by rrdharan on Tuesday March 14, 2017 @10:52AM
(#13867910)
What advantage does using WKWebView provide for an app over SFSafariViewController? Is it just the ability to change the color and icons to match the rest of the app's style?
Or are apps generally switching over to SFSafariViewController? Curious to hear some iOS folks' thoughts on the matter since I'm uninformed.
Re:Let's crash the integrated browser in Facebook
by objclxt on Tuesday March 14, 2017 @11:04AM
(#13868009)
Most notably apps can inject arbitrary JS into WKWebView, making it much easier to track The user’s actions.
Re:Let's crash the integrated browser in Facebook
by chrisdroukas on Tuesday March 14, 2017 @12:04PM
(#13868685)
You can roll your own browser interface using WKWebView — if (for whatever reason) your app supplements the browsing experience, you'd use WKWebView.
SFSafariViewController provides its own Safari-like interface and has an extremely limited set of configuration/customization options.
EDIT - (thanks saagarjha) newer versions of Tweetbot appear to use SFSafariViewController not WKWebView.