Visually Explained The PhoneGap
To attend the tech conferences, meeting with the groups, and meeting with the developers in their offices, I get more feedback from them on mobile development and PhoneGap. There are some regular questions that I am often asked, and I hope this insight can help everyone to understand PhoneGap better.PhoneGap
The PhoneGap provides, HTML content without chrome browser or the other regular web browser. You can develop your own application to take an advantage of this space, and you can develop the navigational or interactive elements and application chrome into your HTML and CSS based user interface.
The web view used by PhoneGap is the same as the native operating system. In IOS, it is an Objective-C UIWebView class, whereas; in Android, PhoneGap is android Webkit WebView. There are some differences in the web view providing engines between operating systems, and make sure that you account for this in your UI implementation.PhoneGap API
The PhoneGap application can perform on different platforms like, IOS applications; the output is an IPA file) (iOS Application Archive), Android applications; the output is an APK file) (Android Package) and Window Phone; the output is a XAP file (Application Package), etc... These are the some application packaging formats used by "native" applications, and can be distributed with the relevant ecosystems like, iTunes Store, Android Market, Amazon Market, BlackBerry App World, Windows Phone Marketplace, Etc.High-level Application Architecture Of PhoneGap
The higher level application architectures are going to differentiate in a case basis, the many data-driven applications use the following basic architecture. This application acts like a client for the user to interact with. The client connects to an application server to receive data. The PhoneGap application server can handle the business and communicates with a back-end data archive.
The PhoneGap application server is generally used as a web server (Apache, IIS, etc...) and has a server side scripting language like ColdFusion, Java, .NET, PHP, etc. This application is agnostic of back-end technologies and can work with some different application server using standard web protocols. The PhoneGap application server can perform business logic and calculations, and generally change the data from a separate data archive - this is generally called a relational database, but could be any other structure or mechanism for data endurance.
The PhoneGap applications normally do not relate directly to a database; communication is the main route to connect an application server. The application server communication can be based upon standard HTTP requests for HTML content, Restful XML services, JSON services, or SOAP (or Websockets if your OS supports it). These are the exact same techniques which are used in the desktop browser. This is based on the Ajax application.
The client-side architecture, mainly use the single-page application structure, where the application logic is inside a single HTML page. This page is never be loaded from memory. The complete data will be displayed by updating the HTML DOM, data is changed from the application server using AJAX techniques, and variables.
The PhoneGap application supports the multipage client-side application architecture, but are not recommended to others because you can drop in-memory variables, when loading a separate page.