Save the date! Android Dev Summit is coming to Mountain View, CA on November 7-8, 2018.

Web-based content

Figure 1. You can make your web content available to users in two ways: in a traditional web browser and in an Android application, by including a WebViewin the layout.

Android offers a variety of ways to present content to a user. To provide a user experience that’s consistent with the rest of the platform, it’s usually best to build a native app that incorporates framework-provided experiences, such as Android App Links or Search. Additionally, you can use Google Play-based experiences, such as App Actions and Slices, where Google Play services is available. Some apps, however, may need increased control over the UI. In this case, a WebView is a good option for displaying trusted first-party content.

Figure 1 illustrates how you can provide access to your web pages from either a browser or your own Android app. The WebView framework allows you to specify viewport and style properties that make your web pages appear at the proper size and scale on all screen configurations for all major web browsers. You can even define an interface between your Android app and your web pages that allows JavaScript in the web pages to call upon APIs in your app—providing Android APIs to your web-based application.

However, you shouldn't develop an Android app simply as a means to view your website. Rather, the web pages you embed in your app should be designed especially for that environment.

Alternatives to WebView

Although WebView objects provide increased control over the UI, there are alternatives that may provide similar functionality and require less configuration.

Consider using these alternatives to WebView if your app falls into the following use cases:

To start developing web pages for Android-powered devices using WebView objects, see the following documents.