IM Conversation Management via Idle Archive Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Instant Messaging (IM) applications on communication devices face inefficiencies due to large lists of conversations, which hinder user navigation and interface effectiveness, especially on devices with small displays, as many conversations become idle and irrelevant, cluttering the interface.
Innovation Solution
Implementing an IM conversation management system that archives idle conversations after a defined period with no unread messages, allowing users to review archived conversations and optionally save them, while automatically deleting archived conversations when the archive reaches a size limit or when device memory is low.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users maintain multiple active conversations simultaneously, then communication versatility is improved, but the conversation list grows large making navigation difficult
Solution Approach 1:
The patent segments the conversation list into multiple pages, with each page displaying a limited number of conversations (e.g., 5-10 items). Users can navigate between pages to access different sets of conversations, making it easier to locate desired conversations without being overwhelmed by a single long list.
Solution Approach 2:
The patent introduces a temporal dimension by organizing conversations into chronological pages. Instead of a single flat list, conversations are distributed across multiple time-based pages, allowing users to navigate through different time periods to find specific conversations.
2Loss of information
If all conversations are kept in the active list, then information completeness is improved, but interface clutter increases on small displays
Solution Approach 1:
The patent divides the complete conversation set into multiple pages, each displaying only a subset of conversations. This segmentation allows the interface to show fewer items at once, reducing clutter on small displays while maintaining access to all conversations through page navigation.
Solution Approach 2:
The patent displays only a partial view of the complete conversation list at any given time (one page at a time). This partial display approach reduces the amount of information visible simultaneously, making the interface less cluttered while still providing access to the full set of conversations through pagination.
3Loss of information
If the conversation list is kept long to maintain history, then information retention is improved, but navigation time increases
Solution Approach 1:
The patent segments the conversation history into chronological pages, allowing users to quickly jump to specific time periods or recent conversations. This segmentation reduces the time needed to navigate through the entire history compared to scrolling through a single long list.
Solution Approach 2:
The patent pre-organizes conversations into pages based on time criteria (e.g., most recent, oldest, or custom time ranges). This preliminary organization allows users to directly navigate to relevant time periods without sequentially scrolling through all conversations, reducing navigation time.
4Productivity
If idle conversations are removed from the active list, then interface efficiency is improved, but access to old conversations becomes more difficult
Solution Approach 1:
The patent moves removed conversations to a separate archival dimension rather than deleting them. The archive functions as a distinct storage space where old conversations are preserved and can be accessed through dedicated archive navigation, separating active conversation management from historical record-keeping.
Solution Approach 2:
The patent introduces an archive as an intermediary storage space between active conversations and permanent deletion. This archive serves as a mediator that preserves removed conversations while keeping them separate from the active conversation list, allowing efficient active list management while maintaining accessibility to historical conversations.
Data Source
AI summary
A method and apparatus for managing IM conversations is provided. In response to idle time and, preferably, read message status, particular current conversations are removed from a list of current conversations. The removed conversations may be moved to an archive which may be automatically maintained in response to size constraints. An archive interface is facilitated to review conversations, save all or portions thereof, delete, etc. The archived conversations are preferably associated with the contact for the conversation to show a history of conversations.