Background App Preloading with Launch Origin Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for reducing user interface latency in user devices, such as smartphones, are inadequate in handling uncommon application launch flows, which can lead to errors and suboptimal behavior, and struggle to distinguish between preload-initiated and user-initiated UI displays, affecting user experience.
Innovation Solution
The system preloads user applications in a background mode, identifies and replaces uncommon launch flows with alternative common flows, and differentiates between preload-initiated and user-initiated UI displays by assessing user interaction and OS handling schemes, while managing focus states and displaying temporary windows to enhance user interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If preloading is performed using uncommon flows, then the application can be loaded in the background, but errors and suboptimal behavior occur
Solution Approach 1:
The system performs preliminary actions by preloading the application in the background using common flows before the user actually accesses it. This allows the application to be ready for immediate use when launched, improving loading speed while avoiding errors by using only common, well-tested flows during the preloading phase.
Solution Approach 2:
The system introduces an intermediary mechanism that detects and replaces uncommon flows with common flows during preloading. This intermediary layer ensures that only reliable common flows are executed in the background, preventing errors while still enabling background loading functionality.
2Ease of operation
If the system distinguishes between preload-initiated and user-initiated UI displays, then user experience is improved, but system complexity increases
Solution Approach 1:
The system uses feedback mechanisms to track the origin of UI display launches. By monitoring whether a launch occurred during preloading or by user action, the system can apply appropriate handling schemes. This feedback-based approach improves user experience through consistent behavior while managing complexity through systematic tracking.
Solution Approach 2:
An intermediary detection mechanism is introduced that sits between the flow execution and UI display rendering. This intermediary detects the launch origin (preload vs. user-initiated) and routes to appropriate handling schemes, improving user experience while containing complexity within a dedicated detection layer.
3Reliability
If uncommon flows are replaced with alternative common flows, then reliability is improved, but the preloading process takes longer
Solution Approach 1:
The system performs preliminary identification of common flows before execution. By pre-selecting and validating only common flows for background preloading, the system ensures reliable execution while optimizing the preloading process to use efficient, well-tested flow paths that minimize unnecessary delays.
Data Source
AI summary
A user device includes a display screen and one or more processors. The one or more processors are configured to preload one or more user applications in a background mode, in which User Interface (UI) displays associated with preloaded user applications are invisible on the display screen, to detect a launch of a UI display that is associated with a given preloaded user application, to assess whether the UI display is a preload-initiated UI display that is invoked due to preloading of the given user application, or whether the UI display is a user-initiated UI display that is invoked due to an action by the user, to handle the UI display using a first handling scheme if the UI display is assessed to be a preload-initiated UI display, and, if the UI display is assessed to be a user-initiated UI display, to handle the UI display using a second handling scheme, different from the first handling scheme.