Application starting method and device, electronic equipment and storage medium

Abstract

The invention provides an application starting method and device, electronic equipment and a storage medium, and relates to the technical field of terminals.The method comprises the steps that when a trigger event for a notification message in a notification bar is monitored, a landing content page corresponding to the notification message in a target application is started, and the target application is started; if it is detected that the currently created Activity is the push Activity of the third-party message push service, setting the display attribute of the push Activity to be visible; creating a first window for pushing Activity, and drawing a transition animation corresponding to a default homepage of the target application; and starting the first window to display the transition animation. Therefore, visual feedback can be provided for the user as soon as possible, so that the user knows that the current system normally executes the operation of starting the application, the waiting time of the user is shortened, and the use experience of the user in an application starting scene is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an application launch method, apparatus, electronic device, and storage medium. Background Technology

[0002] Notification messages (or push messages) in the notification bar are message push services provided by electronic device manufacturers to application (APP) developers. The purpose is to establish a stable and reliable long connection. Message delivery does not require the application to reside in the background. At the same time, the message is encrypted during transmission. In terms of both delivery rate and security, it has more significant advantages than individual developers.

[0003] Among them, the push services of electronic device manufacturers mostly exist in the form of SDKPush (Software Development Kit Push). During the application startup process, an SDKPush activity (SdkPushActivity, or simply push Activity) is first created, and then the data carried by the notification message is passed to the subsequent Activity. Finally, the application decides to launch the landing content page corresponding to the notification message.

[0004] In this process, SDKPushActivity is often set to transparent to conceal its presence as much as possible. However, during application cold starts, setting SDKPushActivity to transparent causes the foreground interface to remain displayed after the user clicks on the notification message, and the electronic device fails to open the application for a long time. This effect is seriously inconsistent with user expectations, and user feedback will show that the electronic device system is slow and lagging significantly. Summary of the Invention

[0005] This application aims to at least partially address one of the technical problems in the related art.

[0006] To this end, this application proposes an application launch method, apparatus, electronic device, and storage medium to provide users with visual feedback as quickly as possible, enabling users to understand that the system is performing the application launch operation normally, reducing user waiting time, and improving user experience in application launch scenarios.

[0007] One embodiment of this application proposes an application launch method, including: when a trigger event for a notification message in the notification bar is detected, and during the process of launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created activity is a push activity of a third-party message push service, then the first display attribute of the push activity is set to visible; a first window of the push activity is created, and a transition animation corresponding to the default homepage of the target application is drawn; the first window is launched to display the transition animation.

[0008] As one possible implementation, during the process of detecting a trigger event for a notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created Activity is a push Activity of a third-party push service, then the first display attribute of the push Activity is set to visible. This includes: during the process of detecting a trigger event for a notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, determining whether the target application meets a first set condition; if the target application meets the first set condition and the currently created Activity is a push Activity, then the first display attribute of the push Activity is set to visible.

[0009] As one possible implementation, the first setting condition includes: the target application is located in the set application list; wherein, the set application list includes function tags of multiple applications, and the function tags are used to indicate whether the application has the set function; the function tag of the target application in the set application list is the target tag; wherein, the target tag is used to indicate that the target application has the set function.

[0010] As one possible implementation, the content displayed in the transition animation matches the theme style of the target application's default homepage; in response to the target application launching from the desktop, the transition animation is displayed as a gradual zoom-in; in response to the target application launching from a non-desktop location, the transition animation is displayed as a left-shift toggle or a right-shift toggle.

[0011] As one possible implementation, the method further includes: in response to the window removal timing of the push Activity, determining whether the theme of the default homepage is available; if available, setting the value of the first flag bit to the first value; wherein the first flag bit is used to indicate whether the removal of the first window of the push Activity is allowed, and the first value is used to indicate that the removal of the first window is not allowed; and displaying the default homepage through the first window.

[0012] As one possible implementation, the method further includes: if it is detected that the currently created Activity is a non-landing page Activity of the target application, then read the second display attribute of the non-landing page Activity; and display the default home page according to the second display attribute.

[0013] As one possible implementation, based on the first display attribute, the default homepage is displayed, including: in response to the second display attribute being visible, launching a second window of the non-landing page Activity and disabling transition animations within the second window; and continuing to display the content displayed in the first window through the second window.

[0014] As one possible implementation, after creating the first window of the push activity and drawing the transition animation corresponding to the default home page of the target application, the method further includes: setting the value of the second flag bit to a second value; wherein the second flag bit is used to indicate whether the launch window of the push activity has been created, and the second value is used to indicate that the launch window of the push activity has been created.

[0015] As one possible implementation, in response to the second display attribute being visible, a second window of the non-landing page Activity is launched, and transition animations are prohibited from being drawn in the second window. This includes: in response to the second display attribute being visible, determining whether the value of the second flag bit is the second value, and determining whether the target application meets the first set condition; if the value of the second flag bit is the second value, and the target application meets the first set condition, then the second window of the non-landing page Activity is launched, and transition animations are prohibited from being drawn in the second window.

[0016] As one possible implementation, the method further includes: when the content displayed in the first window continues to be displayed through the second window, setting the value of the first flag to a third value; wherein the first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the third value is used to indicate that the removal of the first window is allowed; and performing a destruction operation on the push Activity to remove the first window.

[0017] As one possible implementation, displaying a default homepage based on a first display attribute includes: refusing to launch a second window in response to a second display attribute being transparent; and continuing to launch the first window to display the default homepage.

[0018] As one possible implementation, the method further includes: in response to the window removal timing of the non-landing page Activity, determining whether the second window of the non-landing page Activity has been launched; if the second window has been launched, setting the value of the third flag to the fourth value; wherein the third flag is used to indicate whether the removal of the second window of the non-landing page Activity is allowed, and the fourth value is used to indicate that the removal of the second window is allowed; removing the second window, and displaying the removal animation corresponding to the default homepage during the removal of the second window; wherein the removal animation is displayed in the form of gradually disappearing.

[0019] As one possible implementation, after determining whether the second window has been launched, the method further includes: if the second window has not been launched, then, under the condition of satisfying the second setting, setting the value of the first flag to the third value, and performing a destruction operation on the pushing Activity to remove the first window; wherein, the first flag is used to indicate whether the removal of the first window of the pushing Activity is allowed, and the third value is used to indicate that the removal of the first window is allowed; wherein, the second setting condition includes: there is an Activity with the display attribute set to visible among the Activities created after the currently created Activity.

[0020] As one possible implementation, the method further includes: if it is detected that the currently created Activity is the landing page Activity of the target application, then a third window of the landing page Activity is launched to display the rendering frame of the landing content page in the third window.

[0021] Another embodiment of this application proposes an application launching device, including:

[0022] The settings module is used to set the first display attribute of the push activity to visible if it is detected that the currently created activity is a push activity of a third-party message push service when a trigger event of a notification message in the notification bar is detected and the landing content page corresponding to the notification message in the target application is launched.

[0023] Create a module to create the first window for the push activity;

[0024] The drawing module is used to draw the transition animation corresponding to the default homepage of the target application;

[0025] The display module is used to launch the first window to display the transition animation.

