| Latest revision |
Your text |
| Line 1: |
Line 1: |
| | |
| | Would it be beneficial to introduce the ability to add contextual comments directly beneath your original messages? |
|
| |
|
| == Problem == | | == Problem == |
| Line 5: |
Line 7: |
| Should we allow threading in chat? | | Should we allow threading in chat? |
|
| |
|
| If so, in which way? | | If so, in which way? |
| | |
| | [[File:Chat threading.png|alt=Threading in Chat|thumb|Threading in Chat]] |
|
| |
|
| == Possible solutions == | | == Possible solutions == |
| Line 16: |
Line 20: |
| * Providing a 'view thread' in the filters tabs above people/groups | | * Providing a 'view thread' in the filters tabs above people/groups |
| * Enabling to switch between threaded and chronological views | | * Enabling to switch between threaded and chronological views |
|
| |
| == 1. WhatsApp Threading Potential: Contextual Comments Beneath Original Messages ==
| |
| Would it be beneficial to add contextual comments directly beneath your original messages?
| |
|
| |
| [[File:Chat threading.png|alt=Threading in Chat|thumb|Threading in Chat 1]]
| |
|
| |
| === Main Characteristics ===
| |
|
| |
| * Add details to an already sent message
| |
| * Provide immediate clarifications
| |
| * Maintain conversation context
| |
| * Prevent misunderstandings
| |
|
| |
| === Communication Advantages ===
| |
|
| |
| * Enrich original information
| |
| * Avoid sending multiple messages
| |
| * Maintain an orderly conversational flow
| |
| * Allow more articulated explanations
| |
|
| |
| === Technological Context ===
| |
| Currently not a standard feature in chats like WhatsApp, but would represent a significant evolution in digital communication, allowing:
| |
|
| |
| * Linear comments under the original message
| |
| * Preservation of original context
| |
| * Facilitation of supplementary explanations
| |
| == 2. WhatsApp Threading Potential: Contextual Conversation Branching ==
| |
| [[File:Recent conversations.png|alt=Threading Chat 2|thumb|Threading in Chat 2]]
| |
| Would it be beneficial to transform message interaction from linear to contextually adaptive?
| |
|
| |
| === Main Characteristics ===
| |
|
| |
| * Enable focused discussions from specific messages
| |
| * Reduce conversation noise
| |
| * Provide granular communication options
| |
| * Context preservation
| |
|
| |
| === Potential Implementation ===
| |
|
| |
| * Long-press on a specific message
| |
| * Create a new thread/conversation branch
| |
| * Option to invite specific contacts to the new conversation
| |
|
| |
| === Conversation List Placement ===
| |
| The new conversation threads could be referenced in:
| |
|
| |
| * A dedicated "Threads" section
| |
| * Integrated within existing chat lists
| |
| * Accessible through a new filter category
| |
|
| |
| === User Experience Considerations ===
| |
|
| |
| * Optional feature to prevent overwhelming users
| |
| * Clear visual distinction for threaded conversations
| |
| * Easy navigation between original and new threads
| |
|
| |
|
| |
| ''The fact that Teams is used in work contexts rather than WhatsApp by most companies makes me think that our target prefers structured and topic-organized conversations instead of casual ones.''
| |
|
| |
| == Professional Communication Preferences ==
| |
| WhatsApp has significantly more total users, but Teams dominates in professional communication contexts
| |
|
| |
| https://www.businessofapps.com/data/microsoft-teams-statistics/
| |
|
| |
| == User Experience Insights ==
| |
|
| |
| * WhatsApp excels in casual, personal communication
| |
| * Teams is designed for professional users
| |
| * The choice depends on prioritizing powerful features vs. simplicity
| |
|
| |
|
| |
| ''Can we use the semplicity of WhtsApp UI and making it more powerful in terms of organized conversations?''
| |
|
| |
| ← Go back to [[Main Page]]
| |