A method, device, and storage medium for controlling application startup

Abstract

The present application provides a method, apparatus, and storage medium for controlling application startup, so as to provide a way to pull an application alive and avoid the splash screen page of the application indicated to be started. In the present application, in response to an application startup instruction triggered by a user, an application startup page is displayed, where the application startup page is a blank interface without UI capabilities; during the process of displaying the application startup page, after determining that the startup conditions of the target application are met, the business interface of the target application is displayed, where the target application is the first application indicated to be started by the application startup instruction or the second application indicated to be pulled alive in the pre-pulled configuration information obtained from the server. When pulling the second application alive, the splash screen page of the first application is avoided.

Description

Background Art

[0002] With the development of Internet technology, APPs (applications) have become an important part of users' lives. Users can use various APPs for shopping, reading, audio and video playback, chatting, etc.

[0003] At the same time, with the continuous increase in various APPs, the usage volume of a certain APP fails to meet expectations. Therefore, in order to increase the usage volume of this APP, a technical solution for application activation is proposed, that is, to activate the APP when it is launched.

[0004] In the prior art, when starting an APP and entering another APP that needs to be activated, after receiving the application start instruction triggered by the user, first enter the splash screen page of the APP indicating the start. The logo of the APP indicating the start is displayed on this splash screen page, and then enter the application program interface of the APP that needs to be activated. Every time an APP activates another APP, the splash screen page of the APP indicating the start will be displayed. Therefore, when an APP activates another APP, the splash screen cannot be avoided. Summary of the Invention

[0005] Embodiments of the present application provide a method, device, and storage medium for controlling application startup, so as to provide a way of application activation to avoid the splash screen page of the application indicating the start.

[0006] In a first aspect, the present application provides a method for controlling application startup, the method including:

[0007] Respond to the application start instruction triggered by the user, and display an application start page, where the application start page is a blank page without UI (User Interface) capabilities;

[0008] During the process of displaying the application start page, after determining that the startup condition of the target application is met, display the business interface of the target application, where the target application is the first application indicated to be started by the application start instruction, or the second application indicated to be activated in the pre-pulled configuration information obtained from the server.

[0009] In a second aspect, the present application provides a device for controlling application startup, the device including:

[0010] A first display unit, configured to respond to the application start instruction triggered by the user, and display an application start page, where the application start page is a blank page without UI capabilities;

[0011] A second display unit, which is configured to display the business interface of a target application after determining that the startup condition of the target application is met during the process of displaying the application startup page, where the target application is the first application indicated by the application startup instruction to be started or the second application indicated to be pulled alive in the pre-pulled configuration information obtained from the server.

[0012] In a possible implementation, if the application startup instruction is triggered by clicking on an application icon, the application startup page is the Splash Activity (welcome interface) created in the first application;

[0013] Among them, the taskAffintiy of the SplashActivity is different from the name of the taskAffintiy of the business interface of the first application.

[0014] In a possible implementation, the second display unit determines whether the startup condition of the target application is met in the following manner:

[0015] During the process of displaying the application startup page, it is determined whether the startup condition of the target application is met according to the pre-pulled configuration information obtained from the server. The pre-pulled configuration information is obtained from the server when the first application indicated by the previous application startup instruction is started;

[0016] Among them, the pre-pulled configuration information includes one or a combination of: indication information for indicating whether there is a second application that needs to be pulled alive, the address information of the second application, whether the pull-alive task is valid, and the valid duration of the pull-alive task.

[0017] In a possible implementation, the second display unit is specifically configured to:

[0018] After determining that there is no second application that needs to be pulled alive, display the business interface of the first application; or

[0019] After determining that there is a second application that needs to be pulled alive but the pull-alive task fails, display the business interface of the first application; or

[0020] After determining that there is a second application that needs to be pulled alive and the pull-alive task is valid, display the business interface of the second application.

[0021] In a possible implementation, the second display unit is further configured to:

[0022] After displaying the business interface of the second target application, end the task stack of the first application indicated by the application startup instruction.

