Before iOS 9, developers spent time creating their own user interface for web browsing, which could lead to problems for users. This is the perfect scenario for the safari view controller. The majority of apps, however, just need to provide a generalized web viewing experience. You also have other affordances, such as loading files securely and using WKWebsiteDataStore for querying cookies. This approach lets you build the entire user interface from scratch.
It's the successor to UIWebView and includes several enhancements, such as utilizing the Nitro JavaScript engine. If you find your app fits into this scenario, then use WKWebView. If the extent of your user's web experience inside of your app falls into the first use case, the safari view controller is probably not what you need. In those cases, you are displaying content that you own and control, and may need to extensively customize. For this tutorial, we aren't going to focus on that scenario. The user needs to browse the web momentarily to either log in to a service or navigate a website.Īlso keep in mind that there is a third use case, web-based authentication. Viewing Websites: This is the most common scenario.Here, the user is looking at one piece of content and not doing much else. This could be a report or something similar generated from an API or server. Custom Web Content: This is content not meant for browsing.On iOS, there are two major use cases for viewing web content. Now that we know how content can be displayed, let's cover why it might be displayed in an app. Knowing when you had to use one or the other depended on the context of the presented content. While working on the demo application, we are going to use all three options. SFSafariViewController : With SFSafariViewController, you can use nearly all of the benefits of viewing web content inside Safari without forcing users to leave your app.īefore iOS 9, the first two options were the only options for developers.Custom Viewing Experience: You can leverage WKWebView or UIWebView to create a browsing experience from scratch.Safari: Use openURL(_:) to show the page inside of safari, forcing the user to leave your application.
Options for Showing Web ContentĪs of iOS 9, developers have three options to display web content to a user: The real value of the safari view controller comes from understanding when to use it and, more importantly, why.
#TWEETBOT IOS8 CODE#
As you'll see later, there really isn't much code involved with using the safari view controller. Demo Overviewīefore we begin, I'm going to lay out the approach I've taken with the demo app that goes along with this tutorial.
#TWEETBOT IOS8 FULL#
That's all changed with iOS 9 and the introduction of the SFSafariViewController class. With it, you can now provide a full web viewing experience inside your app without having to spend important development time providing it. Both of these approaches bring inherent disadvantages that were previously unavoidable.
For years, iOS developers have been charged with either creating their own web viewing experience inside their app or handing off the URL to Safari. Mobile apps and viewing content on the web are ubiquitous now.
0 kommentar(er)