[0026] As one possible implementation, the settings module is specifically used to: during the process of detecting a trigger event for a notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, determine whether the target application meets a first set condition; if the target application meets the first set condition, and the currently created Activity is a push Activity, then set the first display attribute of the push Activity to visible.

[0027] As one possible implementation, the first setting condition includes: the target application is located in the set application list; wherein, the set application list includes function tags of multiple applications, and the function tags are used to indicate whether the application has the set function; the function tag of the target application in the set application list is the target tag; wherein, the target tag is used to indicate that the target application has the set function.

[0028] As one possible implementation, the content displayed in the transition animation matches the theme style of the target application's default homepage; in response to the target application launching from the desktop, the transition animation is displayed as a gradual zoom-in; in response to the target application launching from a non-desktop location, the transition animation is displayed as a left-shift toggle or a right-shift toggle.

[0029] As one possible implementation, the device also includes:

[0030] The judgment module is used to determine whether the default homepage theme is available in response to the window removal event of the push Activity;

[0031] The settings module is also used to: if available, set the value of the first flag to the first value; wherein the first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the first value is used to indicate that the removal of the first window is not allowed;

[0032] The display module is also used to: display the default homepage through the first window.

[0033] As one possible implementation, the device also includes:

[0034] The reading module is used to read the second display attribute of the non-landing page Activity if it is detected that the currently created Activity is a non-landing page Activity of the target application;

[0035] The display module is also used to: display the default homepage based on the second display attribute.

[0036] As one possible implementation, the display module is specifically used to: launch a second window of the non-landing page Activity in response to the second display attribute being visible, and prevent the drawing of transition animations in the second window; and continue to display the content displayed in the first window through the second window.

[0037] As one possible implementation, the setting module is also used to: set the value of the second flag to a second value; wherein the second flag is used to indicate whether a launch window for the push Activity has been created, and the second value is used to indicate that a launch window for the push Activity has been created.

[0038] As one possible implementation, the display module is specifically used to: in response to the second display attribute being visible, determine whether the value of the second flag bit is the second value, and determine whether the target application meets the first set condition; if the value of the second flag bit is the second value, and the target application meets the first set condition, then start the second window of the non-landing page Activity, and prohibit drawing transition animations in the second window.

[0039] As one possible implementation, the setting module is also used to: set the value of the first flag to a third value when the content displayed in the first window continues to be displayed through the second window; wherein the first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the third value is used to indicate whether the removal of the first window is allowed;

[0040] The device also includes an execution module for performing a destruction operation on the push Activity to remove the first window.

[0041] As one possible implementation, the display module is specifically used to: refuse to start the second window in response to the second display property being transparent; and continue to start the first window to display the default homepage.

[0042] As one possible implementation, the device further includes: a processing module, configured to, in response to the window removal timing of the non-landing page Activity, determine whether the second window of the non-landing page Activity has been launched; if the second window has been launched, set the value of the third flag bit to the fourth value; wherein the third flag bit is used to indicate whether the removal of the second window of the non-landing page Activity is allowed, and the fourth value is used to indicate that the removal of the second window is allowed; remove the second window, and during the removal of the second window, display the removal animation corresponding to the default homepage; wherein the removal animation is displayed in the form of gradually disappearing.

[0043] As one possible implementation, the processing module is further configured to: if the second window is not started, then, under the condition of satisfying the second setting, set the value of the first flag to the third value, and perform a destruction operation on the pushing Activity to remove the first window; wherein, the first flag is used to indicate whether the removal of the first window of the pushing Activity is allowed, and the third value is used to indicate that the removal of the first window is allowed; wherein, the second setting condition includes: there is an Activity with the display attribute set to visible among the Activities created after the currently created Activity.

[0044] As one possible implementation, the device also includes a startup module, which, if it is detected that the currently created Activity is the landing page Activity of the target application, launches a third window of the landing page Activity to display the frame of the landing content page in the third window.

[0045] Another embodiment of this application proposes an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the application launch method as described in the foregoing aspect.

[0046] Another embodiment of this application proposes a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the application startup method as described in the foregoing aspect.

[0047] Another embodiment of this application proposes a chip including an interface circuit and a processing circuit coupled to each other, the interface circuit being used to input or output signals, and the processing circuit being configured to execute the application startup method as described in the foregoing aspect.

[0048] Another embodiment of this application proposes a computer program product having a computer program stored thereon, which, when executed by a processor, implements the application startup method as described in the foregoing aspect.

[0049] The application launch method, device, electronic device, and storage medium proposed in this application, when detecting that the currently created Activity is a push Activity of a third-party message push service (such as SdkPushActivity), update the display attribute of the push Activity from transparent to visible, create and launch the first window of the push Activity to display the transition animation corresponding to the default home page of the target application. This can provide visual feedback to the user as soon as possible, so that the user understands that the system is normally performing the operation of launching the application, reduce the user's waiting time, and improve the user experience in the application launch scenario.

[0050] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0051] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0052] Figure 1 This is a flowchart illustrating an application startup method provided in an embodiment of this application.

[0053] Figure 2 This is a flowchart illustrating another application launch method provided in an embodiment of this application;

[0054] Figure 3 A flowchart illustrating another application launch method provided in an embodiment of this application;

[0055] Figure 4 A flowchart illustrating another application launch method provided in an embodiment of this application;

[0056] Figure 5 A flowchart illustrating another application launch method provided in an embodiment of this application;

[0057] Figure 6 A schematic diagram illustrating the display of various application activities in the notification bar before and after optimization, as provided in the embodiments of this application.

[0058] Figure 7 A time consumption statistics chart of response time before and after optimization provided for embodiments of this application;

[0059] Figure 8 A schematic diagram illustrating the implementation principle of the overall solution for improving the response speed of application launch from the notification bar, as provided in the embodiments of this application.

[0060] Figure 9 This is a flowchart illustrating the implementation scheme for two activities created before and after each other during the process of launching an application via the notification bar, as provided in the embodiments of this application.

[0061] Figure 10 A comparison chart showing the response time of each application before and after optimization, provided in the embodiments of this application;

[0062] Figure 11 This is a schematic diagram of the structure of an application launch device provided in an embodiment of this application;

[0063] Figure 12 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0064] Figure 13 This is a schematic diagram of the structure of a chip proposed in an embodiment of this application. Detailed Implementation

[0065] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0066] In recent years, with the continuous development of information technology, applications on electronic devices have become increasingly diverse, accompanied by a massive influx of push notifications. Electronic devices recommend information or resources through push notifications, content recommendations, and pop-up ads. Among these, launching an application by clicking a push notification is a common scenario in recommendation scenarios. This process is as important as launching an application from the desktop. Furthermore, launching an application by clicking a push notification in the notification bar (hereinafter referred to as notification message) becomes more complex and varied due to the continuous launch of multiple interfaces. In this scenario, how to respond more quickly to user click events and shorten response time is a crucial metric to focus on.

[0067] In related technologies, when a user clicks a notification in the notification bar to launch the application's landing page, the first Activity created is usually provided by SDK Push and set as a transparent page. Subsequent Activities of the corresponding application are then launched until the final landing page of the application is displayed. Because the initial Activity does not create a launch window, the launch animation is delayed until the application's Activities, resulting in a slow response time.

