Method, device, mobile terminal and storage medium for generating desktop shortcut

Abstract

This application relates to a method, device, mobile terminal, and storage medium for generating desktop shortcuts. The method includes: when a creation instruction is detected, obtaining a first target function page corresponding to the creation instruction, where the first target function page is a function page loaded in a target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application; obtaining configuration information of the first target function page according to the creation instruction; and generating a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information. By using this method, the function of quickly entering the function page of the application can be achieved.

Description

Technical Field

[0001] The present application relates to the field of computer technologies, and particularly to a method and apparatus for generating desktop shortcuts, a mobile terminal, and a storage medium. Background Art

[0002] With the rapid development of the mobile Internet, the market share of mobile terminals is getting higher and higher. As software installed on mobile terminals, APPs (Applications) provide various services for users. In recent years, not only are there more and more categories of APPs, but also the functions provided by the same APP are increasing, so the functional pages that make up the APP are also increasing.

[0003] When a user needs to access a functional page, they need to first open the home page of the APP and then open another functional page through the home page of the APP. However, when there are many functional pages in the APP, the user needs to open multiple functional pages to enter the functional page to be accessed, which results in cumbersome operations. Summary of the Invention

[0004] Based on this, in view of the above technical problems, it is necessary to provide a method and apparatus for generating desktop shortcuts, a mobile terminal, and a storage medium that can quickly access the functional pages of an application program.

[0005] A method for generating a desktop shortcut, the method comprising:

[0006] When a creation instruction is detected, obtain a first target functional page corresponding to the creation instruction, where the first target functional page is a functional page loaded in a target application program, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application program;

[0007] Obtain the configuration information of the first target functional page according to the creation instruction;

[0008] Generate a desktop shortcut corresponding to the first target functional page on the desktop of the mobile terminal according to the configuration information.

[0009] An apparatus for generating a desktop shortcut, the apparatus comprising:

[0010] A detection module, configured to obtain a first target functional page corresponding to a creation instruction when the creation instruction is detected, where the first target functional page is a functional page loaded in a target application program, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application program;

[0011] An obtaining module, configured to obtain the configuration information of the first target functional page according to the creation instruction;

[0012] A creation module is used to generate a desktop shortcut corresponding to a first target function page on the desktop of a mobile terminal according to configuration information.

[0013] A mobile terminal includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the following steps are implemented:

[0014] When a creation instruction is detected, obtain a first target function page corresponding to the creation instruction. The first target function page is a function page loaded in a target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application;

[0015] Obtain the configuration information of the first target function page according to the creation instruction;

[0016] Generate a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information.

[0017] A computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the following steps are implemented:

[0018] When a creation instruction is detected, obtain a first target function page corresponding to the creation instruction. The first target function page is a function page loaded in a target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application;

[0019] Obtain the configuration information of the first target function page according to the creation instruction;

[0020] Generate a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information.

[0021] In the above method, device, mobile terminal, and storage medium for generating a desktop shortcut, when a creation instruction is detected, obtain a first target function page corresponding to the creation instruction, obtain the configuration information of the first target function page according to the creation instruction, and generate a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information. The first target function page is a function page loaded in a target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application. In this way, a desktop shortcut is set for the function page of the application, and through the desktop shortcut of the function page, the function page of the application can be quickly entered, avoiding cumbersome operations. Description of the Drawings

[0022] Figure 1 It is a schematic flowchart of the method for generating a desktop shortcut in an embodiment;

[0023] Figure 2Schematic diagram of creating an icon in an embodiment;

[0024] Figure 3 Schematic diagram of the protocol corresponding to an instruction in an embodiment;

[0025] Figure 4 Schematic diagram of a desktop shortcut in an embodiment;

[0026] Figure 5 Schematic diagram of a pop-up message in an embodiment;

[0027] Figure 6 Schematic diagram of a prompt message in an embodiment;

[0028] Figure 7 Schematic diagram of a permission management interface in an embodiment;

[0029] Figure 8 Schematic diagram of a pop-up message in another embodiment;

[0030] Figure 9 Schematic diagram of deleting an icon in an embodiment;

[0031] Figure 10 Schematic diagram of deleting an icon in another embodiment;

[0032] Figure 11 Schematic diagram of updating an icon in an embodiment;

[0033] Figure 12 Schematic diagram of updating an icon in another embodiment;

[0034] Figure 13 Flow schematic diagram of a method for generating a desktop shortcut in another embodiment;

[0035] Figure 14 Structural block diagram of a device for generating a desktop shortcut in an embodiment;

