Native vs hybrid vs web mobile Application Application Development For mobile Devices

Download Native vs hybrid vs web mobile Application Application Development For mobile Devices

Post on 23-Dec-2015




1 download

Embed Size (px)


<ul><li> Slide 1 </li> <li> Native vs hybrid vs web mobile Application Application Development For mobile Devices </li> <li> Slide 2 </li> <li> Slide 3 </li> <li> Hybrid apps </li> <li> Slide 4 </li> <li> HTML5 VS Native app all hybrid apps developed with cross-platform HTML5 wrapped in a native container. They were not built from scratch in platform-specific languages like Objective-C or Java. Pure HTML5 web apps cannot appear in app markets like the iTunes App Store or Google Android Market, but these apps can because they have that native wrapper. This wrapper also gives these apps access to native capabilities like the camera, microphone, contact list, or notification system that are off limits to the browser. </li> <li> Slide 5 </li> <li> BrightCove AppCloud HTML5 CSS3 JAVASCRIPT </li> <li> Slide 6 </li> <li> A primary reason that many companies are not already jumping on the HTML5 bandwagon is the belief that HTML apps cannot access native device features. Indeed, pure mobile web apps (i.e., those that run in the browser not hybrid ones) are currently restricted in their access to features such as the camera, microphone, address book, and so forth. And while there is work in progress at the W3C to allow web apps to access such device services, mobile browsers do not currently provide such functionality a key requirement for many innovative mobile apps. access such device services </li> <li> Slide 7 </li> <li> Access to device features is not the only difference between hybrid apps and mobile web apps. Another important difference is that hybrid apps are mostly distributed through app stores: You dont browse to a hybrid app you download and install it. </li> <li> Slide 8 </li> <li> What is hybrid app(html5) A hybrid app is a native, downloadable app, that runs all or some of its user interface in an embedded browser component. To the user, a hybrid app is almost indistinguishable from a native one: it is downloaded from the app store or marketplace, it is stored on the device, and it is launched just like any other app. But to developers there is a huge difference, because instead of rewriting the app from scratch for each mobile OS, they write at least some of their application code in HTML, CSS and JavaScript, and reuse it across devices </li> <li> Slide 9 </li> <li> How the web app and native app work offline </li> <li> Slide 10 </li> <li> PhoneGap Nasrullah </li> <li> Slide 11 </li> <li> PhoneGap PhoneGap is opensource mobile development framework to build mobile application using javascript,HTML5,and CSS3. The resulting application will by hybrid Neither it would be native nor it is web based. </li> <li> Slide 12 </li> <li> PhoneGap is an open source platform that allows you to create cross-platform mobile applications with HTML, JavaScript, and CSS In order to interact with device hardware, PhoneGap provides a JavaScript API that will interface with features such as the on-board camera, GPS, and accelerometer </li> <li> Slide 13 </li> <li> Supported platforms PhoneGap currently supports development for the operating systems Apple iOS, Google Android, HP webOS, Microsoft Windows Phone, Nokia Symbian OS and RIM BlackBerry </li> <li> Slide 14 </li> <li> WHY PHONEGAP Mobile development is a mess. Building applications for each device--iPhone, Android, Windows Mobile and more--requires different frameworks and languages. One day, the big players in mobile may decide to work together and unify third-party app development processes. Until then, PhoneGap will use standards-based web technologies to bridge web applications and mobile devices. Plus, because PhoneGap apps are standards compliant, theyre future-proofed to work with browsers as they evolve. </li> <li> Slide 15 </li> <li> Appache software foundation 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. Through the ASF, future PhoneGap development will ensure open stewardship of the project. It will always remain free and open source under the Apache License, Version 2.0. </li> <li> Slide 16 </li> <li> Titanium Titanium provides a single platform for building native, hybrid and mobile web apps and is the first mobile application platform to combine the flexibility of open source development technologies with the power of the cloud through Appcelerator Cloud Services. </li> <li> Slide 17 </li> <li> Web developers become mobile developers overnight. Single platform for building rich, connected apps Get to market 70% faster than developing in Objective-C or Java. Unlimited extensibility for best-of-breed capabilities. </li> </ul>