[0068] In other words, most push services from electronic device manufacturers exist in the form of SDKPush. During application launch, an SDKPushActivity is created first, and then the data carried in the notification message is passed to subsequent Activities. Finally, the application decides to launch the landing content page corresponding to the notification message. In this process, SDKPushActivity is often set to transparent to minimize its presence. However, during application cold starts, because SDKPushActivity is set to transparent (i.e., no window is launched), when the user clicks the notification message, the relevant animation is not performed until the application's first Activity (marked as Activity1) is launched. From the user's visual feedback, this manifests as follows: when the user clicks the notification message and launches the application, the notification bar collapses first. Since SDKPush is transparent at this time, the foreground interface is displayed. If the subsequent Activity1 of the application is visible, the application's home page is displayed, and then the landing content page begins to appear; if the subsequent Activity1 of the application is transparent, the foreground interface remains displayed. The entire process manifests as the electronic device failing to open the application for a prolonged period after the user clicks on the notification message. This outcome is significantly different from the user's expectations, and the user's feedback will reflect a slow and severely lagging electronic device system response.

[0069] To address the aforementioned problems, this application proposes an application startup method, apparatus, electronic device, and storage medium.

[0070] The application launching method, apparatus, electronic device, and storage medium of this application are described below with reference to the accompanying drawings.

[0071] Figure 1 This is a flowchart illustrating an application startup method provided in an embodiment of this application.

[0072] This application embodiment illustrates the application launch method configured in an application launch device. The application launch device can be applied to any electronic device so that the electronic device can perform the application launch function.

[0073] Among them, electronic devices can be any device with computing capabilities, such as mobile terminals, which can be hardware devices with various operating systems, touch screens and / or displays, such as mobile phones, tablets, personal digital assistants, wearable devices, etc.

[0074] In any embodiment of this application, the application startup method can be executed by a chip. The chip includes image signal processing (ISP), central processing unit (CPU), application-specific integrated circuit (ASIC), digital signal processor (DSP), field-programmable gate array (FPGA), system-on-a-chip (SoC), reduced instruction set computer (RISC), etc., which will not be listed individually here.

[0075] like Figure 1 As shown, the application launch method may include the following steps S101 to S103:

[0076] In step S101, during the process of detecting the trigger event of the notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created Activity is a push Activity of a third-party message push service, then the first display attribute of the push Activity is set to visible.

[0077] Triggering events include, but are not limited to: click events, press events, etc.

[0078] The notification message can be any message pushed in the notification bar.

[0079] The landing page is used to display the complete message content corresponding to the notification message.

[0080] In this embodiment of the application, when it is detected that the user has triggered a trigger event for the notification message in the notification bar, the landing content page corresponding to the notification message in the target application can be launched. During the launch of the landing content page, it can be detected whether the currently created Activity is a push Activity of a third-party message push service (such as SdkPushActivity). If so, the display attribute of the push Activity (referred to as the first display attribute in this application) can be updated from transparent to visible.

[0081] Step S102: Create the first window of the push Activity and draw the transition animation corresponding to the default home page of the target application.

[0082] The transition animation is used to gradually display the target application's default homepage.

[0083] In this embodiment, a launch window for the push Activity (referred to as the first window in this application) can be created, and a transition animation corresponding to the default homepage of the target application can be drawn.

[0084] Step S103: Start the first window to display the transition animation.

[0085] In this embodiment of the application, the transition animation of the default homepage can be displayed by launching the first window.

[0086] The application launch method of this application, when detecting that the currently created Activity is a push Activity of a third-party message push service (such as SdkPushActivity), updates the display attribute of the push Activity from transparent to visible, creates and launches the first window of the push Activity to display the transition animation corresponding to the default home page of the target application. This can provide visual feedback to the user as soon as possible, so that the user understands that the system is normally performing the operation of launching the application, reducing the user's waiting time and improving the user experience in the application launch scenario.

[0087] This application provides another method for launching an application. Figure 2 This is a flowchart illustrating another application startup method provided in an embodiment of this application.

[0088] It should be noted that the application startup method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0089] like Figure 2 As shown, the application launch method may include the following steps S201 to S204:

[0090] Step S201: During the process of detecting the trigger event of the notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, it is determined whether the target application meets the first set condition.

[0091] The first setting condition is a pre-set condition.

[0092] For example, the first setting condition may include: the application category to which the target application belongs matches the set category (such as audio and video, communication, news, games, etc.).

[0093] For example, the first setting condition may include: the target application is located in the setting application list, wherein the setting application list includes function tags of multiple applications, the function tags are used to indicate whether the application has a setting function (such as the function of performing the technical solution provided in this application), and the function tag of the target application in the setting application list is a target tag; wherein the target tag is used to indicate that the target application has a setting function.

[0094] For example, taking the function flag as an on / off state as an example, the function flag has two values: on and off. When the function flag of an application is on, it indicates that the application has the setting function, while when the function flag of an application is off, it indicates that the application does not have the setting function.

[0095] It should be understood that in practical applications, other initial conditions can be set according to application requirements, and this application embodiment does not limit this.

[0096] In this embodiment of the application, when a trigger event for a notification message in the notification bar is detected and the landing content page corresponding to the notification message in the target application is launched, it can be determined whether the target application meets the first set condition. If the target application does not meet the first set condition, the landing content page corresponding to the notification message can be launched according to the existing solution. If the target application meets the first set condition, the technical solution provided in this application can be executed, that is, the subsequent steps can be continued.

[0097] In step S202, if the target application meets the first set condition and the currently created Activity is a push Activity of a third-party message push service, then the first display attribute of the push Activity is set to visible.

[0098] In this embodiment of the application, if the target application meets the first set condition, it can be further determined whether the currently created Activity is a push Activity of a third-party message push service (such as SdkPushActivity). If so, the first display attribute of the push Activity can be updated from transparent to visible.

[0099] In step S203, the first window of the push activity is created, and the transition animation corresponding to the default home page of the target application is drawn.

[0100] The explanation of step S203 can be found in the relevant description in any embodiment of this application, and will not be repeated here.

[0101] In any embodiment of this application, the content displayed in the transition animation can match or be consistent with the theme style of the target application's default homepage to ensure that the startup content is consistent with the content when the target application is cold-started from the desktop.

[0102] In any embodiment of this application, when the target application is launched from the desktop, the transition animation can be displayed as a gradual zoom-in.

[0103] In any embodiment of this application, when the target application is not launched from the desktop, the transition animation can be displayed by switching to the left or switching to the right.

[0104] In step S204, the first window is started to display the transition animation.

[0105] The explanation of step S204 can be found in the relevant description in any embodiment of this application, and will not be repeated here.

[0106] The application launch method of this application embodiment only updates the display attribute of the push activity from transparent to visible, and creates and launches the first window of the push activity to display the transition animation corresponding to the default homepage of the target application, when the target application meets the first set condition and the currently created Activity is a push activity of a third-party message push service (such as SdkPushActivity). This can meet the personalized application needs in different scenarios.

[0107] This application provides another method for launching an application. Figure 3 This is a flowchart illustrating another application startup method provided in an embodiment of this application.

