W3C home > Mailing lists > Public > public-mw4d@w3.org > August 2008

Re: Fwd: updated framework

From: Slim Amamou <slim@alixsys.com>
Date: Tue, 5 Aug 2008 15:35:41 +0200
Message-ID: <e5c98a400808050635v44ce5d13j649ac95ee33758fe@mail.gmail.com>
To: "Stephane Boyera" <boyera@w3.org>
Cc: "Renjish Kumar" <renjish.kumar@gmail.com>, public-mw4d@w3.org
On Tue, Aug 5, 2008 at 2:31 PM, Stephane Boyera <boyera@w3.org> wrote:

> (...)
> Well i might agree or disagree with you depending on what you mean by
> "support web functionalities".
> For me, there are two different things:
> - where the content is stored: on the web
> - and from where the user is accessing the content: the mobile device
> So that's our context.
> For me, mobile browsing (using a browser on a mobile phone) is just one way
> of accessing web content.
> Voice is another way to access web content on mobile phones
> Widgets might be a third option
> SMS might also be another channel of delivering web content
> Java/native applications yet another option.
> So in my view, we have ot explore all these options, the requirements on
> the devices, the strenghts and weaknesses,...

> (...)

this is the wrong point of view. It is hard to browse web content from
> mobile phones. But at the opposite you can make very easy to use web content
> or applications on mobile phones if you take into account that you are
> developing for this platform.
> This is imho the visin to take.

I totally agree here. Most mobile devices greet the user with some kind of
menu showing services available (including : contacts, sms, settings,
etc...) I think seamless integration of web apps in this menu, and generally
seamless integration in the native device user interface, is the key to
success for any service in the developing world.

Slim Amamou
Received on Tuesday, 5 August 2008 13:36:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:07:08 UTC