[0036] Figure 15 Internal structure diagram of a mobile terminal in an embodiment. Detailed implementation manners

[0037] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0038] In one embodiment, as Figure 1As shown, a method for generating a desktop shortcut is provided. In this embodiment, the method is exemplified by being applied to a terminal. It can be understood that the method can also be applied to a server, or to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0039] Step 102: When a creation instruction is detected, obtain a first target function page corresponding to the creation instruction. The first target function page is a function page loaded in a target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application.

[0040] Among them, the creation instruction is used to create a desktop shortcut for the function page of an application. An application refers to software installed on a mobile terminal, such as WeChat APP, Xinyue Club APP, etc. A function page is an operation interface of an application, that is, the instruction part designed for the operator in the software for operation and feedback of information. An application is composed of at least one function page, and each function page may include function modules for implementing different functions. A function module is a software module in an application that can implement a specific function. The function module is displayed in the function page through a visual identifier, and the visual identifier can be used as an operation entry for the function module for the operator to use. The target application is an application that can recognize the creation instruction. The first target function page is a function page loaded in the target application, which is the function page corresponding to the creation instruction.

[0041] In one embodiment, the creation instruction can be triggered by a creation icon in the first target function page. The creation icon is a visual identifier for creating a desktop shortcut for the first target function page. The creation icon can be set at any position in the first target function page. For example, as Figure 2 shown, Figure 2 "Add to Desktop" in

[0042] is the creation icon. The user can trigger the creation instruction by clicking, double-clicking, long-pressing the creation icon, etc.

[0043] In one embodiment, an instruction set of a target application is preset, and the instruction set may include creation instructions, update instructions, deletion instructions, jump instructions, etc. The update instruction is used to update the desktop shortcut of the function page of the application, the deletion instruction is used to delete the desktop shortcut of the function page of the application, and the jump instruction is used to jump to the function page of the application.

[0044] In one embodiment, the protocol corresponding to the instructions in the instruction set is a preset protocol. The protocol is character information that can be recognized and parsed, such as combinations of numbers, letters, etc. The protocol can be uniquely recognizable by the target application. For example, the creation instruction can only be recognized by the target application and cannot be recognized by other applications, so it is invalid for other applications.

[0045] In one embodiment, as Figure 3 shown, the protocol corresponding to the instruction may include application program character information, function page character information, function page class name, parameter character information, etc. The application program character information is used to represent the application program to be operated. Among them, the application program character information of the target application is unique; the function page character information is used to represent the function page to be operated. Among them, each function page of the target application has unique function page character information, and there is a mapping relationship between the function page character information and the function page class name. The target application can call the function page class name to execute actions; the parameter character information is used to describe the specific parameters for generating the desktop shortcut corresponding to the first target function page, which can be empty or at least one.

[0046] In one embodiment, a routing resolver is created in the target application. The routing resolver is used to parse the protocol corresponding to each instruction in the instruction set to obtain an instruction parsing result; further, the routing resolver can also judge the integrity and executability of the instruction parsing result, such as whether it is a protocol uniquely recognizable by the target application, whether it includes dynamic information such as creation, update, deletion, etc.; when it is determined that the instruction parsing result is complete and executable, the target application executes the action corresponding to the instruction parsing result.

[0047] Specifically, when a creation instruction is detected, it is identified whether it is the target application according to the application program character information. When it is identified as the target application, the first target function page corresponding to the creation instruction is determined according to the function page character information. Among them, according to the mapping relationship between the function page character information and the function page class name, the function page class name is determined, and the creation intention is determined according to the function page class name and the parameter character information. The API (Application Programming Interface) is called to start the creation intention, and thus the desktop shortcut corresponding to the first target function page can be generated.

[0048] In one embodiment, when the application detects a creation instruction, the application obtains a first target function page corresponding to the creation instruction.

[0049] Step 104: Obtain the configuration information of the first target function page according to the creation instruction.

[0050] The configuration information is used to configure and generate a desktop shortcut corresponding to the first target function page. The desktop shortcut is a visual identifier that is displayed on the desktop of the mobile terminal and can quickly connect to the function page of the application, and it can be displayed in the form of an icon.

[0051] In one embodiment, the configuration information may include the picture of the desktop shortcut of the first target function page, the name of the desktop shortcut of the first target function page, the address of the target function page, the title of the target function page, etc.

[0052] In one embodiment, the application obtains the configuration information of the first target function page according to the creation instruction.

[0053] Step 106: Generate a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information.