[0108] It should be noted that the application startup method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0109] like Figure 3 As shown, the application launch method may include the following steps S301 to S306:

[0110] In step S301, during the process of detecting the trigger event of the notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created Activity is a push Activity of a third-party message push service, then the first display attribute of the push Activity is set to visible.

[0111] Step S302: Create the first window of the push Activity and draw the transition animation corresponding to the default home page of the target application.

[0112] Step S303: Start the first window to display the transition animation.

[0113] The explanation of steps S301 to S303 can be found in the relevant description in any embodiment of this application, and will not be repeated here.

[0114] Step S304: In response to the window removal timing of the push Activity, determine whether the theme of the default homepage is available.

[0115] The window removal timing of the push Activity refers to the removal timing that is set in advance for the launch window (i.e., the first window) of the push Activity. For example, the window removal timing of the push Activity can be: the transition animation has finished displaying.

[0116] The availability of a theme for the target application's default homepage means that the default homepage has a theme and the theme value is not 0; the unavailability of a theme for the default homepage means that the default homepage has no theme or the theme value of the default homepage is 0.

[0117] In this embodiment of the application, when the window of the push Activity is removed at the current time, it can be determined whether the theme of the default homepage is available. For example, it can be determined whether the theme value of the default homepage is 0. If the theme value of the default homepage is 0, it indicates that the theme of the default homepage is unavailable. If the theme value of the default homepage is not 0, it indicates that the theme of the default homepage is available.

[0118] In this application, if the default homepage theme is available, the subsequent steps can be performed. If the default homepage theme is unavailable, the landing content page corresponding to the notification message can be launched according to the existing solution.

[0119] Step S305: If available, set the value of the first flag bit to the first value; wherein the first flag bit is used to indicate whether the removal of the first window of the push Activity is allowed, and the first value is used to indicate that the removal of the first window is not allowed.

[0120] The first flag is used to indicate whether the removal of the first window of the push Activity (such as SdkPushActivity) is allowed. For example, the first flag can also be called: whether the removal of the SdkPushActivity window is allowed.

[0121] It should be noted that if the window of the pushed Activity is removed immediately, the following problem may occur: if the display attribute of the subsequently created Activity is transparent, a screen flickering problem will occur, that is, the screen will be switched back to the foreground, which will seriously degrade the user experience.

[0122] To address the aforementioned issues, this application allows setting the first flag to the first value when the default homepage theme of the target application is available. This temporarily prevents the removal of the first window of the push Activity, thus avoiding screen flickering caused by prematurely removing the first window while subsequent Activities still have transparent pages (i.e., the display attribute of subsequent Activities is transparent).

[0123] Step S306: Display the default homepage through the first window.

[0124] In this embodiment of the application, the default homepage of the target application can continue to be displayed through the first window.

[0125] In any embodiment of this application, after steps S102, S103, S203, S204, S302, or S303, the value of the second flag bit can be set to a second value; wherein the second flag bit is used to indicate whether a launch window for the push Activity has been created, and the second value is used to indicate that a launch window for the push Activity has been created.

[0126] For example, the second flag is marked as FlagA. The newly added FlagA can be used to identify the improvement of the activity launch window stage of the push Activity (SdkPushActivity) in the above embodiments. When FlagA is the second value, it indicates that the landing content page corresponding to the notification message in the target application is launched in accordance with the technical solution provided in this application. When FlagA is not the second value, it indicates that the landing content page corresponding to the notification message in the target application is launched in accordance with the technical solution provided in the prior art.

[0127] The application launch method of this application embodiment, when the window of the push activity (such as SDKPushActivity) of the third-party message push service is removed and the theme of the default homepage of the target application is available, does not remove the first window of the push activity temporarily, and continues to display the default homepage through the first window. This can avoid the screen flickering problem caused by removing the first window in advance and the subsequent activity still having a transparent page (i.e. the display attribute of the subsequent activity is transparent), thus improving the user experience.

[0128] This application provides another method for launching an application. Figure 4 This is a flowchart illustrating another application startup method provided in an embodiment of this application.

[0129] It should be noted that the application startup method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0130] like Figure 4 As shown, the application launch method may include the following steps S401 to S402:

[0131] In step S401, during the process of detecting the trigger event of the notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created Activity is a non-landing page Activity of the target application, then the second display attribute of the non-landing page Activity is read.

[0132] Non-landing page Activity refers to all other Activities in the target application's activities other than the landing page Activity (i.e., LandAppActivity), including any Activity created before the target application's LandAppActivity, such as the first Activity (i.e., FirstAppActivity), the second Activity, etc.

[0133] The second display attribute includes transparency and visibility.

[0134] In this embodiment of the application, when a user triggers a notification message in the notification bar, the landing content page corresponding to the notification message in the target application can be launched. During the launch of the landing content page, it can be detected whether the currently created Activity is a non-landing page Activity of the target application. If the currently created Activity is a non-landing page Activity of the target application, the display attributes of the non-landing page Activity (referred to as the second display attribute in this application) can be further read.

[0135] Step S402: Display the default homepage of the target application according to the second display attribute.

[0136] In this embodiment of the application, the default homepage of the target application can be displayed specifically based on the second display attribute of the non-landing page Activity.

[0137] In any embodiment of this application, when the second display attribute of a non-landing page Activity is visible, the launch window of the non-landing page Activity (referred to as the second window in this application) can be launched, and the transition animation corresponding to the default homepage can be prevented from being drawn in the second window. The content displayed in the first window can continue to be displayed through the second window.

[0138] As an example, when the second display attribute of the non-landing page Activity is visible, it can be further determined whether the value of the second flag is the second value, and whether the target application meets the first set condition. If the value of the second flag is the second value, and the target application meets the first set condition, then the second window of the non-landing page Activity is launched, and the transition animation corresponding to the default homepage is prohibited from being drawn in the second window, so that the content displayed in the first window can continue to be displayed through the second window.

[0139] The explanation of the second flag bit and the first setting condition can be found in the relevant descriptions in the above embodiments of this application, and will not be repeated here.

[0140] It should be noted that replacing the content displayed in the currently launched second window with the content displayed in the first window launched by the push activity of a third-party message push service (such as SdkPushActivity) will not be noticeable to the user since the content drawn in both is the default home page of the target application. This maintains the consistency of the interface content and improves the user experience.

[0141] In any embodiment of this application, when the second display attribute of a non-landing page Activity is transparent, the launch of the second window of that non-landing page Activity can be refused, and the first window can continue to launch to display the default homepage of the target application. This avoids the situation where the foreground interface is switched back when the display attribute of the currently created Activity is transparent, thus improving the user experience.

[0142] In any embodiment of this application, when the second display attribute of the non-landing page Activity is visible, and the content displayed in the first window continues to be displayed through the second window of the non-landing page Activity, the value of the first flag can be set to a third value, and a destruction operation can be performed on the push Activity to remove the first window. Therefore, after a visible activity appears, performing a destruction operation on the push Activity to remove the first window not only avoids the problem of prematurely switching back to the foreground interface, but also allows for timely release of resources.

[0143] The first flag indicates whether the removal of the first window of the push Activity is allowed, and the third value indicates whether the removal of the first window is allowed. It should be noted that the explanation of the first flag can be found in the relevant description in the above embodiments of this application, and will not be repeated here.

