Preface
Almost nobody reads past the first sentence or two of a preface, so I’ll say the most important thing right away: this book is about programming Chrome Apps, not Chrome Extensions or web apps in general.
Still here? There’s some more important stuff to know, so please continue.
Chapter 1 explains in detail what a Chrome App is, but briefly, its relationship to Chrome is the same as a Windows app to Windows, or a Mac app to OS X: an app that you install on the platform and that makes use of application program interfaces (APIs) unique to that platform. This would be obvious but for the fact that the platform in this case, Chrome, is better known as a web browser and most of the “apps” that you run on it are really just fancy web pages. I’m thinking of Gmail, Facebook, Amazon, and a zillion others. Hence the confusion.
Why consider programming a Chrome App at all? Here are two good reasons:
- They’re portable across all of the major operating systems: Windows, Mac OS X, Linux, Chrome OS (for Chromebooks and Chromeboxes), and, with some restrictions, even Android and iOS.
- Although web apps are equally as portable, they can’t access the local computer as Chrome Apps can. The most important example of this is that Chrome Apps can access the computer’s filesystem, just as native apps can.
I’m unable to think of any other platform that offers these two advantages.
With the good comes the not-so-good. Here are the chief disadvantages of Chrome Apps:
- On desktop operating systems, they ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access