Mobile browsers on most phones that are out there on the market today face main challenges, the key one is their quality of rendering, which also involves of course the memory of the handsets.
Let me sum up some facts on mobile browsers:
  1. Native browsers suck = try browsing mobile web i.e. on a Samsung handset. You use it, when you close the sliding phone, the site or download falls down with no other options, etc.

  2. New browsers are not there yet = although coming, I wrote some thought recently on the Google Chrome Mobile, read my blog for more information
  3. iPhone browsers are still not enough for  internet to be real on a handsets - most companies still optimise the mobile handsets
  4. The most spread out resolution worldwide is still 128 or 176 pixels on width, giving the user little space to be able to navigate the site
So the challenges mobile browsers will face as a result of mobile is:
  • Screen size will be limited to around 200 pixels of width = either understand it and use it, don’t try to put internet on the devices

  • Memory of the handsets are slow, they need very optimised pages = developers please be aware of this, make light pages
  • Mobile browsers need some level of JAVA script or equivalent of an easy scripting language, flashlite is not an alternative because of speed and obvious memory issues - API’s can be more widespread
Let’s see what happens and how mobile browsers will evolve - it’s a long-shot, but I just wanted to throw it in the ring for readers to follow my train of thoughts.

Tags: ,