Mobile phones and mobile web interfaces

Lately I have been playing a bit with various fat client applications for my Nokia e61i. I have been comparing the features and ease of use offered by the default Symbian S60 clients (and other vendor supplied "thick client" applications) with those offered by the service providers mobile web interface (if they have one?!).

I am talking about applications which use the web as a main focus and resource E.g. - email, IM, Twitter, Internet search and RSS to name a few.

I am trying to figure which approach is the best for me. I am also concerned with how easy it is to go between using my mobile and a laptop or desktop computer. I realise the experience is always greater on the laptop/desktop but I was out to test whether the fat client mobile approach is better than the web mobile interface/client.

I am basing my thoughts, not on any one application/website in particular, but more on the ease of use for me on my humble mobile device. I am looking for the best solution between the mobile client and the web interface on a mobile device.

Things that are against the fat client approach include:

  • The time it takes to fire up one of these applications.
  • The resources chewed up on the phone.
  • How easy/fast it is to flick between applications.

Things for the fat client approach include:

  • Integrated into the phone so you know it will be there and *just* work.
  • Provides an integrated approach between applications and information portability. E.g. Taking photos and sending them directly via email all works easily as the pre-installed apps all talk to each other.


Things that are against the web interface:

  • You need to be connected to make it work at all
  • The current cost in being connected and using data can be expensive if you are not careful.
  • The speed is sometimes a little slow depending on the connection you have.

Things that are for the web interface:

  • Everything you do is live and replicated to every source every time you use it - instantly
  • Sites which are designed to cater for mobile web are fast and easy to use
  • All performed in the one place on the phone - no need to have multiple applications running at the same time (although I can if I want too, iPhone users :-p)

So what if I access them all through the built in web browser and the WiFi connection. I can quickly flick between "bookmarks" for the services which I am interested in and these days as the service providers are becoming savvy enough they are providing mobile specific web interfaces which are cut down graphically. This provides a fast load time and zero load on the phone web browser.

So I think I have a tendency to leaning towards the web interface and access (on a 3G/NextG device). If this is the case then I would stick to the *cloud* for all my mobile web interface. Although I am still struggling internally (in my head) with the *fat client's* doing everything you need (albeit not as attractively - to look at) as the web interface and there being a some vendors who are failing in the mobile web market.

Looks like I will be using both methods for a while to come.....or maybe the Google phone will change all this???

PS - This is a repost after my hosting provider had a server crash and lost the last one

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Copy the characters (respecting upper/lower case) from the image.