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

Design Android Tool bar with constraint layout

 Toolbar in Android plays a very important role in quick page movement.  Steps to implement toolbar in Android 1. Create a layout file toolbar.xml in r es/layout directory 2. add below code into your toolbar.xml file. 3. Customize this as per your requirement <? xml version ="1.0"  encoding ="utf-8" ?> <layout xmlns: android ="http://schemas.android.com/apk/res/android" xmlns: app ="http://schemas.android.com/apk/res-auto" xmlns: tools ="http://schemas.android.com/tools" > <androidx.appcompat.widget.Toolbar android :id ="@+id/toolbar" android :layout_width ="match_parent" android :layout_height ="?attr/actionBarSize" android :background ="@color/colorPrimaryDark" app :elevation ="0dp" app :layout_collapseMode ="pin" > <androidx.constraintlayout.widget.ConstraintLayout android
Post a Comment
Read more

Building Phone Gap App for Windows Phone 8

Before you start  developing an phone gap based App you need to keep following things in your mind. General Practice: Set any controls height and width always in term of percentage. Same should be applied with Div. Don't use margin at all. Use margin only to give spacing with controls- 5 px - 20 px Design a parent page.Only this page should contain head and body tag. Other layout should only contain div. After that only Remove and Append Div based on the required layout. Use boot strap to provide a web-responsive feature to your application Above practice will help you building a nice android and IOS application. but in-case of windows application same application won't work as it is. Things to take care in Phone Gap based Application. All append function will start throwing security Exceptions Use the following tag around your append code. MSApp.execUnsafeLocalFunction( function () { var body = document.getElementsByTagName( 'body' )[0]; body
Post a Comment
Read more