All of that power comes “for free” with a web view. It gives your app a browser interface, comparable to Mobile Safari; you can just stand back and let it do its work. You don’t have to know anything about networking. Links and other ancillary resources work automatically. If your web view’s HTML refers to an image, the web view will fetch it and display it. If the user taps on a link, the web view will fetch that content and display it; if the link is to some sort of media (a sound or video file), the web view will allow the user to play it.
A web view also knows how to display various other types of content commonly encountered as Internet resources. For example, a web view is an excellent way to display PDF files. It can also display documents in such formats as Microsoft Word (.doc and .docx) and Pages. (A Pages file that is actually a bundle must be compressed to form a single .pages.zip resource.)
A web view should also be able to display .rtf and (compressed) .rtfd files; as of this writing, .rtf files are working in iOS 8.1, but .rtfd files are not. ...