[0023] In a third aspect, an embodiment of the present application provides a computing device, including at least one processor and at least one memory. The memory stores program code, and the processor is configured to read the program code stored in the memory and execute the method for controlling application startup as in the first aspect.

[0024] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing computer instructions, which, when executed by a processor, implement the method for controlling application startup in the first aspect provided by the embodiments of the present application.

[0025] The beneficial effects of the present application are as follows:

[0026] The present application provides a method, device, and storage medium for controlling application startup. After responding to an application startup instruction triggered by a user, an application startup page is displayed, and the application startup page is a blank interface without UI capabilities. During the process of displaying this blank interface, it is determined whether the startup conditions of the target application are met. After determining that the startup conditions of the target application are met, the business interface of the target application is displayed. The target application is the first application instructed to be started by the application startup instruction, or the second application instructed to be pulled alive in the pre-pulled configuration information obtained from the server. That is, during the process of displaying this blank page, after determining that the startup conditions of the first application instructed to be started are met, the business interface of the first application is displayed; or after determining that the startup conditions of the second application instructed to be pulled alive are met, the business interface of the second application is displayed. It can be seen that during the process of pulling alive the second application by the first application, the splash screen page of the first application is not displayed before the business interface of the second application is displayed, thus avoiding the splash screen page of the first application.

[0027] Other features and advantages of the present application will be described in the subsequent description, and some of them will become obvious from the description or be understood by implementing the present application. The objectives and other advantages of the present application can be achieved and obtained through the structures specifically pointed out in the written description, claims, and drawings. Description of the Drawings

[0028] To more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0029] Figure 1 Schematic diagram of the interface for pulling alive an application through an application icon in the related art;

[0030] Figure 2 Flowchart of pulling alive an application through an application icon in the related art;

[0031] Figure 3 Schematic diagram of the interface for activating an application through a third-party entry on the business side in the related art;

[0032] Figure 4 Schematic diagram of the quick access bar display interface after successfully activating the application in the related art;

[0033] Figure 5 Schematic diagram of an application scenario for controlling the startup of an application provided by an embodiment of the present application;

[0034] Figure 6 Flowchart of a method for controlling the startup of an application provided by an embodiment of the present application;

[0035] Figure 7 Schematic diagram of the interface for controlling the startup of an application by application identifier provided by an embodiment of the present application;

[0036] Figure 8 Another schematic diagram of the interface for controlling the startup of an application by application identifier provided by an embodiment of the present application;

[0037] Figure 9 Schematic diagram of the display interface of the quick access bar after successfully activating the application provided by an embodiment of the present application;

[0038] Figure 10 Overall flowchart of a method for controlling the startup of an application by application identifier provided by an embodiment of the present application;

[0039] Figure 11 Schematic diagram of the interface for controlling the startup of an application through a third-party entry on the business side provided by an embodiment of the present application;

[0040] Figure 12 Structural diagram of a device for controlling the startup of an application provided by an embodiment of the present application;

[0041] Figure 13 Structural diagram of a computing device provided by an embodiment of the present application. Detailed implementation manners

[0042] In order to make the objectives, technical solutions and beneficial effects of the present application clearer and more understandable, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0043] In the description and claims of the present invention and in the above drawings, terms such as "first", "second", etc. are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein.

[0044] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0045] The following explains some terms in the embodiments of the present application to facilitate the understanding of those skilled in the art.

[0046] 1. Activity:

[0047] Activity is one of the four most basic and common components in Android. It is an application component that provides a screen for user interaction to complete a certain task.

[0048] 2. Splash Activity:

[0049] The application startup page. When opening an application, the first thing presented to the user is not the application interface but a welcome-like interface, which is called SplashActivity. Generally, some application data initialization work can be done on this interface. The logo of the application, or advertisements, pictures, etc. can be displayed on this interface.

[0050] 3. Launch Activity:

[0051] Each application has a Launch Activity, and the default startup method is to start the APP through the Launch Activity.

[0052] 4. taskAffinity:

