×
Namespaces

Variants
Actions
(Difference between revisions)

Threaded Conversation View Design

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata etc)
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
(5 intermediate revisions by one user not shown)
Line 1: Line 1:
 +
[[Category:Mobile Design Patterns]][[Category:Usability]]
 +
{{ArticleNeedsUpdate|timestamp=20120508053806|user=[[User:Hamishwillee|<br />----]]|The threaded/non-threaded images below aren't very good - they show only a view with messages associated with a particular user. A good image would be the conversation view on a phone where sent/received messages are displayed adjacent to each other, in order. Alternatively, a facebook view.}}
 
{{ArticleMetaData <!-- v1.2 -->
 
{{ArticleMetaData <!-- v1.2 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
Line 14: Line 16:
 
|translated-from-title= <!-- Title only -->
 
|translated-from-title= <!-- Title only -->
 
|translated-from-id= <!-- Id of translated revision -->
 
|translated-from-id= <!-- Id of translated revision -->
|review-by= <!-- After re-review: [[User:username]] -->
+
|review-by=
|review-timestamp= <!-- After re-review: YYYYMMDD -->
+
|review-timestamp=  
|update-by= <!-- After significant update: [[User:username]]-->
+
|update-by= [[User:Hamishwillee]]
|update-timestamp= <!-- After significant update: YYYYMMDD -->
+
|update-timestamp= 20120507
 
|creationdate= 20090621
 
|creationdate= 20090621
 
|author= [[User:Prakash.raman]]
 
|author= [[User:Prakash.raman]]
 
}}
 
}}
[[Category:Mobile Design]] [[Category:Mobile Design Patterns]] [[Category:Usability]]
 
  
=Introduction=
+
==Introduction==
There are many modes currently available via which one can communicate using a mobile device and so there are lot of ways how these communication events are arranged, assembled and shown on device. ''Threaded Communication'' is just a way these communication events are presented to user. The focus of this design is, ''chain of events'' of communication happening between user and some contact and not only a event.
+
Threaded communication is where messages are presented as a "conversation"; associated messages are grouped, ordered according to when they are sent or received, and clearly identify the sender(s) and recipient(s). In some implementations the messages may simply be grouped by the recipients; in others, the grouping might be at a further granularity of "subject".
  
=Modes of Communication=
+
As users are often connected across a number of mechanisms, including SMS, MMS, email, instant messaging, phone calls, VoIP, facebook, twitter, blogs, the threaded view is becoming an even more important tool to help users remember where they are in their conversation.
The current means of communication are:
+
* Call
+
* SMS
+
* MMS
+
* E-Mail
+
In future there might be more ways people will be connected via mobile device. Like scrap books, blogs etc.
+
  
=Current Scenario=
+
==Design Images==
Currently while managing events, focus is just one event type. Every event type is handled in different section for individual communication means. For example:
+
* Calls are maintained under Incoming, Out going and Missed call
+
* SMS are maintained in Inbox, Sent, Outbox and Draft
+
* E-Mails are managed in a different sections too.
+
+
==Points to be notice==
+
* This design has in focus the event type. If you look from the point of view of object orientation, here object is individual event. And there are different manager for each type of event.
+
* Contact are not priorities in communication. Also contact from Contact book is taken as separate entity than that of emails.While both might be same for most of contact.
+
* In this scenario, if some one need to trace all communication between self and some person, he/she needs to jump from incoming calls to out going to inbox SMS to sent SMS and there also need to search among other events.
+
 
+
+
=Threaded View Design=
+
In threaded view design, communication is given more priority than the just a event.
+
 
+
==Implementation==
+
 
+
* All communication is managed at one place, under some thing like Communication Manager.
+
* Communication Manager will have list of thread per contact. A thread will be started when any communication event occur.
+
* All communications with a Contact will be appended to the thread for the contact as events.
+
* Communication threads can be sorted on basis of time of last activity on the thread
+
* Each Item in a thread can be deleted individually or whole thread it self can be deleted
+
* Each item can open in special handler for that item or can expand in the thread it self to show the details.
+
* While replying to the contact of the thread, prompt will be provided asking for means to reply, that can be call, SMS, MMS, or e-mail
+
 
+
===Design Images===
+
 
+
[[File:Thread list.png| List of threads inside Communication Manager ]]
+
 
+
'''Image shows the list of threads arranged on basis of last event time in Communication Manager'''
+
 
+
 
+
[[File:Expanded thread list.png | Inline expansion for last event inside Communication Manager ]]
+
 
+
'''Image shows inline expansion for last event.'''
+
 
+
 
+
[[File:Thread.png | View of a thread of events from one contact]]
+
 
+
'''Image shows view for events in a thread'''
+
  
 +
The images below contrast a non-threaded and threaded view. Both images show a communication manager which displays both calls and SMS messages. The first image displays a non-threaded view where messages are sorted by arrival order. The second message shows a threaded view, where events associated with a user are displayed together.
 +
<gallery widths=300px heights=300px>
 +
File:Thread list.png|Traditional communication where messages are sorted by arrival time
 +
File:Thread.png|Threaded view, where events associated with a user are grouped
 +
</gallery>
  
 
==Points to be notice==
 
==Points to be notice==
* Tracing and managing communications will be very easy.
+
* Tracing and managing communications is easy.
* Can be used as chat over SMS or E-Mail.
+
* In future, other things like blogs, scraps, comments from web pages can be linked to this threading mechanism.
+

Latest revision as of 06:26, 9 May 2012

Needs-update.pngThis article needs to be updated: If you found this article useful, please fix the problems below then delete the {{ArticleNeedsUpdate}} template from the article to remove this warning.

Reasons: hamishwillee (08 May 2012)
The threaded/non-threaded images below aren't very good - they show only a view with messages associated with a particular user. A good image would be the conversation view on a phone where sent/received messages are displayed adjacent to each other, in order. Alternatively, a facebook view.

Article Metadata
Article
Created: prakash.raman (21 Jun 2009)
Updated: hamishwillee (07 May 2012)
Last edited: hamishwillee (09 May 2012)

[edit] Introduction

Threaded communication is where messages are presented as a "conversation"; associated messages are grouped, ordered according to when they are sent or received, and clearly identify the sender(s) and recipient(s). In some implementations the messages may simply be grouped by the recipients; in others, the grouping might be at a further granularity of "subject".

As users are often connected across a number of mechanisms, including SMS, MMS, email, instant messaging, phone calls, VoIP, facebook, twitter, blogs, the threaded view is becoming an even more important tool to help users remember where they are in their conversation.

[edit] Design Images

The images below contrast a non-threaded and threaded view. Both images show a communication manager which displays both calls and SMS messages. The first image displays a non-threaded view where messages are sorted by arrival order. The second message shows a threaded view, where events associated with a user are displayed together.

[edit] Points to be notice

  • Tracing and managing communications is easy.
This page was last modified on 9 May 2012, at 06:26.
70 page views in the last 30 days.