Search This Blog

01 February 2015

Hybrid application

For most of us a hybrid application is equal to a bad thing. You end up getting neither a native snappy experience, nor the comfort of changing content and style overnight like when you are using a web application.
I say it doesn't have to be that way.
If we can answer a few questions we would  know if we need a web application, native application or a hybrid application.

Do we have a web application/site which is responsive/touch friendly. (touch friendly is a term I like to use and which I will explain in a separate post, but in short by "touch friendly" I mean a web page that is easy to use on a device which uses a touch interface/screen) ?
Do we want a presence in the relevant app store of the target platform ?
Do we have the time and resources to develop a native application ?

My opinion is that hybrid frameworks like PhoneGap and even Xamarin which produces a real native code are inferior to native programming. But if you already have the content ready and made in a responsive/touch friendly web pages why not reuse some of it. And you can do that with the approach of Hybrid Framework for HTML
(available for iOS and Android. The android version intentionally does not use Java injection just to be compatible with the iOS version and to support a single API for both platforms).
With this framework you can have an application developed in native code and take advantage of the content that you already have developed in HTML/JavaScript. You don't have to develop this content again in native code/interface development tool of the platform. We use our hybrid framework as the glue which connects Java/Objective-C code to our JavaScript code. We save time and not double or triple the work for creating a content if it is already available in HTML pages. But we do take the advantage that native developers have for the platform we are developing. Lets face it HTML/JavaScript is code that is run in a browser, that is the platform of that technology.
It doesn't matter even if a great part of the application is developed in native code, there still is that bit that doesn't need to be native and makes sense to reuse or just use HTML formatting. It is good, proven technology for defining content and presenting it in a beautiful way.

No comments:

Post a Comment