[0053] taskAffinity can be translated as task affinity. This parameter identifies the name of the task stack required by an Activity. By default, the name of the task stack required by all Activities is the package name of the application. When an Activity sets the taskAffinity attribute, this Activity will run in the task stack with the same name as taskAffinity when it is created. If not, a new task stack specified by taskAffinity will be created and the Activity will be placed in this stack.

[0054] 5. Task Stack:

[0055] The task stack can also be called the back stack. A task is a collection of Activities. The task stack is used to manage the Activities in the task. The Activities in the task stack are stored in the order in which the tasks are started.

[0056] 6. Scheme:

[0057] Scheme is an in-interface jump protocol. Through this protocol, it is relatively convenient to jump to a certain interface of the App.

[0058] 7. Cold Start:

[0059] Cold start is a startup method for a terminal device. This startup method is to cut off the power of the terminal device and restart it. At this time, all the things in the memory are lost, the hardware is re-detected, and then the operating system is started accordingly.

[0060] 8. Startup Page:

[0061] The startup page is the first window of the application.

[0062] During the loading process of the startup page, the client can perform many actions in the background, such as permission checking, login status checking, version update obtaining, push function checking, pulling application data, and so on.

[0063] 9. Splash Screen Page:

[0064] The splash screen page is generally for brand promotion and advertising content.

[0065] The design concept of the embodiments of the present application will be briefly introduced below.

[0066] In order to increase the usage of the APP, the technology of application activation is usually used. For example, during a certain special period, a large amount of activation promotion is required. When there is a new plan for a certain APP C and promoting this APP C mainly, a large number of activations of this APP C are required.

[0067] App activation by redirection means that when triggering the startup of a certain APP, another APP is launched instead, and the launched APP realizes app activation by redirection.

[0068] Currently, the implementation methods of activating an APP include:

[0069] I. Activating by clicking the ICON (icon) on the desktop:

[0070] As Figure 1 shown, it is a schematic interface diagram of activating APP B by clicking the icon of APP A on the desktop in the related art. As can be seen from Figure 1 , when the user clicks the icon of APP A on the desktop, it jumps to the splash screen page of APP A, and then jumps to the business interface of APP B after a few seconds. Correspondingly, Figure 2 it is a flowchart of activating an application by an icon. First, it responds to the application startup instruction triggered by the user clicking the icon of APP A, then shows the splash screen page of APP A, and finally shows the business interface of APP B to realize the activation of APP B.

[0071] II. Activating from a third-party entry on the business side by clicking business messages such as push notifications or advertisements:

[0072] As Figure 3 shown, it is a schematic interface diagram of activating APP B by the third-party entry on the business side when starting APP A in the related art. As can be seen from Figure 3 , when the user triggers the startup instruction of APP A through the push message, it jumps to the splash screen page of APP A, and then jumps to the business interface of APP B after a few seconds to realize the activation of APP B.

[0073] From the above content, it can be seen that in the related art, when activating APP B through APP A, the first page entered is the splash screen page of APP A, and this splash screen page cannot be avoided every time it is started.

[0074] Based on the above content, the present application provides a method, device, and storage medium for controlling application startup, so as to provide a way of app activation by redirection to avoid the splash screen page of the indicated startup application.

[0075] In this application, after responding to an application start instruction triggered by a user, an application start page is displayed. The application start page is a blank interface that does not carry UI capabilities. During the process of displaying this blank interface, it is determined whether the start conditions of the target application are met. After determining that the start conditions of the target application are met, the business interface of the target application is displayed. The target application is the first application indicated to be started by the application start instruction, or the second application indicated to be pulled to life in the pre-pulled configuration information obtained from the server. That is, during the process of displaying this blank page, after determining that the start conditions of the first application indicated to be started are met, the business interface of the first application is displayed; or after determining that the start conditions of the second application indicated to be pulled to life are met, the business interface of the second application is displayed. It can be seen that during the process of pulling the second application to life through the first application, the splash screen page of the first application will not be displayed before the business interface of the second application is displayed, thus avoiding the splash screen page of the first application.

