Activity Stack Return Navigation for Multi-Interface App Backtracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing applications require multiple user operations to return to a previous interface, leading to complex navigation and loss of operation records, compromising user experience.
Innovation Solution
A quick interface return method that allows popping multiple activities from the stack with a single user operation, enabling direct return to a previous interface within the same or different application, with options for different user interactions and interface display modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the user triggers a return button multiple times to return level by level through a stack of activities, then the user can return to a previous interface, but the user operations become complex and time-consuming
Solution Approach 1:
The system performs preliminary detection of the activity stack structure and pre-calculates the return path. When a long-press gesture is detected, the system has already prepared the list of intermediate interfaces and can immediately execute the jump without requiring multiple sequential return operations, thus saving time and simplifying user operations
Solution Approach 2:
The patent introduces an intermediary mechanism (the long-press gesture trigger) that mediates between the user's return intent and the system's navigation execution. This intermediary activates a special return mode that bypasses the traditional level-by-level return process, allowing direct jumping to the target interface while preserving operation records
2Ease of operation
If the user quits and restarts the application to return to a previous interface, then the user can access the main interface, but previous operation records are lost and operations need to be performed again
Solution Approach 1:
The system performs preliminary detection of the activity stack structure and pre-calculates the return path. When a long-press gesture is detected, the system has already prepared the list of intermediate interfaces and can immediately execute the jump without requiring multiple sequential return operations, thus saving time and simplifying user operations
Solution Approach 2:
The patent introduces an intermediary mechanism (the long-press gesture trigger) that mediates between the user's return intent and the system's navigation execution. This intermediary activates a special return mode that bypasses the traditional level-by-level return process, allowing direct jumping to the target interface while preserving operation records
3Ease of operation
If the system pops multiple activities from the stack with a single operation, then the return navigation is simplified and user experience is enhanced, but the processing load increases
Solution Approach 1:
The system applies partial action by only executing the multi-activity pop operation when specifically triggered by a long-press gesture, rather than always performing complex processing. This conditional execution approach balances user experience improvement with energy conservation, as the enhanced navigation feature is activated only when needed
Solution Approach 2:
The system performs preliminary detection of the activity stack structure and pre-calculates the return path. When a long-press gesture is detected, the system has already prepared the list of intermediate interfaces and can immediately execute the jump without requiring multiple sequential return operations, thus saving time and simplifying user operations
Data Source
AI summary
This application provides a quick interface return method and an electronic device. The method is applied to an electronic device. The method includes: displaying a first interface of a first application, where the first interface is associated with a first activity, the first activity is a stack top activity of a first activity stack, and the first activity stack includes the first activity, a second activity, and a third activity; receiving a first user operation; and in response to the first user operation, popping at least two activities of the first activity stack, and displaying a second interface of the first application, where the second interface is associated with the second activity; or in response to the first user operation, popping at least two activities of the first activity stack, and displaying a third interface of a second application, where the third interface is associated with the third activity.