[0054] Specifically, as Figure 4 shown, Figure 4 is a schematic diagram of the desktop shortcut corresponding to the first target function page in one embodiment. Through the desktop shortcut corresponding to the first target function page, the first target function page can be directly entered without first opening the target application and then entering the first target function page through multiple function pages.

[0055] In one embodiment, the application generates a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information.

[0056] In the above method for generating a desktop shortcut, when a creation instruction is detected, a first target function page corresponding to the creation instruction is obtained, the configuration information of the first target function page is obtained according to the creation instruction, and a desktop shortcut corresponding to the first target function page is generated on the desktop of the mobile terminal according to the configuration information. The first target function page is a function page loaded in the target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application. In this way, a desktop shortcut is set for the function page of the application. Through the desktop shortcut of the function page, the function page of the application can be quickly entered, avoiding cumbersome operations, and increasing the exposure rate of the function page, thereby improving the information conversion rate of the function page.

[0057] In one embodiment, before obtaining the configuration information of the first target function page according to the creation instruction, it further includes: comparing the application program character information with the preset application program character information; when the application program character information is consistent with the preset application program character information, performing the step of obtaining the configuration information of the first target function page according to the creation instruction.

[0058] Among them, the protocol corresponding to the creation instruction includes application program character information, and the application program character information is used to represent the application program to be operated, and the preset application program character information is the unique identifier of the target application program.

[0059] Specifically, when comparing the application program character information with the preset application program character information, if the application program character information is consistent with the preset application program character information, it indicates that the instruction is for the target application program and is executable; if the application program character information is inconsistent with the preset application program character information, it indicates that the instruction is not for the target application program and is not executable.

[0060] In this embodiment, by comparing the application program character information with the preset application program character information, when the application program character information is consistent with the preset application program character information, obtaining the configuration information of the first target function page according to the creation instruction, thus improving the security of instruction execution in the target application program.

[0061] In one embodiment, obtaining the configuration information of the first target function page according to the creation instruction includes: determining the configuration information of the first target function page according to the parameter character information.

[0062] Among them, the protocol corresponding to the creation instruction includes parameter character information, and the parameter character information is used to describe the specific parameters for generating the desktop shortcut corresponding to the first target function page. It can be empty or at least one, and it can include: picture character information of the desktop shortcut, name character information of the desktop shortcut, address character information of the target function page, title character information of the target function page, etc.

[0063] In one embodiment, the picture of the desktop shortcut can be determined according to the picture character information of the desktop shortcut, the name of the desktop shortcut can be determined according to the name character information of the desktop shortcut, the address of the target function page can be determined according to the address character information of the target function page, and the title of the target function page can be determined according to the title character information of the target function page, so as to determine the configuration information of the first target function page according to the parameter character information.

[0064] In this embodiment, determining the configuration information of the first target function page according to the parameter character information improves the accuracy of creating the desktop shortcut of the function page.

[0065] In one embodiment, before generating a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information, it further includes: detecting whether the target application has the permission to generate a desktop shortcut. In one embodiment, the method further includes: when the target application does not have the permission to generate a desktop shortcut, outputting a prompt message for indicating to enable the permission of the target application to generate a desktop shortcut.

[0066] Specifically, some mobile terminals set the permission to generate a desktop shortcut for third-party applications. When the target application does not have the permission to generate a desktop shortcut, a prompt message is output to indicate to enable the permission of the target application to generate a desktop shortcut.

[0067] In one embodiment, the prompt message can be displayed in the form of a message pop-up box or in the form of a function page. The prompt message can only prompt the user to enable the permission of the target application to generate a desktop shortcut, or can also include the method for enabling the permission of the target application to generate a desktop shortcut. Optionally, the prompt message can include a jump function module for jumping to the function page for setting the permission of the desktop shortcut.

[0068] In one embodiment, when the target application does not have the permission to generate a desktop shortcut, as Figure 5 shown, a pop-up message "has tried to add to the desktop" is output, and this pop-up message can also include a "return" icon and an "understand details" icon. When the user selects the "return" icon, the action of adding to the desktop is cancelled; when the user selects the "understand details" icon, a prompt message is output. As Figure 6 shown, this prompt message is used to indicate to enable the permission of the target application to generate a desktop shortcut, and the user can switch to the Figure 7 shown permission management page according to the prompt message to enable the permission of the target application to generate a desktop shortcut.