[0144] The application launch method of this application embodiment displays the default homepage of the target application based on the second display attribute of the non-landing page Activity, which can take into account both user experience and resource consumption.

[0145] This application provides another method for launching an application. Figure 5 This is a flowchart illustrating another application startup method provided in an embodiment of this application.

[0146] It should be noted that the application startup method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0147] like Figure 5 As shown, the application startup method may include the following steps S501 to S506:

[0148] In step S501, during the process of detecting the trigger event of the notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created Activity is a non-landing page Activity of the target application, then the second display attribute of the non-landing page Activity is read.

[0149] The explanation of step S501 can be found in the relevant description in the above embodiments of this application, and will not be repeated here.

[0150] In any embodiment of this application, if the currently created Activity is not a non-landing page Activity of the target application, for example, if the currently created Activity is a landing page Activity (LandAppActivity) of the target application, the launch window of the landing page Activity (referred to as the third window in this application) can be launched to display the frame of the landing content page in the third window, so that the user can know the specific message content displayed in the landing content page in a timely manner.

[0151] Step S502: Display the default homepage of the target application according to the first display attribute.

[0152] The explanation of step S502 can be found in the relevant description in the above embodiments of this application, and will not be repeated here.

[0153] In step S503, in response to the window removal timing of the non-landing page Activity, it is determined whether the second window of the non-landing page Activity has been launched. If yes, steps S504 to S505 are executed; otherwise, step S506 is executed.

[0154] The window removal timing for non-landing page Activities refers to the removal timing that is pre-set for the launch window (i.e., the second window) of the non-landing page Activity. For example, the window removal timing for non-landing page Activities can be: the application homepage has finished displaying.

[0155] In this embodiment of the application, when the window of the non-landing page Activity of the target application is removed at the current time, it is determined whether the second window of the non-landing page Activity has been started. If yes, steps S504 to S505 are executed; if no, step S506 is executed.

[0156] It should be noted that steps S504 to S505 and step S506 are two parallel implementation methods, and in actual application, only one needs to be executed.

[0157] Step S504: Set the value of the third flag to the fourth value; wherein the third flag is used to indicate whether the removal of the second window of the non-landing page Activity is allowed, and the fourth value is used to indicate whether the removal of the second window is allowed.

[0158] In this embodiment of the application, when the second window of the non-landing page Activity has been launched (i.e., the second display attribute of the non-landing page Activity is visible), the value of the third flag can be set to the fourth value; wherein, the third flag is used to indicate whether the removal of the second window of the non-landing page Activity is allowed, and the fourth value is used to indicate whether the removal of the second window of the non-landing page Activity is allowed.

[0159] Step S505: Remove the second window, and during the removal of the second window, display the removal animation corresponding to the default homepage; wherein the removal animation is displayed in the form of gradually disappearing.

[0160] The removal animation is used to show the default homepage gradually disappearing. For example, the default homepage can be made to gradually disappear by gradually changing its transparency.

[0161] In this embodiment of the application, in order to reduce resource consumption, when the window removal time of the non-landing page Activity is reached, the second window can be removed, and during the removal of the second window, the removal animation corresponding to the default homepage is displayed, so as to realize the gradual disappearance of the default homepage.

[0162] In step S506, if the second setting condition is met, the value of the first flag is set to the third value, and the push Activity is destroyed to remove the first window.

[0163] The first flag indicates whether the removal of the first window of the push Activity is allowed, and the third value indicates whether the removal of the first window is allowed. It should be noted that the explanation of the first flag can be found in the relevant description in the above embodiments of this application, and will not be repeated here.

[0164] In this embodiment, if the second window of the non-landing page Activity is not launched (i.e., the second display attribute of the non-landing page Activity is transparent), the first window can be temporarily not removed until the second set condition is met. Then, the first flag is set to the third value, and the push Activity is destroyed to remove the first window. This avoids the screen flickering problem caused by prematurely removing the first window while the subsequent Activity still has a transparent page (i.e., the display attribute of the subsequent Activity is still transparent), thus improving the user experience.

[0165] The second condition includes: there exists an Activity with a visible display attribute among the Activities created after the currently created Activity. That is, if the display attribute of an Activity (including the landing page Activity) created between the first Activity (FirstAppActivity) and the landing page Activity (LandAppActivity) of the target application is visible, the launch window of that Activity can be launched to display relevant content, and the second condition is satisfied. In this case, the first flag can be set to the third value, and the push Activity can be destroyed to remove the first window.

[0166] The application launch method of this application embodiment removes the second window when the window of a non-landing page Activity is removed and the second window of the non-landing page Activity has been launched. During the removal of the second window, a removal animation corresponding to the default homepage is displayed. This not only enables timely release of resources but also enhances visual continuity and improves the user experience. When the window of a non-landing page Activity is removed but the second window of the non-landing page Activity has not been launched, the first window is not removed until a second predefined condition is met. This avoids the screen flickering problem caused by prematurely removing the first window while subsequent Activities still have transparent pages (i.e., the display attribute of subsequent Activities remains transparent), thus improving the user experience.

[0167] In any embodiment of this application, to address the problems existing in the prior art, this application redesigns the window launch process and the timing of the rendering of the before and after animations, and executes them in advance. The specific process includes: if it is detected that the first Activity launched by the application is provided by a third-party SDKPush, the application launch process begins. First, the display attribute of the SDKPushActivity to be launched is set to transparent, the theme is replaced with the theme of the default homepage of the application to be launched, the launch window is opened, and the display attribute of the current SDKPushActivity is set to visible. Then, when removing the window, the launch window of the SDKPushActivity created this time is not removed temporarily. Second, when launching the launch window of the first Activity of the application, the transition animation is canceled. Subsequently, the window removal action of the first Activity of the application is executed normally, and the gradually disappearing window animation is played. Finally, when a displayable interface appears, the window removal operation of SDKPushActivity is allowed to be executed, completing the release of resources. This solution can shorten the response time of the user clicking on the notification message to launch the application, improving the user experience.

[0168] In other words, if the current application is detected to have been launched via a notification, the process proceeds to the landing content page corresponding to the notification. During this process, the first Activity is typically provided by SDK Push and set to transparent, followed by subsequent launches of the application's Activities until the final landing content page is displayed. This process suffers from slow response times because the initial Activity doesn't create a launch window, causing the launch animation to lag behind the application's Activities. To address this issue, this application redesigns the window launch process and the timing of the animation rendering, executing them earlier to improve the response speed of launching the application from the notification bar.

[0169] As an example, the display of various app activities launched in the notification bar before and after optimization can be shown as follows: Figure 6 As shown, before optimization (following the existing solution), when a user clicks the notification message to launch the application, the visual feedback from the user's perspective is as follows: First, the notification bar collapses. Since the SDKPushActivity is a transparent page at this time, the foreground interface is displayed. If the first activity of the subsequent application is visible, the application home page is displayed, and then the landing content page begins to be displayed. If the first activity of the subsequent application is transparent, the foreground interface is still displayed.

