Shortcut creation method, related device and medium

Abstract

The invention provides a shortcut creation method, a related device and a medium. The method comprises the following steps: displaying a simulator interface in response to calling trigger on a simulator on a first interface of a first terminal; in response to a call trigger for a target application on the simulator interface, displaying a target application interface on the simulator interface, the target application being an application adapted to a second terminal of a type different from that of the first terminal; and in response to a shortcut creation trigger for the target function on the target application interface, displaying a first target shortcut of the target function on the first interface. According to the embodiment of the invention, under the condition that the current terminal runs the applications of other types of terminals through the simulator, the time cost for accessing the application function corresponding to the shortcut is reduced, and the opening reach rate of the simulator is improved. The embodiment of the invention is applied to scenes such as cross-end interaction.

Description

Technical Field

[0001] The present disclosure relates to the field of desktop management, and in particular to a shortcut creation method, related devices and media. Background Art

[0002] An emulator is a tool that simulates the operating system of another type of terminal on one type of terminal, so that applications adapted to another type of terminal can be run on the terminal of this type. For example, video application A is only adapted to Android phones. If you need to use video application A on a computer, you can open the emulator on the computer and run video application A in the emulator.

[0003] The purpose of creating a shortcut is to quickly access the application corresponding to the shortcut. If you create a shortcut for an application running in the simulator, the current shortcut manager only supports displaying the shortcut of the application in the simulator interface. For example, if a user wants to create a shortcut for video application A in the simulator, the shortcut can only be displayed in the simulator interface. After the simulator is minimized or closed, if the user wants to quickly access the application interface corresponding to the shortcut, he needs to open the simulator to click the shortcut. Therefore, it increases the time cost of accessing shortcuts and reduces the opening reach rate of the simulator. Summary of the invention

[0004] The embodiments of the present disclosure provide a shortcut creation method, related devices and media, which can reduce the time cost of accessing application functions corresponding to shortcuts and improve the opening reach rate of simulators when the current terminal runs applications of other types of terminals through simulators.

[0005] According to one aspect of the present disclosure, a shortcut creation method is provided, the shortcut creation method comprising:

[0006] In response to a call trigger of the simulator on the first interface of the first terminal, displaying the simulator interface;

[0007] In response to a call trigger of a target application on the simulator interface, displaying a target application interface on the simulator interface, wherein the target application is an application adapted to a second terminal of a type different from that of the first terminal;

[0008] In response to a shortcut creation trigger for a target function on the target application interface, a first target shortcut for the target function is displayed on the first interface.

[0009] According to one aspect of the present disclosure, a shortcut creation device is provided, the shortcut creation device comprising:

[0010] A first response unit, configured to display a simulator interface in response to a call trigger of the simulator on a first interface of the first terminal;

[0011] a second response unit, configured to display a target application interface on the simulator interface in response to a call trigger of a target application on the simulation interface, wherein the target application is an application adapted to a second terminal of a type different from that of the first terminal;

[0012] The third response unit is used to display a first target shortcut of the target function on the first interface in response to a shortcut creation trigger for the target function on the target application interface.

[0013] Optionally, the simulator interface covers a portion of the first interface;

[0014] The third response unit is specifically used for:

[0015] On the target application interface, receiving the shortcut creation trigger for the target function of the target application interface;

[0016] While the simulator interface is displayed on the first interface, the first target shortcut to the target function is displayed on a portion of the first interface not occupied by the simulator interface.

[0017] Optionally, the third response unit is further configured to:

[0018] On the target application interface, receiving a target function entry trigger for the target function;

[0019] In response to the target function entry trigger, displaying a target function page of the target function, wherein the target function page has a shortcut creation control;

[0020] The shortcut creation trigger for the shortcut creation control is received.

[0021] Optionally, the first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon;

[0022] The third response unit is specifically used for:

[0023] In response to the shortcut creation trigger for the target function on the target application interface, if the target function includes a target function image, the first target shortcut icon is displayed as a composite image of the target function image and the simulator shortcut icon.

[0024] Optionally, the first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon;

[0025] The third response unit is specifically used for:

[0026] In response to the shortcut creation trigger for the target function on the target function application interface, if the target function does not include a target function image, the first target shortcut icon is displayed as a composite image of the target function text image corresponding to the target function and the simulator shortcut icon.

[0027] Optionally, the third response unit is specifically used to:

[0028] In response to the shortcut creation trigger for the target function on the target application interface, while displaying the first target shortcut of the target function on the first interface, a second target shortcut of the target function is displayed on the simulator interface.

[0029] Optionally, the first target shortcut and the second target shortcut of the same target function have the same target attribute.

[0030] Optionally, the third response unit is specifically used to:

[0031] On the first interface, displaying a target area corresponding to the target application;

[0032] The first target shortcut of the target function is displayed in the target area.

[0033] Optionally, the target function includes a first target function and a second target function, and the second target function belongs to the first target function;

[0034] The third response unit is further specifically configured to: display the first target shortcut of the second target function as having an associated mark with the first target shortcut of the first target function.

[0035] Optionally, the third response unit is further configured to:

[0036] In the target area, displaying a target tree;

[0037] displaying the first target shortcut of the first target function as a parent node of the target tree;

[0038] The first target shortcut to the second target function is displayed as a child node of the parent node.

[0039] Optionally, the third response unit is further configured to:

[0040] In response to the shortcut creation trigger for the target function on the target application interface, the first target shortcut of the target function is displayed on the first interface based on a display attribute corresponding to a function type of the target function.

[0041] Optionally, the third response unit is further configured to:

[0042] During execution of the target function on the target application interface, receiving a shortcut creation trigger for the target function;

[0043] In response to the shortcut creation trigger, while displaying a first target shortcut of the target function on the first interface, an execution progress of the target function is displayed in association with the first target shortcut.

[0044] Optionally, the third response unit is further configured to:

[0045] In response to the shortcut creation trigger for the target function on the target application interface, multiple target shortcuts are displayed on the first interface, the multiple target shortcuts include the first target shortcut for the target function, and the multiple target shortcuts are sorted according to the creation time of the multiple target shortcuts.

[0046] Optionally, the third response unit is further configured to:

[0047] In response to a shortcut creation trigger for a target function on the target application interface, displaying an animation of the target function being transferred to the first interface;

[0048] After the animation ends, the first target shortcut of the target function is displayed on the first interface.

[0049] Optionally, the third response unit is further configured to:

[0050] In response to the shortcut creation trigger for the target function on the target application interface, while displaying the first target shortcut of the target function on the first interface, the first target shortcut is displayed on the second interface of the second terminal bound to the first terminal.

[0051] Optionally, the third response unit is further configured to:

[0052] In response to the shortcut creation trigger for the target function on the target application interface, displaying a shortcut creation notification, wherein the shortcut creation notification includes a shortcut cross-interface creation control;

[0053] In response to a call trigger for the shortcut cross-interface creation control, the first target shortcut of the target function is displayed on the first interface.

[0054] Optionally, the first terminal includes a simulator shortcut creation module and a client shortcut creation module;

[0055] The third response unit is further specifically used for:

[0056] By the simulator shortcut creation module, in response to the shortcut creation trigger for the target function on the target application interface, obtaining shortcut information from the shortcut creation trigger, and sending the shortcut information to the client shortcut creation module;

[0057] The first target shortcut is created based on the shortcut information through the client shortcut creation module, and the first target shortcut is displayed on the first interface.

[0058] Optionally, the first terminal further comprises a simulator shortcut manager and a client shortcut manager;

[0059] The third response unit is further specifically used for:

[0060] Modify the routine of the simulator shortcut manager so that after acquiring the shortcut information from the shortcut creation trigger, the shortcut information is sent to the client shortcut manager through the simulator shortcut creation module;

[0061] The routine is executed, so that the shortcut information is sent to the client shortcut manager and forwarded to the client shortcut creation module through the client shortcut manager.

[0062] Optionally, the shortcut creation device further includes:

[0063] The fourth response unit is used to display a target function page of the target function corresponding to the first target shortcut in response to the call trigger of the first target shortcut.

[0064] Optionally, the third response unit is specifically used to: in response to the shortcut creation trigger for the target function during the execution of the target function on the target application interface, interrupt the execution of the target function, and display the first target shortcut of the target function on the first interface;

[0065] The fourth response unit is specifically configured to: in response to the calling trigger of the first target shortcut, display the target function page of the target function corresponding to the first target shortcut from the interrupt position of the target function.

[0066] Optionally, the first terminal further includes a simulator shortcut startup module and a client shortcut startup module;

[0067] The fourth response unit is specifically used for:

[0068] By means of the client shortcut startup module, in response to the call trigger of the first target shortcut, access information is obtained from the call trigger, and the access information is sent to the simulator shortcut startup module;

[0069] The target function page of the target function corresponding to the first target shortcut is displayed based on the access information through the simulator shortcut startup module.

[0070] Optionally, the access information includes an interruption position of the target function when the shortcut creation trigger is received;

[0071] The fourth response unit is further specifically used for:

[0072] The starting module through the simulator shortcut, based on the access information, displays the target function page of the target function corresponding to the first target shortcut, including:

[0073] The target function page of the target function corresponding to the first target shortcut is displayed from the interruption position through the simulator shortcut startup module.

[0074] According to one aspect of the present disclosure, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the shortcut creation method as described above when executing the computer program.

[0075] According to one aspect of the present disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the shortcut creation method as described above is implemented.

[0076] According to one aspect of the present disclosure, a computer program product is provided. The computer program product includes a computer program. The computer program is read and executed by a processor of a computer device, so that the computer device executes the shortcut creation method as described above.

[0077] In the embodiment of the present disclosure, after the user calls the target application supported by another type of terminal different from the type of the current terminal through the simulator, a shortcut creation trigger is made for the target function on the target application interface. In response to the shortcut creation trigger, the first target shortcut of the target function is not displayed on the simulator interface, but the first target shortcut of the target function is displayed on the current terminal interface. Therefore, only the first target shortcut needs to be triggered to open the target function interface corresponding to the first target shortcut and execute the target function without opening the simulator, thereby realizing quick access to the function within the application. In the case where the current terminal runs the application of other types of terminals through the simulator, the embodiment of the present disclosure reduces the time cost of accessing the in-application function corresponding to the shortcut and improves the opening reach rate of the simulator. Moreover, the embodiment of the present disclosure can reduce the access time cost for the in-application function, rather than for the application. It targets a finer dimension and can reduce the access time cost in a finer dimension, thereby being more conducive to reducing the overall access time cost.

[0078] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by practicing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] The accompanying drawings are used to provide further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure.

[0080] Figure 1 is a system architecture diagram of a shortcut creation method according to an embodiment of the present disclosure;

[0081] FIG. 2A to FIG. 2C is a schematic diagram of applying the shortcut creation method of an embodiment of the present disclosure to a cross-terminal interaction scenario;

[0082] Figure 3 is an overall flow chart of a shortcut creation method provided by an embodiment of the present disclosure;

[0083] FIG. 4A to FIG. 4C is a schematic diagram of an interface for creating a shortcut provided by an embodiment of the present disclosure;

[0084] Figure 5 is a schematic diagram of a simulator interface provided by an embodiment of the present disclosure;

[0085] Figure 6 yes Figure 3 Step 330 is a flowchart of displaying the first target shortcut when the simulator interface covers a portion of the first interface;

[0086] Figure 7 is a schematic diagram of a simulator interface provided by an embodiment of the present disclosure covering the entire first interface;

[0087] Figure 8 yes Figure 6 A flowchart of step 610 receiving a shortcut creation trigger;

[0088] Fig. 9A is a schematic diagram of a target application interface provided by an embodiment of the present disclosure;

[0089] Fig. 9B is a schematic diagram of a shortcut creation control provided by an embodiment of the present disclosure;

[0090] Fig.10 yes Figure 3 Step 330 is a flowchart of displaying a first target shortcut when the target function includes a target function image;