[0069] Further, when the target application has the permission to generate a desktop shortcut, as Figure 8 shown, a pop-up message "add to the home screen" is output, and this pop-up message can also include a "cancel" icon and an "add" icon. When the user selects the "cancel" icon, the action of adding to the desktop is cancelled; when the user selects the "add" icon, the target application generates a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal according to the configuration information.

[0070] In this embodiment, it is detected whether the target application has the permission to generate a desktop shortcut. When the target application does not have the permission to generate a desktop shortcut, a prompt message is output, and the prompt message is used to indicate to enable the permission for the target application to generate a desktop shortcut. In this way, it is avoided that when the target application does not have the permission to generate a desktop shortcut, the situation where the desktop shortcut cannot be created.

[0071] In one embodiment, the method further includes: when a deletion instruction is detected, obtaining a second target function page corresponding to the deletion instruction, where the protocol corresponding to the deletion instruction is a protocol uniquely recognizable by the target application; clearing the desktop shortcut corresponding to the second target function page on the desktop of the mobile terminal.

[0072] Wherein, the deletion instruction is used to delete the desktop shortcut of the function page of the application. The second target function page is a function page loaded in the target application, and it is the function page corresponding to the deletion instruction.

[0073] In one embodiment, the deletion instruction can be triggered by a deletion icon in the second target function page. Optionally, the deletion icon can be set at any position in the second target function page. For example, as Figure 9 shown, Figure 9 the "Delete" in Figure 10 is the deletion icon. Optionally, the deletion icon can be set on the desktop shortcut corresponding to the second target function page. For example, as Figure 10 shown, Figure 10 the deletion mark in is the deletion icon. The user can trigger the deletion instruction by clicking, double-clicking, long-pressing the deletion icon, etc.

[0074] In one embodiment, the deletion instruction can be triggered by preset behavior information, and the behavior information can be sliding track information, etc. The sliding track information received in the second target function page is compared with the pre-stored sliding track information. When the received sliding track information matches the pre-stored sliding track information, the deletion instruction is triggered. Optionally, a deletion area can be set in the second target function page, and the deletion area is used to receive the input sliding track information.

[0075] Specifically, when a deletion instruction is detected, it is identified whether the deletion instruction corresponds to the target application according to the application character information. When it is identified that the deletion instruction corresponds to the target application, the second target function page corresponding to the deletion instruction is determined according to the function page character information. Among them, according to the mapping relationship between the function page character information and the function page class name, the function page class name is determined, and the deletion intention is determined according to the function page class name and the parameter character information. The API is called to start the deletion intention, and thus the desktop shortcut corresponding to the second target function page can be cleared on the desktop of the mobile terminal.

[0076] In this embodiment, when a deletion instruction is detected, the second target function page corresponding to the deletion instruction is obtained, and the desktop shortcut corresponding to the second target function page is cleared on the desktop of the mobile terminal, so as to avoid interference of redundant desktop shortcuts with user operations.

[0077] In one embodiment, the method further includes: when an update instruction is detected, obtaining a third target function page corresponding to the update instruction, where the protocol corresponding to the update instruction is a protocol uniquely recognizable by the target application; obtaining update information according to the update instruction; and updating the desktop shortcut corresponding to the third target function page on the desktop of the mobile terminal according to the update information.

[0078] Among them, the update instruction is used to update the desktop shortcut of the function page of the application. The third target function page is a function page loaded in the target application and is the function page corresponding to the update instruction.

[0079] In one embodiment, the update instruction can be triggered by an update icon in the third target function page. Optionally, the update icon can be set at any position in the third target function page. For example, as Figure 11 shown, Figure 11 the "Update" in Figure 12 is the update icon. Optionally, the update icon can be set on the desktop shortcut corresponding to the third target function page. For example, as Figure 12 shown, Figure 12 the update identifier in

[0080] In one embodiment, the update instruction can be triggered by preset behavior information, and the behavior information can be sliding track information, etc. The sliding track information received in the third target function page is compared with the pre-stored sliding track information. When the received sliding track information matches the pre-stored sliding track information, the update instruction is triggered. Optionally, an update area can be set in the third target function page, and the update area is used to receive the input sliding track information.

[0081] In one embodiment, an update instruction can be generated regularly to update the desktop shortcut corresponding to the third target function page regularly.

