Android Email Deletion via Sliding Gesture and Dynamic Button
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing email deletion method on ANDROID™ platforms is operationally complex, leading to a poor user experience due to multiple steps and potential mis-operations during the deletion process.
Innovation Solution
A method that detects a sliding operation on an email interface, shifts the deletion button to a target position based on preset coordinates and interface shift thresholds, allowing for easy deletion of emails by sliding the email content, thereby simplifying the deletion process and reducing false triggering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the existing email deletion method (long-press or multi-step selection) is used, then the deletion function is available, but the operational complexity increases and user experience deteriorates
Solution Approach 1:
The deletion interface is segmented into distinct regions: a first region for displaying email content and a second region for displaying the deletion button. This spatial segmentation allows the deletion button to be positioned away from the email content, reducing accidental clicks while maintaining accessibility. The layout file coordinates system is also segmented to independently control the positioning of different UI elements.
Solution Approach 2:
A drag operation is introduced as an intermediary action between selecting an email and deleting it. The user drags the email from the first region toward the second region, and only when the email overlaps with the deletion button does the deletion option become active. This intermediary drag gesture reduces mis-operations compared to direct clicking, while maintaining a simple two-step process.
2Adaptability or versatility
If multiple action options are provided in the popup menu, then the functionality is comprehensive, but the risk of mis-operation increases
Solution Approach 1:
The deletion button is extracted from the traditional popup menu and placed as a separate, persistent element in the second region of the interface. This extraction eliminates the need for users to navigate through multiple popup menu options, reducing the risk of selecting the wrong action. The deletion function is isolated and clearly distinguished from other potential actions.
Solution Approach 2:
The deletion button's state is dynamic: it becomes active and clickable only when the email is dragged into overlap with it. Before the drag operation completes, the deletion button remains inactive, preventing accidental deletions. This dynamic activation based on user intent improves operation accuracy while maintaining functional versatility.
3Productivity
If the deletion button is always visible, then the deletion operation is fast, but the risk of false triggering increases
Solution Approach 1:
The deletion button is positioned in a different spatial dimension (second region) separated from the email content (first region). The drag operation introduces a temporal and spatial dimension to activation: the button becomes active only when the email traverses the space between regions and overlaps with the button. This dimensional separation reduces false triggering while maintaining quick access for intentional deletions.
Solution Approach 2:
The system performs a preliminary check during the drag operation to determine whether the email overlaps with the deletion button before enabling the deletion function. This preliminary action filters out accidental touches that don't intend to delete, while allowing quick deletion for users who deliberately drag to the button. The overlap detection serves as a preliminary validation step.
Data Source
AI summary
The present disclosure provides a method for deleting an email from a terminal device running Android system. The method includes: acquiring sliding trace information of a touch point; acquiring, if a sliding operation of the touch point meets a pre-determined condition, initial coordinates of the control in a first layout file of an email interface where the touch point is located, target coordinates of a deletion button in a second layout file, and a preset interface shift threshold; shifting, according to the interface shift threshold, the initial coordinates of the control in a preset direction, and shifting, according to the interface shift threshold and a width value of the deletion button, the deletion button in a preset direction to the target coordinates of the deletion button; and deleting the email when a touch point is detected in a deletion button region of the email interface.