In late 90s and initial few years during the last decade, developers (and the users too) used to have a confusion. If they need a software solution, for an example, invoice management system, how do they need it? An installable PC based software or a Web application? (Why don’t we ever call it as Web software?). Due to Bandwidth limitations, many of our customers preferred to get their software in PC. Some of our clients felt unsecured of using web applications.
But when years passed by, the requirements too changed. When we started working collaboratively, (which was made easy with the internet and the bandwidth growth) people slowly started moving into web based application. Web based Emails are possibly the first web applications people used. People started developing cross-browser compatible web applications. We stopped application development with VB and started focusing only on ASP and then ASP.NET. Now Web 2.o has changed the perspective of ’software’ completely. Also Hybrid applications became possible with APIs etc.
Likewise, in Mobile, there are two ways to develop Mobile applications. Mobile browser based applications – which are websites optimized for Mobile browsers and Installable or Native Mobile applications. They both has advantages and disadvantages.
Why Mobile Browser based applications and why not?
Mobile Brower based applications are slow due to the bandwidth limitations and will eat up your download limits in your plan. Also, the user need to remember the URLs, Type it which is really hard. Advantage is that the development cost is low since the developer pays additional attention only to make it compatible with most possible mobile browsers. Also now the many Mobile browsers supports HTML and the smart phones comes with bigger screens to see the full sized websites, if not by zooming it. We have keyboards too to manage this. But, if you want to browse sites, you can do that in your tiny Netbook, which you carry with you always, right?
So, In short: The advantage is the low development cost and the disadvantage is the bandwidth limitations and the limitations of Mobile websites which does not access your Phone’s components like Address book, Camera etc.
Why Native mobile applications and why not?
Native (installable) application resides in your Mobile, if you launch it, the search with parameters which are within your mobile (Eg. The 50 state names in USA, Your favorite locations to see daily weather etc). Except free text search, the rest of the search parameters can be stored in the mobile – OR they can be updated just one time. The communication between the Data/Web server and the mobile could be drastically reduced. An application like share portfolio can be created within your Phone and stored. Every day you just need to update the stock prices. You need not download the entire portfolio each day. Also, the application resides within the phone can access phone’s capability such as camera, phone book /contacts etc to and make the applications ‘Native’.
I also absorbed another hidden advantage of native application is brand loyalty. If the customer installs a mobile application which you supply, he will rely on your application. For Eg. I use Viigo for regular information updates (News, weather etc) But a site called Justdial.com or Google local for local address research. If Justdial comes with a Blackberry solution, they captured me as their user
The disadvantage is obviously the development cost. No two mobile platforms share a mobile application, and there are too many Mobile operating systems (or platforms) exist in the market. If you develop a mobile application to market it widely, you need to develop that in J2ME (for phones that support only Java with no loaded OS), Symbian, Mac iPhone, Android, RIM, WebOS( for Palm pre), LinMo and Windows mobile. Though J2ME (or Java ME) is widely used, it has the Graphic limitations and I am sure it won’t look nice in my Blackberry Bold!. If the developer do not have expertise in more than one technology, then you need to run behind various mobile developers, finding them under one roof would be difficult.
So, In short: The advantage is quick access, less data transaction and the disadvantage is the cost of development.
Hybrid mobile applications?
No, Hybrid application is not ‘going Green’ or developing applications ‘environment friendly!’
They are Applications that uses browser interfaces and native mobile components. With HTML5 and JavaScripts now the browsers are becoming capable of accessing phone’s built in features like contacts, camera etc. We started developing applications using PhoneGap and I believe solutions like PhoneGap should fill-in this gap. Platform free mobile solutions are what we need now and the gap between the browser based applications and native mobile applications is getting closure.
Finally what could be the disadvantages in hybrid mobile applications? Two things comes to my mind. Application security and learning curve for the developers. Mobile developers need to know HTML and Web developers need to know mobile phone APIs. Right? Let us see how we overcome these.
Posts
Twitter
Technorati
Delicious
StumbleUpon
BlogCatalog
Feed Agg
MyBlogLog
reddit
digg







