[0170] To more clearly depict the specific response time, the display of various activities in the notification bar before and after optimization can be shown as follows: Figure 7 As shown. When a user clicks on a notification message, multiple activities will be created sequentially. The SDKs provided by electronic device manufacturers that include push notification services are uniformly named SDKPushActivity, while activities launched by the application itself are called AppActivity. According to... Figure 7 The described process, before optimization, involves handling Input button press events. During a cold start, process incubation and creation (bindApplication operation) are performed, followed by the creation of SDKPushActivity, and then AppActivity. Because SDKPushActivity is transparent, no content is displayed. If AppActivity is visible, the window is drawn and the launch animation is executed, resulting in a response time of DA (Daily Action). If the application's first activity is also transparent, the window is drawn and the launch animation is executed only when the next activity becomes visible, meaning both the launch window and animation are delayed until the next activity, resulting in a response time of EA (Exponential Action). In both scenarios, the delay becomes more pronounced during cold starts due to the time-consuming process creation. While warm starts may reduce response time, the transparency of SDKPushActivity still causes a delay. Overall, a more reasonable design is needed to shorten the response time in this scenario.

[0171] The application launch method provided in this application represents an optimized version, such as... Figure 6 As shown, after optimization (implemented according to the solution provided in this application), clicking the notification message will launch the application's homepage. Subsequent activities will also display the application's homepage until the final landing content page is shown, thus providing the user with visual feedback as quickly as possible and allowing the user to understand that the system is successfully launching the application. Similarly, the optimized response time statistics are as follows: Figure 7As shown, when the display attribute of SdkPushActivity is set to visible, the startup window and animation operations will be executed in parallel with the application creation process after Input, resulting in a response time of BA. Assuming that the ideal interval time for each segment ABCDE is T, this application reduces the response time by 2T to 3T.

[0172] The entire process of launching an application via the notification bar mainly involves the creation and activation of two or more activities. For example... Figure 8 The overall solution for improving the response speed of launching applications via the notification bar is shown below. Taking the creation of three activities during the application launch process as an example, the logic before and after optimization is explained. Let the activity launched by the message push service provided by the electronic device manufacturer's SDK be SDKPushActivity, the first activity launched by the application be FirstAppActivity, and the final landing page activity after clicking the notification message be LandAppActivity.

[0173] It should be noted that, Figure 8 In this context, "Land" refers to the landing page or landing content page, and "Next" refers to the content displayed in the launch window of the next Activity after the currently created Activity.

[0174] Before optimization, when a user clicked a notification in the notification bar, the system would launch the application. Due to the transparency attribute of SDKPushActivity, no window would be launched, and there would be no transition animation. When the activity was created, since no window was launched, there was no window removal operation. When the application's first activity was launched, a window would be launched, displaying a transition animation. The displayed content was the theme configured for the current activity, and the transition animation was a gradual enlargement of the application's homepage. After the enlargement transition animation finished, the application's homepage would be fully displayed. When the subsequent application's landing page was created, launched, and its frames were drawn, FirstAppActivity would perform a window removal operation. This was accompanied by a removal animation where the current window gradually disappeared, and the frames of the subsequent landing page were gradually displayed, finally waiting for the landing page to load the notification message. It's easy to see that each activity goes through the logic of window launch and removal, such as... Figure 7 As shown in the detailed logic, taking SdkPushActivity and FirstAppActivity as examples, both have a window launch and removal judgment, but the former selects the non-launched window and the latter selects the launched window, which is the key to affecting the response time.

