User Interface Concept Proposal

quaintmayoMobile - Wireless

Dec 10, 2013 (3 years and 9 months ago)

58 views

1
User Interface Concept Proposal
Contents
1 Document Information .................................................................................................... 2
2 User Interface Concept Proposal .................................................................................... 2
2.1 Description............................................................................................................... 2
2.2 Benefits ................................................................................................................... 2
2.3 Benchmark .............................................................................................................. 2
2.4 Visualize .................................................................................................................. 4
2.4.1 Hybrid mode ................................................................................................... 4
2.4.1.1 Item selection .................................................................................................. 4
2.4.1.2 Performing default item action ......................................................................... 4
2.4.1.3 Performing other item related actions .............................................................. 5
2.4.1.4 Multiselection ................................................................................................... 6
2.4.2 Touch Mode ......................................................................................................... 7
2.4.2.1 Item selection .................................................................................................. 7
2.4.2.2 Performing default item action ......................................................................... 7
2.4.2.3 Performing other item related actions .............................................................. 8
2.4.2.4 Multiselection ................................................................................................... 8
2.4.3 Switching between modes .............................................................................. 8
2.5 Localization .............................................................................................................. 8
2.5.1 Languages ...................................................................................................... 8
2.5.2 User feedback elements ................................................................................. 8
2.5.3 Hardware/key mapping ................................................................................... 8
2.6 Dependencies .......................................................................................................... 9
2.7 Exclusions ............................................................................................................... 9
3 Revision History ............................................................................................................. 9


1 Document Information
Improve Single Tap Support
Feature sponsor / Document author
Ixonos
Lead Technology Domain
User Interface
Lead Technology Domain manager
Scott Weiss
Revision number
0.4
Last revised date
30.10.2009
Development Proposal ID
<Insert ID>
Status
Draft
2 User Interface Concept Proposal
2.1 Description
The proposed change seeks to remove double tapping from Symbian^3 Platform. The S60
5th Edition touch UI uses mainly single tap inputs. There are, however, instances where
double tapping is required, which disrupts user experience.
User can interact with the touch device in two ways depending how the device is used. When
hardware keys are hidden or they dont exist in the device, mode is regarded as touch mode.
When user enables hardware keys, the input mode is regarded as hybrid mode. For example
in N97, hybrid mode is enabled by pushing the screen forward so that the QWERTY
keyboard becomes visible.
In hybrid mode, a selection is visible in lists just like it is currently implemented in 5th Edition
platform. User can move the highlight using hardware joystick, open item or use an action for
the selected element from the option menu.
User can also use touch to open an item. Double tap is removed so that single tap on a list
element will automatically open the tapped target.
The touch mode removes static highlight on lists. The highlight is shown only shortly when
user single taps a list element. Because there is no active highlight, the options menu and its
elements will be updated dynamically.
2.2 Benefits
Many users have expressed frustration and confusion about this two-tap UI model. The
inconsistency among platform applications is also an issue. For example Home screen or
Nokia maps applications use single tap to activate items, while other applications like
Contacts, Calendar, Messaging use double tapping.
On top of that, single tapping seems to become standard way to interact with applications on
majority of platforms, therefore Symbian should follow this standard in order not to confuse
users.
Removing double tapping improves user experience and removes inconsistencies among
various applications.
2.3 Benchmark
The most common platform where single tap is used is in web applications. Double click is
rarely ever used because of the way hypertext links work in most browsers. Examples are
Google Docs or Gmail.
iPhone uses single tap model for its user interface
(
http://www.youtube.com/watch?v=E4aQpczZC00
).

Android also uses single tap (
http://www.youtube.com/watch?v=MBRFkLKRwFw
).
Windows Mobile (
http://www.youtube.com/watch?v=Al6hrV9bOB8
)

2.4 Visualize
UI behaviour depends on the currently selected mode. Mode can be either Hybrid, used
when there are HW keys available, or Touch mode, when HW keys are hidden and user
uses only touch screen interface. Use cases are therefore described for both modes
individually.
2.4.1 Hybrid mode
2.4.1.1 Item selection
Selection is always visible in lists and grids just like it is currently implemented in 5
th
Edition
platform. When application starts User can then move the highlight using hardware joystick.



Figure 4 Context sensitive pop-up menu displaying item related commands.
2.4.1.4 Multiselection
Multiselection in hybrid mode can be achieved using HW keys (using shift and/or control key)
or using Mark / Unmark commands in options menu. Mark / Unmark submenu is also placed
to context sensitive pop-up menu, as seen in Figure 5.

Figure 5 Mark/Unmark in pop-up menu.

2.4.2 Touch Mode
2.4.2.1 Item selection
In touch mode, no item is originally selected when the list is displayed. Item is selected only
for a short time when tapping it. Because there is no active highlight, all item related
commands from the options menu are removed.

Figure 6 Item related menu commands are removed in touch mode
2.4.2.2 Performing default item action
Default item action (e.g. opening the item) is performed by single tapping the item.
Figure 7 demonstrates a use case where a contact is opened using single tap on touch
mode. The initial state of contacts view does not highlight any item. When the user taps
contact called ilkka following steps happen:
1. Contact ilkka is highlighted when finger or stylus hits the screen
2. When user pulls stylus from the screen the contact opens
3. In single contact view no list items are highlighted


2.6 Dependencies
The solution is independent of other proposals.
2.7 Exclusions
This proposal introduces extensive change to user interface behaviour, therefore usability
study might be required.
3 Revision History

Revision

Author
Date
Description
0.1 Martin Komara 13.10.2009 Initial draft.
0.2 Martin Komara 15.10.2009 Use cases added.
0.3 Martin Komara 19.10.2009 Cleaning
0.4 Ilkka Syrjälä 30.10.2009 Multiselection in
touch only mode.