Brief Idea of PhoneGap Framework – Good and Bad Points

March 10, 2014
Left Inverted Comma PhoneGap is one of the remarkable mobile development frameworks, enables software programmers to develop mobile applications using JavaScript, HTML5, and CSS3. This framework has uncountable advantages along with some disadvantages, let’s see what they are. Right Inverted Comma

Brief Idea of PhoneGap Framework

PhoneGap is one of the most popular frameworks for cross-platform development based on HTML/JavaScript. It allows developing application for seven mobile platforms. There is uncountable number of articles written by native developers or front-end developers to share their views. This helps us to know what is good or bad about this framework, considering the real field of activities. However, there are many developers, who actively participating to PhoneGap development and studying the subtleties of this cross-platform framework.

No universal solution is available in cross-platform development or in native development. Some of you know that everything depends on the software project. To know whether PhoneGap should be selected as the platform for the project or not can only decides through these subtleties. One can get PhoneGap’s cross-platform capabilities through many ways like:

A native project is created, distinctive for each platform that includes a browser as the main component. With this browser, one can simply display HTML/JavaScript code as a usual web page. The part of a file server is acted by the file system of this process to provide access to the page. Moreover, an object is available that enables PhoneGap for standardize the access to native features of mobile devices that runs the supported OS like accelerometer, contacts, camera, compass, etc.

If you are not finding the default API is appropriate then PhoneGap Plugin API is there to write code for you that implements the lacking functionality. Such types of codes are written on the native programming languages specific to each peculiar platform. Generally, a PhoneGap project comes with four functional parts that makes sure the execution of the HTML/JavaScript code:

  • file storage, which contains HTML, JavaScript, and other web resources of the application.
  • structured API for accessing the native functionality of a mobile device from JavaScript code;
  • a native browser (webView), embedded in the project;
  • API for writing native plugins;

As a result, one can simply build a service-oriented, single-page HTML-5 application using PhoneGap. According to some calculation, about 99% of PhoneGap development is lay-outing and JS-coding with consideration for the environment peculiarities and browsers. At the time of PhoneGap development, one must have to consider the specificity of each platform, it’s a default browser.

When it comes to architecture and optimization, this framework is very demanding. Much time spend on the project as users interface has to be optimized for each platform. Previously, some experts touched upon the issue of PhoneGap and found out four major problems like DOM structure optimization, the 300 millisecond lag, the problem of touching, and long lists while developing a responsive app on PhoneGap. Looking at such problem, we come to know about the negative side of PhoneGap.

To conclude, every framework has positive as well as negative side, it doesn’t mean framework is not good for your development task. One must have to solve such minor problems and develop the best cross platform application.

Back to Top