[0076] In the related art, when pulling the second application to life through the first application, since the splash screen page of the first application is entered first and the business interface of the second application is finally displayed, there is both the splash screen page of the first application and the business interface of the second application in the task stack. As Figure 4 shown, there will be remnants of the first application in the recent task stack, and when clicking back from the pulled-to-life second application, it will return to the business interface of the first application, reducing the user experience. Therefore, the blank page without UI capabilities designed in this application is the Splash Activity created in the first application; the task affinity of the SplashActivity is different from the task affinity of the business interface of the first application, so this blank page has no association with the business interface of the first application. And in this application, after pulling the second application to life and displaying the business interface of the second application, the task stack of the first application is ended, that is, the Splash Activity of the first application is no longer displayed, and only the business interface of the second application is displayed, and there will be no task remnants in the recent task stack, improving the user experience.

[0077] After introducing the design concept of the embodiments of this application, the application scenarios set in this application will be briefly described below.

[0078] As Figure 5 shown, the embodiments of this application provide an application scenario for controlling application start. This application scenario includes a terminal device 10 and a server 20;

[0079] Among them, the terminal device 10 is a hardware device that supports the installation of various applications and can run various applications. It can be a PC (Personal Computer), tablet computer, PDA (Personal Digital Assistant), notebook, mobile phone and other terminal devices, or a computer with a mobile terminal device, including various portable, pocket-sized, handheld, computer-integrated or vehicle-mounted mobile devices, which can provide users with voice, data or voice and data connectivity, and exchange voice, data or voice and data with the radio access network.

[0080] The server 11 is a server for providing pre-fetch configuration information, and this server is the server corresponding to the application instructed to start by the application start instruction. This server can be independent, or any single background running device or a cluster or distributed system composed of multiple background running devices that can provide Internet services, or a device that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0081] In practical applications, the terminal device 10 and the server 11 are communicatively connected. As Figure 5 shown, the terminal device may include terminal devices 101 and 102, etc. The server 11 can be a cloud server composed of at least one server. Among them, the terminal device 102 communicates with the server 11 through a wireless access point 12 or the Internet to obtain the required pre-fetch configuration information.

[0082] In a possible application scenario, in order to facilitate reducing communication latency, the server 11 can be deployed in each region, or for load balancing, different servers 11 can respectively serve the regions corresponding to each terminal device 10. Multiple servers 11 can achieve data sharing through a blockchain. Multiple servers 11 are equivalent to a data sharing system composed of multiple servers 11. For example, the terminal device 10 is located at location a and communicates with the server 11, and the terminal device 10 is located at location b and communicates with other servers 11.

[0083] For each server 11 in the data sharing system, there is a node identifier corresponding to the server 11. Each server 11 in the data sharing system can store the node identifiers of other servers 11 in the data sharing system, so that the generated blocks can be broadcast to other servers 11 in the data sharing system according to the node identifiers of other servers 11 later. A node identifier list as shown in the following table can be maintained in each server 11, and the server 11 name and the node identifier are correspondingly stored in the node identifier list. Among them, the node identifier can be an IP (Internet Protocol) address and any other information that can be used to identify the node. Only the IP address is taken as an example in Table 1 for illustration.

[0084] Table 1

[0085] Server Name Node Identifier Node 1 119.115.151.174 Node 2 118.116.189.145 … … Node N 119.124.789.258

[0086] Next, in combination with the application scenario described above, the method for controlling the startup of an application provided by the exemplary embodiment of the present application will be described with reference to the accompanying drawings. It should be noted that the above application scenario is only shown for the convenience of understanding the spirit and principle of the present application, and the embodiments of the present application are not limited in this regard.

[0087] As Figure 6 shown, a method for controlling the startup of an application provided by an embodiment of the present application includes the following steps:

[0088] Step S600, in response to an application startup instruction triggered by a user, display an application startup page, where the application startup page is a blank interface without UI capabilities;

