| OLD | NEW |
| 1 <meta name="doc-family" content="apps"> | 1 <meta name="doc-family" content="apps"> |
| 2 <div id="pageData-name" class="pageData">What Are Packaged Apps?</div> | 2 <h1>What Are Packaged Apps?</h1> |
| 3 <div id="pageData-showTOC" class="pageData">true</div> | 3 |
| 4 | 4 |
| 5 <p> | 5 <p> |
| 6 Packaged apps deliver an experience as capable as a native app, | 6 Packaged apps deliver an experience as capable as a native app, |
| 7 but as safe as a web page. | 7 but as safe as a web page. |
| 8 Just like web apps, | 8 Just like web apps, |
| 9 packaged apps are written in HTML5, JavaScript, and CSS. | 9 packaged apps are written in HTML5, JavaScript, and CSS. |
| 10 But packaged apps look and behave like native apps, | 10 But packaged apps look and behave like native apps, |
| 11 and they have native-like capabilities | 11 and they have native-like capabilities |
| 12 that are much more powerful than those available to web apps. | 12 that are much more powerful than those available to web apps. |
| 13 </p> | 13 </p> |
| (...skipping 22 matching lines...) Expand all Loading... |
| 36 | 36 |
| 37 <h2 id="look">How they look</h2> | 37 <h2 id="look">How they look</h2> |
| 38 | 38 |
| 39 <p> | 39 <p> |
| 40 When a user opens a packaged app, | 40 When a user opens a packaged app, |
| 41 their focus is specifically on the tasks | 41 their focus is specifically on the tasks |
| 42 relating to the app. | 42 relating to the app. |
| 43 Packaged apps have no traditional chrome: | 43 Packaged apps have no traditional chrome: |
| 44 the omnibox (address bar), tab strip, | 44 the omnibox (address bar), tab strip, |
| 45 and other browser interface elements no longer appear. | 45 and other browser interface elements no longer appear. |
| 46 Like native apps, they don’t live within the browser. | 46 Like native apps, they don't live within the browser. |
| 47 When launched, packaged apps can open in windows | 47 When launched, packaged apps can open in windows |
| 48 that look like this (and you can style | 48 that look like this (and you can style |
| 49 your windows in all different ways): | 49 your windows in all different ways): |
| 50 </p> | 50 </p> |
| 51 <br> | 51 <br> |
| 52 | 52 |
| 53 <img src="../images/editor.png" | 53 <img src="{{static}}/images/editor.png" |
| 54 width="770" | 54 width="770" |
| 55 height="586" | 55 height="586" |
| 56 alt="Text editor packaged app in a standalone window"> | 56 alt="Text editor packaged app in a standalone window"> |
| 57 | 57 |
| 58 <h2 id="behave">How they behave</h2> | 58 <h2 id="behave">How they behave</h2> |
| 59 | 59 |
| 60 <p> | 60 <p> |
| 61 Packaged app pages always load locally. | 61 Packaged app pages always load locally. |
| 62 This allows apps to be less dependent on the network. | 62 This allows apps to be less dependent on the network. |
| 63 Once a user installs an app, they have full control over the app's lifecycle. | 63 Once a user installs an app, they have full control over the app's lifecycle. |
| (...skipping 44 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 108 shows how to use the powerful network and hardware APIs, | 108 shows how to use the powerful network and hardware APIs, |
| 109 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. |
| 110 </li> | 110 </li> |
| 111 <li> | 111 <li> |
| 112 <a href="app_deprecated.html">Disabled Features</a> | 112 <a href="app_deprecated.html">Disabled Features</a> |
| 113 describes the web features that have been disabled | 113 describes the web features that have been disabled |
| 114 and what to use in their place, where relevant. | 114 and what to use in their place, where relevant. |
| 115 </li> | 115 </li> |
| 116 </ul> | 116 </ul> |
| 117 | 117 |
| 118 <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 |