| Scott Main | 50e990c | 2012-06-21 17:14:39 -0700 | [diff] [blame] | 1 | page.title=Web Apps |
| Scott Main | 50e990c | 2012-06-21 17:14:39 -0700 | [diff] [blame] | 2 | |
| Scott Main | 08810efc | 2010-10-11 15:37:14 -0700 | [diff] [blame] | 3 | @jd:body |
| 4 | |
| Scott Main | 5342f65 | 2013-09-10 10:54:46 -0700 | [diff] [blame] | 5 | <div class="figure" style="width:327px"> |
| 6 | <img src="{@docRoot}images/webapps/webapps.png" alt="" /> |
| 7 | <p class="img-caption"><strong>Figure 1.</strong> You can make your web content available to |
| 8 | users in two ways: in a traditional web browser and in an Android application, by |
| 9 | including a WebView in the layout.</p> |
| 10 | </div> |
| Scott Main | 08810efc | 2010-10-11 15:37:14 -0700 | [diff] [blame] | 11 | |
| Scott Main | 5342f65 | 2013-09-10 10:54:46 -0700 | [diff] [blame] | 12 | <p>There are essentially two ways to deliver an application on Android: as a |
| 13 | client-side application (developed using the Android SDK and installed on user devices in an APK) |
| 14 | or as a web application (developed using web standards and accessed through a web |
| 15 | browser—there's nothing to install on user devices).</p> |
| Scott Main | 08810efc | 2010-10-11 15:37:14 -0700 | [diff] [blame] | 16 | |
| Scott Main | 5342f65 | 2013-09-10 10:54:46 -0700 | [diff] [blame] | 17 | <p>If you chose to provide a web-based app for Android-powered devices, you can rest |
| 18 | assured that major web browsers for Android (and the {@link android.webkit.WebView} framework) |
| 19 | allow you to specify viewport and style properties that make your web pages appear at the proper |
| 20 | size and scale on all screen configurations.</p> |
| Scott Main | 08810efc | 2010-10-11 15:37:14 -0700 | [diff] [blame] | 21 | |
| Scott Main | 5342f65 | 2013-09-10 10:54:46 -0700 | [diff] [blame] | 22 | <p>Figure 1 illustrates how you can provide access to your web pages from either |
| 23 | a web browser or your your own Android app. However, you shouldn't develop an Android |
| 24 | app simply as a means to view your web site. Rather, the web pages you embed in your |
| 25 | Android app should be designed especially for that environment. You can even define an |
| 26 | interface between your Android application and your web pages that allows JavaScript in the web |
| 27 | pages to call upon APIs in your Android application—providing Android APIs to your web-based |
| 28 | application.</p> |
| 29 | |
| 30 | <p>To start developing web pages for Android-powered devices, see the following documents:</p> |
| 31 | |
| 32 | <dl> |
| 33 | <dt><a href="{@docRoot}guide/webapps/targeting.html"><strong>Supporting Different Screens from Web |
| 34 | Apps</strong></a></dt> |
| 35 | <dd>How to properly size your web app on Android-powered devices and support |
| 36 | multiple screen densities. The information in this document is important if you're building a web |
| 37 | application that you at least expect to be available on Android-powered devices (which you should |
| 38 | assume for anything you publish on the web), but especially if you're targeting mobile devices |
| 39 | or using {@link android.webkit.WebView}.</dd> |
| 40 | <dt><a href="{@docRoot}guide/webapps/webview.html"><strong>Building Web Apps in |
| 41 | WebView</strong></a></dt> |
| 42 | <dd>How to embed web pages into your Android application using {@link |
| 43 | android.webkit.WebView} and bind JavaScript to Android APIs.</dd> |
| 44 | <dt><a href="{@docRoot}guide/webapps/debugging.html"><strong>Debugging Web Apps</strong></a></dt> |
| 45 | <dd>How to debug web apps using JavaScript Console APIs.</dd> |
| 46 | <dt><a href="{@docRoot}guide/webapps/best-practices.html"><strong>Best Practices for Web |
| 47 | Apps</strong></a></dt> |
| 48 | <dd>A list of practices you should follow, in order to provide an effective web application on |
| 49 | Android-powered devices.</dd> |
| 50 | </dl> |