5342f65aa8
remove the overview page, remove a bunch of stuff from the doc about screens and refer to external docs instead, and add tips about debugging on 4.4 w/ dev tools. Change-Id: I1fadb7cdf6fee469dc41a1f4e2dc2daf1fde52d1
50 lines
2.8 KiB
Plaintext
50 lines
2.8 KiB
Plaintext
page.title=Web Apps
|
|
|
|
@jd:body
|
|
|
|
<div class="figure" style="width:327px">
|
|
<img src="{@docRoot}images/webapps/webapps.png" alt="" />
|
|
<p class="img-caption"><strong>Figure 1.</strong> 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 WebView in the layout.</p>
|
|
</div>
|
|
|
|
<p>There are essentially two ways to deliver an application on Android: as a
|
|
client-side application (developed using the Android SDK and installed on user devices in an APK)
|
|
or as a web application (developed using web standards and accessed through a web
|
|
browser—there's nothing to install on user devices).</p>
|
|
|
|
<p>If you chose to provide a web-based app for Android-powered devices, you can rest
|
|
assured that major web browsers for Android (and the {@link android.webkit.WebView} framework)
|
|
allow you to specify viewport and style properties that make your web pages appear at the proper
|
|
size and scale on all screen configurations.</p>
|
|
|
|
<p>Figure 1 illustrates how you can provide access to your web pages from either
|
|
a web browser or your your own Android app. However, you shouldn't develop an Android
|
|
app simply as a means to view your web site. Rather, the web pages you embed in your
|
|
Android app should be designed especially for that environment. You can even define an
|
|
interface between your Android application and your web pages that allows JavaScript in the web
|
|
pages to call upon APIs in your Android application—providing Android APIs to your web-based
|
|
application.</p>
|
|
|
|
<p>To start developing web pages for Android-powered devices, see the following documents:</p>
|
|
|
|
<dl>
|
|
<dt><a href="{@docRoot}guide/webapps/targeting.html"><strong>Supporting Different Screens from Web
|
|
Apps</strong></a></dt>
|
|
<dd>How to properly size your web app on Android-powered devices and support
|
|
multiple screen densities. The information in this document is important if you're building a web
|
|
application that you at least expect to be available on Android-powered devices (which you should
|
|
assume for anything you publish on the web), but especially if you're targeting mobile devices
|
|
or using {@link android.webkit.WebView}.</dd>
|
|
<dt><a href="{@docRoot}guide/webapps/webview.html"><strong>Building Web Apps in
|
|
WebView</strong></a></dt>
|
|
<dd>How to embed web pages into your Android application using {@link
|
|
android.webkit.WebView} and bind JavaScript to Android APIs.</dd>
|
|
<dt><a href="{@docRoot}guide/webapps/debugging.html"><strong>Debugging Web Apps</strong></a></dt>
|
|
<dd>How to debug web apps using JavaScript Console APIs.</dd>
|
|
<dt><a href="{@docRoot}guide/webapps/best-practices.html"><strong>Best Practices for Web
|
|
Apps</strong></a></dt>
|
|
<dd>A list of practices you should follow, in order to provide an effective web application on
|
|
Android-powered devices.</dd>
|
|
</dl> |