[0082] In one embodiment, update information can be determined according to the parameter character information in the protocol corresponding to the update instruction, and the target application can obtain the parameter character information from the server. Specifically, when an update instruction is detected, it is identified whether the update instruction corresponds to the target application according to the application character information. When it is identified that the update instruction corresponds to the target application, the third target function page corresponding to the update instruction is determined according to the function page character information. Among them, according to the mapping relationship between the function page character information and the function page class name, the function page class name is determined, and the update intention is determined according to the function page class name and the parameter character information, and the API is called to start the update intention, so as to update the desktop shortcut corresponding to the third target function page on the desktop of the mobile terminal.

[0083] In this embodiment, when an update instruction is detected, the third target function page corresponding to the update instruction is obtained, the update information is obtained according to the update instruction, and according to the update information, the desktop shortcut corresponding to the third target function page is updated on the desktop of the mobile terminal. In this way, the diversity of the desktop shortcut display is enhanced.

[0084] In one embodiment, the method further includes: when the target application is uninstalled, the desktop shortcut corresponding to the first target function page is cleared on the desktop of the mobile terminal.

[0085] In this embodiment, when the target application is uninstalled, the desktop shortcut corresponding to the first target function page is cleared on the desktop of the mobile terminal. In this way, the rationality of the desktop shortcut display is enhanced.

[0086] This application also provides an application scenario, which applies the above-mentioned method for generating desktop shortcuts. Specifically, the application of the method for generating desktop shortcuts in this application scenario is as follows: when the user uses the target application, the usage times of one of the function pages are relatively frequent. As Figure 13 shown, the method includes:

[0087] First, when a creation instruction is detected, the application obtains the target function page corresponding to the creation instruction. The target function page is the function page loaded in the target application, and the protocol corresponding to the creation instruction is the protocol uniquely recognizable by the target application.

[0088] Next, the application character information in the protocol corresponding to the creation instruction is compared with the preset application character information.

[0089] Further, when the application character information is consistent with the preset application character information, the configuration information of the target function page is determined according to the parameter character information in the protocol corresponding to the creation instruction.

[0090] Next, detect whether the target application has the permission to generate a desktop shortcut.

[0091] Further, when the target application does not have the permission to generate a desktop shortcut, output a prompt message, which is used to indicate to enable the permission for the target application to generate a desktop shortcut.

[0092] Next, when the target application has the permission to generate a desktop shortcut, generate a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal according to the configuration information.

[0093] Further, after generating a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal, when an update instruction is detected, the application obtains the target function page corresponding to the update instruction, obtains update information according to the update instruction, and updates the desktop shortcut corresponding to the target function page on the desktop of the mobile terminal according to the update information, where the protocol corresponding to the update instruction is a protocol uniquely recognizable by the target application.

[0094] Alternatively, after generating a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal, when a deletion instruction is detected, the application obtains the target function page corresponding to the deletion instruction and clears the desktop shortcut corresponding to the target function page on the desktop of the mobile terminal, where the protocol corresponding to the deletion instruction is a protocol uniquely recognizable by the target application.

[0095] In this embodiment, a desktop shortcut is set for the function page of the application. Through the desktop shortcut of the function page, the function page of the application can be quickly entered, avoiding cumbersome operations; increasing the exposure rate of the function page, thereby improving the information conversion rate of the function page; the desktop shortcut set for the function page can be updated and deleted, enhancing the diversity and rationality of the desktop shortcut display.

[0096] The present application also provides another application scenario, which applies the above-mentioned method for generating a desktop shortcut. Specifically, the application of the method for generating a desktop shortcut in this application scenario is as follows: When the user uses the target application, the usage times of one of the function pages are relatively frequent, and the function page is as Figure 2 shown. A creation icon is set in this function page, that is, Figure 2 "Add to Desktop" in

[0097] First, the user clicks the "Add to Desktop" icon to trigger a creation instruction. The target application detects the creation instruction and obtains the target function page corresponding to the creation instruction, where the target function page is a function page loaded in the target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application.

[0098] Next, compare the application character information in the protocol corresponding to the creation instruction with the preset application character information.

[0099] Further, when the application character information is consistent with the preset application character information, determine the configuration information of the target function page according to the parameter character information in the protocol corresponding to the creation instruction.

[0100] Next, detect whether the target application has the permission to generate a desktop shortcut.

[0101] Further, when the target application does not have the permission to generate a desktop shortcut, as Figure 5 shown, output a pop-up message "Has tried to add to the desktop", and this pop-up message may also include a "Return" icon and a "Learn More" icon. When the user selects the "Return" icon, the action of adding to the desktop is cancelled; when the user selects the "Learn More" icon, output a prompt message, and this prompt message is as Figure 6 shown, this prompt message is used to indicate to enable the permission for the target application to generate a desktop shortcut, and the user can go to the Figure 7 shown permission management page according to the prompt message to enable the permission for the target application to generate a desktop shortcut.