[0091] Fig.11 yes Figure 3 Step 330 is a flowchart of displaying a first target shortcut when the target function does not include a target function image;

[0092] Fig.12 yes Fig.11 A schematic diagram showing a first target shortcut when the target function does not include a target function image;

[0093] Fig.13 yes Figure 3 A flowchart of displaying a second target shortcut on the simulator interface while displaying the first target shortcut in step 330;

[0094] Fig.14A and Fig. 14B yes Fig.13 A schematic diagram showing a first target shortcut and a second target shortcut on the simulator interface at the same time;

[0095] Fig.15 yes Figure 3 A flowchart of step 330 in which a first target shortcut is displayed when a target area corresponding to a target application is provided;

[0096] Fig.16A and Fig. 16B is a schematic diagram showing a first target shortcut when a target area corresponding to a target application is provided;

[0097] Fig.17 yes Fig.15 A flowchart of step 1520 of displaying a first target shortcut of a target function in a target area;

[0098] Fig.18 yes Fig.17 At step 1710 , the first target shortcut of the second target function is displayed as a flow chart having an associated mark with the first target shortcut of the first target function;

[0099] Fig.19 yes Figure 3 Step 330 is a flow chart showing the first target shortcut when the function type and the display attribute are set correspondingly;

[0100] Fig. 20 yes Fig.19 A schematic diagram showing the first target shortcut when the function type and display attribute are set correspondingly;

[0101] Fig.21 yes Figure 3 A flowchart showing the progress of target function execution while displaying the first target shortcut in step 330;

[0102] Fig. 22 yes Fig.21 A schematic diagram showing the progress of target function execution while displaying the first target shortcut;

[0103] Fig.23 yes Figure 3 Step 330 is a flow chart showing a first target shortcut when multiple target shortcuts are sorted by creation time;

[0104] Fig.24 yes Fig.23 A schematic diagram showing the first target shortcut when multiple target shortcuts are sorted by creation time;

[0105] Fig.25 yes Figure 3 Step 330 displays a flow chart of the first target shortcut;

[0106] Fig.26 yes Fig.25 A schematic diagram showing a shortcut to the first target;

[0107] Fig. 27 yes Figure 3In step 330, while displaying the first target shortcut, a schematic diagram of the first target shortcut is displayed on the second interface of the second terminal;

[0108] Fig.28 yes Fig. 27 A schematic diagram of a first target shortcut is displayed on a second interface of a second terminal;

[0109] Fig.29 yes Figure 3 Step 330 displays the first target shortcut when a shortcut creation notification is provided;

[0110] Fig.30 yes Fig.29 A diagram of a shortcut to create a notification;

[0111] Fig.31 is a flow chart of background processing of shortcut creation provided by an embodiment of the present disclosure;

[0112] Fig.32A and Fig.32B is a schematic diagram of background processing of shortcut creation provided by an embodiment of the present disclosure;

[0113] Fig.33 yes Fig.31 Step 3110 is a flowchart of sending shortcut information to a client shortcut creation module;

[0114] Fig.34 is a flow chart of the invocation triggering of the first target shortcut provided by an embodiment of the present disclosure;

[0115] Fig.35A and Fig.35B yes Fig.34 Schematic diagram of the call triggering of the first target shortcut;

[0116] Fig.36 yes Fig.34 Step 3410 displays a flow chart of a target function page of a target function corresponding to the first target shortcut;

[0117] Fig.37 yes Fig.34 A flowchart of background processing of a target function page of a target function corresponding to a first target shortcut is displayed;

[0118] Fig.38 yes Fig.37 A schematic diagram showing background processing of a target function page of a target function corresponding to a first target shortcut;

[0119] Fig.39 yes Fig.37Step 3720 displays a flow chart of a target function page of a target function corresponding to the first target shortcut;

[0120] Fig.40 is a module diagram of a shortcut creation device according to an embodiment of the present disclosure;

[0121] Fig.41 is a terminal structure diagram for executing a shortcut creation method according to an embodiment of the present disclosure;

[0122] Fig.42 4 is a server structure diagram for executing a shortcut creation method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0123] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0124] Before further describing the embodiments of the present disclosure in detail, the nouns and terms involved in the embodiments of the present disclosure are described. The nouns and terms involved in the embodiments of the present disclosure are subject to the following interpretations:

[0125] Shortcut: It is a very practical function in computer operation, which can help users quickly start programs, files or websites. The application of shortcuts can significantly improve the user's operating efficiency, reduce time waste, and achieve fast startup and efficient operation.

[0126] Emulator: An emulator is a piece of hardware or software that mimics the operating system of another type of terminal. It can replicate the operation of the current terminal and use the instruction set of the simulated interrupt to perform tasks.

[0127] An emulator is a tool that simulates the operating system of another type of terminal on one type of terminal, so that applications adapted to another type of terminal can be run on the terminal of this type. For example, video application A is only adapted to Android phones. If you need to use video application A on a computer, you can open the emulator on the computer and run video application A in the emulator.

[0128] The purpose of creating a shortcut is to quickly access the application corresponding to the shortcut. If you create a shortcut for an application running in the simulator, the current shortcut manager only supports displaying the shortcut of the application in the simulator interface. For example, if a user wants to create a shortcut for video application A in the simulator, the shortcut can only be displayed in the simulator interface. After the simulator is minimized or closed, if the user wants to quickly access the application interface corresponding to the shortcut, he needs to open the simulator to click the shortcut. Therefore, it increases the time cost of accessing shortcuts and reduces the opening reach rate of the simulator.

[0129] Based on this, the embodiments of the present disclosure provide a shortcut creation method, related devices and media. The shortcut creation method can reduce the time cost of accessing the application function corresponding to the shortcut and improve the opening reach rate of the simulator when the current terminal runs the application of other types of terminals through the simulator.

[0130] System architecture and scenario description of the application of the embodiments of the present disclosure

[0131] Figure 1 : is a system architecture diagram used by the shortcut creation method according to an embodiment of the present disclosure. Figure 1 As shown, the system architecture used by the shortcut creation method includes: a terminal 110 , the Internet 120 , a gateway 130 , and a server 140 .

[0132] The terminal 110 is a device used by the object to view the simulator and the shortcuts created. The terminal 110 includes various forms such as desktop computers, laptops, tablet computers, PDAs (personal digital assistants), mobile phones, vehicle-mounted terminals, home theater terminals, and dedicated terminals. In addition, it can be a single device or a collection of multiple devices. For example, multiple devices are connected through a local area network and share a display device to work together, forming a terminal. The terminal 110 can also communicate with the Internet 120 in a wired or wireless manner to exchange data.

[0133] The gateway 130 is also called an internetwork connector or a protocol converter. The gateway 130 realizes network interconnection at the transport layer and is a computer system or device that acts as a converter. The gateway 130 is a translator between two systems that use different communication protocols, data formats or languages, or even completely different architectures. At the same time, the gateway 130 can also provide filtering and security functions. The message sent by the object terminal 110 to the server 140 is sent to the corresponding server 140 through the gateway 130. The message sent by the server 140 to the object terminal 110 is also sent to the corresponding object terminal 110 through the gateway 130.

[0134] The server 140 refers to a computer system that provides shortcut creation services. Compared with the terminal 110, the server 140 has higher requirements in terms of stability, security, performance, etc. The server 140 can be a high-performance computer in a network platform, a cluster of multiple high-performance computers, a part of a high-performance computer (such as a virtual machine), a combination of parts of multiple high-performance computers (such as virtual machines), etc. The server 140 can also communicate with the Internet 120 in a wired or wireless manner to exchange data.

[0135] The embodiments of the present disclosure can be applied in various scenarios, such as FIG. 2A to FIG. 2C The cross-terminal interaction scenarios shown, etc.

[0136] Figure 2A The video application A in the example is only compatible with Android phones. In the cross-terminal interactive scenario, the computer can simulate the operating environment of the Android phone through the simulator, and then run the video application A in the simulator, thereby obtaining Figure 2B The interface diagram shown realizes the operation of video application A on the computer.

[0137] exist Figure 2B In the simulator, the video application A is playing the episode XXXX1. The playback interface of the episode XXXX1 has an "Add to Desktop" control. Click the "Add to Desktop" control to add the shortcut of the episode XXXX1 to the mobile phone desktop simulated by the simulator, so that the following is displayed: Figure 2C The shortcuts shown are shown. Figure 2C , the shortcut corresponding to the playback interface of episode XXXX1 in the video application A running on the simulator is located on the computer desktop. Figure 2C In the interface shown, the user can click the shortcut to call the episode XXXX1 in the video application A without opening the simulator.

[0138] It should be understood that the above content only illustrates some application scenarios of the present disclosure. The business scenarios to which the present disclosure can be applied may include but are not limited to the specific embodiments listed above.

[0139] General description of the disclosed embodiments

[0140] It should be emphasized that the embodiments of the present disclosure can be applied to a variety of application scenarios, such as cross-terminal interaction scenarios. The relevant technology only supports displaying shortcuts of applications running in the simulator in the simulator interface. After the simulator is minimized or closed, if the user wants to quickly access the application interface corresponding to the shortcut, he needs to open the simulator to click the shortcut. Therefore, it increases the time cost of accessing the shortcut and reduces the opening reach rate of the simulator. Some embodiments of the present disclosure provide a shortcut creation method, related devices and media, which can reduce the time cost of accessing the application function corresponding to the shortcut and improve the opening reach rate of the simulator when the current terminal runs applications of other types of terminals through the simulator.

[0141] The shortcut creation method of the disclosed embodiment responds to the shortcut creation trigger for the target function on the target application interface running on the simulator interface, and displays the shortcut bound to the target function on the desktop of the first terminal installed with the simulator. The method can reduce the time cost of accessing the application function corresponding to the shortcut when the current terminal runs the application of other types of terminals through the simulator, and improve the opening reach rate of the simulator.

[0142] The shortcut creation method of the embodiment of the present disclosure may be executed on the terminal 110 , may be executed on the server 140 , or may be executed partially on the terminal 110 and partially on the server 140 .

[0143] like Figure 3 As shown, taking the application of a shortcut creation method according to an embodiment of the present disclosure to a first terminal as an example, the shortcut creation method includes:

[0144] Step 310: In response to a call triggering the simulator on a first interface of the first terminal, displaying a simulator interface;

[0145] Step 320: In response to a call trigger of a target application on the simulator interface, displaying a target application interface on the simulator interface, where the target application is an application adapted to a second terminal of a type different from that of the first terminal;

[0146] Step 330: In response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut for the target function is displayed on a first interface.

[0147] Steps 310 to 330 are described in detail below.

[0148] In step 310, in response to a triggering call to the simulator on a first interface of a first terminal, a simulator interface is displayed.

[0149] The first terminal is a terminal installed with a simulator, such as a desktop computer, a laptop computer, etc. The following description assumes that the first terminal is a desktop computer. The first interface is the main interface of the desktop computer, and the first interface includes shortcuts to multiple applications installed on the desktop computer. Figure 4A and Figure 5 , the first interface of the desktop computer includes the shortcut "This PC", the shortcut "Recycle Bin" and the shortcut "Simulator".

[0150] The simulator can be called and triggered in many ways, such as double-clicking the shortcut "Simulator" on the first interface, right-clicking and opening the shortcut "Simulator". In addition, the simulator can also be called and triggered by clicking the control corresponding to the simulator in the start menu bar. When the simulator is minimized, the simulator can be called and triggered by the mouse, keyboard, etc.

