Home | History | Annotate | Download | only in webapps

Lines Matching full:application

7 users in two ways: in a traditional web browser and in an Android application, by
11 <p>There are essentially two ways to deliver an application on Android: as a
12 client-side application (developed using the Android SDK and installed on user devices as an {@code
13 .apk}) or as a web application (developed using web standards and accessed through a web
16 <p>The approach you choose for your application could depend on several factors, but Android makes
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
25 <p>Thus, your decision to develop a web application for Android can exclude consideration for
29 <p>Another great feature of Android is that you don't have to build your application purely on
31 application that embeds some web pages (using a {@link android.webkit.WebView} in your Android
32 application layout). Figure 1 visualizes how you can provide access to your web pages from either
33 a web browser or your Android application. However, you shouldn't develop an Android
34 application simply as a means to launch your web site. Rather, the web pages you embed in your
35 Android application should be designed especially for that environment. You can even define an
36 interface between your Android application and your web pages that allows JavaScript in the web
37 pages to call upon APIs in your Android application&mdash;providing Android APIs to your web-based
38 application.</p>
49 <p>To develop a web application for Android-powered devices, you should read the
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
68 <dd>A list of practices you should follow, in order to provide an effective web application on