[0102] Further, when the target application has the permission to generate a desktop shortcut, as Figure 8 shown, output a pop-up message "Add to Home Screen", and this pop-up message may also include a "Cancel" icon and an "Add" icon. When the user selects the "Cancel" icon, the action of adding to the desktop is cancelled; when the user selects the "Add" icon, the target application generates a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal according to the configuration information, and the desktop shortcut corresponding to the target function page is as Figure 4 shown.

[0103] Further, after generating a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal, as Figure 11 shown, when the user clicks the "Update" icon, trigger an update instruction, the application obtains the target function page corresponding to the update instruction, obtains update information according to the update instruction, and updates the desktop shortcut corresponding to the target function page on the desktop of the mobile terminal according to the update information, where the protocol corresponding to the update instruction is the only recognizable protocol for the target application.

[0104] Or, after generating a desktop shortcut corresponding to the target function page on the desktop of the mobile terminal, as Figure 9As shown in the figure, when the user clicks the "Delete" icon, a deletion instruction is triggered, and the application obtains the target function page corresponding to the deletion instruction, and clears the desktop shortcut corresponding to the target function page on the desktop of the mobile terminal. Among them, the protocol corresponding to the deletion instruction is the protocol uniquely recognizable by the target application.

[0105] In this embodiment, a desktop shortcut is set for the function page of the application. Through the desktop shortcut of the function page, the function page of the application can be quickly entered, avoiding cumbersome operations; increasing the exposure rate of the function page, thereby improving the information conversion rate of the function page; the desktop shortcut set for the function page can be updated and deleted, enhancing the diversity and rationality of the desktop shortcut display.

[0106] It should be understood that although Figure 1 、 13 each step in the flowchart is shown in sequence according to the arrow indication, these steps are not necessarily executed in the order indicated by the arrow. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, Figure 1 、 13 at least a part of the steps in

[0107] In one embodiment, as Figure 14 shown, a device for generating a desktop shortcut is provided. This device can be a software module or a hardware module, or a combination of the two to become a part of the mobile terminal. The device specifically includes: a detection module 1402, an acquisition module 1404, and a creation module 1406, where:

[0108] The detection module 1402 is configured to obtain the first target function page corresponding to the creation instruction when detecting the creation instruction. The first target function page is the function page loaded in the target application, and the protocol corresponding to the creation instruction is the protocol uniquely recognizable by the target application;

[0109] The acquisition module 1404 is configured to obtain the configuration information of the first target function page according to the creation instruction;

[0110] The creation module 1406 is configured to generate a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal according to the configuration information.

[0111] In the above desktop shortcut generation device, when a creation instruction is detected, the first target function page corresponding to the creation instruction is obtained, the configuration information of the first target function page is obtained according to the creation instruction, and according to the configuration information, a desktop shortcut corresponding to the first target function page is generated on the desktop of the mobile terminal. Among them, the first target function page is a function page loaded in the target application, and the protocol corresponding to the creation instruction is a protocol uniquely recognizable by the target application. In this way, a desktop shortcut is set for the function page of the application. Through the desktop shortcut of the function page, the function page of the application can be quickly entered, avoiding cumbersome operations. Moreover, the exposure rate of the function page is increased, thereby improving the information conversion rate of the function page.

[0112] In one embodiment, the protocol corresponding to the creation instruction includes application program character information; the desktop shortcut generation device further includes a comparison module and an execution module. The comparison module is used to: compare the application program character information with the preset application program character information; the execution module is used to: when the application program character information is consistent with the preset application program character information, execute the step of obtaining the configuration information of the first target function page according to the creation instruction.

[0113] In this embodiment, the application program character information is compared with the preset application program character information. When the application program character information is consistent with the preset application program character information, the configuration information of the first target function page is obtained according to the creation instruction. In this way, the security of instruction execution in the target application is improved.

[0114] In one embodiment, the protocol corresponding to the creation instruction includes parameter character information; the obtaining module 1404 is further used to: determine the configuration information of the first target function page according to the parameter character information.

[0115] In this embodiment, the configuration information of the first target function page is determined according to the parameter character information, which improves the accuracy of creating the desktop shortcut of the function page.

[0116] In one embodiment, the detection module 1402 is further used to: detect whether the target application has the permission to generate a desktop shortcut; the desktop shortcut generation device further includes an output module. The output module is used to: when the target application does not have the permission to generate a desktop shortcut, output a prompt message, and the prompt message is used to indicate to enable the permission of the target application to generate a desktop shortcut.