[0175] Based on the above logic, combined with Figure 9This application describes the scheme for launching the application via the notification bar and the corresponding activities before and after. The following five key modifications are made to optimize this scenario (where, Figure 9 The phrase "following the original route" refers to implementing the existing plan.

[0176] (1) Based on the SdkPushActivity activity launch window stage, when it is determined that the currently created activity is an SdkPushActivity and meets other relevant preset conditions (such as the currently clicked application being in the set application list, and the function mark in the set application list being the target mark), it indicates that the SdkPush activity creation stage of the notification bar launch application process has been entered. This stage will add a launch window and corresponding transition animation, set the display attribute of the currently created activity to visible, and specify that the animation content of the drawn transition animation is the theme style of the default homepage of the currently clicked application, ensuring that the launch content is consistent with the content when the application is cold-started from the desktop. In addition, the display form of the transition animation is designed to be a gradual zoom effect when launching from the desktop, and a left-shifting or right-shifting switching effect when launching from outside the desktop. A new flag flagA is added to indicate the above changes.

[0177] (2) Based on the SdkPushActivity activity window removal stage, when it is determined that the currently created activity is an SdkPushActivity and meets other relevant preset conditions, it is determined whether the theme value obtained in (1) is 0. If it is not 0 (i.e. the default homepage theme is available), then in its window removal logic, the launch window of the currently created activity will not be removed temporarily, and it is stipulated that the launch window will continue to be displayed. The specific removal time will be postponed until a visible content page appears, which can avoid the screen flickering problem caused by removing the window in advance and the subsequent created activities still having transparent pages.

[0178] (3) Based on the FirstAppActivity activity launch window stage, there are two cases: 1. If the activity in this stage is set to visible, a launch window is required. At this time, it is determined whether the FlagA flag is enabled and whether the relevant preset conditions are met. If so, the transition animation is prohibited in its window, and only the window is launched. The display content of the current launch window will replace the display content of the window launched by the SdkPushActivity activity. Since the content drawn by both is the same, which is the default home page of the application, the user will not be aware of the replacement operation. That is, the user will not be visually aware, and the consistency of the interface content can be maintained. 2. If the activity in this stage is set to transparent, there is no need to launch a window. The window of the SdkPushActivity activity will be retained and continue to be displayed. The display content is still the default home page of the application.

[0179] (4) Based on the FirstAppActivity activity window removal phase, if the FirstAppActivity has already started a window, the corresponding window will be removed. The removal animation is a gradual disappearance animation. After it disappears, the content of the next Activity's frame will be displayed.

[0180] (5) Based on the activities initiated by the application up to the LandAppActivity activity, if any of the activities is visible, the flag allowing the removal of the SDKPushActivity's launch window will be enabled, and the window will be removed when SDKPushActivity performs the Destroy operation. Furthermore, the Finish time of SDKPushActivity is uniformly postponed until after a visible activity appears; otherwise, its Finish operation will be prevented to avoid prematurely switching back to the foreground interface.

[0181] The technical solution provided in this application is applicable to various applications that integrate third-party push services for push notifications, including but not limited to audio / video apps, browser apps, communication apps, news apps, and game apps. It can improve the response speed and shorten response time when launching applications via the notification bar. Based on the technical solution provided in this application, the applicant selected six of the most frequently used third-party applications for testing. The comparison results of response time before optimization (implemented according to the existing solution) and after optimization (implemented according to the solution provided in this application) are as follows: Figure 10 As shown.

[0182] To implement the above embodiments, this application also proposes an application launch device.

[0183] Figure 11 This is a schematic diagram of an application launch device provided in an embodiment of this application.

[0184] like Figure 11 As shown, the application launch device 1100 may include: a setting module 1110, a creation module 1120, a drawing module 1130, and a display module 1140.

[0185] Among them, the setting module 1110 is used to set the first display attribute of the push activity to visible if it is detected that the currently created activity is a push activity of a third-party message push service when the trigger event of the notification message in the notification bar is detected and the landing content page corresponding to the notification message in the target application is launched.

[0186] Create module 1120 to create the first window for the push activity;

[0187] The drawing module 1130 is used to draw the transition animation corresponding to the default homepage of the target application;

[0188] Display module 1140 is used to start the first window to display the transition animation.

[0189] Furthermore, in one implementation of this application embodiment, the setting module 1110 is specifically used to: determine whether the target application meets the first set condition during the process of detecting the triggering event of the notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application; if the target application meets the first set condition and the currently created Activity is a push Activity, then set the first display attribute of the push Activity to visible.

[0190] In one implementation of this application, the first setting condition includes: the target application is located in the set application list; wherein, the set application list includes function tags of multiple applications, and the function tags are used to indicate whether the application has a setting function; the function tag of the target application in the set application list is a target tag; wherein, the target tag is used to indicate that the target application has a setting function.

[0191] In one implementation of this application, the content of the transition animation matches the theme style of the default homepage of the target application; in response to the target application being launched from the desktop, the transition animation is displayed by gradually zooming in; in response to the target application being launched from a non-desktop location, the transition animation is displayed by switching to the left or to the right.

[0192] In one implementation of this application embodiment, the application launching device 1100 may further include:

[0193] The judgment module is used to determine whether the default homepage theme is available in response to the window removal event of the push Activity;

[0194] The setting module 1110 is also used to: if available, set the value of the first flag bit to the first value; wherein the first flag bit is used to indicate whether the removal of the first window of the push Activity is allowed, and the first value is used to indicate that the removal of the first window is not allowed;

[0195] Display module 1140 is also used to: display the default homepage through the first window.

[0196] In one implementation of this application embodiment, the application launching device 1100 may further include:

[0197] The reading module is used to read the second display attribute of the non-landing page Activity if it is detected that the currently created Activity is a non-landing page Activity of the target application;

[0198] Display module 1140 is also used to: display the default homepage according to the second display attribute.

[0199] In one implementation of this application, the display module 1140 is specifically used to: in response to the second display attribute being visible, launch a second window of the non-landing page Activity and prohibit drawing transition animations in the second window; and continue to display the content displayed in the first window through the second window.

[0200] In one implementation of this application, the setting module 1110 is further configured to: set the value of the second flag bit to a second value; wherein the second flag bit is used to indicate whether a launch window for the push Activity has been created, and the second value is used to indicate that a launch window for the push Activity has been created.

[0201] In one implementation of this application, the display module 1140 is specifically used to: in response to the second display attribute being visible, determine whether the value of the second flag bit is the second value, and determine whether the target application meets the first set condition; if the value of the second flag bit is the second value and the target application meets the first set condition, then start the second window of the non-landing page Activity, and prohibit drawing transition animations in the second window.

[0202] In one implementation of this application, the setting module 1110 is further configured to: when the content displayed in the first window continues to be displayed through the second window, set the value of the first flag bit to a third value; wherein the first flag bit is used to indicate whether the removal of the first window of the push Activity is allowed, and the third value is used to indicate that the removal of the first window is allowed;

[0203] The application launcher 1100 may also include:

[0204] The execution module is used to perform a destruction operation on the push Activity to remove the first window.

[0205] In one implementation of this application, the display module 1140 is specifically used to: refuse to start the second window in response to the second display attribute being transparent; and continue to start the first window to display the default homepage.

[0206] In one implementation of this application embodiment, the application launching device 1100 may further include:

[0207] The processing module is used to respond to the window removal timing of the non-landing page Activity, and to determine whether the second window of the non-landing page Activity has been launched; if the second window has been launched, the third flag is set to the fourth value; wherein, the third flag is used to indicate whether the removal of the second window of the non-landing page Activity is allowed, and the fourth value is used to indicate that the removal of the second window is allowed; the second window is removed, and during the removal of the second window, the removal animation corresponding to the default home page is displayed; wherein, the removal animation is displayed in the form of gradually disappearing.

[0208] In one implementation of this application, the processing module is further configured to: if the second window is not started, then, if the second set condition is met, set the value of the first flag to a third value, and perform a destruction operation on the push Activity to remove the first window;

[0209] The first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the third value is used to indicate whether the removal of the first window is allowed.

[0210] The second condition includes: there exists an Activity with a visible display attribute among the Activities created after the currently created Activity.

[0211] In one implementation of this application embodiment, the application launching device 1100 may further include:

[0212] The startup module is used to launch a third window of the landing page activity if it is detected that the currently created Activity is the landing page activity of the target application, so as to display the frame of the landing content page in the third window.

[0213] It should be noted that the foregoing explanation of the application launch method embodiment also applies to the application launch device of this embodiment, and will not be repeated here.

[0214] In the application launch device of this application embodiment, when it is detected that the currently created Activity is a push Activity of a third-party message push service (such as SDKPushActivity), the display attribute of the push Activity is updated from transparent to visible, and the first window of the push Activity is created and launched to display the transition animation corresponding to the default homepage of the target application. This can quickly provide visual feedback to the user, allowing the user to understand that the system is normally performing the application launch operation, reducing the user's waiting time, and improving the user experience in application launch scenarios.

[0215] To implement the above embodiments, this application also proposes an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the application startup method as described in any of the foregoing method embodiments.

[0216] Figure 12 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. For example, the electronic device 1200 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0217] Reference Figure 12 The electronic device 1200 may include one or more of the following components: processing component 1202, memory 1204, power component 1206, multimedia component 1208, audio component 1210, input / output (I / O) interface 1212, sensor component 1214, and communication component 1216.

[0218] Processing component 1202 typically controls the overall operation of electronic device 1200, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1202 may include one or more processors 1220 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1202 may include one or more modules to facilitate interaction between processing component 1202 and other components. For example, processing component 1202 may include a multimedia module to facilitate interaction between multimedia component 1208 and processing component 1202.

[0219] Memory 1204 is configured to store various types of data to support the operation of electronic device 1200. Examples of such data include instructions for any application or method operating on electronic device 1200, contact data, phonebook data, messages, pictures, videos, etc. Memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0220] Power component 1206 provides power to various components of electronic device 1200. Power component 1206 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 1200.

[0221] Multimedia component 1208 includes a screen that provides an output interface between the electronic device 1200 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1208 includes a front-facing camera and / or a rear-facing camera. When the electronic device 1200 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0222] Audio component 1210 is configured to output and / or input audio signals. For example, audio component 1210 includes a microphone (MIC) configured to receive external audio signals when electronic device 1200 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1204 or transmitted via communication component 1216. In some embodiments, audio component 1210 also includes a speaker for outputting audio signals.