[0089] Step S601, during the process of displaying the application startup page, after determining that the startup conditions of the target application are met, display the business interface of the target application, where the target application is the first application indicated to be started by the application startup instruction, or the second application indicated to be pulled to life in the pre-pulled configuration information obtained from the server.

[0090] In the present application, the way to trigger the application startup instruction is:

[0091] Trigger the application startup instruction by clicking on the application identifier on the desktop, where the application identifier is an application icon or text; or

[0092] Trigger the application startup instruction through a third-party entry on the business side.

[0093] In the present application, the application startup logics corresponding to different application startup instructions are different, and the interface display processes are also different. The technical solution for controlling the startup of an application in the present application will be described in detail through the following embodiments.

[0094] Embodiment 1: Trigger an application start instruction by clicking on the application icon on the desktop.

[0095] The user clicks on the application icon of the first application on the desktop of the terminal device to trigger an application start instruction, such as Figure 7 the interface shown in (a) below, or Figure 8 the interface shown in (a) below, where the user clicks on the icon of APP4 on the desktop to trigger an application start instruction.

[0096] Correspondingly, the terminal device responds to the application start instruction triggered by the user and creates a blank interface Splash Activity that does not carry UI capabilities in the first application. This Splash Activity is completely transparent and does not require any views, and this Splash Activity is before the business interface of the first application, such as Figure 7 the interface shown in (b) below, or the interface shown in (b) of 8.

[0097] It should be noted that in this application, Splash Activity is set as the Launch Activity and has no external open interface. Therefore, during normal cold start, it will always start from SplashActivity, that is, every time an application is started by clicking on the desktop application icon, SplashActivity is started first.

[0098] During the process of displaying this SplashActivity, the terminal device determines whether the start conditions of the target application are met according to the pre-pull configuration information obtained from the server, where the target application is the first application indicated by the application start instruction to be started, or the second application indicated to be pulled alive in the pre-pull configuration information obtained from the server; such as Figure 7 or Figure 8 as shown below, the first application is APP4 and the second application is APP5;

[0099] That is, during the process of displaying this SplashActivity, it is determined according to the pre-pull configuration information obtained from the server whether the start conditions of the first application or the second application are met. The pre-pull configuration information is obtained and updated from the server when the first application indicated by the application start instruction was started last time. This pre-pull configuration information contains various information such as indication information for indicating whether to pull alive the second application, the scheme (external start general address) of the second application, the package name of the second application, the ID address of the second application, whether the pull alive task is valid, and the valid time of the pull alive task;

[0100] Therefore, when starting the target application according to the pre-pull configuration information obtained from the server:

[0101] If the indication information in the pre-pull configuration information indicates that the second application does not need to be pulled to life, then directly start the first application and display the business interface of the first application, such as Figure 7 the interface shown in (c) and subsequent in

[0102] to display the business interface of APP4; or Figure 7 If there is no first application that needs to be pulled to life in the pull configuration information, then directly start the first application and display the business interface of the first application, such as

[0103] the interface shown in (c) and subsequent in Figure 7 to display the business interface of APP4; or

[0104] Among them, whether the pull-to-life task fails can be directly determined according to the information on whether the pull-to-life task is valid included in the pre-pull configuration information, or can be indirectly determined according to the information on the valid time of the pull-to-life task included in the pre-pull configuration information; or

[0105] If the indication information in the pre-pull configuration information indicates that the second application needs to be pulled to life, there is address information of the second application that needs to be pulled to life, and after the pull-to-life task is valid, then start the second application according to the address, package name, etc. information of the second application in the pre-pull configuration information, and display the business interface of the second application, such as Figure 8 the interface shown in (c) and subsequent in

[0106] to display the business interface of APP5.

[0107] In this application, set the taskAffintiy of this SplashActivity to be different from the taskAffintiy of the business interface of the first application, that is, set an independent name for the taskAffintiy of this SplashActivity, so that this SplashActivity has no association relationship with other business interfaces of the first application, that is, distinguish this SplashActivity from other business interfaces of the first application, so that it does not affect the business function of the first application.

