A WebView is a reusable browser component that a native application can place inside its own layout to render web content. Unlike a full web browser, it typically has no address bar, navigation chrome, or tabs; it simply displays a page driven by the host app. Android’s documentation describes its component this way: “The WebView class is an extension of Android’s View class that lets you display web pages as a part of your activity layout. It doesn’t include the features of a fully developed web browser, such as navigation controls or an address bar. All WebView does, by default, is show a web page.”
The two dominant mobile platforms each expose such a component. On Android, the class is simply named WebView, and the documentation shows it being added to an activity in XML layout or instantiated in code and pointed at a URL, with the app required to declare the internet permission to load remote content. On Apple platforms, the modern equivalent is WKWebView, the WebKit framework’s view for displaying interactive web content, which renders pages using the same WebKit engine as Mobile Safari. WKWebView was introduced in iOS 8 in 2014 as a more performant, out-of-process replacement for the older UIWebView class.
WebViews are the technical foundation of the hybrid app, an application that is packaged and distributed as a native app but whose user interface is built largely from HTML, CSS, and JavaScript rendered inside an embedded browser. Frameworks such as Apache Cordova rely on exactly this mechanism: they wrap a web application in a thin native shell containing a WebView, then expose device features like the camera or GPS to the JavaScript inside through a bridge. This let teams reuse a single web codebase across platforms instead of writing separate native applications.
The component is also used in narrower, less architectural ways. Android’s documentation lists common cases such as displaying frequently updated content like end-user license agreements or help guides, showing content that requires an internet connection, and embedding web pages designed specifically for the app. In these uses the WebView is just one screen or panel inside an otherwise native app, rather than the whole application.
The WebView sits at the heart of a long-running debate about how mobile software should be built. Because it lets web technology run inside native distribution, it blurs the line between web app and native app, and it underpins much of the cross-platform tooling that followed. It also carries trade-offs, including performance overhead, security considerations around mixing native and web code, and the dependence of in-app content on the host platform’s browser engine.