Lines Matching refs:to
6 <p class="img-caption"><strong>Figure 1.</strong> You can make your web content available to
11 <p>There are essentially two ways to deliver an application on Android: as a
14 browser—there's nothing to install on user devices).</p>
17 the decision to develop a web application easier by providing:</p>
19 <li>Support for viewport properties that allow you to properly size your web application
21 <li>CSS and JavaScript features that allow you to provide different styles and images
25 <p>Thus, your decision to develop a web application for Android can exclude consideration for
26 screen support, because it's already easy to make your web pages look good on all types of screens
29 <p>Another great feature of Android is that you don't have to build your application purely on
32 application layout). Figure 1 visualizes how you can provide access to your web pages from either
34 application simply as a means to launch your web site. Rather, the web pages you embed in your
37 pages to call upon APIs in your Android application—providing Android APIs to your web-based
41 applications to embed web content in their layout and bind JavaScript to Android APIs. After
43 screens), Android 2.0 added features to the WebKit framework to allow web pages to specify
44 viewport properties and query the screen density in order to modify styles
55 <dd>How to properly size your web app on Android-powered devices and support
57 application that you at least expect to be available on Android-powered devices (which you should
62 <dd>How to embed web pages into your Android application using {@link android.webkit.WebView} and
63 bind JavaScript to Android APIs.</dd>
65 <dd>How to debug web apps using JavaScript Console APIs.</dd>
68 <dd>A list of practices you should follow, in order to provide an effective web application on