RE: ISSUE-6: User Interface Issues for Mobile Browsing

I agree on extending 10.1, possibly with a sub-section "10.0.1 UI Issues
in Mobile Browsing" giving a very brief summary and then a link to my
contribution. But we need to agree also where to store the contribution
itself. Maybe the Wiki's DocsRepository? This is the least we should do.
 
I also think that some parts of this could be incorporated into section
"6 Use Cases". The current text is desktop browser focused with a static
user. It should be possible to capture the case when a user is on the
move and uses her phone to visit a web site to e.g. pay a bill or
retrieve some information after logging in.
 
Regarding the applicability, I think we should sync on this with
upcoming Action-239.
 
Luis

________________________________

From: Mary Ellen Zurko [mailto:Mary_Ellen_Zurko@notesdev.ibm.com] 
Sent: den 15 juni 2007 17:04
To: Luis Barriga (KI/EAB)
Cc: public-wsc-wg@w3.org
Subject: RE: ISSUE-6: User Interface Issues for Mobile Browsing



Thanks Luis. This is obviously much more useful and comprehensive than
the brief editor's note suggested when the issue was first opened. 

What do you think is the best way to incorporate this into wsc-usecases?
In other words, now's the time to propose the literal, concrete change.
My first thought is that 10.1, which currently discusses public review
expertise, can be extended to include participant expertise, and have a
pointer to this stating participant expertise in mobile browsing. I
could also see a section on the Applicability section of our proposal
template, and how mobile modalities is one being considered (either with
all this text or a pointer to it). Luis, how do you think this should be
incorporated in wsc-usecases? Tyler, as editor, other better thoughts? 

          Mez





"Luis Barriga (KI/EAB)" <luis.barriga@ericsson.com> 

06/13/2007 10:13 AM

To
"Mary Ellen Zurko" <Mary_Ellen_Zurko@notesdev.ibm.com> 
cc
<public-wsc-wg@w3.org> 
Subject
RE: ISSUE-6: User Interface Issues for Mobile Browsing	

		




Hej,
 
>> I don't quite understand what "state" means ... I imagine "context"
is ...
 
User's state means predispositions, expectations, needs, motivation,
mood, etc. Context is not only physical (like the ones you mentioned),
but also social (people surrounding the user), temporal (how long time a
user has for browsing) and task (what the user is trying to achieve).
All these impact mobile browsing.
 
>> isn't there some chrome? 
 
I meant the visible part of the chrome. There is still the possibility
of controlling the browser via button clicks.
 
>> I don't understand the "T9 feature". 
It's a predictive text (faster typing) technology (Text-on-9-keys) due
to lack of a complete keyboard.
 
Attached is a revisited version where I have considered your comments
and re-written some unclear part of the previous (inline) contribution.
 
Luis


________________________________

From: public-wsc-wg-request@w3.org [mailto:public-wsc-wg-request@w3.org]
On Behalf Of Mary Ellen Zurko
Sent: den 4 juni 2007 21:59
To: Luis Barriga (KI/EAB)
Cc: public-wsc-wg@w3.org
Subject: Re: ISSUE-6: User Interface Issues for Mobile Browsing


Thanks Luis. 

> X.1 User Interface Issues for Mobile Browsing
> 
> 
> Previous studies reveals that mobile browsing user experience is 
> affected by the user's state, context, mobile device, browser 
> application, network infrastructure, and web sites [Phone Web 
> Browsing]. Although modern mobile phones come with better 

I don't quite understand what "state" means. Can you give an explanation
or some examples? I imagine "context" is the user's physical context -
noisy, quiet, moving, walking, lots of light, home, work, etc. 

> X.1.1 Indistinguishable/Non-Existing Chrome 
> 
> 
> In desktops, there are cases when the chrome becomes blurred with 
> small windows. This issue is permanent in with phone browsers due to
> limitations in screen size. Phone browser designers have chosen to 
> give more space to content presentation, keeping the chrome 
> indistinguishable at best.

Given that "Chrome" is the entire control surface of the application:
http://www.w3.org/2006/WSC/wiki/Glossary

isn't there some chrome? If not menus, then dialogs? There must be
something that communicates "control" information. 


> X.1.2 Fewer Security Indicators
> 
> 
> Due to the small screen limitations, current phone browsers have 
> prioritized to only present security full/crossed padlock when 
> applicable. The URL bar is commonly not displayed or partially 
> displayed. Users who are familiar with the https:// <https:///>  
> prefix may become deceived by such limitation. Favicons are not
displayed.

Good that they don't display favicons :-). Plus there's seems to be a
lot of problems with relying on the "raw" URL for security anyway. 

> X.1.3 Longer time and more clicks for better security
> 
> 
> Typing username and password when entering sites is more cumbersome 
> with numeric keypads than with desktops keyboards.  The T9 feature 
> commonly available in phones is not useful since usernames and 
> passwords are normally not part of the dictionary. As a result, 
> authentication takes longer time and users and error prone.

I don't understand the "T9 feature". 

> X.1.Z Open Issues
> 
> 
> There are no studies on security usability in mobiles phones. A 
> comparative usability study is in place.

Please point us to the results when the time comes. 
       Mez
[attachment "UI Issues in Mobile Devices.html" deleted by Mary Ellen
Zurko/Westford/IBM]