Call History GUI Segmented Lists for Voicemail Visibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The separation of call history and voicemail interfaces in mobile devices can lead to voicemails being pushed down the list, making them less visible to users, and it is non-intuitive to separate missed calls from associated voicemails, potentially causing users to overlook important voicemails.
Innovation Solution
A call history graphical user interface that concurrently displays a new list and an old list, where the new list includes missed calls and associated unopened voicemails, and the old list includes previously displayed missed calls and opened voicemails, with indicators for voicemails within the missed call elements, allowing users to easily review voicemails without merging the lists.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If call history and voicemail interfaces are separated, then call history can be organized chronologically, but voicemails are pushed down the list and become less visible to users
Solution Approach 1:
The interface is segmented into two distinct lists: a call history list and a voicemail list. Each list serves a specific function and is displayed separately rather than being merged into a single chronological list. This segmentation allows voicemails to maintain prominent visibility while preserving the organizational structure of call history.
2Ease of operation
If call history and voicemail lists are merged, then all communication events are visible in one place, but voicemails may be pushed down and users may not review them
Solution Approach 1:
Rather than merging call history and voicemail into a single list, the interface segments them into two separate lists displayed concurrently. The voicemail list is positioned to ensure visibility, and navigation mechanisms allow users to access both lists efficiently, maintaining ease of operation while preventing voicemail oversight.
Solution Approach 2:
The interface transitions from a single-dimensional chronological list to a two-dimensional layout with separate sections for call history and voicemails. This dimensional change allows both types of information to be presented prominently without one pushing the other down the list.
3Stability of the object's composition
If missed calls and voicemails are separated, then call history remains clear, but it becomes non-intuitive and users may not associate voicemails with missed calls
Solution Approach 1:
The interface provides feedback mechanisms that associate voicemails with their corresponding missed calls. Visual indicators, icons, or linking mechanisms show the relationship between a missed call entry and its associated voicemail, helping users intuitively understand the connection while maintaining separate organizational structures.
Solution Approach 2:
An intermediary element or indicator is introduced that bridges the gap between missed calls and voicemails. This intermediary provides visual or functional links that help users associate voicemails with missed calls while preserving the separate structure of both lists.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computing device displays a call history graphical user interface (GUI). The call history GUI includes a new list and an old list. The new list may include new missed call elements and missed call elements associated with new unopened voicemails. The old list may include other call history GUI elements, such as old missed call elements and missed call elements associated with opened voicemails.