[0151] The simulator is an application used in the first terminal to simulate other types of terminals. The simulator interface can be displayed in a variety of ways. Figure 4A The simulator interface shown is determined based on the interface of the terminal simulated by the simulator. Specifically, if the simulator needs to simulate mobile phone A, then Figure 4A The simulator interface shown includes the desktop of mobile phone A. The display style and arrangement of each mobile phone application in the simulator interface are consistent with the desktop of mobile phone A. Figure 5 The simulator interface shown only includes multiple applications installed in the terminal simulated by the simulator, such as Game Center, Video Application A, Game A, and Video Application B, and the icons and controls corresponding to the multiple applications are displayed in a list on the simulator interface.

[0152] Reference Figure 4A and Figure 5 To facilitate the operation of the simulator, the simulator interface also includes multiple controls, such as volume adjustment control, simulator input method control, return control, minimize control, maximize control, close control, etc.

[0153] In step 320, in response to a call trigger of a target application on the simulator interface, a target application interface is displayed on the simulator interface, where the target application is an application adapted to a second terminal of a type different from that of the first terminal.

[0154] The type of the second terminal is different from the type of the first terminal. If the first terminal is a desktop computer, the second terminal is a terminal of a different type from the computer, such as a mobile phone or a tablet. Assume that the desktop computer is installed with a simulator, which is specifically used to simulate the operating environment of the mobile phone.

[0155] The target application is an application adapted to the second terminal, and the target application is usually not applicable to the first terminal. The target application is installed on the second terminal, and on the first terminal, the target application runs based on the environment of the second terminal simulated by the simulator. Figure 4A In the example, the applications adapted to the second terminal include a game center and a video application A. Figure 5 In the example, the applications adapted to the second terminal include a game center, a video application A, a game A, and an adapted application B.

[0156] In the simulator interface, the user can select an application as the target application as needed, and display the target application interface on the simulator interface by calling the target application.

[0157] The target application interface is the interface of the target application. If the target application is not running before the target application is called and triggered, the target application interface displayed is the main interface of the target application, such as the game launch interface of the game application, the bookstore or bookshelf interface of the e-book application. If the target application is in the background running state before the target application is called and triggered, the target application interface displayed is the interface when the target application was last closed.

[0158] Reference Figure 4A and Figure 5 , the first terminal is a computer, and the second terminal is a mobile phone. Figure 4A The simulator interface shown is the same as the mobile desktop of the second terminal. Then, the target application can be called and triggered by clicking the shortcut corresponding to the target application, that is, the video application A, so that the target application interface is displayed on the simulator interface. Figure 5 The simulator interface shown can trigger the call of the target application by clicking the "Open" control corresponding to the target application, that is, video application A, so that the target application interface is displayed on the simulator interface.

[0159] In step 330 , in response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut for the target function is displayed on a first interface.

[0160] The target function corresponds to the target application interface and is a function in the target application. If the target application is a video application, the target function can be "TV series", "variety show", "movie", etc., or it can be a specific TV series. If the target application is an e-book application, the target function can be a certain e-book or a chapter of the e-book.

[0161] The shortcut creation trigger corresponds to the target function, and the purpose of the shortcut creation trigger is to create a first target shortcut corresponding to the target function on the first interface of the first terminal.

[0162] The first target shortcut is bound to the interface corresponding to the target function. The creation of the first target shortcut can help users quickly open the target function on the first interface, thereby improving the user's operating efficiency, reducing time waste, and achieving fast startup and efficient operation.

[0163] Reference Figure 4B and Figure 2B , video application A is the target application, and the drama XXXX1 in video application A is the target function. In the interface of video application A, a corresponding first target shortcut can be created for drama XXXX1. Figure 4C The first target shortcut in the is triggered in response to a click Figure 4B The Add to Desktop control shown creates the display. Figure 2C The first target shortcut in the is triggered in response to a click Figure 2B The Add to Desktop control shown creates the displayed. Figure 4C and Figure 2C The first target shortcut is located on the computer desktop of the first terminal. The name of the first target shortcut is "XXXX1-Video Application A". By calling and triggering the shortcut, the drama XXXX1 can be quickly started and the interface of the drama XXXX1 can be displayed.

[0164] In the above-mentioned embodiment of step 310 to step 330, after the user calls the target application supported by another type of terminal different from the type of the current terminal through the simulator, a shortcut creation trigger is made on the target application interface. In response to the shortcut creation trigger, the first target shortcut of the target function is not displayed on the simulator interface, but the first target shortcut of the target function is displayed on the current terminal interface. Therefore, only the first target shortcut needs to be triggered to open the target function interface corresponding to the first target shortcut and execute the target function without opening the simulator, thereby realizing quick access to the function within the application. In the case where the current terminal runs the application of other types of terminals through the simulator, the embodiment of the present disclosure reduces the time cost of accessing the function within the application corresponding to the shortcut and improves the opening reach rate of the simulator. Moreover, the embodiment of the present disclosure can reduce the access time cost for the function within the application, rather than for the application. It targets a finer dimension and can reduce the access time cost in a finer dimension, thereby being more conducive to reducing the overall access time cost.

[0165] The above is a general description of step 310 to step 330. Since step 310 and step 320 have been described in detail above, only the specific implementation process of step 330 will be described in detail below.

[0166] Detailed description of step 330

[0167] In step 330 , in response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut for the target function is displayed on a first interface.

[0168] In one embodiment, the simulator interface covers a portion of the first interface, referring to Figure 6 , step 330 includes:

[0169] Step 610: On the target application interface, receiving a shortcut creation trigger for a target function of the target application interface;

[0170] Step 620: while displaying the simulator interface on the first interface, display a first target shortcut to the target function on a portion of the first interface not occupied by the simulator interface.

[0171] Step 610 and step 620 are described in detail below.

[0172] In step 610, on a target application interface, a shortcut creation trigger for a target function of the target application interface is received.

[0173] The simulator interface covers part of the first interface. Figure 4A and Figure 5 , the simulator interface is in a non-maximized state, then the simulator interface only covers part of the first interface. In this case, by dragging the simulator interface, multiple shortcuts of the simulator interface and the first interface can be displayed simultaneously.

[0174] In the target application interface, users can trigger the shortcut of the target function by clicking or other operations as needed to create a shortcut to the target function.

[0175] In step 620, while the simulator interface is displayed on the first interface, a first target shortcut to the target function is displayed on a portion of the first interface not occupied by the simulator interface.

[0176] If the simulator interface covers a portion of the first interface, the first interface can display the simulator interface and the first target shortcut at the same time. To ensure that the first interface displays the simulator interface and the first target shortcut at the same time, after receiving a shortcut creation trigger for the target function of the target application interface, the first target shortcut of the target function is displayed on the portion of the first interface not occupied by the simulator interface.

[0177] Before the first target shortcut is displayed, if the simulator interface occupies the portion of other shortcuts in the first interface, in response to the shortcut creation trigger for the target function on the target application interface, the displayed first target shortcut is located in a different area of ​​the first interface from the other shortcuts. Figure 5In the first interface shown, if the simulator interface covers the shortcuts "This Computer", "Recycle Bin", and "Simulator" on the left side of the first interface, then the first target shortcut displayed later is located on the right side of the first interface and also on the right side of the simulator interface. This shortcut is located in a different area from other shortcuts.

[0178] Before the first target shortcut is displayed, if the simulator interface does not occupy the portion of other shortcuts, then in response to a shortcut creation trigger for the target function on the target application interface, the displayed first target shortcut can be displayed based on the position of other shortcuts. Figure 5 , the shortcuts of the simulator interface and the first interface are displayed on the first interface at the same time, then the first target shortcut displayed later is as follows Figure 2C As shown, the first target shortcut is arranged in order based on the existing shortcuts in the first interface. In addition, in this case, the first target shortcut can also be displayed in different areas of the first interface with other shortcuts, for example, other shortcuts are located on the left side of the simulator, and the first target shortcut is located on the right side of the simulator.

[0179] In the embodiment of the above-mentioned steps 610 and 620, on the target application interface, a shortcut creation trigger for a target function of the target application interface is received, and the simulator interface covers a portion of the first interface. Then, while the simulator interface is displayed on the first interface, the first target shortcut of the target function is displayed on the portion of the first interface not occupied by the simulator, so that the simulator interface and the first target shortcut are displayed on the first interface at the same time, thereby being able to directly determine that the first target shortcut is created successfully, reducing the time for determining whether the shortcut is created successfully.

[0180] The above is a general description of step 610 and step 620. Since step 620 has been described in detail above, only the specific implementation process of step 610 will be described in detail below.

[0181] In another embodiment, referring to Figure 7 , the simulator interface covers the entire first interface. In the target application interface, a shortcut creation trigger for a target function of the target application interface is received. Afterwards, in response to receiving a call trigger for the first interface, the first interface is displayed, and the first interface includes a first target shortcut to the target function.

[0182] It should be noted that the call trigger for the first interface can be implemented in a variety of ways, such as displaying the first interface through the minimize control, close control, or keyboard shortcut of the simulator interface. The first interface displayed in this way does not include the simulator interface. In addition, the size and position of the simulator interface can also be changed by combining the "restore" control of the simulator interface with the mouse operation to display the simulator interface and the first target shortcut on the first interface at the same time.

[0183] In step 610, on a target application interface, a shortcut creation trigger for a target function of the target application interface is received.

[0184] In one embodiment, referring to Figure 8 , step 610 includes:

[0185] Step 810: On the target application interface, receiving a target function entry trigger for a target function;

[0186] Step 820: In response to the target function entry trigger, display the target function page of the target function, where the target function page has a shortcut creation control;

[0187] Step 830: Receive a shortcut creation trigger for a shortcut creation control.

[0188] Steps 810 to 830 are described in detail below.

[0189] In step 810 , a target function entry trigger for a target function is received on a target application interface.

[0190] The target application includes multiple functions, and correspondingly, the target application interface includes target function entry trigger controls corresponding to each function. Fig. 9A In the example, the target application interface corresponding to video application A includes trigger controls corresponding to episode XXXX1, episode XXXX2, and episode YYY. Clicking the trigger control can trigger the target function. The trigger control can be set according to the target application. Fig. 9A In the video application A interface shown, the trigger control is displayed as the corresponding episode poster and episode name. In the e-book interface, the trigger control is displayed as the book cover and book name.

[0191] In step 820 , in response to a target function entry trigger, a target function page of the target function is displayed, and a shortcut creation control is provided on the target function page.

[0192] The target function page is the display interface corresponding to the target function. Fig. 9A For the episode XXX1 shown in the figure, its corresponding target function page is as follows Figure 5 shown.

[0193] The shortcut creation control is associated with the creation of the first target shortcut. Figure 5 In the target function page shown, the shortcut creation control is the "Add to Desktop" control.

[0194] In step 830 , a shortcut creation trigger for a shortcut creation control is received.

[0195] The target function page has a shortcut creation control. Triggering the shortcut creation control can trigger the shortcut creation trigger for the target function of the target application interface.

[0196] Figure 5 The simulator interface shown includes an opening control corresponding to the target application, that is, video application A. In response to the triggering of the opening control corresponding to video application A, the following is displayed: Fig. 9A In response to the entry trigger of the episode XXXXX1 of the video application A interface, the target application interface shown in FIG. Figure 2B In response to the triggering of the "Add to Desktop" control, the following target function page is displayed: Figure 2C The first target shortcut is shown.

[0197] In the embodiment of the above steps 810 to 830, in the target application interface, first, in response to the target function entry trigger, the target function page of the target function is displayed. Afterwards, in response to the triggering of the shortcut creation control on the target function page, the first target shortcut of the target function is displayed on the first page. This method facilitates the creation of shortcuts on the target function page and improves the association between the first target shortcut and the target function page.

[0198] In another embodiment, referring to Fig. 9B , the target application interface includes a function list, the function list includes a shortcut creation control corresponding to the target function, in response to the shortcut creation trigger of the shortcut creation control in FIG. 9, a first target shortcut corresponding to the target function is displayed on the first interface, and the first target shortcut is as follows Figure 2C shown.

[0199] The function list includes a target function entry control corresponding to the target function, that is, the control is "opened", and in response to the triggering of the target function entry control, the display Figure 2B The target function page is shown.

