MWI Team Blog

Dispatches from members of the W3C Mobile Web Initiative Team

Categories: Current state (32) | Developing Countries (15) | Events (20) | Looking forward (13) | News (42) | Technical (33) |

W3C Mobile Web Initiative - what's next? — 10 May 2008

During W3C's bi-annual member meeting, I presented a few slides on where we see the Mobile Web Initiative going in the future - copied below.

We'd be interested in your feedback, so see question at end.


Mobile: Where do we stand?


MWI: Where do we stand?

Screenshot of mobileOK checker


Future Priority: Mobile Web Applications


Future Priority: Mobile Web in Developing Countries

Man with mobile phone in Asia.  AFP, Deshakalyan Chowdhury

Future Priority: Improving Standards Compliance and Testing

Screenshot of Web compatibility test

  • No "dominant browser" in mobile
  • Non-standards compliance even bigger problem for developers than on desktop
  • W3C work has started
    • Test harness simplifies testing Web specs on mobile device, 45K results collected via "crowdsourcing"
    • Web compatibility test to check "difficult" feature support (ACID inspired)

But of course, the mobile community is bigger than just W3C members ...

So, where do you see the mobile Web going in the next few years?

And what do you think should be the contribution of W3C's Mobile Web Initiative?

Share your thoughts below!

by Philipp Hoschka in Looking forward, Current state 1 comment Permalink

Comments, Pingbacks:

Comment from: Vadym Kramar [Visitor] · http://www.pbol.org
Boundaries between different types of mobile devices are so uncertain at these days. Quite many devises from wrist watches till Linux/Windows-enabled desktop replacements may be considered as mobile. Just their browsers are different. It may happened that the principles that are applied today to the mobile devices may become to be valid (to some extend they are already valid) to devices with conventional browsers. But even the devices with conventional browsers may be of vast variety of types, forms, form-factors, input controls and output interfaces. For example, refrigerator control touch-panel, intelligent hose control touch-panel, in-sauna entertainment screen, LCD TV connected to HTPC or DVB reseiver – they all may be served by full-scaled Lunux PCs and have Mozilla Firefox browser installed. But how different are their controls and interfaces!

An extended user agent profile may not be sufficient enough to help in handling several content presentations available from the same URI. Even more, there may be a need to get more than one content presentation to the same user agent based on certain user preferences. For example, one may like to see in his browser a simplified GUI (let’s say pretty much similar he can see in his phone’s browser) of his online bank account rather than complicated GUI of the entire online bank portal – just by following to the same URL.

These all may remind a concept of a Virtual Home Environment – the same look and feel regardless of place, time and device particularities. At the same time these questions are closer to an activity scope of the UWA Working Group. And their Delivery Context Ontology may serve well for those purposes. Still, some work could have been done to extend the principles of MWI Working Group quite behind the mobile domain.
PermalinkPermalink 2008-05-13 @ 11:42

Contacts: Dominique Hazael-Massieux