The mobile web has changed dramatically the past 6 years. Not so long ago , low speed (GPRS), small screen mobile devices on mobile networks accessed the internet with minimal functionality via the WAP protocol. It seems ages to me when during my university Thesis I was researching ways advancing and bringing the real Internet to the mobile device without sacrificing any functionality - all efforts led to the development of WAP 2.0 and advanced mobile web browsers.
Old browsers where rendering the web on a small phone screen and the end user experience was pathetic. We should remember how unsuccessful WAP proved to be due to the poor user experience.
Some "old generation" browsers are the following:
- Unwired Planet's - UP.Browser (later renamed to Openwave)
embedded browser in : Ericsson, Motorola and Nokia handsets - Bluelark,
- i-mode
- PalmScape
- Pocket Internet Explorer
From a user perspective, things like advanced Web with Flash, or even worst, fast JavaScript execution, were simply impossible. Users were frustrated and unsatisfied since they were accustomed to desktop browsing.
Things started to change gradually and nowadays, after 6 years, wireless devices are much more powerfull, i.e. the Apple iPhone, the Nokia N95 8GB, the HTC Touch HD and finally the Google Android G1, have comparable functionality to a low-end PC.
The web evolved to Web 2.0 with many services existing in the "cloud". Current devices need to have advanced functionalities in order to keep up with this new web trend. Simple web 1.0 is not enough anymore. Users request to have their web 2.0 PC experience on the mobile, anytime anywhere.
This new need transformed the small handset devices to larger screen mobile computers with high resolution screens, advanced imaging capabilities and broadband connectivity (WiFi, 3G, HSDPA, WiMAX).
These capabilities have introduced the opportunity for a mobile web 2.0 experience. The enabler here is once again the mobile browser.
Today's mobile browsers include:
- Apple's - Safari, (MAC OS)
- RIM's - Blackberry browser, (RIM)
- Google's - Chrome Mobile, (Linux)
- Nokia's - S60 broser, (Symbian OS)
- Microsoft's - Internet Explorer (WM)
- Mozilla's - Mobile Firefox (Linux & WM)
- Opera's - Opera Mobile (Linux & WM)
- Palm's - Blazer,
- Obigo browser (all OSes)
The two basic modules current browsers consist of are:
- An interface: for displaying the web content
- A rendering engine: handles user inputs and turns HTML, XML, JavaScript plus other code into user understable content.
WebKit, is an open source engine that is used by many as a mobile and PC rendering engine i.e:
- Nokia's S60 browser
- Apple's Safari browser
- Google's Chrome
- Internet Explorer Mobile,
- Opera's Presto
- Mozilla's Gecko
Mozilla is also working on competing technologies like their TraceMonkey, scheduled to appear in Firefox 3.1.
Thin-client browsers
These browsers are less-functional browsers and can be used by older less powerful phones, allowing them to run a rich Web experience.
By running the rendering and other CPU intensive processes on server farms, a representation of the website that the device could not run on its own is send to the mobile client. Data compression techniques are also used in order to increase rendering performance as well as safe handset battery life.
several vendors are offering thin-client browsers some of which are:
- Opera's - Mini browser
- Skyfire's - Skyfire
- Bitstream's - ThunderHawk