[0200] In one embodiment, the first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon.

[0201] Reference Fig.10 , step 330 includes:

[0202] Step 1010 , in response to a shortcut creation trigger for a target function on a target application interface, if the target function includes a target function image, display a first target shortcut icon as a composite image of the target function image and a simulator shortcut icon.

[0203] It should be noted that shortcuts are displayed via shortcut icons. Figure 2B The shortcut icon of the shortcut corresponding to this computer is an image containing a computer logo.

[0204] The first interface displays the simulator shortcut of the simulator. The simulator shortcut includes the simulator shortcut icon. Figure 2B , the simulator shortcut icon is a ring. Correspondingly, the first target shortcut of the target function is displayed on the first interface through the first target shortcut icon.

[0205] Step 1010 is described in detail below.

[0206] In step 1010 , in response to a shortcut creation trigger for a target function on a target application interface, if the target function includes a target function image, a first target shortcut icon is displayed as a composite image of the target function image and a simulator shortcut icon.

[0207] The target function image is a binding image of the target function. Through the target function image, the function corresponding to the image can be determined. Assuming that the target function is the drama XXXX1, the target function image is the poster of the drama XXXX1. Assuming that the target function is an e-book, the target function image is the cover of the e-book.

[0208] When the target function includes a target function image, the first target shortcut icon is displayed as a composite image of the target function image and the simulator shortcut icon, and then based on the first target shortcut icon, the target function corresponding to the shortcut and the corresponding open application, i.e., the simulator application, can be determined.

[0209] Reference Figure 2B , the target function is the episode XXXX1, then the target function image is the poster of the episode XXXX1, and the composite image of the poster of the episode XXXX1 and the simulator shortcut icon is used as the first target shortcut icon corresponding to the episode XXXX1. The displayed first target shortcut icon is as follows Figure 2CAs shown in the figure, the target function image is the main part of the first target shortcut icon in the poster of the drama XXXX1, and the simulator shortcut icon is located in the lower right corner of the poster of the drama XXXX1. The setting method of the first target shortcut icon can highlight the target function information while displaying the simulator information, thereby improving the efficiency of information transmission.

[0210] In addition, in the first target shortcut icon, the target function image and the simulator shortcut icon can be set in other ways. For example, the simulator shortcut can be located in various positions such as the upper left corner, upper right corner, and lower left corner of the target function image. The simulator shortcut and the target function image can each occupy half of the area of ​​the first target shortcut icon, and the two can be distributed left to right, or up and down.

[0211] In the embodiment of the above-mentioned step 1010, when the target function includes a function image, the first target shortcut icon is displayed as a composite image of the target function image and the simulator shortcut icon, so that the first target shortcut displayed on the first interface displays the target function information and the simulator information, thereby improving the information transmission efficiency of the first target shortcut.

[0212] In one embodiment, the first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon.

[0213] Reference Fig.11 , step 330 includes:

[0214] Step 1110, in response to a trigger for creating a shortcut to a target function on a target function application interface, if the target function does not include a target function image, display a first target shortcut icon as a composite image of a target function text image corresponding to the target function and a simulator shortcut icon.

[0215] Step 1110 is described in detail below.

[0216] In step 1110, in response to a shortcut creation trigger for a target function on a target function application interface, if the target function does not include a target function image, the first target shortcut icon is displayed as a composite image of a target function text image corresponding to the target function and a simulator shortcut icon.

[0217] If the target function does not contain a target function image, for example, an e-book does not have an e-book cover or a browser page does not contain an image, the first target shortcut icon will be displayed as a composite image of the target function text image corresponding to the target function and the simulator shortcut icon.

[0218] The target function text image is determined based on the target function. The target function text image can be an image containing the first character of the text title of the target function, or the first preset number of characters. For example, if the drama XYZ does not have a drama poster, then its corresponding target function text image is an image containing "X", or "XY", or "XYZ". For e-books, the corresponding target function text image is usually an image containing the name of the e-book. Fig.12 , the name of the e-book is ZYAI, then the target function text image corresponding to the e-book ZYAI is an image containing the characters ZYAI. Based on this image and the simulator shortcut icon, it can be determined as follows Fig.12 The first target shortcut icon is shown.

[0219] In the first target shortcut icon, the target function text image and the simulator shortcut icon can be arranged in a variety of ways, for example, the target function text image is set as the main part of the first target shortcut icon, and the reduced simulator shortcut icon is set in the lower right corner or lower left corner of the target function text image, etc. This setting method can highlight the information of the target function while displaying the simulator information, thereby improving the efficiency of information transmission. In addition, in the first target shortcut icon, the simulator shortcut and the target function text image can each occupy half of the area of ​​the first target shortcut icon, and the two can be distributed left and right, or up and down.

[0220] In the embodiment of the above-mentioned step 1110, when the target function does not include a target function image, the first target shortcut icon is displayed as a composite image of the target function text image corresponding to the target function and the simulator shortcut icon. This method is applicable to more diverse functions, thereby improving the applicability of the shortcut creation method.

[0221] In one embodiment, the shortcut further includes a shortcut name, and correspondingly, the first target shortcut includes a first target shortcut name. In response to a shortcut creation trigger for a target function on a target function application interface, the first target shortcut name is determined based on the target function name corresponding to the target function and the target application name corresponding to the target application, and then the first target shortcut is displayed on the first interface. The first target shortcut name determined in this way displays the target function information and the target application information, which facilitates the identification of the first target shortcut from multiple shortcuts, thereby improving the information transmission efficiency of the first target shortcut.

[0222] Reference Figure 2C , the target function name is XXXX1, the target application name is video application A, then the first target shortcut name is displayed as XXXX1-Video Application A. Fig.12, the target function name is the e-book name, i.e. ZYAI, and the target application name is the e-book application, then the first target shortcut name is displayed as ZYAI-e-book application.

[0223] In one embodiment, referring to Fig.13 , step 330 includes:

[0224] Step 1310 , in response to a shortcut creation trigger for a target function on a target application interface, display a first target shortcut of the target function on a first interface and display a second target shortcut of the target function on a simulator interface.

[0225] Step 1310 is described in detail below.

[0226] In step 1310 , in response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut of the target function is displayed on a first interface, and a second target shortcut of the target function is displayed on a simulator interface.

[0227] The second target shortcut is a shortcut bound to a target function, but unlike the first target shortcut, the second target shortcut is displayed on the simulator interface.

[0228] exist Figure 4B In response to a shortcut creation trigger for a target function on a target application interface, the shortcut creation trigger is processed by the shortcut creation method provided by the embodiment of the present disclosure, thereby displaying Fig.14A interface. Fig.14A In the example, the first target shortcut is located on the first interface, and the second target shortcut is located on the simulator interface. Then, in the simulator interface, the target function page can be displayed by triggering the first target shortcut.

[0229] exist Figure 2B In response to a shortcut creation trigger for a target function on a target application interface, the shortcut creation trigger is processed by the shortcut creation method provided by the embodiment of the present disclosure, thereby displaying Fig. 14B interface. Fig. 14B The function list shown includes drama XXX1 and an opening control corresponding to drama XXX1. In response to triggering the opening control of drama XXXX1, the interface of drama XXXX1 is displayed.

[0230] The embodiment of the above step 1310 creates a first target shortcut that displays the target function on the first interface, and at the same time creates a second target shortcut that displays the target function on the simulator interface. Then, when browsing the simulator interface, the in-application page corresponding to the target function can be directly accessed through the second target shortcut without returning to the first interface, thereby reducing the time cost of accessing the target function.

[0231] In one embodiment, the first target shortcut and the second target shortcut of the same target function have the same target attribute. This setting facilitates finding the second target shortcut corresponding to the first target shortcut in the simulator interface, or finding the first target shortcut corresponding to the second target shortcut in the first interface. The first target shortcut is unified with the second target shortcut, which reduces the amount of information acquisition for determining the shortcut corresponding to the same function in different interfaces.

[0232] Target properties include the name, icon, and other display styles of the target shortcut. Fig.14A and Fig. 14B , the first target shortcut and the second target shortcut have the same name, but the second target shortcut is located in the simulator interface, so the second target shortcut does not contain the simulator shortcut icon.

[0233] In one embodiment, referring to Fig.15 , step 330 includes:

[0234] Step 1510: Displaying a target area corresponding to a target application on the first interface;

[0235] Step 1520: Display a first target shortcut of the target function in the target area.

[0236] Step 1510 and step 1520 are described in detail below.

[0237] In step 1510, a target area corresponding to a target application is displayed on a first interface.

[0238] The target area is an area of ​​the first interface, and the target area corresponds to the target application. Fig.16A , video application A corresponds to area 2, the e-book application corresponds to area 3, and area 1 is the area where other shortcuts that are not created based on application functions in the simulator are located.

[0239] It should be noted that different target applications have different corresponding target areas. In order to improve the information transmission efficiency of shortcuts corresponding to different applications, the embodiments of the present disclosure can set different display attributes for different areas. The display attributes may include display background, icon display size, etc. Fig.16A, the display background corresponding to area 1 is blank, the display background corresponding to area 2 is diagonal stripes, and the display background corresponding to area 3 is horizontal stripes.

[0240] In step 1520 , a first target shortcut of the target function is displayed in the target area.

[0241] The target area corresponds to the target application, so in response to a shortcut creation trigger for the target function on the target application interface, a first target shortcut to the target function is displayed in the target area of ​​the first interface.

[0242] Reference Fig.16A , area 2 corresponds to video application A, so the shortcuts "XXXX1-Video Application A", "XXXX1 Episode 2-Video Application A", and "XXXX1 Episode 5-Video Application A" created based on the functions in video application A are displayed in area 2. Area 3 corresponds to the e-book application, so the shortcut "ZYAI-E-book Application" is located in area 3. In addition, other shortcuts that are not created based on the application functions in the simulator, such as Computer, Recycle Bin, and Simulator, are located in area 1.

[0243] In the above-mentioned embodiments of step 1510 and step 1520, different areas are set for different applications in the first interface. The area corresponding to the target application in the first interface is the target area, and the shortcuts corresponding to the functions in the target application are displayed in the target area. Then, the first target shortcut of the target function is displayed in the target area, so that it is convenient to quickly determine the required shortcut according to the location of different areas, thereby improving the efficiency of information transmission of shortcuts.

[0244] The above is a general description of step 1510 and step 1520. Since step 1510 has been described in detail above, only the specific implementation process of step 1520 will be described in detail below.

[0245] In step 1520 , a first target shortcut of the target function is displayed in the target area.

[0246] In one embodiment, the target function includes a first target function and a second target function, and the second target function belongs to the first target function.

[0247] Reference Fig.17 , step 1520 includes:

[0248] Step 1710: Display the first target shortcut of the second target function as having an associated mark with the first target shortcut of the first target function.

[0249] Step 1710 is described in detail below.

[0250] The first target shortcut of the second target function is displayed to have an associated mark with the first target shortcut of the first target function.

[0251] The first target function and the second target function are both functions within the target application, and the first target function and the second target function are subordinate to each other, and the second target function belongs to the first target function. Assuming that the first target function is the drama XXXX1, the second target function can be the first episode of the drama XXXX1, the second episode of the drama XXXX1, etc. Assuming that the first target function is the e-book ZYAI, then the second target function is a specific chapter in the e-book ZYAI.

[0252] The association mark is displayed between the first target shortcuts corresponding to the first target function and the second target function, and is used to indicate the subordinate relationship between the two first target shortcuts. Fig. 16B , the shortcuts “XXXX1 Episode 2 - Video Application A” and “XXXX1 Episode 5 - Video Application A” both extend arrows pointing to the shortcut “XXXX1 - Video Application A”, indicating that the in-app functions corresponding to the shortcuts “XXXX1 Episode 2 - Video Application A” and “XXXX1 Episode 5 - Video Application A” belong to the in-app functions corresponding to “XXXX1 - Video Application A”.

