&lt;number&gt; So to summarize, let’s look at all 3 development approaches compared to each other. Native excels in performance and device access, but suffers in cost and updates. Web is much simpler, less expensive, easier to update, but is currently more limited. Hybrid provides a middle ground, which in many situations is the best of both worlds – especially if you’re targeting multiple operating systems. Which should you choose? That really depends on your specific needs. There isn’t a single approach that works for everyone. So to provide you with a few more tips that will help you decide, I’d like to transfer the microphone over to Jonathan - who will examine the approaches from a business perspective, and discuss how they fit into the bigger picture of defining the mobile strategy of your organization.

3.
Overview

An open-source mobile development framework for
building cross-platform mobile applications with
HTML5, CSS3 and JavaScript for Smartphone /
Tablet

4.
Overview
 UI,
Logic, and Communication with server is
based on HTML5/CSS3/JavaScript
 PhoneGap provide the JavaScript API that
allows Your JavaScript Code to access to the
device features
 Communicate and Control the device is
based on the Native Language, e.g. Java,
Object-C

9.
Feature
 Accelerometer

Enables the application to sense change in the
Device’s Orientation
 Camera

API
API
Allows the application to retrieve a picture from
either the Camera or fetch the images from
already existing Photo Galleries

12.
Feature
 Notification

Allows the application to notify the user by making
a Sound, Vibration, or Alert
 Storage

API
API (as HTML5 ?)
Provides a Built-in SQL database for the
application
 The
features of PhoneGap Overlaps the
features of HTML5?!

31.
jQueryMobile Integration
 Access
cross-domain pages from within a
PhoneGap application is controlled by two
key things…

$.support.cors


Set to True to tell $.ajax to load cross-domain pages
$.mobile.allowCrossDomainPages

Set to True to $.mobile.loadPage() to allow crossdomain requests and wrapping this in a mobileinit
event handler

32.
PhoneGap Plug-in
 JavaScript
has certain inherent limitations
when implementing complex processing and
background work
 Plug-in is an extension of the PhoneGap
feature
 In order to write plug-in for each platform, you
have to write two parts


Native Code that does the heavy lifting
JavaScript Code that expose this native code

34.
Advantages
 Faster
to develop across platforms basically, code once and distribute to multiple
platforms
 Its also easier to develop the UI and logic if
you have experience in web development

35.
Disadvantages
 Distributing
it to multiple platforms is not as
seamless as they'd like you to believe
 Your application will look the same across all
platforms
 Generated code is not as efficient as natively
authored app, so performance is not as great
 You do not get access to the full range of
features offered by native SDKs

37.
Conclusion
 PhoneGap
was called by the name Apache
Callback, but now Apache Cordova
 Say goodbye to SDKs, Compilers and
Hardwares

Upload your code package to the PhoneGap
Build Service and get back app-store ready apps
for various mobile devices
 Q&A