• Binary executable files on the device.
• Can access all API’s made available by OS vendor.
• SDK’s are platform-specific.
• Each mobile OS comes with its own unique tools
and GUI toolkit.
Native Apps: Diversity
* IBM, Native, web or hybrid mobile app development, 2012. IBM Software
Thought Leadership White Paper
Different tools, languages and distribution channels associated with
leading mobile operating systems
Native Apps: Pros & Cons
Easy low-level hardware
Easy access to high level
services important to
Full use of all
modern mobile devices
have to offer.
Code Reusability : Low
consuming & expensive.
Designers are required
to be familiar with
different UI components
of each OS.
Upgrade flexibility: Low.
Hybrid Apps: Intro
• Combines native development with web
• The web app runs inside a thin wrapper native
• The wrapper native app uses the OS API’s to
create an embedded HTML rendering engine
which provides a bridge between the browser and
• The communication between web app and native
Hybrid Apps: Skills needed
Additionally you need to refer hybrid frameworks API
Scenario: If you need to access camera, you need to
framework and how to use it
Hybrid Apps: Pros & Cons
Flexibility of web apps
combined with feature
richness of native apps.
Poorer user experience
as compared to native
Access to advanced
Is Hybrid Apps Suits You?
• Want to target multiple mobile platforms
• Need faster time to market
• Want to take advantage of device capabilities like
geolocation, accelerometer or the camera
• Want the app to be useable when the device is
• More dynamic content which needs to be loaded
from remote service
• Don’t need the advanced graphics performance
that you can only get from a native app
Challenges: Cross Platform Compilation
• Even hybrid apps need compilation
• Your operating system might not support some
platform specific compilations
– E.g. To compile iOS app you need a Mac PC/Laptop
– Use cloud services
• E.g. Apache PhoneGap Cloud Build