That makes Phonegap a hybrid-framework because it would allow the applications to be build using a mix of native and web technologies. “Brilliant!” you may say.
How does PhoneGap actually work ?
- rapid testing and deployment
- reusable code
- support for enterprise and Cloud Services
- easy deployment
- easy access to many plugins that can plug into other services.
So why PhoneGap usage is still disapproved by some developers?
Firstly, you have to take into consideration the fact that in case of highly intensive graphical applications PhoneGap will not offer a good performance. A native app is faster than a mobile web app.
Another big disadvantage is the lack of the pre-build user-interface widgets and standard controllers. Therefore you will spend a great amount of time only to make the application look native.
Also a PhoneGap app can occupy more memory than a native app, moreover the memory will grow in time because web developers will not have direct control over objects in memory.
The biggest misconception about PhoneGap is that it does everything for you. The truth is that it only offers you the base of your app. Access to device features like camera, contacts list and others are provided. Additionally packaging the app is also supported. The look and feel is simple and does not resemble Android or iOS.
PhoneGap may reduce your development time offering a one size fits all solution. At the moment the framework is lacking a few things as there still does not exist any ‘magic’ framework that replaces the original look and feel successfully on every device. You can deploy on almost any device but it won’t be a native app. If you really need something that offers the native experience maybe you should be willing to spend some more time and opt for native. PhoneGap does the best it can to provide a cross-platform solution.