Re: ISSUE-6 & ACTION-239 ... User Interface Issues for Mobile Browsing

This made it to the list's administrative address, but not to the
list....
-- 
Thomas Roessler, W3C  <tlr@w3.org>





On 2007-09-12 08:18:12 +0000, Luis Barriga (KI/EAB) wrote:
> From: "Luis Barriga (KI/EAB)" <luis.barriga@ericsson.com>
> To: public-wsc-wg-request@w3.org
> Cc: tyler.close@hp.com
> Date: Wed, 12 Sep 2007 08:18:12 +0000
> Subject: Re: ISSUE-6 & ACTION-239 ... User Interface Issues for Mobile Browsing
> X-Spam-Level: 
> Old-Date: Wed, 12 Sep 2007 10:15:38 +0200
> X-Diagnostic: Already on the subscriber list
> X-Diagnostic:  37 tlr@w3.org                         32757 tlr@w3.org
> X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.1.5
> 
> Here is a proposal to add to the use cases document addressing
> ISSUE-6 on mobile browsing aspects . Also, I have used as input
> previous contribution from Jan on ACTION-239 plus other material
> previously posted here. 
>  
> comments? suggestions?
>  
> Luis
>  
> 
> 6.3.2 Smartphone
> 
> 
> The user agent in a mobile brower differs from the desktop
> counterpart due to several mobile-specific context factors:
> 
> *	Screen: a small, limited color viewing area
> 
> *	Navigation input: keyboard, stylus or pointing device
> 
> *	Small keyboard pad:  on-screen keyboard and predictive text technology e.g. T9
> 
> *	Tactile feedback: vibration
> 
> *	A/V interfaces
> 
> Users also interact with the user agent in a different way due
> other mobile-specific factors are traffic cost-awareness, slow
> connection speed and trust in mobile network infrastructure.
> Alltogether, these factors influence how the security indicators
> are presented to the user by different smartphone mobile
> browsers. 
> 
> Our findings show that the visible part of the chrome has fewer
> options and overlaps with the phone menus. Also, obtaining
> secondary security information is cumbersome requiring several
> clicks. Due to lack of screen space, only the padlock is shown,
> but the URL is partially shown, if at all. Favicons are often not
> displayed, not for security reasons but due to limited screen
> size. The password management function is not always supported in
> all phones. In some cases, the accessed web pages have a modified
> look and feel to simplify browsing in a small screen size, but
> this may create suspicion among security-aware users e.g. in
> mobile shopping. Mobile browsers don't use consistent terminology
> to warn about the same security situation. Revocated certificates
> are rarely checked since it generates air traffic. Some root CA
> certificates commonly found in desktop browsers are not
> provisioned in mobile browsers leading to non-comprehensive
> messages for sites that users have previously visited on
> desktops. Large pages that do not fit in the phone's RAM can
> cause unexpected UA behavior on security indicators.
> 
> -----Original Message-----
> From: Close, Tyler J. [mailto:tyler.close@hp.com <mailto:tyler.close@hp.com> ]
> Sent: den 30 augusti 2007 01:39
> To: Luis Barriga (KI/EAB)
> Cc: Thomas Roessler; Mary Ellen Zurko
> Subject: RE: ISSUE-6: User Interface Issues for Mobile Browsing
> 
> Hi Luis,
> 
> If you'ld like to take a stab at writing a summary for the Note,
> that would be great. Perhaps the summary could be an expansion on
> the section at:
> 
> http://www.w3.org/2006/WSC/drafts/note/Overview.html#smartphone <http://www.w3.org/2006/WSC/drafts/note/Overview.html#smartphone> 
> 
> Thanks,
> Tyler
> 
> -----Original Message-----
> From: Luis Barriga (KI/EAB) [mailto:luis.barriga@ericsson.com <mailto:luis.barriga@ericsson.com> ]
> Sent: Wednesday, August 29, 2007 2:03 AM
> To: Thomas Roessler; Mary Ellen Zurko; Close, Tyler J.
> Subject: FW: ISSUE-6: User Interface Issues for Mobile Browsing
> 
> I think we agreed that this contribution would be somehow
> incorporated into the use cases, but there were two ways forward.
> 
> The original proposal was to write a short intro text and a
> reference to the wiki (see emails below). But, if I recall
> correctly, another proposal was to summarize the findings and put
> then in the document. Which one was agreed?
> 
> Let me know how we proceed with this. I can certainly help with
> what is needed.
> 
> Luis
> 
> -----Original Message-----
> From: public-wsc-wg-request@w3.org [mailto:public-wsc-wg-request@w3.org <mailto:public-wsc-wg-request@w3.org> ]
> On Behalf Of Luis Barriga (KI/EAB)
> Sent: den 16 juli 2007 17:05
> To: Thomas Roessler
> Cc: Mary Ellen Zurko; public-wsc-wg@w3.org
> Subject: RE: ISSUE-6: User Interface Issues for Mobile Browsing
> 
> 
> 
> Thomas>> Nice one. I wonder if we can incorporate this one and then
> consider ISSUE-6 closed?
> 
> Probably not (yet). This scenario was the second half addressing
> ISSUE-6. The first half was a description of some findings that
> were suggested to add to section 10.1.1. See my email from July
> 3.
> 
> http://lists.w3.org/Archives/Public/public-wsc-wg/2007Jul/0028.html <http://lists.w3.org/Archives/Public/public-wsc-wg/2007Jul/0028.html> 
> 
> We still need to agree whether that can be incorporated too.
> 
> -- Luis
> 
> -----Original Message-----
> From: Thomas Roessler [mailto:tlr@w3.org <mailto:tlr@w3.org> ]
> Sent: den 11 juli 2007 14:11
> To: Luis Barriga (KI/EAB)
> Cc: Mary Ellen Zurko; public-wsc-wg@w3.org
> Subject: Re: ISSUE-6: User Interface Issues for Mobile Browsing
> 
> On 2007-07-03 20:02:13 +0200, Luis Barriga (KI/EAB) wrote:
> 
> > ------8X------8X------8X------8X------8X------
> >
> > While on the move, Alice suddenly remembers she has to make an urgent
> > banking transaction. She has used her mobile browser previously for
> > retrieving information from the web, but this time she decides to use
> > her phone due to the urgency. She starts her mobile phone browser and
> > enters a URL that she recalls having seen on her home desktop browser.
> > After some delay, longer than usual, the phone starts showing a page.
> > Due to screen size, Alice notices that the layout is somewhat
> > familiar, but still not the same as the one in her dekstop. She can't
> > see the full URL either. Alice scrolls and spots the link that takes
> > her to the transaction page and clicks on it. After some delay, the
> > phone displays a page asking her to enter her usual bank credentials.
> > How is Alice to know that her bank credentials can be safely entered
> into the page?
> >
> > Destination site
> >     no prior interaction, known organization
> >
> > Navigation
> >     typing
> >
> > Intended interaction
> >     submission of sensitive information
> >
> > Actual interaction
> >     submission of sensitive information
> >
> > ------8X------8X------8X------8X------8X------
> 
> Nice one.  I wonder if we can incorporate this one and then consider
> ISSUE-6 closed?
> 
> Cheers,
> --
> Thomas Roessler, W3C  <tlr@w3.org>
> 
> 
> 
> 
>

Received on Wednesday, 12 September 2007 11:35:10 UTC