Hello World of The Android Mobile Web Development

This is officially my first technical article ever. Hurray. This topic strongly related with my hWorld project. In that project, I used the Android technology to develop that particular mobile application. At first, I proposed that the application should use “the smart client” model. But, I change my plan because my limited time (sorry, that’s an excuse) and the width applicable area if I use “the thin client” model. So, the first prototype of hWorld project is supposedly a mobile web application.

In order to accomplish that, I must polish my skills in this completely new things, “Developing Web Application for Mobile”. So, approximately, in the next 3 days, I hope I will master it. That’s a little too optimistic, isn’t it? Okay, I promise minimally I will master it by the end of this week. So, it is a deal, right? I will share all of my experience in learning current topic in this blog. Basically, I learn this material from the book entitled “Pro Android Web Apps: Develop for Android using HTML5, CSS3 & JavaScript”, its source code, and forums in the internet. So, this blog will literally summarize what I have learned from those materials.

Oh, this blog maybe don’t include many theory that lies behind mobile web application development. But, I hope upcoming 2 paragraphs can cover a little about the background behind it. So, why we develop a mobile web application instead of native application? We know that smartphone platform until now is monopolized by 3 (or maybe 4) big vendors. Let me say, those are Android, iPhone, Blackberry (, and WP7).When we begin developing native application, we usually determine the platform early. For example, we want to develop an application in Android. But, when our apps grow larger and larger, the problem arise. We started to think to enlarge our market by widen our apps into others platform. The answer is to make our apps cross-platform. For big company, that’s a little thing. But, for start up company, it can make our head a lot dizzier.

We also consider the area of applicability whether we use native application. When we develop a native application, even when it is cross-platformed, the mid-low end handset can’t be covered. So, some people think that it is better when we develop it based on web application development. Its nature is already cross-platform, its width coverage, and some other. But, it isn’t raw translated from desktop web application into mobile web application. There are much more adaptability involved. We consider the variety of sensors, tools, which desktop don’t have, like camera (aside of web cam), accelerometer, touch screen, call and messaging, etc. Beside of those, we also start to consider the application of HTML5 and CSS3 as the next generation of web development. So, in developing mobile web application, we will embed those two new things (HTML5 and CSS3) into. In order to enable the capability of HTML5 and CSS3, until now, the handset must use WebKit or ChromeOS. iPhone and Android browser has already been built based on WebKit. So, because I don’t have an iPhone gadget (or Macbook), I decide to develop it into Android gadget as a practice.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s