[0107] After determining to display the business interface of the second application, end the task stack of the first application instructed to be started by the application start instruction, that is, there will be no task stack of the first application in the system's recent task stack. At this time, there will be no interface of the first application in the display interface of the quick launch bar, but there is the business interface of the second application, such as Figure 9 shown.

[0108] At this time, there will be no residue of the first task in the recent task stack. When the return button is clicked in the business interface of the second application, since the task stack of the first application has ended, it will not return to the business interface of the first application, improving the user experience.

[0109] As Figure 10 shown, the following is an overall method flowchart for controlling application startup through an application identifier provided by an embodiment of the present application, including the following steps:

[0110] Step S1000, respond to an application startup instruction triggered by a user clicking an application icon.

[0111] Step S1001, create an empty Splash Activity in the first application and display the SplashActivity.

[0112] Step S1002, in the process of displaying the Splash Activity, determine whether it is necessary to wake up the second application according to the pre-pulling configuration information obtained from the server. If so, execute Step S1003; otherwise, execute Step S1005.

[0113] Step S1003, determine whether the wake-up task is valid according to the pre-pulling configuration information obtained from the server. If so, execute Step S1004; otherwise, execute Step S1005.

[0114] Step S1004, wake up the second application, display the business interface of the second application, and end the first application, removing the task stack of the first application.

[0115] Step S1005, start the first application and display the business interface of the first application.

[0116] Embodiment 2: Trigger an application startup instruction through a third-party entry on the business side.

[0117] In the related art, when an application startup instruction is triggered through a third-party entry on the business side such as push, other applications will also be woken up. At this time, the business-side functions of the application indicated to be started are affected. For example, it is shown in the push resources that the garbage in the first application needs to be cleared. If the second application is entered, the garbage clearance of the first application cannot be achieved, affecting the business functions of the first application. To avoid this situation, in the present application, it is set to start the application indicated to be started by triggering an application startup instruction through a third-party entry on the business side in the form of Scheme.

[0118] In this application, the SplashActivity in the application is not registered with the Scheme. At this time, there is no way for the SplashActivity to be launched from other external channels, and thus the logic of pulling the application alive by the SplashActivity cannot be triggered. This protects the logic of launching the app from other channels.

[0119] And because the SplashActivity in this application is not registered with the Scheme, the way of launching the application in the scheme form will not start from the splashActivity, that is, it will not go to the logic of pulling the second application alive. As Figure 11 shown, it is a schematic diagram of the interface for controlling the application launch through the three-party entry on the business side provided by the embodiment of this application. When the three-party entry on the business side such as user push triggers the application launch instruction, the first application indicated to be launched is directly launched, and the business interface of the first application is displayed.

[0120] In this application, while avoiding the splash screen page generated during the application pulling process, when triggering the application launch instruction through the application identifier and the three-party entry on the business side, due to different launch logics, the sources can be accurately distinguished, without affecting the normal functions of the first application indicated to be launched, and improving the user experience.

[0121] Based on the same inventive concept, the embodiment of this application also provides a device 1200 for controlling the application launch, as Figure 12 shown, the device 1200 includes: a first display unit 1201 and a second display unit 1202, where:

[0122] The first display unit 1201 is used to respond to the application launch instruction triggered by the user and display the application launch page, where the application launch page is a blank interface without UI capabilities;

[0123] The second display unit 1202 is used to determine to display the business interface of the target application after the start condition of the target application is met during the process of displaying the application launch page, where the target application is the first application indicated to be launched by the application launch instruction, or the second application indicated to be pulled alive in the pre-pulled configuration information obtained from the server.

[0124] In a possible implementation manner, if the application launch instruction is triggered by clicking the application identifier, the application launch page is the Splash Activity created in the first application;

[0125] Among them, the taskAffintiy of the SplashActivity is different from the name of the taskAffintiy of the business interface of the first application.

[0126] In a possible implementation, the second display unit 1202 determines whether the startup condition of the target application is met in the following manner:

