The document discusses PhoneGap and Apache Cordova, highlighting the difference between them, with PhoneGap being an Adobe-specific implementation. It emphasizes Cordova's role as an application container that allows access to native phone features through a JavaScript API and plugins. Additionally, it mentions Adobe's development of extra tools for PhoneGap within the Creative Cloud ecosystem.

1. PhoneGap
JavaScript for Mobile Apps

2. What’s in a Name?
• There are two hard things in computer
science: cache invalidation, naming things,
and off-by-one errors
- Phil Karlton + Martin Fowler
• Adobe Bought the PhoneGap Name!

3. Cordova & PhoneGap
• Apache Cordova is the engine
• api, libraries, underlying tools
• Adobe PhoneGap is an implementation
• Adobe is also building extra tools just for their
implementation
(like Webkit vs Safari or Chrome)

4. Cordova is an
Application Container
• Native Application
• .ipa for iOS; .apk for Droid; .xap for Win
• Use’s OSes native browser toolkit
• yay Webkit! (could be old, though)

5. Cordova Provides a
Starting Template
• Put your JavaScript in “www” dir
• awesomeness note: make “www” a separate git repo
and include it here as a submodule!

6. Cordova Provides a
JavaScript API
• Access to Native Phone Features
• Or build your own as Plugins
• like for accessing the Apple GameCenter
• native file (obj-c, java, etc) + javascript wrapper
• a bunch of common plugins at
github.com/phonegap/phonegap-plugins

7. Adobe is Building Out
PhoneGap Build tools are part of Creative Cloud