Notification Interaction Interface With Progressive Touch Expansion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing interaction method for electronic devices, such as smartphones, requires users to jump between application interfaces to view or operate notification messages, leading to cumbersome operations and poor user experience due to CPU resource occupation.
Innovation Solution
An interaction method that allows users to perform touch operations on notification messages to progressively display content and operation buttons on the current interface without jumping to the application, using varying touch amplitudes or durations to reveal additional information and functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the user taps the notification message to jump to the corresponding application, then the user can view complete details and perform operations, but the operation becomes cumbersome and time-consuming
Solution Approach 1:
The notification interaction is segmented into multiple progressive stages: initial notification display, first expansion level showing basic details, second expansion level showing more comprehensive information, and final level showing all details with operation buttons. This segmentation allows users to access information incrementally without requiring a full application jump, reducing operation time while preserving access to complete notification details when needed.
Solution Approach 2:
The solution adds a dimensional expansion mechanism to the notification interface. Instead of requiring users to navigate to a separate application (spatial jump), the notification message itself expands in-place through multiple levels of detail revelation. This dimensional change allows complete notification details to be accessed within the current interface context, eliminating the need for application switching and reducing operation time.
2Loss of information
If the notification displays complete details immediately, then the user can view all information at once, but it causes visual interference and clutter
Solution Approach 1:
The notification interface employs dynamic expansion where the amount of displayed information changes based on user interaction. Initially, only essential notification information is shown to maintain a clean interface. Upon user tapping, the notification dynamically expands to reveal additional details, operations, and buttons in a controlled sequence. This dynamic approach ensures complete information availability while minimizing visual interference at each interaction stage.
Solution Approach 2:
The notification content is segmented into multiple display levels: Level 1 shows basic notification info, Level 2 adds detailed message content, and Level 3 includes operation buttons and additional controls. This segmentation allows the interface to present information in manageable portions, reducing visual clutter while ensuring all notification details are accessible through progressive expansion.
3Loss of information
If the notification expands to show all content at once, then the user can access all information, but it occupies excessive screen space and reduces interface efficiency
Solution Approach 1:
The notification employs dynamic size adjustment based on user interaction needs. The notification starts compact, occupying minimal screen space. When users tap, it expands dynamically to reveal more content, and can expand further for additional details. This dynamic sizing ensures that the notification occupies only the necessary screen space at each interaction stage, maintaining interface efficiency while providing access to complete notification content when required.
Solution Approach 2:
The notification structure follows a nested expansion pattern where content is organized in concentric layers. The core notification info is at the center, with additional details nested within, and operation buttons nested at the outermost layer. This nesting allows the notification to expand from a compact core outward, efficiently utilizing screen space by only displaying the necessary level of detail for each user interaction.
4Ease of operation
If the notification requires jumping to the application, then the user can perform operations, but the CPU resource occupation increases
Solution Approach 1:
The solution extracts and implements essential notification operations directly within the notification interface itself, without requiring full application launch. Critical operations such as reply, delete, and other common actions are made available through the expanded notification UI. This extraction eliminates the need for complete application loading, significantly reducing CPU resource occupation while maintaining full operational capability for common notification tasks.
Solution Approach 2:
The expanded notification serves as an intermediary interface between the user and the full application. It provides a simplified but functional environment for common operations without requiring the overhead of complete application execution. This intermediary layer handles routine notification tasks efficiently, reducing CPU resource occupation while maintaining ease of operation for typical user needs.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This application relates to the field of terminal technologies, and discloses an interaction method for an electronic device and an electronic device. After receiving a touch instruction, the electronic device parses a touch manner and a to-be-operated object that correspond to the touch instruction. The touch manner includes at least one type, and each type of touch manner includes a plurality of touch operations. Based on an amplitude of each touch operation, content carried by the to-be-operated object is successively and correspondingly displayed at an upper layer of an operation interface currently browsed by a user. When the user views the content in the to-be-operated object, jumping between the operation interface currently browsed by the user and an app corresponding to the to-be-operated object is avoided, CPU resource occupation of the electronic device due to an application jumping process is avoided, and freezing of the electronic device is also avoided, thereby improving user experience.