| Latest revision |
Your text |
| Line 1: |
Line 1: |
|
| |
|
| == Problem == | | == Chat threading == |
| WhatsApp doesn't allow editing messages after a few minutes of sending them. This limitation can lead to chaotic conversations where topics bounce back and forth like a ping pong ball. What if there was a possibility to add secondary messages to your own messages or those of others? This feature could be useful when you forget details you need to add or when you want to keep the conversation tidy. It would prevent situations where you're discussing Phase 1 while your colleagues have moved on to Phase 10.
| | Based on the available research and user feedback in the internet, the most intuitive and preferred chat threading approach appears to be in-line threading with some specific features: |
|
| |
|
| Should we allow threading in chat?
| | ==== In-line Threading Advantages ==== |
|
| |
|
| If so, in which way?
| | * Provides better topical coherence than standard chat |
| | * Supports more balanced participation among group members |
| | * Allows users to maintain coherent sequences of conversational turns more easily |
| | * Helps in decision-making processes and organizing information |
|
| |
|
| == Possible solutions == | | ==== Opportunities ==== |
| 1. Displaing threaded comments with a distiguiscible color (e.g. 30% less opacity for both green/white = sent/received)
| |
|
| |
|
| 2. Users can to long-press (in mobile) a message to start a thread. Threads will be displaied taking the first line of the message you long-press (you can even select multiple messages) and the new conversation will appear:
| | # Visual Cues: Implement clear visual indicators to show message threads, avoiding overwhelming users with long, unbroken streams of messages <nowiki>https://www.cometchat.com/blog/chat-app-design-best-practices</nowiki> |
| | # Customizable Thread Display: Offer options to show newest messages at top or bottom, catering to individual preferences |
| | # Improved Thread Navigation: Provide easy expansion and collapse of conversation threads |
| | # Enhanced Search Within Threads: Implement better tools for finding specific messages in long conversations |
| | # Unified Interface: Integrate threads into the main interface instead of opening them in separate side panels |
| | # Multi-Thread Expansion: Allow users to expand multiple threads simultaneously for efficient exploration of various discussions |
|
| |
|
| * Together with people and groups on the left pane, in chronologic order so the one at the top is the most recent that received a new message
| | == Our solutions == |
| * In a specific part only for threads above people and groups
| |
| * Providing a 'view thread' in the filters tabs above people/groups
| |
| * Enabling to switch between threaded and chronological views
| |
|
| |
|
| == 1. WhatsApp Threading Potential: Contextual Comments Beneath Original Messages ==
| | * Context-Aware Scrolling: When a user answer to a old thread, we'll scroll to that specific point in the thread while still displaying the entire conversation for context. |
| Would it be beneficial to add contextual comments directly beneath your original messages?
| | * Flexible Thread Placement: We'll show the thread starter where it originally appeared and display the full thread at the most recent message's location. Users can choose which option they prefer. |
| | | * Customizable Threading Options: We'll provide user-configurable settings for threading behavior, allowing individuals to tailor the experience according to what they prefer. |
| [[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]]
| |