OLD | NEW |
1 <h1 class="page_title">What Are Packaged Apps?</h1> | 1 <meta name="doc-family" content="apps"> |
| 2 <h1>What Are Packaged Apps?</h1> |
| 3 |
| 4 |
2 <p> | 5 <p> |
3 Packaged apps deliver an experience as capable as a native app, | 6 Packaged apps deliver an experience as capable as a native app, |
4 but as safe as a web page. | 7 but as safe as a web page. |
5 Just like web apps, | 8 Just like web apps, |
6 packaged apps are written in HTML5, JavaScript, and CSS. | 9 packaged apps are written in HTML5, JavaScript, and CSS. |
7 But packaged apps look and behave like native apps, | 10 But packaged apps look and behave like native apps, |
8 and they have native-like capabilities | 11 and they have native-like capabilities |
9 that are much more powerful than those available to web apps. | 12 that are much more powerful than those available to web apps. |
10 </p> | 13 </p> |
11 | 14 |
12 <p> | 15 <p> |
13 <iframe title="YouTube video player" width="610" height="380" src="http://www.yo
utube.com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen></iframe> | 16 <iframe title="YouTube video player" width="610" height="380" src="http://www.yo
utube.com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen></iframe> |
14 </p> | 17 </p> |
15 | 18 |
16 <p> | 19 <p> |
17 With access to Chrome APIs and services | 20 Packaged apps have have access to Chrome APIs and services not available to |
18 not available to traditional web apps, | 21 traditional web sites. You can build powerful apps that interact with network |
19 you can build powerful apps that interact | 22 and hardware devices, media tools, and much more. Here's a short list of |
20 with network and hardware devices, | 23 examples: |
21 as well as, media apps. | |
22 Here's a short list of examples: | |
23 </p> | 24 </p> |
24 | 25 |
25 <ul> | 26 <ul> |
26 <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li> | 27 <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li> |
27 <li>Music/video streaming</li> | 28 <li>Music/video streaming</li> |
28 <li>Photo/video/music editing</li> | 29 <li>Photo/video/music editing</li> |
29 </ul> | 30 </ul> |
30 | 31 |
| 32 <p> |
| 33 Watch the <a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">Chrome Apps |
| 34 Google I/O presentation</a> for an in-depth introduction. |
| 35 </p> |
| 36 |
31 <h2 id="look">How they look</h2> | 37 <h2 id="look">How they look</h2> |
32 | 38 |
33 <p> | 39 <p> |
34 When a user opens a packaged app, | 40 When a user opens a packaged app, |
35 their focus is specifically on the tasks | 41 their focus is specifically on the tasks |
36 relating to the app. | 42 relating to the app. |
37 Packaged apps have no traditional chrome: | 43 Packaged apps have no traditional chrome: |
38 the omnibox (address bar), tab strip, | 44 the omnibox (address bar), tab strip, |
39 and other browser interface elements no longer appear. | 45 and other browser interface elements no longer appear. |
40 Like native apps, they don't live within the browser. | 46 Like native apps, they don't live within the browser. |
(...skipping 61 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
102 shows how to use the powerful network and hardware APIs, | 108 shows how to use the powerful network and hardware APIs, |
103 and how to connect your app to other apps using web intents. | 109 and how to connect your app to other apps using web intents. |
104 </li> | 110 </li> |
105 <li> | 111 <li> |
106 <a href="app_deprecated.html">Disabled Features</a> | 112 <a href="app_deprecated.html">Disabled Features</a> |
107 describes the web features that have been disabled | 113 describes the web features that have been disabled |
108 and what to use in their place, where relevant. | 114 and what to use in their place, where relevant. |
109 </li> | 115 </li> |
110 </ul> | 116 </ul> |
111 | 117 |
112 <p class="backtotop"><a href="#top">Back to top</a></p> | 118 <p class="backtotop"><a href="#top">Back to top</a></p> |
OLD | NEW |