Skip to main content

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.








Comments

Post a Comment

Thanks for your Comment

Popular posts from this blog

How to build an Android based phone gap application which supports all android Version?

As all we know, the very  first purpose of development of a phone gap based application is to support as much as platforms possible using a single code base. Though phone gap uses simple HTML, javascript and CSS, but Is it still enough to build an application which supports all android platforms. If you are using a phone KITKAT or LOLLYPOP based android phones for development, suddenly you will realize that your application  is not Jellybean and lower version. All Lists and buttons etc etc have gone Hayward. So How to correct this problem? Phone Gap has solve this problem in their very recent release using some crosswalk plugin.  Makes your Cordova application use the  Crosswalk WebView   instead of the System WebView. Requires cordova-android 4.0 or greater. Benefits WebView doesn't change depending on Android version Capabilities: such as WebRTC, WebAudio, Web Components Performance improvements (compared to older system webviews) Dr...
Post a Comment
Read more

Basic understanding of Android Fragments and its State

What is Fragment and why did it come into existence? Fragment is one of the highly used class/component in the current mobile and Tab application development. Its has increased the development and usability up to a right scale.   Android introduced fragments in Android 3.0 (API level 11), primarily to support more dynamic and flexible UI designs on large screens, such as tablets. Because a tablet's screen is much larger than that of a handset, there's more room to combine and interchange UI components. Fragments allow such designs without the need for you to manage complex changes to the view hierarchy. By dividing the layout of an activity into fragments, you become able to modify the activity's appearance at runtime and preserve those changes in a back stack that's managed by the activity. For example, a news application can use one fragment to show a list of articles on the left and another fragment to display an article on the rig...
Post a Comment
Read more