Maybe some of us are still confused about ini.Apa PhoneGap PhoneGap is and what real benefits of this is the lack of PhoneGap ini.Berikut I'm going to share with my friends a little explanation of what is considered PhoneGap hell All Friends as a material in selecting the method to develop an application for Android.

As this review when I've analyzed using PhoneGap in the company where I did my analysis are used to my little bekerja.Jadi.
PhoneGap: a solution for a mobile application that is both multi-platform using HTML, JavaScript and CSS to build.
PhoneGap JavaScript API being used.JavaScript API examples:

    
JQTouch (jqtouch.com)
    
NO (joapp.com)
    
Sencha (sencha.com)
    
JQuery Mobile (jquerymobile.com)
    
ZEPTO (zeptojs.com)
Advantage:

    
Multi-platform: iOS, Blackberry, Android, WebOS, Symbian, Windows Phone and Samsung Bada
    
Use only HTML, JavaScript and CSS, we must not, in the sense that you learn Java (Android) Objective C (iOS), C # for Windows Phone, etc..
    
It is open source, the module will be developed from existing shingga many developers.
Loss:

    
Reverse Engineering The number of applications that can be used for JavaScript code that allows for the editing of the original code.
    
The existence of some phone features that are not supported by PhoneGap.
    
The following description of the features supported and not supported by PhoneGap:

    
The mobile
    
For multi-platform PhoneGap often overlooked when there is a new feature on the original platform.
    
Existing screen looks the same on all platforms, and sometimes do not seem to display such as a mobile app.
    
Many restrictions when they synchronized with iOS platform.
    
Although the result in the application of a "build once, run anywhere" applications, which is not optimal, since the original application made by native SDK.
    
The reason for this is because the application must PhoneGap javascript code menginterpret be acceptable to the native SDK, so it takes more time to run.
The following factors comparison between native mobile application with a web app:

    
User interface
    
Development
    
Skill
    
Monetization
    
Type of delivery
    
Versioning app
    
Strengths
    
Weaknesses
User interface


Issues to be considered in the selection:

    
It is a mobile application that we build requires some special features such as accelerometer devices, cameras, etc.?
    
If the application will have to be built features of mobile devices, it is advisable to many local apps.Hal is to use multiple functions in mobile web applications that do not support.

    
The budget available?
    
If the available budget may be less and applications that we want to get up to run multi-platform, it is advisable to use apps.Hal The mobile web mobile web app, in accordance with the principles of "building a once, run anywhere "

    
It is an application that requires an Internet connection built?
    
If the application is not necessary to set up an internet connection then it is always recommended to use native apps.Hal is because the mobile web apps, we membtuhkan internet connection to be able to run it.

    
It is an application that will be built specifically to create a platform or multiple platforms?
    
If the application to be built dkhususkan only one platform, it is advisable to use native apps. This is because native apps, apps built better performance than mobile Web applications that require multiple processes to run the application.

    
Any programming language that we already know?
    
If we are to build knowledge about the objective C iOS app is missing. NET to build Windows Phone and Android apps for Java, it is advisable to only use PhoneGap HTML, JavaScript and CSS can use.
So my little analysis about PhoneGap and native.Dapat conclusion that any method that we use in the development of mobile devices and kekurangan.Oleh definitely has advantages because it expects all friends of the appropriate methods to meet the needs of developing mobile applications will.