W3C home > Mailing lists > Public > public-web-mobile@w3.org > September 2013

Re: Mobile, Web and Multi-device

From: Jorge Rumoroso <jorge.rumoroso@fundacionctic.org>
Date: Wed, 18 Sep 2013 12:53:14 +0200
Message-ID: <5239861A.4060106@fundacionctic.org>
To: public-web-mobile@w3.org

I agree with all comments... My opinion is that "Mobile web" is a 
concept without a clear definition but with a start point in the context 
and the way of the access to the web. The "Mobile web" is related with 
the context and with the device.

It is clear that mobile web is the web that can be access succesfully 
anywhere we want (ok, unless we practice speleology) or we need (except 
when the train goes through a tunnel :( ), including in movement 
(walking, traveling in bus, etc.). It can be used in place A, in place 
B, in place C,... and while we go from A to B to C... That kind of 
access can be make with devices easy to transport like smartphones, with 
tablets, and with the new devices that are comming (like Manrique said, 
watches, glasses, etc...).

"Mobile web" is the web that it is created (or  adapted) to be used as 
soon as the user need it, in multiple context and multiple devices (with 
or without any capability and with some enviromental handicaps), not 
when the user is in an specific situation of place and device.

Jorge Rumoroso

El 18/09/13 11:34, Patrick H. Lauke escribió:
> On 18/09/2013 10:04, Bryan Rieger wrote:
>> Users tend to interact with various sites/apps/services with whatever
>> device is at-hand.
>> They might begin an interaction with their phone only to pick it up a
>> few hours later on their laptop and eventually finish the interaction
>> on their tablet sitting on the sofa in-front of their TV. While the
>> user does indeed move from context to context, so does the
>> site/application itself - ideally maintaining the users state,
>> preferences, etc. but presenting the user with an interface that
>> makes sense in that context.
>> In this sense, it's not only the user that is mobile - but more
>> importantly the site/application as it conforms to the features and
>> constraints present in *every (device) context* the user decides to
>> interact with it.
> In a very limited, embryonic sense (minus the act of maintaining 
> state), I find that the browser tab syncing as it can be found in 
> Firefox and Chrome (strangely, Opera had a powerful sync feature for 
> ages, before all the others, but never got to the actual "tabs" sync 
> stage) is a first iteration of this concept: you're browsing something 
> on device A, then later you can pick up where you left off on device B 
> ("show me which tabs were open on device A").
> Maintaining state would be the next step, and - security and privacy 
> issues notwithstanding - can probably be achieved with current 
> technologies (as an aside, I'm always surprised by shopping sites that 
> only use a local, often cookie based, cart even when the user is 
> logged in...I often end up putting things in a cart for a tentative 
> purchase, forget about it, switch to another device, and the items 
> aren't in my cart on the second device...or the surprise of reopening 
> that shopping site weeks later on the first device and noticing that 
> the cart indicates I've stashed potential items for purchase away 
> there. Surely, for logged-in users, carts should be stored server-side 
> and synchronised across all devices?)
> P

*Jorge Fernando Rumoroso Solana*

*/CTIC-Centro Tecnológico/*
/Unidad de Accesibilidad Web y Estándares/
Parque Científico y Tecnológico de Gijón
c/ Ada Byron, 39 Edificio Centros Tecnológicos
33203 Gijón - Asturias - España
Tel.: +34 984 29 12 12
Fax: +34 984 39 06 12
E-mail: jorge.rumoroso@fundacionctic.org
http://www.fundacionctic.org <blocked::http://www.fundacionctic.org/>
Política de Privacidad: http://www.fundacionctic.org/privacidad 
Received on Wednesday, 18 September 2013 10:53:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:58:59 UTC