[0253] In addition, the association mark can also be implemented in other ways, such as a dynamic object moving back and forth between the shortcut "XXXX1-Video Application A" and the shortcut "XXXX1 Episode 2-Video Application A", and finally staying near the regional shortcut "XXXX1-Video Application A".

[0254] The embodiment of the above step 1710 displays an association mark between the target shortcuts corresponding to the first target function and the second target function having a subordinate relationship, thereby increasing the amount of information contained in the first interface and improving the efficiency of information transmission.

[0255] The above is a general description of step 1710. The specific implementation process of step 1710 is described in detail below.

[0256] In step 1710 , the first target shortcut of the second target function is displayed to have an associated mark with the first target shortcut of the first target function.

[0257] In one embodiment, referring to Fig.18 , step 1710 includes:

[0258] Step 1810: Display a target tree in the target area;

[0259] Step 1820: Display the first target shortcut of the first target function as a parent node of the target tree;

[0260] Step 1830: Display the first target shortcut of the second target function as a child node of the parent node.

[0261] Steps 1810 to 1830 are described in detail below.

[0262] In step 1810, a target tree is displayed in the target area.

[0263] The target tree is a tree structure, and the target tree is used to indicate the association relationship between multiple first target shortcuts corresponding to the target application. It can be said that the target tree is a display form of the association mark. The setting of the tree structure can accurately and indirectly indicate the association relationship between multiple first target shortcuts corresponding to the target tree.

[0264] In step 1820 , the first target shortcut of the first target function is displayed as a parent node of the target tree.

[0265] A parent node is a node in the target tree that has at least one child node under it.

[0266] In step 1830 , the first target shortcut of the second target function is displayed as a child node of the parent node.

[0267] A child node refers to a node contained in the next level of the parent node in the target tree. It can be said that a child node is a node that belongs to the parent node. In addition, the second target function belongs to the first target function, so the first target shortcut of the first target function is used as the parent node of the target tree, and the first target shortcut of the second target function is used as the child node of the parent node, so that the subordinate relationship between the first target function and the second target function is represented by the hierarchical relationship of the target tree.

[0268] exist Fig.16A In the illustrated area 2, a target tree corresponding to the target application is displayed. In the target tree, the shortcut "XXXX1-Video Application A" is displayed as a parent node of the target tree, and the shortcuts "XXXX1 Episode 2-Video Application A" and "XXXX1 Episode 5-Video Application A" are displayed as child nodes of the parent node, indicating that the episodes XXXX1 Episode 2 and XXXX1 Episode 5 belong to the episode XXXX1.

[0269] The embodiment of the above steps 1810 to 1830 displays the association marks between shortcuts through a target tree. Specifically, the first target shortcut of the first target function is displayed as a parent node of the target tree, and the first target shortcut of the second target function is displayed as a child node of the parent node, thereby representing the subordinate relationship between the target functions through the hierarchical relationship between the target trees, thereby increasing the amount of information contained in the first interface and improving the efficiency of information transmission.

[0270] In one embodiment, referring to Fig.19 , step 330 includes:

[0271] Step 1910: In response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut to the target function is displayed on a first interface based on display attributes corresponding to a function type of the target function.

[0272] Step 1910 is described in detail below.

[0273] In step 1910, in response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut to the target function is displayed on a first interface based on display properties corresponding to a function type of the target function.

[0274] Function type is used to distinguish multiple functions corresponding to the target application. If the target application is a video application, the function type can be TV series, movies, variety shows, documentaries, etc. If the target application is an e-book application, the function type can be science fiction, martial arts novels, serious literature, etc.

[0275] In the embodiment of the present disclosure, different function types correspond to different display attributes, and the first target shortcut of the target function is displayed on the first interface through the display attributes. The display attributes include the display background, icon font, icon color, etc. of the shortcut.

[0276] Reference Fig. 20 In video application A, the function type corresponding to XXXX1 is TV series, the function type corresponding to XYXY is variety show, and the function type corresponding to RECORD is documentary. Fig. 20 The multiple shortcuts in the first interface shown clearly show that the display attributes of shortcuts corresponding to different function types are different. Among them, the display background of the shortcut corresponding to the TV series XXXX1 is a grid background, the display background of the shortcut corresponding to the variety show XYXY is a diagonal grid background, and the display background of the shortcut corresponding to the documentary RECORD is a vertical striped background.

[0277] In the embodiment of the above-mentioned step 1910, different function types correspond to different display attributes, and based on the display attributes corresponding to the function type of the target function, the first target shortcut of the target function is displayed on the first interface, so that the function type of the target function corresponding to the shortcut can be determined according to the display style of the shortcut in the first interface, thereby increasing the amount of information contained in the first target shortcut and improving the efficiency of information transmission.

[0278] In one embodiment, referring to Fig.21 , step 330 includes:

[0279] Step 2110: receiving a shortcut creation trigger for the target function during execution of the target function on the target application interface;

[0280] Step 2120: In response to a shortcut creation trigger, while displaying a first target shortcut of the target function on the first interface, the execution progress of the target function is displayed in association with the first target shortcut.

[0281] Step 2110 and step 2120 are described in detail below.

[0282] In step 2110 , during the process of executing the target function on the target application interface, a shortcut creation trigger for the target function is received.

[0283] In the process of executing the target function on the target application interface, the target function page is displayed on the target application interface. If the target application is video application A and the target function is drama XXXX1, then the process of executing the target function is the process of playing drama XXXX1.

[0284] In step 2120 , in response to a shortcut creation trigger, while displaying a first target shortcut of a target function on the first interface, an execution progress of the target function is displayed in association with the first target shortcut.

[0285] The first target shortcut is associated with the display of the execution progress of the target function. Fig. 22 Based on the display interface of the video application A, it can be determined that when the shortcut to the target function is created, the play of the drama XXXX1 is played to the 22 minutes and 46 seconds of the third episode. Then the first target shortcut created on the first interface is associated with the play progress of the drama XXXX1.

[0286] The execution progress of the target function may be displayed in a variety of ways, such as displaying the execution progress of the target function as the display background of the first target shortcut, a part of the first target shortcut icon, or the name of the first target shortcut. Fig. 22 The execution progress of the target function is indicated by the first target shortcut name.

[0287] If the implementation example of the above-mentioned steps 2110 and 2120 triggers the creation of a shortcut to the target function during the execution of the target function on the target application interface, then while the first target shortcut of the target function is displayed on the first interface, the execution progress of the target function is displayed in association with the first target shortcut, so as to facilitate the user to determine the execution progress of the target function, thereby improving the information transmission efficiency of the first target shortcut.

[0288] In one embodiment, referring to Fig.23 , step 330 includes:

[0289] Step 2310: In response to a shortcut creation trigger for a target function on a target application interface, multiple target shortcuts are displayed on a first interface, the multiple target shortcuts include a first target shortcut of the target function, and the multiple target shortcuts are sorted according to the creation time of the multiple target shortcuts.

[0290] Step 2310 is described in detail below.

[0291] In step 2310, in response to a shortcut creation trigger for a target function on a target application interface, multiple target shortcuts are displayed on a first interface, the multiple target shortcuts include a first target shortcut to the target function, and the multiple target shortcuts are sorted according to the creation time of the multiple target shortcuts.

[0292] During the execution of the target application interface, the user can create multiple target shortcuts as needed, and the multiple target shortcuts are sorted according to the creation time of the multiple target shortcuts, so that the creation order of the target shortcuts can be determined based on the order of the target shortcuts displayed on the first interface.

[0293] Fig.24 The shortcuts displayed are sorted by the time they were created. Fig.24 The creation time order of multiple shortcuts is displayed, so that it can be determined that the shortcut with the earliest creation time is "XXXX1 Episode 2 - Video Application A", and the shortcut with the creation time closest to the current time is "XXXX1 Episode 5 - Video Application A". Then the user can click the shortcut "XXXX1 Episode 5 - Video Application A" to connect to the previous viewing progress.

[0294] It should be noted that, not limited to the target application, the shortcuts corresponding to the various functions of the multiple applications corresponding to the simulator are all sorted on the first interface according to the creation time of the shortcuts.

[0295] The embodiment of the above step 2310 displays multiple target shortcuts on the first interface, and the multiple target shortcuts are sorted according to the creation time of the multiple target shortcuts. Then, based on the arrangement order of the target shortcuts, the first target shortcut of the target function closest to the current time can be determined, thereby connecting the execution progress of the previous target function and improving the execution efficiency.

[0296] In one embodiment, referring to Fig.25 , step 330 includes:

[0297] Step 2510: In response to a shortcut creation trigger for a target function on a target application interface, display an animation of the target function being transferred to the first interface;

[0298] Step 2520: After the animation ends, a first target shortcut of the target function is displayed on the first interface.

[0299] Step 2510 and step 2520 are described in detail below.

[0300] In step 2510, in response to a shortcut creation trigger for a target function on a target application interface, an animation of the target function being transferred to the first interface is displayed.

[0301] The animation of the target function transferring to the first interface is the connection animation between the target application interface and the first target shortcut.

[0302] The animation of transferring the target function to the first interface can be implemented in many ways. Fig.26 The animation shown is that the episode playback screen displayed on the target function page is gradually reduced to the icon of the first target shortcut. In addition, the animation can also display the name of the target function to emphasize that the first target shortcut corresponds to the target function, and fade-in, fade-out, gradient, etc. can be added to the animation to increase the aesthetics of the animation.

[0303] In step 2520, after the animation ends, a first target shortcut of the target function is displayed on the first interface.

[0304] The animation is a connection animation between the target application interface and the first target shortcut. After the animation ends, the first target shortcut of the target function is displayed on the first interface.

[0305] In the embodiment of the above step 2510 and step 2520, in response to the triggering of creating a shortcut for the target function on the target application interface, an animation of the target function transferring to the first interface is first displayed, and after the animation ends, a first target shortcut of the target function is displayed on the first interface. The setting of the animation increases the beauty of the shortcut creation process, and the animation can highlight the creation of the first target shortcut corresponding to the target function.

[0306] In one embodiment, referring to Fig. 27 , step 330 includes:

[0307] Step 2710: In response to a shortcut creation trigger for a target function on a target application interface, display a first target shortcut of the target function on a first interface and display the first target shortcut on a second interface of a second terminal bound to the first terminal.

[0308] Step 2710 is described in detail below.

[0309] In step 2710, in response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut to the target function is displayed on a first interface and at the same time, the first target shortcut is displayed on a second interface of a second terminal bound to the first terminal.

[0310] The simulator is used to simulate the operating environment of the second terminal. To achieve synchronization between the simulator operation and the second terminal, the first target shortcut of the target function is displayed on the first interface while the first target shortcut of the target function is displayed on the second interface of the second terminal.

[0311] Fig.28 The second interface of the second terminal bound to the first terminal provided by the embodiment of the present disclosure. Figure 2B The shortcut creation trigger for the target function on the target application interface shown in the figure is displayed on the first interface as follows Figure 2C The first target shortcut is shown, and the second interface is displayed as follows Fig.28 The first target shortcut is shown. Fig.28 The first target shortcut shown in the second terminal is Figure 2C The name of the first target shortcut is the same as shown, but since the second terminal itself does not involve the simulator, Fig.28 The icon of the first target shortcut shown does not include the simulator shortcut icon. In addition, in the second interface, the position, icon size, name font, etc. of the first target shortcut need to be adaptively set with the second terminal to be consistent with the shortcuts of other applications in the second terminal.

[0312] The embodiment of the above-mentioned step 2710 responds to the trigger of creating a shortcut for the target function on the target application interface, displays the first target shortcut of the target function on the first interface, and displays the first target shortcut on the second interface of the second terminal. The second terminal is an interrupt bound to the simulator of the first terminal. This method can realize the synchronization of the simulator and the second terminal, which is convenient for operation on the first terminal and the second terminal anytime and anywhere.