[0127] During the process of displaying the application startup page, it is determined whether the startup condition of the target application is met according to the pre-pulling configuration information obtained from the server. The pre-pulling configuration information is obtained from the server when the first application was started in response to the previous startup application instruction.

[0128] Among them, the pre-pulling configuration information includes: one or a combination of indication information for indicating whether there is a second application that needs to be revived, the address information of the second application, whether the revival task is valid, and the valid duration of the revival task.

[0129] In a possible implementation, the second display unit 1202 is specifically configured to:

[0130] After determining that there is no second application that needs to be revived, display the business interface of the first application; or

[0131] After determining that there is a second application that needs to be revived but the revival task has expired, display the business interface of the first application; or

[0132] After determining that there is a second application that needs to be revived and the revival task is valid, display the business interface of the second application.

[0133] In a possible implementation, the second display unit 1202 is further configured to:

[0134] After displaying the business interface of the second target application, end the task stack of the first application started in response to the startup application instruction.

[0135] For the convenience of description, the above parts are divided into respective units (or modules) according to functions and described separately. Of course, when implementing this application, the functions of the respective units (or modules) can be implemented in the same or multiple software or hardware.

[0136] After introducing the method and apparatus for controlling application startup according to the exemplary embodiments of the present application, next, a computing device during the process of controlling application startup according to another exemplary embodiment of the present application will be introduced.

[0137] Those skilled in the art can understand that various aspects of the present application can be implemented as a system, method, or program product. Therefore, various aspects of the present application can be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which can be collectively referred to as "circuitry", "module", or "system" here.

[0138] In a possible implementation, the computing device provided in the embodiments of the present application may at least include a processor and a memory. Among them, the memory stores program code, and when the program code is executed by the processor, the processor is caused to execute any step in the method for starting a control application in various exemplary embodiments of the present application.

[0139] In some possible embodiments, the embodiments of the present application further provide a computer-readable storage medium, which includes program code. When the program product runs on an electronic device, the program code is used to cause the electronic device to execute the steps of any one of the methods for starting a control application in the above embodiments.

[0140] The following refers to Figure 13 to describe the computing device 1300 according to this embodiment of the present application. Figure 13 The computing device 1300 is only an example and should not impose any limitations on the functions and usage scope of the embodiments of the present application.

[0141] As Figure 13 , the computing device 1300 is presented in the form of a general-purpose computing device. The components of the computing device 1300 may include but are not limited to: the above-mentioned at least one processor 1301, the above-mentioned at least one storage unit 1302, and a bus 1303 connecting different system components (including the storage unit 1302 and the processor 1301).

[0142] The bus 1303 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a processor, or a local bus using any bus structure in a variety of bus structures.

[0143] The storage unit 1302 may include a readable medium in the form of volatile memory, such as a random access memory (RAM) 13021 and / or a cache storage unit 13022, and may further include a read-only memory (ROM) 13023.

[0144] The storage unit 1302 may further include a program / utility 13025 having a set (at least one) of program modules 13024. Such program modules 13024 include but are not limited to: an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0145] The computing device 1300 may also communicate with one or more external devices 1304 (such as a keyboard, a pointing device, etc.), and may also communicate with one or more devices that enable a user to interact with the computing device 1300, and / or communicate with any device that enables the computing device 1300 to communicate with one or more other computing devices (such as a router, a modem, etc.). Such communication may be carried out through the I / O (Input / Output) interface 1305. Moreover, the computing device 1300 may also communicate with one or more networks (such as a LAN (Local Area Network), a WAN (Wide Area Network), and / or a public network, such as the Internet) through the network adapter 1306. As shown in the figure, the network adapter 1306 communicates with other modules for the computing device 1300 through the bus 1303. It should be understood that although not shown in the figure, other hardware and / or software modules may be used in conjunction with the computing device 1300, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0146] In some possible implementation manners, all or part of the steps of implementing the foregoing method embodiments may be completed by hardware related to program instructions. The foregoing program may be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the foregoing method embodiments; and the foregoing storage medium includes: removable storage devices, ROM (Read-Only Memory), RAM (Random Access Memory), magnetic disks, or optical discs and other various media that can store program codes.

