×
Namespaces

Variants
Actions
(Difference between revisions)

Mobile Design Pattern:ShortCuts

From Nokia Developer Wiki
Jump to: navigation, search
mayankkedia (Talk | contribs)
 
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Mobile_Design]] [[Category:Mobile_Design_Patterns]] [[Category:Usability]]
+
{{ArticleMetaData <!-- v1.1 -->
 +
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 +
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 +
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 +
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 +
|id= <!-- Article Id (Knowledge base articles only) -->
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20090626
 +
|author= [[User:Mayankkedia]]
 +
}}
 +
 
 +
[[Category:Mobile Design Patterns]] [[Category:Usability]]
  
 
This design pattern is part of the [[:Category:Mobile Design Patterns|Mobile Design Patterns]] series.<br>
 
This design pattern is part of the [[:Category:Mobile Design Patterns|Mobile Design Patterns]] series.<br>
Line 47: Line 71:
 
[[TSS000024 - Adding an application shortcut to the Go To menu of a S60 device]]
 
[[TSS000024 - Adding an application shortcut to the Go To menu of a S60 device]]
  
[[Defining the Shortcut Keys]]
+
[[Defining shortcut keys for a Symbian app]]
  
 
===Filter existing shortcut behavior===
 
===Filter existing shortcut behavior===
Line 55: Line 79:
 
===Custom shortcut implementation===
 
===Custom shortcut implementation===
  
You can provide your own custom shortcuts from within your application, for instance on the press of a specific number combination, long/short press of a key etc. Another shortcut implementation could be password protected, in cases you don’t want to display certain features/parts of the application unless the user keys in a specific number sequence. On successful keying of the key sequence the feature/view etc is accessible.
+
You can provide your own custom shortcuts from within your application in the following ways :-
 +
*On the press of a specific number combination, long/short press of a key etc.
 +
 
 +
* Password protected shortcut mechanism, in cases you don’t want to display certain features/parts of the application unless the user keys in a specific number sequence. On successful keying of the key sequence the feature/view etc is accessible.
 +
 
 +
* Search field implementation on a list view, allowing the user to quickly access a specifc contact/item from the list rather than having to manually scroll to the item in question.
 +
 
 +
* Using audio cues, details of which can be found at the link <b><u>[[Audio Usability]]</u></b>
 +
 
 +
* Making use of pre-existing native functionalities by the help of the application interworking framework in the case of Symbian C++, as detailed on the link <b><u> [[Application Interworking(AIW)]] </u></b> or even using the media keys as mentioned in the link <b><u> [[TSS000432 - Utilising media keys]] </u></b>
 +
 
 +
==Document them well==
 +
 
 +
It is imperative that you provide details about the various shortcuts that you have implemented in your application in the context sensitive menu and the user guide. If the user is not aware of the shortcuts they might not be able to make full use of them or in some cases might end up in invoking a shortcut only to realise they did not want to use it in the first place.
 +
 
 +
==Make them customizable==
 +
 
 +
One should also consider providing the user a setting page where they can posssibly configure their shortcut keys with which they are more comfortable, rather then forcing them to use default combinations. Specially in the case of password enabled shortcut keys it is a must, as otherwise the user would have to memorize the default password to invoke the protected functionality.
  
 
<b>--- Added by Mayank on 26/06/2009 ---</b>
 
<b>--- Added by Mayank on 26/06/2009 ---</b>

Latest revision as of 09:06, 16 April 2012

Article Metadata
Article
Created: mayankkedia (26 Jun 2009)
Last edited: hamishwillee (16 Apr 2012)

This design pattern is part of the Mobile Design Patterns series.

Contents

[edit] Introduction

On the mobile device, where the interaction mechanisms between the user and the application are quite hampered as compared to the desktop, it is imperative to extend the options that are available. Most devices have soft-key based interaction, where the soft-keys follow the conventions laid down by the style-guide and the same should not be tampered with. However it is surely possible to make use of the other keys which are not bound by the style-guide considerations per se to increase the ease of use for the user.

Making use of the other keys/key combinations etc to expedite the response mechanism from a user’s perspective makes a lot of sense. The usability expert/UI designer should carefully consider the key functionalities of the application, and figure how many key presses it typically takes to get to those functions from the main view of the application. If they find that it is becoming tough from a user’s standpoint to get to a view/function with the use of the conventional navigation approach they should think about providing some kind of shortcuts to the user, so that they can get there faster.

Shortcuts could be provided either by having specific hardware keys mapped to certain applications, or they can be provided through the software by programming them in such a way that they do specific tasks as dictated by the code.

[edit] Existing usage of shortcuts

Even today lots of shortcuts have been developed for the ease of the user, on any Nokia device for instance. Some of the commonly used shortcuts are as follows:-

  • Application launcher shortcuts on the active idle
  • Speed dial mechanism
  • In case of 4 way Centre Soft Key, each side of the joystick is mapped to a specific native application.
  • The LSK/RSK on the active idle provides access to customizable applications.
  • Press of the Green key from the active idle invokes the call log application.
  • Native gaming applications make use of keys for specific actions.
  • Accessing the currently running application list by long press of task list.
  • Browser shortcuts S60 web Browser shortcut keys

[edit] Extensions possible

From a usability standpoint, one can also think of providing shortcuts to the user, to make it easier for them to be able to get to a particular control/view/functionality. Some extensions possible could be as under:-

[edit] Customizing active idle shortcuts

Using the ScShortCuts Engine Wrapper API, 3rd party developers can make changes to the soft key on the active idle to display shortcuts to their applications instead of the native applications.

Details can be had from:-

ScShortcuts Engine Wrapper API

KIS000920 - Shortcuts Engine API not available in S60 3rd Edition, Feature Pack 2


[edit] Adding shortcuts to Go_To Menu

Using Symbian C++, developers can possibly look at providing shortcuts to their applications through the go_to menu.

Details can be had from:-

TSS000024 - Adding an application shortcut to the Go To menu of a S60 device

Defining shortcut keys for a Symbian app

[edit] Filter existing shortcut behavior

It is also possible to override the existing shortcut behavior. Details can be had from TSS000416 - Filtering standard S60 shortcut key behavior

[edit] Custom shortcut implementation

You can provide your own custom shortcuts from within your application in the following ways :-

  • On the press of a specific number combination, long/short press of a key etc.
  • Password protected shortcut mechanism, in cases you don’t want to display certain features/parts of the application unless the user keys in a specific number sequence. On successful keying of the key sequence the feature/view etc is accessible.
  • Search field implementation on a list view, allowing the user to quickly access a specifc contact/item from the list rather than having to manually scroll to the item in question.
  • Using audio cues, details of which can be found at the link Audio Usability

[edit] Document them well

It is imperative that you provide details about the various shortcuts that you have implemented in your application in the context sensitive menu and the user guide. If the user is not aware of the shortcuts they might not be able to make full use of them or in some cases might end up in invoking a shortcut only to realise they did not want to use it in the first place.

[edit] Make them customizable

One should also consider providing the user a setting page where they can posssibly configure their shortcut keys with which they are more comfortable, rather then forcing them to use default combinations. Specially in the case of password enabled shortcut keys it is a must, as otherwise the user would have to memorize the default password to invoke the protected functionality.

--- Added by Mayank on 26/06/2009 ---

This page was last modified on 16 April 2012, at 09:06.
39 page views in the last 30 days.
×