The Big Decision: Phonegap vs Native
Phonegap vs Native, I’ve pondered this a lot
When I first started app development, I was not sure whether to go with Phonegap, Mono (since I do a lot of C# development), or Native coding.
I dropped Mono early on. It is expensive and seems to rely on the inability of people to learn new languages (and it requires the inclusion of a fairly large runtime).
So that left the decision of Phonegap vs native coding for app development.
After nearly a year of app development with dozens of apps created, here are my views.
When Phonegap wins over Native
I’ve been fascinated with Phonegap ever since it came out a few years ago. I have a least a dozen projects that I started in Phonegap while exploring the functionality and what you could do with it. It fascinates me because it gives developers the opportunity to use an existing skill set and build applications which can be used on all devices.
If I had my way, I would do all apps in Phonegap.
And, despite being able to write plugins for Phonegap in native code, there are still a lot of things that Phonegap cannot do. For example, you cannot show a live camera feed (but you can have an app open the video recorder and get the image).
But, in my opinion Phonegap is ideal
For a lot of the apps I see out there, Phonegap would be ideal. Most of our apps have needed the hardware to such a degree that HTML5 was not suitable. Ear Spy, for example, relies so heavily on hardware that it just didn’t make sense to try and create an html5 interface with plugins connecting to native features.
However, if your app is primarily an information app (or social media or whatever) without a lot of intensive use of hardware, Phonegap would be an ideal choice.
In a battle of Phonegap vs native code, you should really use native if performance require it. So, really, you should go native for games and hardware intensive apps.
Are you using Phonegap? If so, I’d love to hear how you find it. What do you think? Phonegap vs Native– which is better? Let us know.