[0313] In one embodiment, referring to Fig.29 , step 330 includes:

[0314] Step 2910: In response to a shortcut creation trigger for a target function on a target application interface, a shortcut creation notification is displayed, where the shortcut creation notification includes a shortcut cross-interface creation control;

[0315] Step 2920: In response to a call trigger for a shortcut cross-interface creation control, display a first target shortcut of a target function on a first interface.

[0316] Step 2910 and step 2920 are described in detail below.

[0317] In step 2910, in response to a shortcut creation trigger for a target function in a target application interface, a shortcut creation notification is displayed, and the shortcut creation notification includes a shortcut cross-interface creation control.

[0318] The shortcut creation notification is a small notification message that reminds the user of the first terminal to create a shortcut across interfaces. The shortcut creation across interfaces refers to creating a shortcut to a function within the simulator application on the first interface.

[0319] The shortcut cross-interface creation control is displayed on the shortcut creation notification page, and the shortcut cross-interface creation control is used to display the first target shortcut of the target function on the first interface.

[0320] In step 2920, in response to a call trigger for a shortcut cross-interface creation control, a first target shortcut of a target function is displayed on a first interface.

[0321] In response to a call trigger for a shortcut cross-interface creation control on a shortcut creation notification, a first target shortcut of a target function is displayed on a first interface.

[0322] Figure 2B The target application interface is displayed. Click the "Add to Desktop" control to trigger the creation of a shortcut to the target function, and then display the following Fig.30 The shortcut creation notification is displayed with "Do you want to create a shortcut on the computer desktop?" and displays a control "Yes" and a control "No". The control "Yes" is a shortcut cross-interface creation control. In response to the click trigger of the control "Yes", the first target shortcut of the target function is displayed on the first interface, and the Figure 2C If the trigger control "No" is clicked, the shortcut to the target function will not be created, or a second target shortcut to the target function will be displayed on the simulator interface.

[0323] In the embodiment of the above steps 2910 and 2920, in response to a shortcut creation trigger for a target function on a target application interface, a shortcut creation notification is first displayed, and the shortcut creation notification includes a shortcut cross-interface creation control. Afterwards, in response to a call trigger for the shortcut cross-interface creation control, a first target shortcut of the target function is displayed on the first interface. The shortcut creation notification improves the secondary confirmation of shortcut creation and provides more shortcut creation options, thereby increasing the scope of application of shortcut creation.

[0324] Background processing of shortcut creation

[0325] The shortcut creation method requires not only front-end display but also background processing to achieve the creation of shortcuts. The background processing process of shortcut creation is described in detail below.

[0326] In one embodiment, the first terminal includes a simulator shortcut creation module and a client shortcut creation module.

[0327] Reference Fig.31 , step 330 includes:

[0328] Step 3110: In response to a shortcut creation trigger for a target function on a target application interface, the simulator shortcut creation module obtains shortcut information from the shortcut creation trigger and sends the shortcut information to the client shortcut creation module.

[0329] Step 3120: Create a first target shortcut based on the shortcut information through the client shortcut creation module, and display the first target shortcut on the first interface.

[0330] Step 3110 and step 3120 are described in detail below.

[0331] In step 3110, in response to a shortcut creation trigger for a target function on a target application interface, the simulator shortcut creation module obtains shortcut information from the shortcut creation trigger and sends the shortcut information to the client shortcut creation module.

[0332] The simulator shortcut creation module is adapted to the simulator, and is a module in the second terminal simulated by the simulator for processing shortcut creation. Correspondingly, the client shortcut creation module is adapted to the first terminal, and is a module in the first terminal for processing shortcut creation.

[0333] Reference Fig.32A , a simulator and a client are running on the first terminal. The simulator simulates the operating environment of the second terminal outside the first terminal. The results of running application 1, application 2... application N on the simulator interface actually represent the results of running application 1, application 2... application N on the second terminal. Assuming that the first terminal is a Windows computer and the second terminal is an Android phone, the simulator can be considered as the system of the simulated Android phone, and the client is the original Windows system on the first terminal. The Android system simulated by the simulator communicates with the Windows system through sockets.

[0334] The target application runs in the environment of the second terminal simulated by the simulator. In response to a shortcut creation trigger for the target function on the target application interface, the simulator shortcut creation module in the simulator first obtains the shortcut information from the shortcut creation trigger and sends the shortcut information to the client shortcut creation module.

[0335] The shortcut information refers to the shortcut information of the target function to be created, and includes the icon, name, and intent of the first target shortcut of the target function. Among them, intent is a mechanism for transmitting messages between different components, and the intent contained in the shortcut information refers to the subsequent operation generated by triggering the first target shortcut.

[0336] Reference Fig.32A In the simulator, if a shortcut is added to an application function, such as a target function of a target application, information corresponding to the added shortcut is sent from the simulator to the client. Specifically, the simulator shortcut creation module in the simulator sends the shortcut information to the client shortcut creation module of the client.

[0337] In step 3120, a first target shortcut is created based on the shortcut information through a client shortcut creation module, and the first target shortcut is displayed on the first interface.

[0338] The client shortcut creation module processes the received shortcut information to generate a first target shortcut, and then displays the first target shortcut on the first interface.

[0339] Reference Fig.32A When creating a shortcut, the client sends relevant information to the first interface to render the first interface, thereby displaying the first target shortcut on the first interface.

[0340] Reference Fig.32B In response to a shortcut creation trigger for a target function on a target application interface, the simulator shortcut creation module obtains shortcut information from the shortcut creation trigger and sends the shortcut information to the client shortcut creation module, so that the client shortcut creation module creates a first target shortcut based on the shortcut information and displays the first target shortcut on the first interface.

[0341] In the embodiment of the above steps 3110 and 3120, a simulator shortcut creation module and a client shortcut creation module are provided in the first terminal. In response to a shortcut creation trigger for a target function on a target application interface, the simulator shortcut creation module obtains shortcut information from the shortcut creation trigger and sends the shortcut information to the client shortcut creation module, so that the client shortcut creation module creates a first target shortcut based on the shortcut information and displays the first target shortcut on the first interface, thereby achieving the creation of the first target shortcut. The simulator shortcut creation module and the client shortcut creation module enhance the association between the target function and the first terminal, and are more conducive to reducing the overall access time cost.

[0342] The above is a general description of step 3110 and step 3120. Since step 3120 has been described in detail above, the specific implementation process of step 3110 will be described in detail below.

[0343] In step 3110, in response to a shortcut creation trigger for a target function on a target application interface, the simulator shortcut creation module obtains shortcut information from the shortcut creation trigger and sends the shortcut information to the client shortcut creation module.

[0344] In one embodiment, the first terminal further includes a simulator shortcut manager and a client shortcut manager.

[0345] Reference Fig.33 , step 3110 includes:

[0346] Step 3310: modify the routine of the simulator shortcut manager so that after obtaining the shortcut information from the shortcut creation trigger, the shortcut information is sent to the client shortcut manager through the simulator shortcut creation module;

[0347] Step 3320: Execute the routine to send the shortcut information to the client shortcut manager, and forward it to the client shortcut creation module through the client shortcut manager.

[0348] Step 3310 and step 3320 are described in detail below.

[0349] In step 3310, the routine of the simulator shortcut manager is modified so that after obtaining the shortcut information from the shortcut creation trigger, the shortcut information is sent to the client shortcut manager through the simulator shortcut creation module.

[0350] The simulator shortcut manager is specifically a simulator ShortCutManager. The simulator shortcut manager is a class used to manage application shortcuts in the system of the second terminal simulated by the simulator. It allows shortcuts to be created, updated, and deleted.

[0351] The client shortcut manager is specifically the client ShortCutManager. The client shortcut manager is a class in the first terminal system for managing application shortcuts, and allows shortcuts to be created, updated, and deleted.

[0352] The routine of the simulator shortcut manager is used to request the creation of a shortcut. The original simulator is a closed-loop management, and the shortcut corresponding to the target function is only displayed on the simulator interface. Therefore, executing the original routine will send the shortcut information to the simulator interface. Therefore, the disclosed embodiment changes the routine of the simulator shortcut manager to send the shortcut information to the client shortcut manager through the simulator shortcut creation module.

[0353] In step 3320, a routine is executed to send shortcut information to the client shortcut manager and forward it to the client shortcut creation module through the client shortcut manager.

[0354] After receiving the shortcut information, the client shortcut manager forwards the shortcut information to the client shortcut creation module.

[0355] Reference Fig.32BIn response to the shortcut creation trigger for the target function in the target application interface, the simulator shortcut manager, i.e., the simulator ShortCutManager, is first obtained. Afterwards, based on the information in the shortcut creation trigger, the shortcut information ShortCutInfo and the shortcut creation intention Intent are filled with parameters. The shortcut creation function requestPi nShortCut in the simulator shortcut manager is called, i.e., the routine. The routine includes two parameters, the shortcut information ShortCutInfo and the intention sending object IntentSender. The routine is changed, i.e., the intention sending object IntentSender is changed to the client shortcut manager. After the routine is changed, the simulator shortcut creation module ShortCutServi c is started. The simulator shortcut creation module converts the shortcut information ShortCutInfo and the shortcut creation intention Intent into shortcut information that is compatible with the simulator, and then the converted shortcut information is serialized in object notation (JavaScript Object Notation, Json), and sent to the client shortcut manager through socket communication.

[0356] The client shortcut manager first stores the shortcut information in Json format, and then forwards it to the client shortcut creation module. The client shortcut creation module creates a first target shortcut based on the shortcut information and displays the first target shortcut on the first interface. The creation of the first target shortcut is completed.

[0357] In the embodiment of the above-mentioned steps 3310 and 3320, the first terminal also includes a simulator shortcut manager and a client shortcut manager. The simulator shortcut manager is provided with a routine. By changing the routine, the shortcut information is sent to the client shortcut manager, and then forwarded to the client shortcut creation module through the client shortcut manager, so that the first target shortcut of the target function can be displayed on the first interface.

[0358] In one embodiment, after step 330, a notification of successful creation of the first target shortcut is displayed on the target application interface. The notification of successful creation of the first target shortcut is used to indicate that the first target shortcut is successfully displayed on the first interface.

[0359] Reference Fig.32BIf the first interface displays the first target shortcut, the client shortcut creation module sends a shortcut creation success message to the simulator shortcut creation module through socket communication, the simulator shortcut creation module broadcasts the received shortcut creation success message, the target application receives the broadcasted shortcut creation success message and displays it on the target application interface.

[0360] Triggering and background processing of the first target shortcut

[0361] The first interface displays a first target shortcut of the target function, and the first target shortcut can be clicked to trigger, and then background processing is performed based on the trigger operation, and a page of the target function is displayed.

[0362] In one embodiment, referring to Fig.34 After step 330, the shortcut creation method further includes:

[0363] Step 3410: In response to the invocation trigger of the first target shortcut, a target function page of the target function corresponding to the first target shortcut is displayed.

[0364] Step 3410 is described in detail below.

[0365] In step 3410 , in response to the invocation trigger of the first target shortcut, a target function page of the target function corresponding to the first target shortcut is displayed.

[0366] The first target shortcut corresponds to the target function, and the target function page is a specific page for executing the target function.

[0367] exist Fig.35A In the first interface shown, the simulator is in a closed state. At this time, calling to trigger the first target shortcut can display the target function page of the target function corresponding to the first target shortcut. The target function page is as follows: Fig.35B shown.

[0368] The calling trigger of the first target shortcut can be realized in a variety of ways, such as double-clicking, right-clicking a mouse, and keyboard shortcut light.