[0223] I / O interface 1212 provides an interface between processing component 1202 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0224] Sensor assembly 1214 includes one or more sensors for providing state assessments of various aspects of electronic device 1200. For example, sensor assembly 1214 may detect the on / off state of electronic device 1200, the relative positioning of components such as the display and keypad of electronic device 1200, changes in position of electronic device 1200 or a component of electronic device 1200, the presence or absence of user contact with electronic device 1200, the orientation or acceleration / deceleration of electronic device 1200, and temperature changes of electronic device 1200. Sensor assembly 1214 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1214 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1214 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0225] Communication component 1216 is configured to facilitate wired or wireless communication between electronic device 1200 and other devices. Electronic device 1200 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 1216 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1216 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0226] In an exemplary embodiment, the electronic device 1200 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0227] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1204 including instructions, which can be executed by a processor 1220 of an electronic device 1200 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0228] To implement the above embodiments, this application also proposes a chip, comprising: an interface circuit and a processing circuit coupled to each other; the interface circuit being used to input or output signals; and the processing circuit being configured to execute the application startup method provided in any of the foregoing embodiments.

[0229] Figure 13 This is a schematic diagram of the structure of a chip according to an embodiment of this application. See also... Figure 13 The diagram shown is a schematic representation of the structure of chip 1300, but it is not limited to this.

[0230] Chip 1300 includes processing circuitry 1301, which is configured to execute any of the above application startup methods.

[0231] In some embodiments, chip 1300 further includes one or more interface circuits 1302. Optionally, interface circuit 1302 is connected to memory 1303, and interface circuit 1302 can be used to receive signals from memory 1303 or other devices, and interface circuit 1302 can be used to send signals to memory 1303 or other devices. For example, interface circuit 1302 can read instructions stored in memory 1303 and send the instructions to processing circuit 1301.

[0232] In some embodiments, the interface circuit 1302 performs at least one of the communication steps such as sending and / or receiving in the above method, while the processing circuit 1301 performs other steps.

[0233] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0234] In some embodiments, chip 1300 further includes one or more memories 1303 for storing instructions. Optionally, all or part of the memories 1303 may be located outside of chip 1300.

[0235] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the application startup method as described in any of the foregoing method embodiments.

[0236] To implement the above embodiments, this application also proposes a computer program product having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the application startup method as described in any of the foregoing method embodiments.

[0237] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0238] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0239] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0240] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0241] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0242] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes one or a combination of the steps of the method embodiments.

[0243] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0244] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. An application launch method, characterized in that, include: When a trigger event for a notification message in the notification bar is detected and the landing content page corresponding to the notification message in the target application is launched, if it is detected that the currently created activity is a push activity of a third-party message push service, then the first display attribute of the push activity is set to visible. Create the first window of the push Activity and draw the transition animation corresponding to the default home page of the target application; The first window is launched to display the transition animation.

2. The method according to claim 1, characterized in that, In the process of detecting a trigger event for a notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, if it is detected that the currently created activity is a push activity of a third-party message push service, then the first display attribute of the push activity is set to visible, including: During the process of detecting a trigger event for a notification message in the notification bar and launching the landing content page corresponding to the notification message in the target application, it is determined whether the target application meets the first set condition. If the target application meets the first set condition, and the currently created Activity is the push Activity, then the first display attribute of the push Activity is set to visible.

3. The method according to claim 2, characterized in that, The first set conditions include: The target application is located in the set application list; wherein, the set application list includes function tags of multiple applications, and the function tags are used to indicate whether the application has the set function; The target application's function marker in the specified application list is a target marker; wherein, the target marker is used to indicate that the target application has the specified function.

4. The method according to claim 1, characterized in that, The content displayed in the transition animation matches the theme style of the default homepage of the target application; In response to the target application being launched from the desktop, the transition animation is displayed as a gradual zoom-in; In response to the target application being launched from a non-desktop location, the transition animation is displayed by switching to the left or to the right.

5. The method according to claim 1, characterized in that, The method further includes: In response to the window removal event of the push Activity, determine whether the theme of the default homepage is available; If available, the first flag is set to the first value; wherein the first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the first value is used to indicate that the removal of the first window is not allowed. The default homepage is displayed through the first window.

6. The method according to claim 1, characterized in that, The method further includes: If it is detected that the currently created Activity is a non-landing page Activity of the target application, then the second display attribute of the non-landing page Activity is read; The default homepage is displayed according to the second display attribute.

7. The method according to claim 6, characterized in that, The step of displaying the default homepage according to the first display attribute includes: In response to the second display attribute being visible, a second window of the non-landing page Activity is launched, and the transition animation is prevented from being drawn within the second window; The content displayed in the first window continues to be displayed in the second window.

8. The method according to claim 7, characterized in that, After creating the first window of the push Activity and drawing the transition animation corresponding to the default homepage of the target application, the method further includes: The second flag is set to a second value; wherein the second flag is used to indicate whether the launch window of the push Activity has been created, and the second value is used to indicate that the launch window of the push Activity has been created.

9. The method according to claim 8, characterized in that, The response that the second display attribute is visible, launching the second window of the non-landing page Activity, and preventing the transition animation from being drawn within the second window, includes: In response to the second display attribute being visible, it is determined whether the value of the second flag bit is the second value, and whether the target application meets the first set condition; If the value of the second flag is the second value, and the target application meets the first set condition, then the second window of the non-landing page Activity is launched, and the transition animation is prohibited from being drawn in the second window.

10. The method according to claim 7, characterized in that, The method further includes: When the content displayed in the first window continues to be displayed through the second window, the value of the first flag is set to a third value; wherein, the first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the third value is used to indicate whether the removal of the first window is allowed; Perform a destruction operation on the push Activity to remove the first window.

11. The method according to claim 6, characterized in that, The step of displaying the default homepage according to the first display attribute includes: In response to the second display property being transparent, the second window is not launched; The first window will continue to be launched, displaying the default homepage.

12. The method according to any one of claims 6-11, characterized in that, The method further includes: In response to the window removal event of the non-landing page Activity, determine whether the second window of the non-landing page Activity has been launched; If the second window has been launched, the third flag is set to the fourth value; wherein the third flag is used to indicate whether the removal of the second window of the non-landing page Activity is allowed, and the fourth value is used to indicate whether the removal of the second window is allowed. Remove the second window, and during the removal of the second window, display the removal animation corresponding to the default homepage; wherein the removal animation is displayed in the form of gradually disappearing.

13. The method according to claim 12, characterized in that, After determining whether the second window has been started, the method further includes: If the second window is not started, then if the second set condition is met, the value of the first flag is set to the third value, and the push Activity is destroyed to remove the first window; The first flag is used to indicate whether the removal of the first window of the push Activity is allowed, and the third value is used to indicate whether the removal of the first window is allowed. The second setting condition includes: among the Activities created after the currently created Activity, there exists an Activity whose display attribute is visible.

14. The method according to claim 1, characterized in that, The method further includes: If it is detected that the currently created Activity is the landing page Activity of the target application, then the third window of the landing page Activity is launched to display the frame of the landing content page in the third window.

15. An application activation device, characterized in that, include: The settings module is used to set the first display attribute of the push activity to visible if it is detected that the currently created activity is a push activity of a third-party message push service when a trigger event of a notification message in the notification bar is detected and the landing content page corresponding to the notification message in the target application is launched. Create a module to create the first window of the push Activity; The drawing module is used to draw the transition animation corresponding to the default homepage of the target application; The display module is used to launch the first window to display the transition animation.

16. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the method as described in any one of claims 1-14.

17. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-14.

Images