Forum Nokia Web Talks - One web?? Your thoughts?

Use cases are different

widianuser

More than engineering, mobile services are about user psychology when runtimes and browsers improve. It is true that you can use the same services with your desktop and mobile, but will you be happy as a user when you do that? In desktop environment you have high speed connection, large screen, keyboard, mouse, comfortable chair, cup of coffee and relaxing music playing at the background when you browse the wonders of the internet. In mobile environment it is raining, you have phone in one hand and screaming child on the other and you must get an answer to a specific question quickly - when does the bus leave?

I've tried to open discussion on topics like this on my site, mobilitics.net.

//Harri

Context optimized

jsmanrique

It is not about mobile optimized but context optimized (user, device, environment, ..). Of course, devices are getting more powerful, but AJAX is making them consume more battery, and the screen won't be bigger than my hand... Sometimes I use mobile versions of some sites in my N810 and sometimes I use the 'desktop' version, it depends on the context (at home, at bus stop, ...), so that's one of the main advantages of 'one web' defined as "optimized context aware information", and that's reason W3C has a W3C Mobile Web Initiative working in things like "Device Description", "Delivery Context Ontologies"...

TeaShark

tote_b5

Hi,

I've stumbled upon TeaShark (http://teashark.com/index.html) recently. They're doing the same as Opera Mini, but a bit differently. One of the 'bits' is that they use WebKit on the server side (http://www.russellbeattie.com/blog/opera-mini-has-competition-but-who-is-teashark) to render the pages so that it always fits to small screens comfortably. Of course, the client app is Java-based and will run on many phones including feature phones.

I think if something makes 'one web' closer in the near future then it must be rather TeaShark than the Google Reader.

Tote

One web

neil.bellamy

If designers, writers and other content producers create compliant code, it can be rendered appropriately by whichever interface it's user has chosen to employ, without recourse to specific optimisation.

The next problem is that (to pick a couple of names from a hat) Adobe and W3C will have very different ideas of what standard code looks like, requiring each user to install a plethora of software interfaces geared to various types of information.

Perhaps emphasising the benefits of appropriate standards and encouraging cross-proprietary solutions would help ?