Splash Screen Control for Application Activation Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques for displaying splash screens during application activation can lead to unintended timing and increased user operation burden, as applications may become resident and require initialization processing, affecting activation time and user experience.
Innovation Solution
A method that determines whether the application activation is initiated by a user or the operating system, and controls splash screen display based on first-time screen display flags, ensuring the splash screen is only shown at initial activation by the user, thereby reducing activation time and operation burden.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the application is made resident to shorten activation processing time, then the activation time is shortened, but the splash screen may be displayed at unintended timing and initialization processing for screen display takes time
Solution Approach 1:
The patent applies local quality by differentiating the splash screen display behavior based on the activation context. When activated by the operating system, the application does not display the splash screen, but when activated by user instruction, the splash screen is displayed. This localized differentiation resolves the contradiction by optimizing the resident activation experience while preserving the expected user feedback for manual activation.
Solution Approach 2:
The patent introduces dynamic behavior by tracking whether the application has displayed its screen for the first time using a flag. This dynamic state management allows the application to adapt its splash screen display behavior based on its activation history, enabling it to distinguish between first-time user activation and subsequent activations, thereby resolving the timing issue of splash screen display.
2Loss of information
If the application displays splash screen during activation, then activation indication to user is clear, but activation time increases and user experience differs between resident and non-resident states
Solution Approach 1:
The patent applies local quality by differentiating the splash screen display behavior based on the activation context. When activated by the operating system, the application does not display the splash screen, but when activated by user instruction, the splash screen is displayed. This localized differentiation resolves the contradiction by optimizing the resident activation experience while preserving the expected user feedback for manual activation.
3Productivity
If initialization processing is performed to make application resident, then activation time is shortened, but screen display initialization takes time and user experience varies
Solution Approach 1:
The patent extracts the splash screen display logic from the general activation process and handles it separately based on activation context. By isolating the splash screen display decision to specific user-initiated activation scenarios, the patent simplifies the overall initialization processing while maintaining appropriate user feedback, thereby reducing the perceived complexity without sacrificing activation speed.
Data Source
AI summary
It is determined whether an instruction for initial activation of an application is issued by a user or an operating system (step S702). If the instruction is issued by the user, a splash screen is displayed (step S715). If the instruction is issued by the operating system, the application is to be resident without displaying the splash screen (step S704). If a user issues an activation instruction with respect to the resident application (step S705), it is determined whether a screen display based on the activation instruction from the user is a first time or not (step S706). If it is not the first time, the splash screen is not displayed, and whereas if it is the first time, the splash screen is displayed (step S707).