Native Vs Phone gap, What to use and when and why?

Well,  Currently there are millions  of application available in app stores. In that  I would say ~10% of application are based on phone gap, remaining are native.

Looking at the application requirement  and the time slice available for you have to bring it in market, you should decide what to choose.

So, When you must choose only native development?

• If your application requires access to SYSTEM APIs, in that case its compulsory to use native.
• If you want to access of Bluetooth, file operations, storage,  running some background operations, accessing of AT commands, communications with hardware components such as LED, navigation buttons etc.
• If you are building  heavy games, running algorithms to do signal processing , image processing any such heavy operations

These are some of the glimpse of task, where you must use native. Phone gap will never ever will be able to give you support of proper libraries for any of these.

Now, It comes to Phone gap application development When and Why?

• If you don't need to use any of the above mentioned items, if you are a start up/small organization with  very limited time frame and you have to support all the mobile platform, primarily android, Ios and windows now next-.
• If you are building an eCommerce based application, online portals, banking applications, Online Education based portals, to some extends  medical application which doesn't interact with hardware but it does with cloud, social networking based application.
• Yes, When your application interacts mostly with cloud data.

This is when you should choose wisely phone gap platform.