4. What problem are we trying to solve?
• Each device has a different native development SDK and
associated programming language
• For a variety of reasons, it may not be feasible to build
and maintain multiple native apps
• How can we reach all these different devices and app
stores?
4
6. What is the solution?
• Build your application using web standards like HTML5,
CSS3, and JavaScript.
• But what about accessing other features of the device,
such as the camera or contacts list?
6
7. What is PhoneGap?
“PhoneGap is an HTML5 app platform that allows you to
author native applications with web technologies and get
access to APIs and app stores. PhoneGap leverages web
technologies developers already know best... HTML and
JavaScript.” - phonegap.com
7
8. PhoneGap and Nitobi in the News
• In October 2011, Adobe acquired Nitobi enabling the team
to focus solely on the PhoneGap project and continue its
work on efficient expressive design and development
across devices.
• The PhoneGap code was contributed to the Apache
Software Foundation (ASF) under the name Apache
Callback in October 2011. It is currently under incubation
until it can become a full Apache project.
8
16. Phonegap Plugins
• Moving toward “everything is a plugin” model
• Core “plugins” included by default
• New plugins can be added / developed in a consistent
way
– JavaScripts
– Native bridging for each platform e.g .java
• Source Code
– https://github.com/phonegap/phonegap-plugins
16
20. Debugging
• Weinre
– Debugger for web pages
– Designed to work remotely
– Debug web pages on a phone
• Availability
– http://debug.phonegap.com/
– http://phonegap.github.com/weinre/
20
22. html5expense walkthrough
• Phonegap 1.1.0
• jquery Mobile
• Camera API
• “Stopgap” for portability
• PhoneGap build for native builds
– Also created native projects so we can do local builds
• Weinre for remote debugging
• “Hydra” for dynamic update capability
22