[0147] Alternatively, if the foregoing integrated unit is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present invention, in essence, or the part that contributes to the prior art, may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods of the various embodiments of the present invention. And the foregoing storage medium includes: removable storage devices, ROM, RAM, magnetic disks, or optical discs and other various media that can store program codes.

[0148] The foregoing is described with reference to block diagrams and / or flowchart illustrations of methods, apparatus (systems) and / or computer program products according to embodiments of the present application. It should be understood that one block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, and / or other programmable data processing apparatus to produce a machine, such that the instructions executed via the computer processor and / or other programmable data processing apparatus create a means for implementing the functions / acts specified in the block diagrams and / or flowchart block(s).

[0149] Accordingly, the present application can also be implemented in hardware and / or software (including firmware, resident software, microcode, etc.). Further, the present application can take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of the present application, a computer-usable or computer-readable medium can be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

[0150] Obviously, those skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

1. A method for controlling application startup, characterized in that, The method includes: In response to an application startup instruction triggered by a user clicking on an application identifier, presenting an application startup page, where the application startup page is a blank page without user interface capabilities, and the application startup page is a welcome interface created in a first application indicated to be started by the application startup instruction; the task relevance of the welcome interface has a different name from the task relevance of the business interface of the first application. During the process of presenting the application startup page, when there is a second application that needs to be revived and the revival task is valid, present the business interface of the target application, where the target application is the second application indicated to be revived from the pre-pulled configuration information obtained from the server.

2. The method according to claim 1, characterized in that, Determine whether there is a second application that needs to be revived and whether the revival task is valid by the following method: During the process of presenting the application startup page, based on the pre-pulled configuration information obtained from the server, determine whether there is a second application that needs to be revived and whether the revival task is valid, where the pre-pulled configuration information was obtained from the server when the first application indicated to be started by the application startup instruction was started last time.

3. The method according to claim 1 or 2, characterized in that, The method further includes: After determining that there is no second application that needs to be revived, present the business interface of the first application; or When there is a second application that needs to be revived but the revival task fails, present the business interface of the first application.

4. The method according to claim 1, characterized in that, If the target application is the second application, after presenting the business interface of the target application, it further includes: End the task stack of the first application indicated to be started by the application startup instruction.

5. A device for controlling application startup, characterized in that, The device includes: A first presentation unit for presenting an application startup page in response to an application startup instruction triggered by a user clicking on an application identifier, where the application startup page is a blank page without user interface capabilities, and the application startup page is a welcome interface created in a first application indicated to be started by the application startup instruction; the task relevance of the welcome interface has a different name from the task relevance of the business interface of the first application. A second presentation unit for presenting the business interface of the target application during the process of presenting the application startup page when there is a second application that needs to be revived and the revival task is valid, where the target application is the second application indicated to be revived from the pre-pulled configuration information obtained from the server.

6. The device according to claim 5, characterized in that, The second presentation unit determines whether there is a second application that needs to be revived and whether the revival task is valid by the following method: During the process of presenting the application startup page, based on the pre-pulled configuration information obtained from the server, determine whether there is a second application that needs to be revived and whether the revival task is valid, where the pre-pulled configuration information was obtained from the server when the first application indicated to be started by the application startup instruction was started last time.

7. The device according to claim 5 or 6, characterized in that, The second presentation unit is further used for: After determining that there is no second application that needs to be revived, present the business interface of the first application; or When there is a second application that needs to be revived but the revival task fails, present the business interface of the first application.

8. The device according to claim 5, characterized in that, The second presentation unit is further used for: After presenting the business interface of the second target application, end the task stack of the first application indicated to be started by the application startup instruction.

9. A computer-readable medium, characterized in that, It stores a computer program executable by a computing device, and when the program is run on the computing device, the computing device executes the steps of any method described in claims 1 to 4.

Images