Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

(Difference between revisions)

Mobile Design Pattern: Notifications

From Wiki
Jump to: navigation, search
prakash.raman (Talk | contribs)
(New page: Category:Mobile_Design Category:Mobile_Design_Patterns ==Description== Notification mechanism is an essential part for any mobile device. Mobile have events like Call, SMS, e-mail...)
 
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Mobile_Design]]
+
[[Category:Mobile Design Patterns]]
[[Category:Mobile_Design_Patterns]]
+
{{Abstract|Notification mechanisms are an essential part for any mobile device. Devices have events like Call, SMS, e-mail and bluetooth request. An efficient notification mechanism gives user easy and fast access to events. This article outlines some of the different ways by which one can provide notifications.}}
  
==Description==
+
{{ArticleMetaData <!-- v1.1 -->
Notification mechanism is an essential part for any mobile device. Mobile have events like Call, SMS, e-mail and bluetooth request. An efficient notification mechanism gives user easy and fast access to events. There are different ways by which one can provide notifications:
+
|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= 20090513
 +
|author= [[User:Prakash.raman]]
 +
}}
  
==Symbol Based Notification==
+
== Symbol Based Notification ==
 
In this mechanism any event's notification is provided with displaying some symbol in notification area. We can divide this in two categories:  
 
In this mechanism any event's notification is provided with displaying some symbol in notification area. We can divide this in two categories:  
  
===Interactive===
+
=== Interactive===
  
 
In this case, user can directly have interaction with the Notification symbols. By selecting notification user can directly go to its service section where he/she can handle event which has cause the notification. This is very effective in case of touch input based devices.
 
In this case, user can directly have interaction with the Notification symbols. By selecting notification user can directly go to its service section where he/she can handle event which has cause the notification. This is very effective in case of touch input based devices.

Latest revision as of 06:06, 16 April 2012

Notification mechanisms are an essential part for any mobile device. Devices have events like Call, SMS, e-mail and bluetooth request. An efficient notification mechanism gives user easy and fast access to events. This article outlines some of the different ways by which one can provide notifications.

Article Metadata
Article
Created: prakash.raman (13 May 2009)
Last edited: hamishwillee (16 Apr 2012)

Contents

[edit] Symbol Based Notification

In this mechanism any event's notification is provided with displaying some symbol in notification area. We can divide this in two categories:

[edit] Interactive

In this case, user can directly have interaction with the Notification symbols. By selecting notification user can directly go to its service section where he/she can handle event which has cause the notification. This is very effective in case of touch input based devices.

Symbol based intractive.jpg
Figure:  shows a touch based interactive notification.


[edit] Non-Interactive

In this case, on occurrence of event user can see symbols in notification area, but can't have any interaction with it. User will get notified regarding the event but he/she needs to go to notification related service area by himself or herself and handle the event.

Symbol based nonintractive.jpg
Figure: shows Non-interactive symbolic notification.
  • Advantage of Symbol based notification is, it doesn't interfere with user other activities and can be present all through out while user is doing some thing else.

[edit] Menu Based Notification

These are interactive notification. It is generally shown on main screen of device. User can either service it or cancel it.

Menu based.jpg
Figure: shows an interactive menu based notification.
  • The disadvantage of using this notification mechanism is that it interfere with the use other activity. User have to cancel or service notification to remove it form screen.


[edit] Pop-up Based Notification

This kind of notification is generally used for those events which needs urgent servicing, for example incoming call or incoming bluetooth connection request.

Popup based.jpg
Figure: shows a pop-up based notification for incoming call.


[edit] Quick Response via Notification

By adding this functionality to notification system, user experience can be taken one more step ahead. Here user will be directly provided with the ways he/she can respond to event.

Action on notification.jpg
Figure: shows notification linked with the ways, user can respond to event.

[edit] Audio and Vibration Notification

This mechanism is very effective in attracting user's focus towards the event. Generally this mechanism is mixed with the above mentioned systems.

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

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×