[0369] In the embodiment of the above-mentioned step 3410, when the first target shortcut of the target function is displayed on the first interface, in response to the call trigger of the first target shortcut, the target function page of the target function corresponding to the first target shortcut is displayed without opening the simulator, thereby realizing quick access to the target function, reducing the time cost of accessing the in-application function corresponding to the shortcut, and improving the opening reach rate of the simulator.

[0370] The above is a general description of step 3410. The specific implementation process of step 3410 is described in detail below.

[0371] In step 3410 , in response to the invocation trigger of the first target shortcut, a target function page of the target function corresponding to the first target shortcut is displayed.

[0372] In one embodiment, referring to Fig.36 , step 330 includes:

[0373] Step 3610: In response to a shortcut creation trigger for a target function during execution of the target function on a target application interface, execution of the target function is interrupted, and a first target shortcut to the target function is displayed on the first interface.

[0374] Correspondingly, step 3410 includes:

[0375] Step 3620: In response to the invocation trigger of the first target shortcut, display the target function page of the target function corresponding to the first target shortcut from the interruption position of the target function.

[0376] Step 3610 and step 3620 are described in detail below.

[0377] In step 3610, in response to a shortcut creation trigger for a target function during execution of the target function on a target application interface, execution of the target function is interrupted, and a first target shortcut to the target function is displayed on the first interface.

[0378] Reference Fig. 22 If episode XXXX1 is played to episode 3, 22 minutes and 46 seconds when the shortcut creation is triggered, the playback of episode XXXX1 will be interrupted, and the first target shortcut of the target function will be displayed on the first interface.

[0379] In step 3620, in response to the invocation trigger of the first target shortcut, the target function page of the target function corresponding to the first target shortcut is displayed from the interruption position of the target function.

[0380] In response to the invocation trigger of the first target shortcut, starting from the interruption position of the target function when the first target shortcut was previously created, a target function page of the target function corresponding to the first target shortcut is displayed.

[0381] Reference Fig.35A and Fig.35B , the interruption position is 22 minutes and 46 seconds into episode 3 of episode XXXX1, then in response to the call trigger of the first target shortcut, episode XXXX1 continues to be played from 22 minutes and 46 seconds into episode 3.

[0382] The embodiments of the above-mentioned steps 3610 and 3620 are triggered in response to the call of the first target shortcut, starting from the interruption position of the target function when the first target shortcut was previously created, and displaying the target function page of the target function corresponding to the first target shortcut, thereby improving the continuity of the execution of the target function and improving the execution effect of the target function.

[0383] In one embodiment, the first terminal further includes a simulator shortcut activation module and a client shortcut activation module.

[0384] Reference Fig.37 , step 3410 includes:

[0385] Step 3710: In response to a call trigger of the first target shortcut, the client shortcut startup module obtains access information from the call trigger and sends the access information to the simulator shortcut startup module;

[0386] Step 3720: Start the module through the simulator shortcut, and based on the access information, display the target function page of the target function corresponding to the first target shortcut.

[0387] Step 3710 and step 3720 are described in detail below.

[0388] In step 3710, in response to a call trigger of the first target shortcut, the client shortcut startup module obtains access information from the call trigger and sends the access information to the simulator shortcut startup module.

[0389] The simulator shortcut activation module is a module in the second terminal system simulated by the simulator for processing shortcut activation. Correspondingly, the client shortcut activation module is a module in the first terminal system for processing shortcut activation.

[0390] The access information is information corresponding to the first target shortcut, and the access information includes a simulator, a target application, and a target function corresponding to the first target shortcut.

[0391] Reference Fig.32A If a shortcut that triggers the first interface is called, the client shortcut startup module of the client can determine the access information based on the shortcut triggered by the call, and send the access information to the simulator, specifically, to the simulator shortcut startup module.

[0392] In step 3720, the simulator shortcut startup module is used to display a target function page of the target function corresponding to the first target shortcut based on the access information.

[0393] The simulator shortcut startup module can determine the target application and the target function corresponding to the access information based on the access information, and then display the target function page of the target function corresponding to the first target shortcut.

[0394] Reference Fig.38 In response to the call trigger of the first target shortcut, the client shortcut startup module obtains access information from the shortcut call trigger, and the access information is specifically the shortcut corresponding data. Fig.32B In the process, the client shortcut manager stores shortcut information. Therefore, according to the first target shortcut triggered by the call, the shortcut information stored in the client shortcut manager is searched to determine the shortcut information corresponding to the first target shortcut and obtain the access information. The client shortcut startup module sends the access information to the simulator shortcut startup module. The simulator shortcut startup module determines the shortcut information based on the access information. If the shortcut information contains data related to the target function, the target function page is opened and displayed. If the shortcut information does not contain data related to the target function, the target application page is opened. In addition, if the target function is invalid in the target application, for example, the drama XXXX1 is removed from the shelves, then the target application page can be opened or a notification of the invalidation of the target function can be displayed.

[0395] In the embodiment of the above steps 3710 and 3720, the first terminal includes a simulator shortcut startup module and a client shortcut startup module. In response to the call trigger of the first target shortcut, the client shortcut startup module obtains access information from the call trigger, and sends the access information to the simulator shortcut startup module, so that the simulator shortcut startup module displays the target function page of the target function corresponding to the first target shortcut based on the access information, so that the first target shortcut can be accurately started, the time cost of accessing the in-application function corresponding to the shortcut is reduced, and the opening reach rate of the simulator is improved.

[0396] The above is a general description of step 3710 and step 3720. Step 3710 has been described in detail above, and only the specific implementation process of step 3720 will be described in detail below.

[0397] In step 3720, the simulator shortcut startup module is used to display a target function page of the target function corresponding to the first target shortcut based on the access information.

[0398] In one embodiment, the access information includes the interruption position of the target function when the shortcut trigger is received.

[0399] Reference Fig.39 , step 3720 includes:

[0400] Step 3910: Start the module through the simulator shortcut, and display the target function page of the target function corresponding to the first target shortcut from the interruption position.

[0401] Step 3910 is described in detail below.

[0402] In step 3910, the simulator shortcut startup module is used to display the target function page of the target function corresponding to the first target shortcut from the interruption position.

[0403] The access information includes the interruption position of the target function when the shortcut trigger is received, so the simulator shortcut startup module can display the target function page of the target function corresponding to the first target shortcut from the interruption position.

[0404] The setting of the interruption position in the access information of the embodiment of step 3910 facilitates displaying the target function page of the target function corresponding to the first target shortcut from the interruption position, thereby improving the continuity of the target function execution and improving the execution effect of the target function.

[0405] It is to be understood that, although the steps in the above-mentioned flowcharts are sequentially displayed according to the characterization of arrows, these steps are not necessarily executed in sequence according to the order of arrow characterization. Unless there is a clear description in the present embodiment, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the above-mentioned flowcharts can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0406] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to the characteristics of the target object such as the target object attribute information or attribute information set, the permission or consent of the target object will be obtained first, and the collection, use and processing of these data will comply with relevant laws, regulations and standards. In addition, when the embodiment of the present application needs to obtain the attribute information of the target object, the separate permission or separate consent of the target object will be obtained through a pop-up window or jump to a confirmation page. After clearly obtaining the separate permission or separate consent of the target object, the necessary target object-related data used to enable the normal operation of the embodiment of the present application is obtained.

[0407] Description of the apparatus and device of the present disclosure

[0408] Fig.40This is a schematic diagram of the structure of a shortcut creation device provided in an embodiment of the present disclosure. The shortcut creation device 4000 includes:

[0409] A first response unit 4010, configured to display a simulator interface in response to a call trigger of the simulator on a first interface of the first terminal;

[0410] The second response unit 4020 is used to display the target application interface on the simulator interface in response to the call trigger of the target application on the simulation interface, where the target application is an application adapted to a second terminal of a type different from the first terminal;

[0411] The third responding unit 4030 is configured to display a first target shortcut of the target function on the first interface in response to a shortcut creation trigger for the target function on the target application interface.

[0412] Optionally, the simulator interface covers a portion of the first interface;

[0413] The third response unit 4030 is specifically used for:

[0414] On the target application interface, receiving a shortcut creation trigger for a target function of the target application interface;

[0415] While the simulator interface is displayed on the first interface, a first target shortcut of the target function is displayed on a portion of the first interface not occupied by the simulator interface.

[0416] Optionally, the third response unit 4030 is further configured to:

[0417] On the target application interface, receiving a target function entry trigger for the target function;

[0418] In response to a target function entry trigger, displaying a target function page of the target function, wherein the target function page has a shortcut creation control;

[0419] Receives shortcut creation triggers for shortcut creation controls.

[0420] Optionally, the first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon;

[0421] The third response unit 4030 is specifically used for:

[0422] In response to a shortcut creation trigger for a target function on a target application interface, if the target function includes a target function image, a first target shortcut icon is displayed as a composite image of the target function image and a simulator shortcut icon.

[0423] Optionally, the first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon;

[0424] The third response unit 4030 is specifically used for:

[0425] In response to a shortcut creation trigger for a target function on a target function application interface, if the target function does not include a target function image, a first target shortcut icon is displayed as a composite image of a target function text image corresponding to the target function and a simulator shortcut icon.

[0426] Optionally, the third response unit 4030 is specifically configured to:

[0427] In response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut for the target function is displayed on the first interface, and a second target shortcut for the target function is displayed on the simulator interface.

[0428] Optionally, the first target shortcut and the second target shortcut of the same target function have the same target attribute.

[0429] Optionally, the third response unit 4030 is specifically configured to:

[0430] On the first interface, a target area corresponding to the target application is displayed;

[0431] In the target area, the first target shortcut of the target function is displayed.

[0432] Optionally, the target function includes a first target function and a second target function, and the second target function belongs to the first target function;

[0433] The third response unit 4030 is further specifically configured to: display the first target shortcut of the second target function as having an associated mark with the first target shortcut of the first target function.

[0434] Optionally, the third response unit 4030 is further configured to:

[0435] In the target area, the target tree is displayed;

[0436] Displaying a first target shortcut of a first target function as a parent node of the target tree;

[0437] Display the first target shortcut to the second target function as a child node of the parent node.

[0438] Optionally, the third response unit 4030 is further configured to:

[0439] In response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut to the target function is displayed on a first interface based on a display attribute corresponding to a function type of the target function.

[0440] Optionally, the third response unit 4030 is further configured to:

[0441] During the process of executing the target function on the target application interface, receiving a shortcut creation trigger for the target function;

[0442] In response to a shortcut creation trigger, while displaying a first target shortcut of a target function on the first interface, an execution progress of the target function is displayed in association with the first target shortcut.

[0443] Optionally, the third response unit 4030 is further configured to:

[0444] In response to a shortcut creation trigger for a target function on a target application interface, multiple target shortcuts are displayed on a first interface, the multiple target shortcuts include a first target shortcut of the target function, and the multiple target shortcuts are sorted according to creation time of the multiple target shortcuts.

[0445] Optionally, the third response unit 4030 is further configured to:

[0446] In response to a shortcut creation trigger for a target function on a target application interface, displaying an animation of the target function being transferred to the first interface;

[0447] After the animation ends, the first target shortcut of the target function is displayed on the first interface.

[0448] Optionally, the third response unit 4030 is further configured to:

[0449] In response to a shortcut creation trigger for a target function on a target application interface, a first target shortcut to the target function is displayed on a first interface and, at the same time, the first target shortcut is displayed on a second interface of a second terminal bound to the first terminal.

[0450] Optionally, the third response unit 4030 is further configured to:

[0451] In response to a shortcut creation trigger for a target function on a target application interface, displaying a shortcut creation notification, wherein the shortcut creation notification includes a shortcut cross-interface creation control;

[0452] In response to a call trigger for a shortcut cross-interface creation control, a first target shortcut of a target function is displayed on a first interface.

[0453] Optionally, the first terminal includes a simulator shortcut creation module and a client shortcut creation module;

[0454] The third response unit 4030 is further specifically configured to:

[0455] By means of the simulator shortcut creation module, in response to a shortcut creation trigger for a target function on a target application interface, obtaining shortcut information from the shortcut creation trigger, and sending the shortcut information to the client shortcut creation module;

[0456] A first target shortcut is created based on the shortcut information through a client shortcut creation module, and the first target shortcut is displayed on a first interface.

[0457] Optionally, the first terminal further includes a simulator shortcut manager and a client shortcut manager;

[0458] The third response unit 4030 is further specifically configured to:

[0459] Change the routine of the simulator shortcut manager so that after obtaining the shortcut information from the shortcut creation trigger, the shortcut information is sent to the client shortcut manager through the simulator shortcut creation module;

[0460] A routine is executed to send shortcut information to the client shortcut manager and forward it to the client shortcut creation module through the client shortcut manager.

[0461] Optionally, the shortcut creation device 4000 further includes:

[0462] The fourth response unit is used to display a target function page of a target function corresponding to the first target shortcut in response to a call trigger of the first target shortcut.

[0463] Optionally, the third response unit 4030 is specifically used to: in response to a shortcut creation trigger for the target function during the execution of the target function on the target application interface, interrupt the execution of the target function, and display a first target shortcut of the target function on the first interface;

[0464] The fourth response unit is specifically configured to: in response to a call trigger of the first target shortcut, display a target function page of the target function corresponding to the first target shortcut from the interrupt position of the target function.

[0465] Optionally, the first terminal further includes a simulator shortcut startup module and a client shortcut startup module;

[0466] The fourth response unit is specifically used for:

[0467] By means of the client shortcut startup module, in response to a call trigger of the first target shortcut, access information is obtained from the call trigger, and the access information is sent to the simulator shortcut startup module;

[0468] The module is started through the simulator shortcut, and based on the access information, a target function page of the target function corresponding to the first target shortcut is displayed.

[0469] Optionally, the access information includes the interruption position of the target function when the shortcut creation trigger is received;

[0470] The fourth response unit is further specifically used for:

[0471] The module is started through the simulator shortcut, and based on the access information, a target function page of a target function corresponding to the first target shortcut is displayed, including:

[0472] The module is started through the simulator shortcut, and the target function page of the target function corresponding to the first target shortcut is displayed from the interruption position.

[0473] In addition, an embodiment of the present disclosure provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the shortcut creation method of the previous embodiment when executing the computer program. Specifically, the computer device can be set as a terminal, a server, etc.

[0474] Reference Fig.41 , Fig.41 4 is a block diagram of a structure when the computer device is a terminal 110. The terminal 110 includes: a radio frequency (RF) circuit 4110, a memory 4115, an input unit 4130, a display unit 4140, a sensor 4150, an audio circuit 4160, a wireless fidelity (Wi-Fi) module 4170, a processor 4180, and a power supply 4190. Those skilled in the art can understand that Fig.41 The structure of the terminal 110 shown does not constitute a limitation on a mobile phone or a computer, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0475] The RF circuit 4110 may be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information from the base station, it is sent to the processor 4180 for processing; in addition, the designed uplink data is sent to the base station.

[0476] The memory 4115 may be used to store software programs and modules. The processor 4180 executes various functional applications and data processing of the content terminal by running the software programs and modules stored in the memory 4115 .

[0477] The input unit 4130 may be used to receive input digital or character information and generate key signal input related to the setting and function control of the content terminal. Specifically, the input unit 4130 may include a touch panel 4131 and other input devices 4132.

[0478] The display unit 4140 may be used to display input information or provided information and various menus of the content terminal. The display unit 4140 may include a display panel 4141.

[0479] The audio circuit 4160, the speaker 4161, and the microphone 4162 may provide an audio interface.

[0480] In this embodiment, the processor 4180 included in the terminal 110 can execute the shortcut creation method of the previous embodiment.

[0481] The embodiments of the present disclosure can be applied to various scenarios, including but not limited to cross-terminal interaction and other scenarios.

[0482] Fig.42 1 is a block diagram of a structure when the computer device is a server. The server 140 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 4222 (for example, one or more processors) and memory 4232, and one or more storage media 4230 (for example, one or more mass storage devices) storing application programs 4242 or data 4244. Among them, the memory 4232 and the storage medium 4230 may be temporary storage or permanent storage. The program stored in the storage medium 4230 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the server. Furthermore, the central processing unit 4222 may be configured to communicate with the storage medium 4230 to execute a series of instruction operations in the storage medium 4230 on the server.

[0483] The server 140 may also include one or more power supplies 4226, one or more wired or wireless network interfaces 4250, one or more input and output interfaces 4258, and / or one or more operating systems 4241, such as Wi ndows Server™, Mac OS X™, Unix™, Li nux™, FreeBSD™, etc.

[0484] The central processor 4222 in the server 140 may be used to execute the shortcut creation method of the embodiment of the present disclosure.

[0485] The embodiments of the present disclosure also provide a computer-readable storage medium, which is used to store a computer program, and the computer program is used to execute the shortcut creation method of each of the above embodiments.

[0486] The embodiment of the present disclosure also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, so that the computer device executes and implements the shortcut creation method.

[0487] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0488] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present disclosure and the above-mentioned drawings are used to distinguish similar contents, 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 interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "comprises" and "comprising" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0489] It should be understood that in the present disclosure, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated content, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the associated content before and after is in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0490] It should be understood that in the description of the embodiments of the present disclosure, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to not include the number, and above, below, within, etc. are understood to include the number.

[0491] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0492] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0493] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0494] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0495] It should also be understood that the various implementations provided in the embodiments of the present disclosure can be combined arbitrarily to achieve different technical effects.

[0496] The above is a specific description of the implementation methods of the present disclosure, but the present disclosure is not limited to the above implementation methods. Technical personnel familiar with the art can also make various equivalent modifications or substitutions without violating the spirit of the present disclosure. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present disclosure.

Claims

1. A shortcut creation method, characterized in that: The shortcut creation method comprises: In response to a call trigger of the simulator on the first interface of the first terminal, displaying the simulator interface; In response to a call trigger of a target application on the simulator interface, displaying a target application interface on the simulator interface, wherein the target application is an application adapted to a second terminal of a type different from that of the first terminal; In response to a shortcut creation trigger for a target function on the target application interface, a first target shortcut for the target function is displayed on the first interface.

2. The shortcut creation method according to claim 1, characterized in that: The simulator interface covers a portion of the first interface; In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: On the target application interface, receiving the shortcut creation trigger for the target function of the target application interface; While the simulator interface is displayed on the first interface, the first target shortcut to the target function is displayed on a portion of the first interface not occupied by the simulator interface.

3. The shortcut creation method according to claim 2, characterized in that: The step of receiving, on the target application interface, the shortcut creation trigger for the target function of the target application interface includes: On the target application interface, receiving a target function entry trigger for the target function; In response to the target function entry trigger, displaying a target function page of the target function, wherein the target function page has a shortcut creation control; The shortcut creation trigger for the shortcut creation control is received.

4. The shortcut creation method according to claim 1, characterized in that: The first interface includes a simulator shortcut of the simulator, the simulator shortcut includes a simulator shortcut icon, and the first target shortcut includes a first target shortcut icon; In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: In response to the shortcut creation trigger for the target function on the target application interface, if the target function includes a target function image, the first target shortcut icon is displayed as a composite image of the target function image and the simulator shortcut icon.

5. The shortcut creation method according to claim 1, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: In response to the shortcut creation trigger for the target function on the target application interface, while displaying the first target shortcut of the target function on the first interface, a second target shortcut of the target function is displayed on the simulator interface.

6. The shortcut creation method according to claim 5, characterized in that: The first target shortcut and the second target shortcut of the same target function have the same target attribute.

7. The shortcut creation method according to claim 1, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: On the first interface, displaying a target area corresponding to the target application; The first target shortcut of the target function is displayed in the target area.

8. The shortcut creation method according to claim 7, characterized in that: The target function includes a first target function and a second target function, and the second target function belongs to the first target function; Displaying the first target shortcut of the target function in the target area includes: displaying the first target shortcut of the second target function to have an associated mark with the first target shortcut of the first target function.

9. The shortcut creation method according to claim 8, characterized in that: The step of displaying the first target shortcut of the second target function as having an associated mark with the first target shortcut of the first target function includes: In the target area, display a target tree; displaying the first target shortcut of the first target function as a parent node of the target tree; The first target shortcut to the second target function is displayed as a child node of the parent node.

10. The shortcut creation method according to claim 1, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: During execution of the target function on the target application interface, receiving a shortcut creation trigger for the target function; In response to the shortcut creation trigger, while displaying a first target shortcut of the target function on the first interface, an execution progress of the target function is displayed in association with the first target shortcut.

11. The shortcut creation method according to claim 1, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: In response to the shortcut creation trigger for the target function on the target application interface, multiple target shortcuts are displayed on the first interface, the multiple target shortcuts include the first target shortcut for the target function, and the multiple target shortcuts are sorted according to the creation time of the multiple target shortcuts.

12. The shortcut creation method according to claim 1, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: In response to the shortcut creation trigger for the target function on the target application interface, while displaying the first target shortcut of the target function on the first interface, the first target shortcut is displayed on the second interface of the second terminal bound to the first terminal.

13. The shortcut creation method according to claim 1, characterized in that: The first terminal includes a simulator shortcut creation module and a client shortcut creation module; In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: By the simulator shortcut creation module, in response to the shortcut creation trigger for the target function on the target application interface, obtaining shortcut information from the shortcut creation trigger, and sending the shortcut information to the client shortcut creation module; The first target shortcut is created based on the shortcut information through the client shortcut creation module, and the first target shortcut is displayed on the first interface.

14. The shortcut creation method according to claim 13, characterized in that: The first terminal further comprises a simulator shortcut manager and a client shortcut manager; The simulator shortcut creation module, in response to the shortcut creation trigger for the target function on the target application interface, obtains shortcut information from the shortcut creation trigger, and sends the shortcut information to the client shortcut creation module, including: Modify the routine of the simulator shortcut manager so that after acquiring the shortcut information from the shortcut creation trigger, the shortcut information is sent to the client shortcut manager through the simulator shortcut creation module; The routine is executed, so that the shortcut information is sent to the client shortcut manager and forwarded to the client shortcut creation module through the client shortcut manager.

15. The shortcut creation method according to claim 1, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, after displaying a first target shortcut of the target function on the first interface, the shortcut creation method further includes: In response to a call trigger of the first target shortcut, a target function page of the target function corresponding to the first target shortcut is displayed.

16. The shortcut creation method according to claim 15, characterized in that: In response to a shortcut creation trigger for a target function on the target application interface, displaying a first target shortcut of the target function on the first interface includes: in response to the shortcut creation trigger for the target function during the execution of the target function on the target application interface, interrupting the execution of the target function, and displaying the first target shortcut of the target function on the first interface; The displaying, in response to a call trigger to the first target shortcut, a target function page of the target function corresponding to the first target shortcut includes: in response to the call trigger to the first target shortcut, displaying the target function page of the target function corresponding to the first target shortcut from the interrupt position of the target function.

17. A shortcut creation device, characterized in that: The shortcut creation device comprises: A first response unit, configured to display a simulator interface in response to a call trigger of the simulator on a first interface of the first terminal; a second response unit, configured to display a target application interface on the simulator interface in response to a call trigger of a target application on the simulation interface, wherein the target application is an application adapted to a second terminal of a type different from that of the first terminal; The third response unit is used to display a first target shortcut of the target function on the first interface in response to a shortcut creation trigger for the target function on the target application interface.

18. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the shortcut creation method according to any one of claims 1 to 16 is implemented.

19. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the shortcut creation method according to any one of claims 1 to 16 is implemented.

20. A computer program product, comprising a computer program, wherein the computer program is read and executed by a processor of a computer device, so that the computer device executes the shortcut creation method according to any one of claims 1 to 16.

Images