Mobile Application Development Native vs. PhoneGap Tools Interview with Michael Crump
In this twelve minute interview with Michael Crump, iMicrosoft MVP, INETA Community Champion, and author of several .NET Framework books and articles on PhoneGap the mobile application development tools, Michael weighs in on building Mobile Application Development resources natively vs. utilizing open source tools such as PhoneGap.
[display_podcast]
Specifically we learn about:
* Building Mobile Apps with Apache Cordova aka PhoneGap – a How to Guide
* Windows Phone App Porting: Bridging the PhoneGap
* The Beauty of PhoneGap
* One App, Cross platform
* Benefits of HTML5, JavaScript and CSS3
* Free Tutorials and Downloads
* Recommendations for students and teachers
* Open Standards and Open Source Libraries – Knockout and Modernizer
* Microsoft Typescript
* Coffee Script
According to Michael, the real beauty here is that his example application built for Windows Phone, could easily be deployed to other devices. For example, if you’re developing an Android app using PhoneGap, you could simply copy the index.html and main.js from this project into Eclipse and run the same app on a different platform within minutes. It would also work for all the other platforms that PhoneGap supports.
PhoneGap uses what mobile (Web) developers already know: HTML, CSS and JavaScript. Learning the PhoneGap API rather than multiple languages is something for which most modern mobile developers would opt. At the end of the day, it’s about solving customers’ needs in a timely manner – if you have the option of maintaining only one codebase, it becomes a no-brainer.
Follow Michael on his website and blog.
More about PhoneGap
According to Wikipedia, PhoneGap (previously called Apache Callback, but now Apache Cordova is an open-source mobile development framework produced by Nitobi, purchased by Adobe Systems enables software programmers to build applications for mobile devices using JavaScript, HTML5 and CSS3, instead of device specific languages such as Objective-C. The resulting applications are hybrid, meaning that they are neither truly native (because all layout rendering is done via web views instead of the platform’s native UI framework) nor purely web-based (because they are not just web apps, but are packaged as apps for distribution and have access to native device APIs).
History
First developed at an iPhoneDevCamp event in San Francisco, PhoneGap went on to win the People’s Choice Award at O’Reilly Media’s 2009 Web 2.0 Conference and the framework has been used to develop many apps. Apple Inc. has confirmed that the framework has its approval, even with the new 4.0 developer license agreement changes. The PhoneGap framework is used by several mobile application platforms such as Worklight,Convertigo and appMobi as the backbone of their mobile client development engine. Adobe officially announced the acquisition of Nitobi Software (the original developer) on October 4, 2011. Coincident with that, the PhoneGap code was contributed to the Apache Software Foundation to start a new project called Apache Cordova. The project original name, Apache Callback, was viewed as too generic.,Then it also appears in Adobe Systems as Adobe PhoneGap and also as Adobe Phonegap Build.
Hi,
I know information about Mobile Application Development native and PhoneGap tools and i know another one thing that is JavaScript, HTML5 and CSS3 devices are used to build mobile application.This information very useful to me.
It is indeed a very big decision, choosing one option out of these two is a very big thing. Native app helps in building mobile applications with greater interface and usability, but with phonegap you get to save development time and development cost. It totally depends on the choice of mobile operating system.