1 <h1>Before You Start
</h1>
4 This documentation tells you how to write Chrome Apps.
5 All developers, however, should know that the new APIs
6 for Chrome Apps are being released as a developer preview.
7 This means that they are evolving daily,
8 and anything you read now might be different in the near future.
9 Please keep up to date with the API reference and documentation.
14 If you've written packaged apps before,
15 your
<a href=
"/extensions/apps">legacy packaged apps
</a>
16 will still work the way they always have,
17 but they won't have access to the new APIs.
20 <h2 id=
"common">Common platform
</h2>
23 Chrome Apps and extensions share a common platform.
24 They can access many of the same APIs and
25 they have the same manifest and permissions format.
26 If you're familiar with the
27 <a href=
"/extensions/index">Chrome Extension docs
</a>,
28 then the Reference docs should seem familiar.
29 Many of the reference docs are shared;
30 we've filtered accessibility to docs that aren't.
33 <h2 id=
"start">Where to start
</h2>
37 <a href=
"about_apps">Getting Started
</a> guide.
</li>
39 <a href=
"app_codelab">Todo App Codelab
</a>.
</li>
41 <a href=
"api_index">Chrome JavaScript APIs
</a>.
</li>
43 <a href=
"https://github.com/GoogleChrome/chrome-app-samples">chrome-app-samples
</a> and make something of your own.
</li>
45 <a href=
"https://developers.google.com/live/chrome/">Chrome Apps GDL sessions
</a>.
</li>
48 <h2 id=
"help">Send feedback!
</h2>
51 For Chrome Apps to succeed,
52 we need and want your feedback.
53 You can enter feedback at the
54 <a href=
"https://groups.google.com/a/chromium.org/group/chromium-apps">chromium-apps group
</a>,
56 <a href=
"http://crbug.com/new">official issue tracker
</a>,
57 or press
"Send Feedback" at the bottom of every doc page.
60 <p class=
"backtotop"><a href=
"#top">Back to top
</a></p>