[0117] In this embodiment, it is detected whether the target application has the permission to generate a desktop shortcut. When the target application does not have the permission to generate a desktop shortcut, a prompt message is output, and the prompt message is used to indicate to enable the permission for the target application to generate a desktop shortcut. In this way, it is avoided that when the target application does not have the permission to generate a desktop shortcut, the situation where the desktop shortcut cannot be created.

[0118] In one embodiment, the obtaining module 1404 is further configured to: when a deletion instruction is detected, obtain a second target function page corresponding to the deletion instruction, and the protocol corresponding to the deletion instruction is a protocol uniquely recognizable by the target application; the desktop shortcut generation device further includes a deletion module, and the deletion module is configured to: clear the desktop shortcut corresponding to the second target function page on the desktop of the mobile terminal.

[0119] In this embodiment, when a deletion instruction is detected, a second target function page corresponding to the deletion instruction is obtained, and the desktop shortcut corresponding to the second target function page is cleared on the desktop of the mobile terminal. In this way, it is avoided that the redundant desktop shortcuts interfere with the user operation.

[0120] In one embodiment, the obtaining module 1404 is further configured to: when an update instruction is detected, obtain a third target function page corresponding to the update instruction, and the protocol corresponding to the update instruction is a protocol uniquely recognizable by the target application; the obtaining module 1404 is further configured to: obtain update information according to the update instruction; the desktop shortcut generation device further includes an update module, and the update module is configured to: update the desktop shortcut corresponding to the third target function page on the desktop of the mobile terminal according to the update information.

[0121] In this embodiment, when an update instruction is detected, a third target function page corresponding to the update instruction is obtained, update information is obtained according to the update instruction, and the desktop shortcut corresponding to the third target function page is updated on the desktop of the mobile terminal according to the update information. In this way, the diversity of the desktop shortcut display is enhanced.

[0122] In one embodiment, the desktop shortcut generation device further includes a clearing module, and the clearing module is configured to: when the target application is uninstalled, clear the desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal.

[0123] In this embodiment, when the target application is uninstalled, the desktop shortcut corresponding to the first target function page is cleared on the desktop of the mobile terminal. In this way, the rationality of the desktop shortcut display is enhanced.

[0124] For the specific limitations of the device for generating desktop shortcuts, reference can be made to the limitations on the method for generating desktop shortcuts in the foregoing text, which will not be elaborated herein. Each module in the above-mentioned device for generating desktop shortcuts can be implemented in whole or in part by software, hardware, and their combination. Each of the above modules can be embedded in or independent of the processor in the mobile terminal in the form of hardware, or stored in the memory of the mobile terminal in the form of software, so as to facilitate the processor to call and execute the operations corresponding to each of the above modules.

[0125] In one embodiment, a mobile terminal is provided, and its internal structure diagram can be as Figure 15 shown. The mobile terminal includes a processor, a memory, a communication interface, a display screen, and an input device connected through a system bus. Among them, the processor of the mobile terminal is used to provide computing and control capabilities. The memory of the mobile terminal includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the mobile terminal is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a carrier network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a method for generating desktop shortcuts. The display screen of the mobile terminal can be a liquid crystal display screen or an electronic ink display screen, and the input device of the mobile terminal can be a touch layer covered on the display screen, or a button, a trackball, or a touchpad provided on the outer shell of the mobile terminal, or an external keyboard, a touchpad, or a mouse, etc.

[0126] Those skilled in the art can understand that Figure 15 the structure shown in

[0127] is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the mobile terminal to which the solution of this application is applied. The specific mobile terminal may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0128] In one embodiment, a computer-readable storage medium is provided, storing a computer program, and when the computer program is executed by a processor, it implements the steps in the foregoing method embodiments.

[0129] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0130] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0131] The above-described embodiments merely represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A method for generating a desktop shortcut, characterized in that, The method includes: Using a routing resolver created in the target application to resolve the protocol corresponding to the detected instruction, and obtaining an instruction parsing result; When it is determined by the routing resolver that the protocol is the only recognizable protocol of the target application and the instruction parsing result contains dynamic information, then When the dynamic information includes "create", determining the function page character information in the protocol corresponding to the detected instruction, where the function page character information characterizes a first target function page, and the first target function page is a function page loaded in the target application, and the protocol is uniquely recognized by the target application; Determining a function page class name according to the mapping relationship between the function page character information and the function page class name; Determining the configuration information of the first target function page according to the parameter character information in the protocol corresponding to the detected instruction; Determining a creation intention according to the function page class name and the configuration information, calling an API to start the creation intention, and generating a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal.

