Notification Coalescence and Quick Reply Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for providing and interacting with notifications on electronic devices are cumbersome and inefficient, often displaying notifications in a confusing manner with limited interaction capabilities, requiring users to open corresponding applications, which wastes energy and time, especially in battery-operated devices.
Innovation Solution
Implementing faster and more efficient methods and interfaces for electronic devices with touch-sensitive surfaces that coalesce notifications from a single sender, cluster or un-cluster them according to predefined guidelines, provide quick access to application functionalities, and address privacy concerns through authentication mechanisms, allowing users to interact with notifications directly on the device even in a locked state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional notification methods are used, then notifications can be displayed, but user interaction is cumbersome and inefficient
Solution Approach 1:
The notification system is segmented into distinct interaction modes: lock screen notifications, notification center notifications, and quick reply actions. Each segment provides tailored interaction options appropriate to its context, reducing the complexity of the overall system by breaking down the monolithic notification interface into manageable, specialized components.
Solution Approach 2:
The notification interface is designed to perform multiple functions within a unified framework. The same notification can be viewed, replied to, forwarded, or have its associated application launched, all through the same interface paradigm. This multi-functionality reduces the need for separate specialized interfaces for each interaction type.
2Use of energy by moving object
If users open corresponding applications to interact with notifications, then full functionality is available, but energy is wasted
Solution Approach 1:
The system performs preliminary actions by providing quick reply capabilities directly at the notification level. Common operations such as responding to messages, accepting calendar invitations, or dismissing notifications can be completed without launching the full application, thereby conserving battery energy while maintaining productivity for routine tasks.
Solution Approach 2:
The system implements partial action by offering a subset of application functionalities directly within the notification interface. For common notification types, essential interactions are available without full application context, providing sufficient functionality for most users while avoiding the energy cost of complete application launches.
3Loss of information
If notifications are displayed with detailed information, then users have full context, but privacy concerns arise
Solution Approach 1:
The notification interface implements local quality by differentiating information display based on context and authentication state. Sensitive information is hidden or obscured in lock screen notifications, while full details are available in the notification center where the device is unlocked. This contextual quality adjustment protects privacy while maintaining information completeness when appropriate.
Solution Approach 2:
The system introduces an intermediary layer of authentication and context checking between the notification data and its display. Before showing sensitive notification content, the system verifies the device's locked/unlocked state and applies appropriate filtering. This intermediary mechanism balances information completeness with privacy protection by selectively revealing data based on security context.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
An electronic device includes instructions for receiving a first communication; in response to receiving the first communication, generating a first notification for the first communication received at the device, the first notification including content of the first communication; receiving a second communication at the device; and in response to receiving the second communication: determining whether the second communication and the first communication are received from the same sender. The instructions include, in accordance with a determination that the second communication and the first communication are from the same sender, updating the first notification such that the updated first notification concurrently includes the content of the first communication and the second communication; and in accordance with a determination that the second communication and the first communication are not from the same sender, generating a second notification, for concurrent display with the first notification.