Phone Gap

By,
Deven

Building applications for each device–iPhone, android, Windows Mobile & more–requires different frameworks & languages. Phone Gap solves this by using standards-based web technologies to bridge web applications & mobile devices. Since Phone Gap apps are standards compliant, they’re future-proofed to work with browsers as they evolve.

Phone Gap includes two main aspects which include:

·   The web solved cross platform.

·   All technology deprecates with time.

 The web has been the most convincing solution to reach many devices of different with respect to capabilities. C is the only technology that deserves the title but even then, there be dragons there. HTML, CSS, & JavaScript, for all the respective quirks, have reached critical mass. This is in no small part due to the incredibly low barrier for authoring web technologies. Anyone, at anytime, can publish any thing from any where.

With this in mind, we knew hitching our wagon to any one horse could have disastrous consequences. Of course this is not absolute. Some technologies span many years to the profit of the specialist. As technologists, it is our responsibility to remain present & aware of change. Whether we act is the choice. The consequences of not acting could be witness to a technology replacing our own.

Two High level goals with phone Gap

·   The web network as a first class development platform.

·   The ultimate purpose of Phone Gap is to cease to exist.

The web is decidedly not a first class development platform: opaque introspection, blunt tools, poor API surface area & a rather limited set of GUI elements. The web has host of other problems or features, such as the sandbox & many missing APIs which need addressing. In short, the web as a platform is at a disadvantage, & the poly fill those gaps with Phone Gap.