2. The method according to claim 1, characterized in that, The protocol corresponding to the detected instruction includes application program character information, and the method further includes: Comparing the application program character information with preset application program character information; When the application program character information is consistent with the preset application program character information, performing the step of determining the configuration information of the first target function page according to the parameter character information in the protocol corresponding to the detected instruction.

3. The method according to claim 1, wherein Before determining the creation intention according to the function page class name and the configuration information, calling an API to start the creation intention, and generating a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal, it further includes: Detecting whether the target application has the permission to generate the desktop shortcut; The method further includes: When the target application does not have the permission to generate the desktop shortcut, outputting a prompt message for indicating to enable the permission of the target application to generate the desktop shortcut.

4. The method according to claim 1, characterized in that, The method further includes: When the dynamic information includes "delete", obtaining a second target function page corresponding to the detected instruction, where the protocol corresponding to the detected instruction is uniquely recognized by the target application; Clearing the desktop shortcut corresponding to the second target function page on the desktop of the mobile terminal.

5. The method according to claim 1, wherein The method further includes: When the dynamic information includes "update", obtaining a third target function page corresponding to the detected instruction, where the protocol corresponding to the detected instruction is uniquely recognized by the target application; Obtaining update information according to the detected instruction; Updating the desktop shortcut corresponding to the third target function page on the desktop of the mobile terminal according to the update information.

6. The method according to claim 1, wherein The method further includes: When the target application is uninstalled, clearing the desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal.

7. A generating device for desktop shortcuts, characterized in that, The device includes: A detection module, configured to use a route resolver created in a target application to resolve the protocol corresponding to a detected instruction, and obtain an instruction parsing result; when it is determined by the route resolver that the protocol is the only recognizable protocol of the target application, and the instruction parsing result contains dynamic information, then when the dynamic information contains "create", determine the function page character information in the protocol corresponding to the detected instruction, where the function page character information represents a first target function page, the first target function page is a function page loaded in the target application, and the protocol is uniquely recognized by the target application; A determination module, configured to determine a function page class name according to the mapping relationship between the function page character information and the function page class name; determine the configuration information of the first target function page according to the parameter character information in the protocol corresponding to the detected instruction; determine a creation intention according to the function page class name and the configuration information; A creation module, configured to call an API to initiate the creation intention and generate a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal.

8. The generating device of the desktop shortcut according to claim 7, characterized in that The protocol corresponding to the detected instruction includes application program character information, and the device further includes a comparison module, configured to compare the application program character information with preset application program character information; And an execution module, configured to execute the step of determining the configuration information of the first target function page according to the parameter character information in the protocol corresponding to the detected instruction when the application program character information is consistent with the preset application program character information.

9. The generating device of the desktop shortcut according to claim 7, wherein The detection module is further configured to detect whether the target application has the permission to generate the desktop shortcut before determining the creation intention according to the function page class name and the configuration information, calling the API to initiate the creation intention, and generating a desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal; the device further includes an output module, configured to output a prompt message when the target application does not have the permission to generate the desktop shortcut, where the prompt message is used to indicate to enable the permission of the target application to generate the desktop shortcut.

10. The generating device of the desktop shortcut according to claim 7, characterized in that The device further includes an acquisition module, configured to acquire a second target function page corresponding to the detected instruction when the dynamic information contains "delete", where the protocol corresponding to the detected instruction is uniquely recognized by the target application; a deletion module, configured to delete the desktop shortcut corresponding to the second target function page on the desktop of the mobile terminal.

11. The generating device of the desktop shortcut according to claim 7, characterized in that, The device further includes an acquisition module, configured to acquire a third target function page corresponding to the detected instruction when the dynamic information contains "update", where the protocol corresponding to the detected instruction is uniquely recognized by the target application; The acquisition module is further configured to acquire update information according to the detected instruction; an update module, configured to update the desktop shortcut corresponding to the third target function page on the desktop of the mobile terminal according to the update information.

12. The generating device of the desktop shortcut according to claim 7, wherein The device further includes a clearing module, configured to clear the desktop shortcut corresponding to the first target function page on the desktop of the mobile terminal when the target application is uninstalled.

13. A mobile terminal, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

14. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 6 are implemented.

15. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, the method according to any one of claims 1 to 6 is implemented.

Images