Application interaction method and device, equipment and storage medium

Abstract

The invention discloses an application interaction method and device, equipment and a storage medium. Comprising the steps that an interaction desktop is displayed, shortcuts displayed on the interaction desktop comprise a mobile terminal shortcut and a local shortcut, and the mobile terminal shortcut is used for starting a mobile terminal application installed in a mobile terminal simulator; in response to a combination operation performed on the at least two shortcuts, displaying a target combination component; the at least two shortcuts comprise at least one mobile terminal shortcut, and the target combination component is used for uniformly starting target applications corresponding to the at least two shortcuts combined. The target combination component is generated for the plurality of shortcuts including the at least one mobile terminal shortcut, so that the target combination component can start the plurality of applications including the at least one mobile terminal application at one time, the operation steps and time cost of continuously starting the plurality of applications are effectively reduced, the application interaction efficiency is improved, and the user experience is improved. And the target combination component represents a plurality of application shortcuts, so that the application management efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer software technology, and more specifically, to an application interaction method, device, equipment and storage medium. Background Art

[0002] The simulator technology used to run mobile applications on personal computers aims to transplant the functions and environment of mobile operating systems to personal computers through virtualization and simulation technology. This process involves multiple levels of technology, from hardware virtualization to software simulation, as well as the allocation and management of system resources. The simulator can provide a user experience close to that of mobile devices and promote the integration of multi-platform software development and application ecology. For example, a common simulator technology is to run Android applications through the Windows system.

[0003] The Windows system downloads and installs the Android emulator, which creates a virtual Android operating environment on the personal computer. The environment simulates the hardware configuration of the Android device, such as the processor, memory, and storage space, through virtualization technology. This allows users to use input and output devices such as a mouse and keyboard on a personal computer to simulate the interaction of a mobile device. For example, users can use the built-in application store in the Android emulator to search and download the required Android applications, and install Android applications in the Android emulator.

[0004] After the application is successfully installed, the user can simulate the mobile device on the desktop operating system to start and use these mobile applications, such as using the simulation functions of keyboard mapping and mouse control. However, in the scenario of interactive use of mobile applications, personal computers usually need to switch to the simulator to start the mobile application, especially when it involves multi-application interactive operations including mobile applications, which requires more operations, resulting in low application interaction efficiency. Summary of the invention

[0005] The embodiments of the present application provide an application interaction method, apparatus, device and storage medium, which can effectively reduce the operation steps and time cost of starting multiple applications including at least one mobile application, and improve the application interaction efficiency.

[0006] According to one aspect of the present application, an application interaction method is provided, the method comprising: displaying an interactive desktop, the shortcuts displayed on the interactive desktop comprising mobile shortcuts and local shortcuts, the mobile shortcuts being used to start a mobile application installed in a mobile simulator; in response to a combination operation performed on at least two shortcuts, displaying a target combination component; wherein the at least two shortcuts include at least one mobile shortcut, and the target combination component is used to uniformly start a target application corresponding to the at least two shortcuts of the combination.

[0007] According to another aspect of the present application, an application interaction device is provided, which includes a desktop display module for displaying an interactive desktop, wherein the shortcuts displayed on the interactive desktop include mobile shortcuts and local shortcuts, and the mobile shortcuts are used to start a mobile application installed in a mobile simulator; a component display module for displaying a target combination component in response to a combination operation performed on at least two shortcuts; wherein the at least two shortcuts include at least one mobile shortcut, and the target combination component is used to uniformly start a target application corresponding to the at least two shortcuts of the combination.

[0008] Optionally, the component display module may include a single-category selection unit and a shortcut combination unit. The single-category selection unit is used to display multiple target shortcuts in a selected state in response to a selection operation on at least two mobile terminal shortcuts; the shortcut combination unit is used to display a target combination component in response to a combination operation on the multiple target shortcuts.

[0009] Optionally, the component display module may further include a multi-category selection unit and a shortcut combination unit. The multi-category selection unit is used to display multiple target shortcuts in a selected state in response to a selection operation on at least one mobile terminal shortcut and at least one local shortcut; the shortcut combination unit is used to display a target combination component in response to a combination operation on the multiple target shortcuts.

[0010] Optionally, the shortcut combination unit may include an option subunit and a component subunit. The option subunit is used to display a combination option menu in response to a combination operation performed on the plurality of target shortcuts; the component subunit is used to display a target combination component at a desktop position indicated by the target combination option in response to a selection operation performed on a target combination option in the combination option menu.

[0011] Optionally, the component sub-unit can be specifically used to: in response to a selection operation on a target combination option in the combination option menu, obtain application startup information corresponding to the multiple target shortcuts, and analyze each application startup information separately; when the analysis result indicates that the types of the multiple target applications include a mobile application type and a local application type, merge the application startup information corresponding to the mobile shortcut and the application startup information corresponding to the local shortcut, and create a target combination component based on the merged first merge information to display the target combination component at the desktop position indicated by the target combination option; when the analysis result indicates that the types of the multiple target applications are all mobile application types, merge the application startup information corresponding to each mobile shortcut, and create a target combination component based on the merged second merge information to display the target combination component at the desktop position indicated by the target combination option.

[0012] Optionally, the application interaction device may further include an information analysis module, a multi-class startup module, and a single-class startup module. The information analysis module is used to obtain application startup information corresponding to the target combination component in response to a trigger operation on the target combination component, and analyze the application startup information; the multi-class startup module is used to start at least one mobile application interface and at least one local application interface indicated by the application startup information when the analysis result indicates that the types of multiple target applications include mobile application types and local application types; the single-class startup module is used to start at least two mobile application interfaces indicated by the application startup information when the analysis result indicates that the types of multiple target applications are all mobile application types.

[0013] Optionally, the multi-type startup module may include a sequence acquisition unit, a parameter acquisition unit, and a sequential startup unit. The sequence acquisition unit is used to acquire the application startup sequence according to the application startup information; the parameter acquisition unit is used to sequentially acquire the application startup parameters corresponding to each target application based on the application startup sequence; the sequential startup unit is used to sequentially start each target application according to the parameter acquisition sequence of the application startup parameters, so as to display the mobile application interface corresponding to at least one mobile application and the local application interface corresponding to at least one local application.

[0014] Optionally, the application startup parameters include mobile application startup parameters and local application startup parameters, and the target application includes a target mobile terminal application and a target local application; the sequential startup unit may include: a sequence determination subunit and a multi-class startup subunit. The sequence determination subunit is used to determine the parameter acquisition sequence of the mobile application startup parameters and the local application startup parameters; the multi-class startup subunit is used to sequentially start the target mobile terminal application corresponding to each mobile application startup parameter or the target local application corresponding to each local application startup parameter according to the parameter acquisition sequence, so as to display the corresponding at least one mobile terminal application interface and at least one local application interface.

[0015] Optionally, the sequential starting unit may further include a theme determination subunit and a theme loading subunit. The theme determination subunit is used to determine a mobile application theme corresponding to at least one mobile terminal application interface; the theme loading subunit is used to send the mobile application theme to a local application to be loaded in at least one target local application, so that the local application to be loaded loads and displays a theme application interface matching the mobile application theme.

[0016] Optionally, the application startup parameter includes a mobile application startup parameter, and the target application includes a target mobile terminal application; the single-class startup module may include a simulation startup unit and an application startup unit. The simulation startup unit is used to start a mobile terminal simulator based on the simulator address in the mobile application startup parameter; the application startup unit is used to start the target mobile terminal application corresponding to each application resource identifier in the mobile application startup parameter through the mobile terminal simulator to display the mobile terminal application interface of each target mobile terminal application.

[0017] Optionally, the application startup unit may include a parameter analysis subunit, a mobile startup subunit, and an application display subunit. The parameter analysis subunit is used to analyze the mobile application startup parameters to obtain multiple application resource identifiers and application startup methods corresponding to each application resource identifier; the mobile startup subunit is used to start the corresponding target mobile terminal application based on each application resource identifier and the corresponding application startup method; the application display subunit is used to display the mobile terminal application interface corresponding to each target mobile terminal application.

[0018] Optionally, the mobile launch subunit can be specifically used to: obtain the application installation package corresponding to each application resource identifier; create an application running container according to the application startup method corresponding to each application resource identifier; run the corresponding application installation package in each application running container to start the target mobile application corresponding to each application installation package.

[0019] Optionally, the application interaction device may further include a simulation display module and a shortcut display module. The simulation display module is used to display a simulator interface, wherein the simulator interface includes startup components corresponding to multiple mobile terminal applications; and the shortcut display module is used to display a mobile terminal shortcut of the mobile terminal application corresponding to the target startup component on the interactive desktop in response to a shortcut generation operation performed on a target startup component among the multiple startup components.

[0020] Optionally, the application interaction device may further include a component reorganization module, which is used to display the reorganized combined component in response to a dragging operation of dragging other shortcuts to a component position corresponding to the target combined component.

[0021] Optionally, the application interaction device may further include a menu display module, an application setting module and a component update module. The menu display module is used to display a context menu corresponding to the target combination component in response to a setting operation performed on the target combination component; the application setting module is used to display an application setting interface in response to a selection operation performed on an application setting option in the context menu; and the component update module is used to update the target combination component in response to a removal operation performed on the target removal application in the removal application setting item of the application setting interface, and display the updated updated combination component.

[0022] Optionally, the application interaction device may further include a style selection module, an application statistics module, an icon generation module, and an icon replacement module. The style selection module is used to obtain the combination startup information corresponding to each target combination component on the interactive desktop in response to the selection operation of the display style change option in the context menu; the application statistics module is used to perform application statistics on the combination startup information corresponding to each target combination component, and determine the distinguishing application corresponding to each target combination component according to the statistical results; the icon generation module is used to generate the combination application icon of the corresponding target combination component based on the distinguishing application icon of each distinguishing application; the icon replacement module is used to display each target combination component after the icon is replaced.

[0023] According to another aspect of the present application, a computer-readable storage medium is provided, which stores a computer program, wherein the above-mentioned application interaction method is executed when the computer program is executed by a processor.

[0024] According to another aspect of the present application, a computer device is provided. The computer device includes a processor and a memory. The memory stores a computer program. When the computer program is called by the processor, the above-mentioned application interaction method is executed.

[0025] According to another aspect of the present application, a computer program product is provided, which includes a computer program stored in a storage medium; a processor of a computer device reads the computer program from the storage medium, and the processor executes the computer program, so that the computer device executes the above-mentioned application interaction method.

[0026] The present application can display an interactive desktop, and the shortcuts displayed on the interactive desktop may include mobile terminal shortcuts and local shortcuts, and the mobile terminal shortcuts are used to start the mobile terminal application installed in the mobile terminal simulator. Further, in response to the combination operation of at least two shortcuts, a target combination component can be displayed, wherein at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target application corresponding to the at least two shortcuts of the combination. In this way, by generating a target combination component for multiple shortcuts including at least one mobile terminal shortcut, the target combination component can open multiple applications including at least one mobile terminal application at one time. For scenarios where multiple applications need to be used to perform multiple tasks, especially cross-application scenarios between mobile terminal applications and local applications, it is possible to uniformly open multiple applications, maintain task continuity, and avoid the interaction burden of service objects opening different applications. Therefore, the operation steps and time cost of starting multiple applications including at least one mobile terminal application are effectively reduced, and the user interaction experience and application interaction efficiency are improved. In addition, by combining multiple shortcuts, only one target combination component is needed on the interactive desktop to represent multiple applications, reducing the visual confusion caused by multiple independent shortcuts, helping service objects find the required set of applications more quickly, and improving application interaction efficiency while also improving application management efficiency.

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

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0029] Figure 1 A schematic diagram of a system architecture provided in an embodiment of the present application is shown.

[0030] Figure 2A schematic diagram of system deployment provided in an embodiment of the present application is shown.

[0031] Figure 3 A schematic diagram of the main interface of a simulator provided in an embodiment of the present application is shown.

[0032] Figure 4 A schematic diagram of a shortcut to a mobile application provided in an embodiment of the present application is shown.

[0033] Figure 5 A schematic diagram of combined operations of a mobile terminal shortcut provided in an embodiment of the present application is shown.

[0034] Figure 6 A schematic diagram of an interactive desktop combination of a mobile terminal shortcut provided in an embodiment of the present application is shown.

[0035] Figure 7 A flow chart of an application interaction method provided in an embodiment of the present application is shown.

[0036] Figure 8 A desktop schematic diagram of an interactive desktop provided in an embodiment of the present application is shown.

[0037] Fig. 9 A schematic diagram of selecting a single-type shortcut provided in an embodiment of the present application is shown.

[0038] Fig.10 A schematic diagram of selecting a start menu combination option provided in an embodiment of the present application is shown.

[0039] Fig.11 A schematic diagram of a start menu of a target combination component provided in an embodiment of the present application is shown.

[0040] Fig.12 A task bar schematic diagram of a target combination component provided in an embodiment of the present application is shown.

[0041] Fig.13 A schematic diagram of selecting multiple types of shortcuts provided in an embodiment of the present application is shown.

[0042] Fig.14 A schematic diagram of selecting a dock combination option provided in an embodiment of the present application is shown.

[0043] Fig.15 A schematic diagram of a program dock of a target combination component provided in an embodiment of the present application is shown.

[0044] Fig.16 A schematic diagram of a shortcut to a target combination component provided in an embodiment of the present application is shown.

[0045] Fig.17A schematic diagram of dragging a shortcut combination provided in an embodiment of the present application is shown.

[0046] Fig.18 A schematic diagram of a reorganization shortcut provided in an embodiment of the present application is shown.

[0047] Fig.19 A schematic diagram of a context menu of a target combination component provided in an embodiment of the present application is shown.

[0048] Fig. 20 A schematic diagram of an interface for application settings provided in an embodiment of the present application is shown.

[0049] Fig.21 A component schematic diagram of an update combination component provided in an embodiment of the present application is shown.

[0050] Fig. 22 An icon schematic diagram of a plurality of target combination components provided in an embodiment of the present application is shown.

[0051] Fig.23 A schematic diagram showing the differences between multiple target combination components provided in an embodiment of the present application is shown.

[0052] Fig.24 A flow chart of another application interaction method provided in an embodiment of the present application is shown.

[0053] Fig.25 A schematic diagram of an interface of a mobile terminal simulator provided in an embodiment of the present application is shown.

[0054] Fig.26 A schematic diagram of selecting a target startup component provided in an embodiment of the present application is shown.

[0055] Fig. 27 A desktop display schematic diagram of a mobile terminal shortcut provided in an embodiment of the present application is shown.

[0056] Fig.28 A schematic diagram of a multi-mobile application startup process provided in an embodiment of the present application is shown.

[0057] Fig.29 It is a module block diagram of an application interaction device provided in an embodiment of the present application.

[0058] Fig.30 It is a module block diagram of a computer device provided in an embodiment of the present application.

[0059] Fig.31 It is a module block diagram of a computer-readable storage medium provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The implementation methods described with reference to the drawings are exemplary and are only used to explain the present application, and cannot be understood as limitations on the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present application.

[0061] In some processes described in the specification, claims and the above drawings, multiple steps appearing in a specific order are included, but it should be clearly understood that these steps may not be executed in the order in which they appear in this document or may be executed in parallel. The step numbers are only used to distinguish different steps, and the numbers themselves do not represent any execution order. In addition, the descriptions such as "first", "second" or "target" in this document are used to distinguish similar objects, and are not necessarily used to describe a specific order, sequence or quantity.

[0062] It is worth noting that in the specific implementation of the present application, it involves relevant data such as application startup information. When the above embodiments of the present application are applied to specific products or technologies, it is necessary to obtain the permission or consent of the object, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards. For example, when the embodiment of the present application needs to obtain application startup information, a separate permission or separate consent for the application startup information can be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining a separate permission or separate consent, the necessary relevant data for enabling the normal operation of the embodiment of the present application can be obtained.

[0063] The simulator (Emulator) running on the desktop operating system involved in this application, that is, the mobile simulator, is a software tool designed to simulate the hardware and operating system environment of a mobile device so that users can experience and test mobile applications on a computer. In addition to developers, ordinary users can also use this type of simulator to run mobile applications and experience their functions without actually owning a mobile device. Among them, a mobile device may refer to a device that can be operated portablely without relying on a fixed power supply or connection, such as a laptop, a smart phone, a tablet computer, a car terminal, etc., and a mobile application refers to a software application that can run on a mobile device. Mobile applications are usually developed according to the operating systems of different mobile devices (such as iOS, Windows Phone, and Android, etc.), and can be downloaded and installed through the application store in the mobile device. For example, users can use simulators in a desktop environment to try out newly released applications, games, or services to understand their operations and interfaces. This provides a convenient solution for users who temporarily cannot access real devices or want to test the functions of applications on a large screen. This simulator can simulate various device configurations, screen sizes, and resolutions, providing a close-to-real mobile experience, while enabling seamless application trials, functional verification, and user experience evaluation.

[0064] At present, in the relevant technical framework, the simulator on the PC (Personal Computer) device is usually designed to provide an operating environment close to the native mobile device, so as to facilitate the daily use or development and testing of mobile applications on the PC device. However, these simulators do not provide a mechanism that enables users to directly start multiple applications including at least one mobile application on the PC device, but usually need to switch to the simulator to start the mobile application. In addition, the existing technical solutions focus more on starting the PC application on the PC device itself, while ignoring the integration and interaction between the desktop environment of the PC device and the simulator, which brings inconvenience to users when using the simulator.

[0065] For example, a game player downloads a mobile simulator from the simulator's official website and completes the installation on the desktop operating system of a desktop computer. After the installation is complete, the game player starts the mobile simulator and visits the app store on the mobile simulator to download a mobile game, that is, a game software that usually runs on a mobile phone. Due to personal habits, the game player likes to look for game strategies and watch live games while playing games. For this reason, before playing the game each time, the game player needs to open the game application on the mobile simulator first, then open the content sharing application for looking for game strategies, and finally open the video application for watching live games. This frequent launch of multiple mobile applications on the mobile simulator brings a very cumbersome interactive experience to the game player.

[0066] It can be seen from the above examples that the relevant technology usually requires users to operate inside the simulator, such as starting the application through the simulator, and it is impossible to start multiple applications at one time. In particular, in the scenario of using the simulator for multi-tasking, the function usability of the simulator is poor. In addition, when using mobile applications, users need to frequently switch windows or interfaces between the desktop operating system and the mobile simulator, which increases the complexity of the operation. This operation process is not intuitive enough and easily causes interaction confusion. In short, the relevant technology cannot start multiple applications including mobile applications at one time on the desktop operating system, which brings many inconveniences to the user experience, especially the application interaction operation in the scenario of using multiple applications to perform multiple tasks. In order to solve the above problems, the inventor has proposed an application interaction method provided by an embodiment of the present application after research. The following is a description of the system implementation environment of the above method involved in the present application and the related application scenarios.

[0067] See also Figure 1 , Figure 1 A schematic diagram of a system architecture is shown. The application interaction method provided in this application can be applied in the system 100. Figure 1 As shown, the system 100 includes a server 110 and a personal computer 120, the server 110 and the personal computer 120 are connected to each other through a network, and the personal computer 120 also includes a simulator 121 installed thereon. The simulator 121 simulates the operating environment of the mobile device on the personal computer 120 by simulating the hardware and operating system of the mobile device, allowing the user to use the mobile application without actually owning the mobile device. The simulator 121 can be a Host-Guest architecture to create a virtual mobile operating environment in a collaborative manner.

[0068] Exemplarily, the simulator 121 may include a host and a guest. The host refers to the software of the simulator 121 running on the personal computer 120, as well as the hardware abstraction layer, operating system, and user interface components that are compatible with it. The host is responsible for creating and managing the virtual guest, and provides a series of tools and interfaces so that the user can interact with the guest. In the embodiment of the present application, the host is a personal computer software implemented based on the operating system of the personal computer 120. The guest refers to the operating environment of the virtual mobile device created by the host on the personal computer 120. Users can install and run mobile applications in this environment and perform various operations and experiences.

[0069] Among them, personal computer 120 is an entity that requests services or resources from server 110. The entity has a desktop operating system, such as Windows, macOS or Linux, etc. These desktop operating systems provide an environment that supports the operation of simulators, are compatible with various simulator software, and can directly perform human-computer interaction. Server 110 refers to an entity that provides services or resources, is responsible for processing requests from personal computer 120, and returns corresponding data or services. The server usually includes business logic, database management and other background processing functions. Server 110 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (Content Delivery Network, CDN), blockchains, and big data and artificial intelligence platforms.

[0070] It should be noted that Figure 1 It is only a schematic diagram of a system architecture provided in the embodiment of the present application. The system architecture and application scenarios described in the embodiment of the present application are intended to more clearly illustrate the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. Figure 1 Only one personal computer is shown in the figure, but in different embodiments there may be more personal computers accessing the server.

[0071] See also Figure 2 , Figure 2 Schematic diagram of system deployment is shown. For example, the application interaction method provided in the embodiment of the present application can also be deployed in Figure 2 In the system of C / S (Client / Server) architecture shown in FIG. , the system may include a server, a gateway, the Internet, and computer equipment.

[0072] A server is a computer system that can provide certain services to the server side. Compared with ordinary computer equipment, servers have higher requirements in terms of stability, security, and performance. Figure 2 As shown, the server 210 can be a high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of a high-performance computer (e.g., a virtual machine), a combination of portions of multiple high-performance computers (e.g., virtual machines), etc.

[0073] A gateway is also called an internetwork connector or a protocol converter. Figure 2 As shown, gateway 220 realizes network interconnection at the transport layer through Internet 230, and is a computer system or device that acts as a conversion. The gateway 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 can also provide filtering and security functions.

[0074] Computer devices can send requests to servers to access or use resources, data or services on the server. Figure 2 As shown, the computer device may include a laptop computer 240a, a desktop computer 240b, an intelligent service terminal 240c, a tablet computer (not shown), etc. In addition, it may be a single computer device or a collection of multiple computer devices.

[0075] Computer devices can communicate with the Internet in wired or wireless ways to exchange data. Figure 2 As shown, the laptop computer 240a can communicate with the Internet 230 through the wireless router 250. For another example, the message sent by the desktop computer 240b to the server 210 can be transmitted to the corresponding server 210 through the gateway 220. The message sent by the server 210 to the computer device can also be transmitted to the corresponding desktop computer 240b through the gateway 220.

[0076] As an implementation method, the application interaction method provided in the present application can be implemented in part on a server and in part on a computer device. For example, an application service provider provides a mobile terminal simulator and a mobile terminal application download service. The user can download the installation package of the mobile terminal simulator from the server 210 of the application service provider through the Internet 230 on a desktop computer 240b (i.e., a computer device), and then install the mobile terminal simulator on the desktop computer 240b. The user can open the mobile terminal simulator and download and install the required mobile terminal application in the application store of the mobile terminal simulator. In this way, the user can use the installed mobile terminal application through the mobile terminal simulator on the desktop operating system of the desktop computer 240b.

[0077] It should be noted that Figure 2 This is only a schematic diagram of a system deployment provided by the embodiment of the present application. The system deployment scheme described in the embodiment of the present application is only to more clearly illustrate the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided by the embodiment of the present application. For example, a computer device can generally refer to one of multiple devices. This embodiment only refers to Figure 2 The three computer devices (laptop computer 240a, desktop computer 240b, and intelligent service terminal 240c) shown in the figure are used as examples. A person skilled in the art will appreciate that, with the evolution of system deployment solutions, the technical solutions provided in the embodiments of the present invention are also applicable to similar technical problems.

[0078] The application interaction method provided in this application can be applied in various scenarios, for example, Figure 3 to Figure 4 The shortcut creation scenario shown, Figure 5 to Figure 6 The multi-application launch scenario shown, etc.

[0079] (1) Create a shortcut scene.

[0080] Usually, if you want to start a mobile application on the PC, you first find the mobile simulator on the interactive desktop of the PC and open the mobile simulator. Then the simulator main interface of the mobile simulator will be displayed on the interactive desktop of the PC. Then you need to find the icon of the mobile application you want to use on the simulator main interface, and usually click the icon to open the corresponding mobile application. According to the relevant technology, the interactive steps of using mobile applications through the mobile simulator on the PC interactive desktop operating system, the operation of using mobile applications on the interactive desktop operating system is limited to the implementation in the main interface of the mobile simulator. The entire interactive steps are cumbersome and complicated. In addition, the operation of using mobile applications on the interactive desktop operating system is different from the operation of the interactive desktop operating system application, which does not conform to the normal operating habits of the interactive desktop operating system users, thus affecting the user experience.

[0081] The application interaction method provided in this application can provide an interactive method for directly launching a mobile application on an interactive desktop operating system. It is not necessary to first open a mobile simulator and then open the mobile application in the main interface of the mobile simulator, thereby improving the user experience. For example, Figure 3 As shown in the main interface diagram of the simulator, the user can right-click the icon corresponding to the mobile application E on the main interface of the mobile simulator, and then the main interface can display the corresponding context menu. The context menu displays two menu options: Generate shortcut and Generate QR code. Generate shortcut means that this option is used to instruct the interactive desktop operating system to generate a shortcut corresponding to the mobile application E on the interactive desktop. When the user clicks the menu option of Generate shortcut, as shown in Figure 4 The schematic diagram of the shortcut of the mobile terminal application shown in FIG. 1 shows the interactive desktop, and the shortcut of the corresponding mobile terminal application E is displayed. In this way, the mobile terminal application E can be directly opened by double-clicking the shortcut of the mobile terminal application E on the interactive desktop.

[0082] (2) Multiple application startup scenarios.

[0083] Considering user habits or some multi-tasking scenarios, it is necessary to open multiple mobile applications at one time on the interactive desktop operating system. For example, before playing each game, a certain game player needs to open the game application on the mobile simulator first, then open the content sharing application for finding game strategies, and finally open the video application for watching the game live. This operation of frequently launching multiple mobile applications on the mobile simulator brings a very cumbersome interactive experience to the game player. To this end, the application interaction method provided in this application can be used to solve the problem of cumbersome interactive experience.

[0084] For example, Figure 5 The schematic diagram of the combined operation of the mobile terminal shortcuts is shown. The user can press and hold the left mouse button and drag to draw a rectangular area containing the desired combined shortcuts. When the user releases the left mouse button, all shortcuts of mobile application E and mobile application F within this rectangular area are selected. Furthermore, by right-clicking the rectangular area, the main interface can display a corresponding context menu, which displays two menu options: Combine shortcuts and Delete shortcuts, where the combined shortcut means that this option is used to instruct the interactive desktop operating system to combine the shortcuts of the selected mobile terminal applications into one shortcut. When the user clicks on the menu option of the combined shortcut, such as Figure 6 The interactive desktop combination diagram of the mobile terminal shortcuts shown in the figure shows the combined shortcuts corresponding to the mobile terminal application E and the mobile terminal application F. In this way, the user can directly open the mobile terminal application E and the mobile terminal application F through the combined shortcuts on the interactive desktop.

[0085] It should be noted that Figures 3 to 6 These are only two schematic diagrams of application scenarios provided by the embodiments of the present application. The application scenarios described in the embodiments of the present application are only for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. The application interaction method proposed in the present application can also be used in other interaction scenarios where there are shortcuts to use mobile applications on desktop operating systems. It is known to those of ordinary skill in the art that, with the evolution of application scenarios, the technical solutions provided by the embodiments of the present invention are also applicable to similar technical problems.

[0086] According to an embodiment of the present application, an application interaction method is provided. The application interaction method can be executed by a computer device (such as a desktop computer, a laptop computer or other terminal device with certain processing capabilities, etc.), and the computer device has at least storage, calculation and communication functions. Figure 7 FIG. 2 shows a flow chart of the application interaction method provided in this embodiment. Figure 7 As shown, the application interaction method may specifically include:

[0087] Step 110: Display the interactive desktop.

[0088] Creating a shortcut of a mobile application in a mobile simulator on the desktop of a desktop operating system allows users to directly launch the mobile application from the desktop, avoiding the tedious steps of searching for the application through the mobile simulator each time, thereby saving operation time. Considering that in actual application scenarios, there are situations where users need to launch multiple related applications together, this application proposes a method for combining multiple shortcuts including mobile shortcuts to improve the efficiency of application interaction.

[0089] In the embodiment of the present application, the interactive desktop refers to the main interface of the graphical user interface (GUI) of the desktop operating system, and the interactive desktop provides a basic environment for users to interact with the desktop operating system. Among them, the desktop operating system (Desktop Operating System) refers to an operating system for personal computers (PCs) such as desktops and laptops, such as Windows, macOS, and Linux.

[0090] For different types of desktop operating systems, the display styles of the interactive desktop may be different. For example, the Windows desktop environment is the main one, including the taskbar and start menu, etc.; the macOS desktop environment is the main one, including the program dock and menu bar, etc.; the Linux desktop environment is the main one, and the desktop environment is diverse, such as GNOME, KDE Plasma, XFCE, etc. However, desktop shortcuts can be displayed on the interactive desktop corresponding to each type of desktop operating system.

[0091] A desktop shortcut is an icon displayed on the interactive desktop of a desktop operating system. Users can access an application, file, folder, or URL by clicking on the shortcut. A shortcut is essentially a reference to a resource, not the resource itself. For example, a shortcut in a Windows operating system corresponds to a lnk file, which contains a path to the target resource and some additional information. When a user double-clicks the lnk file (i.e., shortcut), Windows will open the target resource according to the path stored in the lnk file. It can greatly simplify the user's interactive operations and reduce the steps required for the user to open an application or file each time. In an embodiment of the present application, the shortcuts displayed on the interactive desktop may include mobile shortcuts and local shortcuts.

[0092] See also Figure 8 , Figure 8 A desktop schematic diagram of an interactive desktop is shown, in which a local shortcut is used to start a PC application installed locally on a personal computer, and a mobile shortcut is used to start a mobile application installed in a mobile simulator. Exemplarily, a mobile shortcut can be generated on an interactive desktop by a mobile application installed in a mobile simulator. The mobile simulator is a local application installed in the desktop operating system corresponding to the interactive desktop. The mobile simulator refers to a simulator that enables mobile applications to run on a desktop operating system by simulating a mobile operating system and a hardware environment. In an embodiment of the present application, the mobile operating system may include Android, iOS, HarmonyOS, etc., which are not limited here.

[0093] Step 120: In response to a combination operation performed on at least two shortcuts, display a target combination component.

[0094] In order to implement a method for combining multiple shortcuts including mobile shortcuts, at least two shortcuts to be combined include at least one mobile shortcut, wherein the target combination component is used to uniformly start the target application corresponding to the at least two shortcuts of the combination. It should be noted that the target combination component is implemented based on computing programming technology and is a virtual component (also understood as a control) with a visual application function, which facilitates human-computer interaction between users and computer devices. The display form and interaction method of the virtual component can be personalized according to the interaction scenario, which is not limited here. For example, the target combination component can be displayed as a shortcut, or as an application icon in the start menu, or as an application icon in the program dock, etc.

[0095] In some embodiments, the combination of multiple shortcuts on the interactive desktop may be a combination of multiple mobile terminal shortcuts, so that the user can open multiple mobile terminal applications at one time. It may also be a combination of mobile terminal shortcuts and local shortcuts, so that the user can open multiple different types of applications at one time, including mobile terminal applications and local applications.

[0096] As an implementation mode, in response to a selection operation on at least two mobile terminal shortcuts, multiple target shortcuts in a selected state may be displayed, and further, in response to a combination operation on the multiple target shortcuts, a target combination component may be displayed.

[0097] As another implementation, in response to a selection operation on at least one mobile shortcut and at least one local shortcut, multiple target shortcuts in a selected state may be displayed, and further, in response to a combination operation on the multiple target shortcuts, a target combination component may be displayed.

[0098] The selection operation for shortcuts refers to the human-computer interaction initiated by the user in order to select shortcuts to be combined on the interactive desktop, which may include multiple selection and dragging operations. The combination operation refers to the human-computer interaction initiated by the user in order to combine multiple selected shortcuts, which may include right-click and long press operations. Specifically, in response to the combination operation on multiple target shortcuts, a combination option menu may be displayed, and in response to the selection operation on the target combination option in the combination option menu, the target combination component may be displayed at the desktop position indicated by the target combination option.

[0099] The selection operation for the combination option menu refers to the human-computer interaction initiated by the user in order to generate a target combination component at a specified desktop location on the interactive desktop, which may include single-click and other operation modes. The combination option menu may be a context menu for providing operation options related to the currently selected object, and it may dynamically display different options according to the object selected by the user or the current interface state. For example, the combination options in the combination option menu may be "generate shortcut", "generate taskbar icon", "generate dock icon", etc.

[0100] For example, Fig. 9As shown in the schematic diagram of selecting a single-type shortcut, in the Windows operating system, the user can select discontinuous shortcuts on the interactive desktop by holding down the "Ctrl" key and clicking the mouse (i.e., a selection operation in a multiple-selection manner). Then, in response to the selection operation in the multiple-selection manner, two target shortcuts in a selected state are displayed: a shortcut to mobile application A and a shortcut to mobile application B. Further, the user right-clicks the target shortcut (i.e., a combination operation in a single-click manner). In response to the combination operation in the single-click manner, as shown in FIG. Fig.10 The schematic diagram of the selection of the start menu combination option shown in FIG. 1 shows the combination option menu. Then, the user can left-click (i.e., perform a single-click selection operation) on the "Generate Start Menu Icon" in the combination option menu. In response to the single-click selection operation, Fig.11 The schematic diagram of the start menu of the target combination component shown in FIG. 1 displays the target combination component on the start menu of the interactive desktop, that is, generates and displays the start menu application icon. Fig.12 The taskbar diagram of the target composite component shown can also display the target composite component on the taskbar of the interactive desktop in response to the user left-clicking "Generate Taskbar Icon" in the composite option menu, that is, generating and displaying a taskbar application icon.

[0101] For example, Fig.13 In the schematic diagram of selecting multiple types of shortcuts shown in the figure, under the macOS operating system, the user selects three consecutive target shortcuts on the interactive desktop by dragging, that is, clicking and holding a certain position on the interactive desktop and moving the mouse while holding it, and then releasing it, including shortcuts corresponding to the mobile application C, the local application X, and the local application Y. Furthermore, the user can right-click the target shortcut (i.e., a combination operation of a single-click method), and in response to the combination operation of the single-click method, Fig.14 The schematic diagram of selecting the combined options of the program dock shown in FIG. generates and displays a combined options menu, and then the user can left-click (i.e., a single-click selection operation) on "Generate Program Dock Icon" in the combined options menu, and in response to the single-click selection operation, as shown in FIG. Fig.15 The target combination component is shown in the program dock schematic diagram, and the target combination component is displayed on the program dock of the interactive desktop, that is, the program dock application icon is generated and displayed. Fig.16 The shortcut diagram of the target composite component shown can also generate and display the target composite component, ie, the composite shortcut, on the interactive desktop in response to the user left-clicking "Generate Shortcut" in the composite option menu.

[0102] In an embodiment of the present application, the combination of multiple shortcuts including mobile application types can be a combination of multiple mobile shortcuts, or a combination of mobile shortcuts and local shortcuts. Considering that there are large differences in resource management methods corresponding to different types of shortcuts, when combining different types of shortcuts, it is necessary to adopt an adaptive combination method to correctly combine shortcuts to meet different user needs. To this end, first, it is possible to determine the types of target applications corresponding to the multiple target shortcuts selected by the user. If there are both mobile application types and local application types, the shortcuts can be combined based on the application startup information of the mobile shortcut and the application startup information of the local shortcut. If there are only mobile application types, the shortcuts can be combined based on the application startup information of each mobile shortcut.

[0103] As an implementation manner, in response to a selection operation on a target combination option in the combination option menu, application startup information corresponding to multiple target shortcuts may be obtained, and further, each application startup information may be analyzed separately.

[0104] In an embodiment of the present application, the application startup information refers to a format file corresponding to a shortcut, for example, a lnk file under a Windows operating system. The format file can be regarded as a pointer to a target object (such as a file, folder, or application, etc.). In a desktop operating system, a user can quickly access the target object by clicking a shortcut on the interactive desktop, without having to access the target object in the form of opening a folder multiple times in a row according to the storage location of the target object. For example, a lnk file stores information such as a target path, startup parameters, and a working directory. Among them, the target path is used to point to the absolute path of the target object; if the target is an executable file, the startup parameters are used to pass command line parameters at startup. For example, in a macOS operating system, a format file can be an alias (Alias) for a link to a file, folder, or application. The following will explain the generation process of the target combination component using a Windows desktop operating system and an Android mobile application.

[0105] Exemplarily, after the user clicks the target combination option in the combination option menu, the lnk file corresponding to each target shortcut can be obtained, and each lnk file can be analyzed separately, and the target application corresponding to each target shortcut can be determined based on the analysis results, whether it is a mobile application or a local application. For example, the target path in the lnk file is obtained to check whether the target path points to the mobile simulator. If the target path points to the mobile simulator, it means that the target shortcut corresponding to the lnk file is a mobile shortcut for opening the mobile simulator to run the mobile application, that is, the target application corresponding to the lnk file is a mobile application. If the target path does not point to the mobile simulator, it means that the target shortcut corresponding to the lnk file is a local shortcut, that is, the target application corresponding to the lnk file is a local application. In this way, it is possible to analyze what types of target applications correspond to the multiple target shortcuts selected by the user.

[0106] When the analysis results indicate that the types of multiple target applications include mobile application types and local application types, the application startup information corresponding to the mobile shortcut and the application startup information corresponding to the local shortcut can be merged. Furthermore, a target combination component can be created based on the merged first merged information to display the target combination component at the desktop location indicated by the target combination option.

[0107] Exemplarily, the application startup information corresponding to the mobile terminal shortcut and the local shortcut can be merged based on a batch processing method. For example, the lnk file corresponding to each mobile terminal shortcut is obtained, and the target path of the corresponding target application is extracted from each lnk file. At the same time, the lnk file corresponding to each local shortcut is obtained, and the target path of the corresponding target application is extracted from each lnk file. Further, the target path corresponding to each mobile terminal shortcut and the target path corresponding to each local shortcut are written into a batch file (.bat), that is, the first merged information, and then a target combination component is created based on the batch file to display the target combination component at the desktop position indicated by the target combination option.

[0108] Considering the resource utilization of computer devices, the target path corresponding to each target application can also be written into a batch file based on the order of computing resource sizes of target applications corresponding to different target shortcuts. For example, in a batch file, the target path corresponding to each target application is written in the order from large to small computing resource requirements. In this way, when multiple target applications are started, target applications that consume large computing resources can be started first to avoid excessive system load.

[0109] When the analysis result indicates that the types of multiple target applications are all mobile application types, the application startup information corresponding to each mobile shortcut is merged, and a target combination component is created based on the merged second merged information to display the target combination component at the desktop location indicated by the target combination option.

[0110] Exemplarily, unlike local shortcuts, the target path (i.e., lnk address) in the lnk file corresponding to the mobile shortcut points to the mobile simulator. In other words, the lnk address points to the executable file of the mobile simulator. In addition, the lnk address also stores the application startup parameters (such as application identification, etc.) corresponding to the target application, which is used to allow the mobile simulator to start the corresponding target application according to the application startup parameters. To this end, when the types of multiple target applications are all mobile application types, a new lnk file can be created, and the lnk address of the new lnk file can be pointed to the mobile simulator, and the application startup parameters can be extracted from the original lnk file of each target application. Then, the startup parameters corresponding to each target application are written into the new lnk file, combined with the lnk address pointing to the mobile simulator, to obtain the second merge information, and then create a target combination component based on the second merge information to display the target combination component at the desktop location indicated by the target combination option.

[0111] Optionally, the startup parameters corresponding to each target application can be written into the lnk file in the form of combined parameters. For example, the application identifiers of mobile application A, mobile application B and mobile application C are app01, app07 and app17 respectively. The three application identifiers are combined together through connection symbols to obtain the combined parameter "app01&app07&app17", and then the combined parameter can be written into the lnk file.

[0112] Consider that the applications that users need to launch in different time periods or work environments are variable. For example, a specific combination of applications is required on certain working days, while a completely different set of applications may need to be launched at other times. This flexible demand determines that users need to adjust the target combination components conveniently and quickly. For example, a mobile software developer may need to uniformly launch an integrated development environment and multiple competing instant messaging apps during the development of an instant messaging app. With different stages of development, it may be necessary to launch a software testing environment later, or a competing instant messaging app may not be needed. At this time, users need to recreate the target combination components based on new usage requirements, but in fact user requirements have not changed much, so the efficiency of re-creation is very low, which brings a cumbersome interactive experience to users.

[0113] To this end, the present application proposes a method in which after creating a target combination component on the interactive desktop, the user can also dynamically adjust the target combination component according to his or her own needs. In some embodiments, the user can drag other shortcuts to be added to the target combination component, so that the target combination component can be updated to a reorganized combination component with the other shortcuts added. In addition, the user can also select the shortcut to be removed through the application setting item of the context menu of the target combination component.

[0114] As an implementation mode, in response to a drag operation of dragging other shortcuts to a component position corresponding to a target composite component, a recombined composite component can be displayed. The other shortcuts refer to shortcuts that the user needs to add to the target composite component. Exemplarily, in response to the drag operation, the application startup information corresponding to the other shortcuts is obtained, and the application startup information corresponding to the other shortcuts is merged with the application startup information corresponding to the target composite component, and then the recombined composite component is created according to the merged startup information and displayed on the interactive desktop.

[0115] For example, see Fig.17 , Fig.17 A schematic diagram of dragging a shortcut combination is shown. The user can hold down the shortcut of the mobile application K with the mouse and drag the shortcut to the position of the target combination component. Then, in response to the drag operation, the target combination component and the shortcut of the mobile application K can be merged to create a new combination component, that is, the combination component is reorganized, such as Fig.18 A schematic diagram of the reorganization shortcut is shown, and the interactive desktop displays the reorganized assembly components after reorganization.

[0116] Optionally, Fig.17 and Fig.18 The illustration is only for a more clear explanation of an example scenario of reorganizing a composite component. In other cases, in response to a dragging operation of dragging other shortcuts to a component position corresponding to a target composite component, other shortcuts on the interactive desktop may also be dragged to a target composite component on a taskbar, a program dock, etc., to create a reorganized composite component, which is not limited here.

[0117] As another implementation, in response to a setting operation on a target combination component, a context menu corresponding to the target combination component is displayed, and in response to a selection operation on an application setting option in the context menu, an application setting interface is displayed. Furthermore, in response to a removal operation on a target removal application in a removal application setting item of the application setting interface, the target combination component can be updated and the updated updated combination component can be displayed, wherein the target removal application refers to the application that the user needs to remove from the multiple target applications corresponding to the target combination component. Exemplarily, in response to an application removal operation on a target removal application in a removal application setting item of the application setting interface, a target path corresponding to the target removal application can be deleted from the application startup information corresponding to the target combination component, and a target combination component can be created based on the application startup information after the target path is deleted.

[0118] For example, see Fig.19 , Fig.19 A schematic diagram of a context menu of a target combination component is shown. A user can right-click the target combination component, and then, in response to the setting operation of the right-click mode, a context menu corresponding to the target combination component is displayed, and the context menu includes multiple options: application settings, which can be used to set various target applications that need to be uniformly started by the target combination component; change display style, which can be used to change the display style of the target combination component; rename, which can be used to modify the component name of the target combination component; delete, which is used to delete the target combination component.

[0119] Further, the user can click on the application setting option in the context menu, and then, in response to the click operation, such as Fig. 20 The interface diagram of the application setting shown in the figure shows the application setting interface, which includes multiple setting items such as removing applications and startup sequence, among which removing applications is used to remove the target removal application; startup sequence can be used to set the startup sequence corresponding to multiple target applications. The user can remove the local application X from the three target applications (mobile application C, local application X and local application Y) corresponding to the target combination component by clicking the removal button corresponding to removing the local application X in the removing application setting item on the application setting interface, that is, the target removal application, and then respond to the click operation of the button, such as Fig.21 The component schematic diagram of the update combination component shown shows the update combination component. At this time, the update combination component can only be used to uniformly start the mobile application C and the local application Y.

[0120] Usually, users can create multiple target combination components based on different usage scenarios, but the target applications corresponding to these target combination components may be repeated. For example, a user creates corresponding target organization components for multiple game development projects. Since the applications used in the development overlap, the icons of the target organization components generated based on the target application icons are not easy for users to distinguish. Fig. 22 A schematic diagram of multiple target combination components is shown, for which the display style of the target organization component can be changed.

[0121] As an implementation mode, in response to a selection operation on a change display style option in a context menu, combination startup information corresponding to each target combination component on the interactive desktop may be obtained, and application statistics may be performed on the combination startup information corresponding to each target combination component, and a distinct application corresponding to each target combination component may be determined based on the statistical results. Exemplarily, combination startup information corresponding to each target combination component on the interactive desktop may be obtained, and for each combination startup information, a difference set between the combination startup information and a target application in other combination startup information may be calculated, thereby obtaining a distinct application corresponding to each target combination component.

[0122] Further, based on the difference application icon of each difference application, a combination application icon of the corresponding target combination component is generated, and each target combination component after the icon is replaced is displayed, such as Fig.23 The schematic diagrams of the differences of multiple target combination components shown in the figure show that the main elements of the icon of each target combination component are icons of different applications that are different from other target combination components. In this way, by differentiating the icons of target combination components, users can easily identify the target combination components used in different scenarios, thereby improving the efficiency of users in finding target combination components.

[0123] This embodiment can display an interactive desktop, and the shortcuts displayed on the interactive desktop may include mobile terminal shortcuts and local shortcuts, and the mobile terminal shortcuts are used to start the mobile terminal application installed in the mobile terminal simulator. Further, in response to the combination operation of at least two shortcuts, a target combination component can be displayed, wherein at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target application corresponding to the at least two shortcuts of the combination. In this way, by generating a target combination component for multiple shortcuts including at least one mobile terminal shortcut, the target combination component can open multiple applications including at least one mobile terminal application at one time. For scenarios that require multiple applications to perform tasks, especially cross-application scenarios between mobile terminal applications and local applications, multiple applications can be opened at the same time to maintain task continuity and avoid the interaction burden of service objects opening different applications. Therefore, the operation steps and time cost of starting multiple applications including at least one mobile terminal application are effectively reduced, and the user interaction experience and application interaction efficiency are improved. In addition, by combining multiple shortcuts, only one target combination component is needed on the interactive desktop to represent multiple applications, reducing the visual confusion caused by multiple independent shortcuts, helping users find the required set of applications more quickly, and improving the efficiency of application management while improving operational efficiency.

[0124] According to an embodiment of the present application, another application interaction method is provided. The application interaction method can be executed by a computer device (such as a desktop computer, a laptop computer or other terminal device with certain processing capabilities, etc.), and the computer device has at least storage, calculation and communication functions. Fig.24 , Fig.24 The schematic diagram of the flow chart of the application interaction method provided by this embodiment is shown. Fig.24 The specific steps of the application interaction method are described below:

[0125] Step 210: Display the simulator interface.

[0126] Considering that the operation of using mobile applications on the interactive desktop operating system is limited to the main interface of the mobile simulator, the entire interactive steps are cumbersome and complicated, which does not conform to the conventional operating habits of interactive desktop operating system users and affects the user experience. Therefore, a shortcut can be generated for the mobile application in the mobile simulator on the interactive desktop, so that users can directly open the mobile application through the mobile shortcut on the interactive desktop.

[0127] In the embodiment of the present application, the simulator interface refers to the interface of the mobile terminal simulator installed on the desktop operating system. The mobile terminal simulator is used to simulate a mobile terminal system environment that is different from the desktop operating system. The simulator interface includes startup components corresponding to multiple mobile terminal applications. Fig.25 , Fig.25 A schematic diagram of the interface of a mobile terminal simulator is shown. Fig.25 As shown, in response to the user clicking on the shortcut of the mobile terminal simulator on the interactive desktop, the simulator interface corresponding to the mobile terminal simulator can be displayed, and two startup components are displayed on the simulator interface, each startup component is composed of an icon, an icon name and an open button of a mobile terminal application, for example, mobile terminal application E and mobile terminal application F that have been installed on the mobile terminal simulator. Optionally, the user can click on the application store icon on the simulator interface to download and install the required mobile terminal application on the mobile terminal simulator.

[0128] Step 220: In response to a shortcut generation operation performed on a target startup component among the multiple startup components, a mobile terminal shortcut of a mobile terminal application corresponding to the target startup component is displayed on the interactive desktop.

[0129] As an implementation mode, in response to a selection operation of a target startup component from among multiple startup components, an options menu may be displayed, and in response to a trigger operation of a shortcut generation option in the options menu, a mobile terminal shortcut of a mobile terminal application corresponding to the startup component may be displayed on the interactive desktop. Exemplarily, taking the Windows desktop operating system as an example, in response to a trigger operation of a shortcut generation option in the options menu, the mobile terminal simulator may send a shortcut creation request to Windows, and the request may carry application startup parameters of the mobile terminal application (e.g., application identifier and installation package address, etc.). When Windows receives the creation request, it may call a Windows API, such as a ShellLink API, to create a corresponding shortcut based on the application startup parameters of the mobile terminal application.

[0130] For example, Fig.26 The target startup component selection schematic diagram shown in FIG. 1 can respond to a user right-clicking on the startup component of the mobile application E to display a corresponding option menu, and further respond to the user clicking on the generate shortcut option on the option menu to create a mobile shortcut corresponding to the mobile application E, and then Fig. 27 The desktop display schematic diagram of the mobile terminal shortcut is shown, and the mobile terminal shortcut corresponding to the mobile terminal application E is displayed on the interactive desktop.

[0131] Step 230: In response to a combination operation performed on at least two shortcuts, display a target combination component.

[0132] As an implementation mode, the at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target application corresponding to the at least two shortcuts in the combination. Specifically, the method for generating the target combination component can refer to the relevant contents of steps 110 to 120 in the above embodiment, which will not be repeated here.

[0133] Step 240: In response to the triggering operation on the target composite component, the application startup information corresponding to the target composite component is obtained, and the application startup information is analyzed.

[0134] Among them, the triggering operation of the target combination component refers to the desktop operating system executing the interactive behavior of the target object pointed to by the target combination component according to the configuration of the target combination component. For example, the user starts the corresponding target application by clicking the left mouse button twice in rapid succession for the target combination component in the form of a shortcut.

[0135] As an implementation manner, the method of obtaining the application startup information corresponding to the target combination component and analyzing the application startup information can refer to the relevant content about analyzing the application startup information in step 120 of the above embodiment, which will not be repeated here.

[0136] Step 250: When the analysis result indicates that the types of the multiple target applications include a mobile application type and a native application type, start at least one mobile application interface and at least one native application interface indicated by the application start information.

[0137] Since there are differences in the startup methods of mobile applications and local applications, after analyzing the application startup information corresponding to the target composite component, an analysis result that can reflect the application types of multiple applications to be started can be obtained, and then the mobile application and the local application can be started using an adaptive startup method based on the analysis result. In addition, in order to improve the overall system performance and thus enhance the user experience, multiple target applications corresponding to the target composite component can be started in an orderly manner, which may include:

[0138] (1) Obtain the application startup sequence based on the application startup information.

[0139] In the embodiment of the present application, when multiple target applications are started, the application startup sequence is arranged in the order in which these applications are started in sequence according to certain rules. The purpose of this sequence is to reasonably allocate system resources, optimize user experience, and ensure the stability and efficiency of the system during operation. The application startup sequence can be set based on rules such as application dependency, resource management, or user experience optimization.

[0140] Among them, application dependency means that some applications may rely on the startup of other applications. For example, the database application must be started before the server application is started to ensure that the application can connect to the database normally. Resource management means that the startup sequence usually needs to consider the resource usage of the system. By starting lightweight applications or resource-intensive applications first, problems such as resource competition and system freezes can be avoided. User experience optimization means that a reasonable startup sequence can reduce user waiting time, give priority to the applications that users need most to enter the available state, and provide a smoother user experience. Optionally, the application startup sequence may not always be fixed, and can also be dynamically adjusted according to factors such as the current resource status of the personal computer, the operating habits of the service object, and the working environment to meet the needs of different scenarios.

[0141] As an implementation method, the application startup sequence can be represented by arranging the startup addresses when merging the application startup information corresponding to different target applications. In this way, the arrangement order of the startup addresses in the application startup information of the target composite component can be used as the application startup sequence. For example, from the batch file (i.e., application startup information) corresponding to the target composite component in the batch file format, the order of the startup addresses of each target application can be obtained as the application startup sequence.

[0142] (2) Based on the application startup sequence, the application startup parameters corresponding to each target application are obtained in turn.

[0143] Application startup parameters refer to a set of additional settings or options that can be passed to the target application when it is launched, which are used to control the behavior, configuration, or execution mode of the target application. These parameters can be used to specify file paths, set startup modes, enable / disable functions, pass service object credentials, etc.

[0144] As an implementation method, the application startup parameters corresponding to each target application can be obtained in sequence from the application startup information corresponding to the target composite component based on the application startup sequence. For example, file path: the target application can specify the file or directory to be loaded at startup through the startup parameter. For example: XXX.exe / file "C:\Documents\example.txt" means that the specified file is directly loaded when the application starts. Startup mode: the application may have multiple startup modes, and a certain mode can be selected through the startup parameters. For example: XXX.exe / safe-mode means running in safe mode when starting the application.

[0145] (3) Starting each target application in turn according to the parameter acquisition order of the application startup parameters to display a mobile application interface corresponding to at least one mobile application and a local application interface corresponding to at least one local application.

[0146] In some embodiments, the application startup parameters may include mobile application startup parameters and local application startup parameters, and the target application may include a target mobile terminal application and a target local application. The target mobile terminal application may be started according to the mobile application startup parameters, and the target local application may be started according to the local application startup parameters.

[0147] As an implementation method, the parameter acquisition order of the mobile application startup parameters and the local application startup parameters can be determined. Furthermore, the target mobile application corresponding to each mobile application startup parameter, or the target local application corresponding to each local application startup parameter, is started in turn according to the parameter acquisition order to display at least one corresponding mobile application interface and at least one local application interface.

[0148] For example, the personal computer first obtains a mobile application startup parameter corresponding to a target mobile application, and then obtains a local application startup parameter corresponding to a target local application. Then, the target mobile application is started based on the mobile application startup parameter, and the corresponding mobile application interface is displayed. Furthermore, the target local application is started based on the local application startup parameter, and the corresponding local application interface is displayed.

[0149] In order to improve user experience and work efficiency, the present application proposes to achieve more seamless application integration by reducing the steps of manual switching operations, intelligently predicting the user's use needs for different applications, and starting related functions in advance. In some embodiments, a mobile application theme corresponding to at least one mobile terminal application interface can be determined, and further, the mobile application theme can be sent to a local application to be loaded in at least one target local application, so that the local application to be loaded loads and displays a theme application interface matching the mobile application theme.

[0150] For example, a user opens a mobile game application and a PC game forum at the same time through the target combination component on a PC device. At this time, the PC device can perform image recognition on the application interface corresponding to the game application, obtain the game name and type of the game application, and then generate a query instruction corresponding to the theme information and send the query instruction to the PC game forum. The PC game forum can directly display the theme application interface related to the theme information based on the query instruction, such as the game strategy discussion group interface.

[0151] Step 260: When the analysis result indicates that the types of the multiple target applications are all mobile application types, at least two mobile application interfaces indicated by the application startup information are started.

[0152] In some embodiments, the application startup parameter includes a mobile application startup parameter, and the target application includes a target mobile terminal application. When the analysis result indicates that the types of multiple target applications are all mobile terminal application types, the mobile terminal simulator can be started first, and then the mobile terminal simulator can start multiple target applications, and then display each corresponding mobile terminal application interface, which can specifically include:

[0153] (1) Start the mobile simulator based on the simulator address in the mobile application startup parameters.

[0154] As an implementation method, the desktop operating system can obtain the simulator address of the mobile simulator from the mobile application startup parameters, and then start the mobile simulator according to the simulator address. For example, the Windows operating system of the PC device starts the Android simulator based on the simulator address. When the Android simulator starts, a virtual machine is created and the image of the Android operating system is loaded. This process may include configuring virtual hardware, and then the Android simulator can initialize the Android system: after the virtual machine is started, the Android system is started and its core services and system components are initialized.

[0155] (2) Starting the target mobile application corresponding to each application resource identifier in the mobile application startup parameter through the mobile terminal simulator to display the mobile application interface of each target mobile terminal application.

[0156] As an implementation method, the application resource identifier is used to represent the application name or application identifier corresponding to the target mobile application. The mobile simulator can start the application by using the application resource identifier corresponding to each target mobile application in the mobile application startup parameters, which may specifically include:

[0157] (2.1) Analyze the mobile application startup parameters to obtain multiple application resource identifiers and the application startup method corresponding to each application resource identifier.

[0158] As an implementation method, the application startup method refers to the specific method and process of starting and running the target mobile application in the operating system of the mobile simulator. Different types of applications may require different startup methods, which mainly depends on the design architecture and usage scenarios of the application. For example, a game application needs to execute a rendering process when it is started, relative to an instant messaging application. Exemplarily, the mobile application startup parameter can be a parameter file, which stores the application resource identifier and application startup method corresponding to each target mobile application. The mobile simulator can read multiple application resource identifiers and the application startup method corresponding to each application resource identifier from the parameter file.

[0159] (2.2) Based on each application resource identifier and the corresponding application startup method, the corresponding target mobile application is started, and the mobile application interface corresponding to each target mobile application is displayed.

[0160] As an implementation method, the mobile simulator can obtain the application installation package corresponding to each application resource identifier, and create an application running container according to the application startup method corresponding to each application resource identifier. Further, the corresponding application installation package is run in each application running container, and then the target mobile application corresponding to each application installation package is started, and the mobile application interface corresponding to each target mobile application is displayed.

[0161] See also Fig.28 , Fig.28 A schematic diagram of a multi-mobile terminal application startup process is shown. For example, Fig.28 The desktop operating system in the example is Windows, and the mobile simulator is Android. When a user double-clicks a shortcut icon (i.e., a target composite component) on the interactive desktop, Windows captures the input event (mouse click). Windows handles this event through the Desktop Window Manager and passes the double-click operation to the core component of Windows, Windows Shell. Windows Shell is responsible for managing the desktop, taskbar, and file explorer.

[0162] Furthermore, after Windows Shell receives the user's double-click event, it will first identify the file as a shortcut (lnk file, that is, mobile application startup information). The system registry provides a way to handle shortcut files, and the system determines how to parse and execute these shortcuts through the registry. For example, the system registry can notify Windows to read the lnk file through the IShellLink interface in the Shell API and parse the metadata therein, including the target path and application startup parameters.

[0163] Furthermore, the system startup module starts the Android simulator according to the target path, and passes the IDs of multiple apps (i.e., target mobile applications) to be started to the application startup module of the Android simulator Host. At this time, the Android simulator host Host will start an Android simulation environment, i.e., the object Guset. At the same time, the application startup module passes the IDs of multiple apps to the shortcut combination module, and the application startup module finds the storage address of the Android installation package (Android Application Package, APK) of the app corresponding to each ID by looking up the table.

[0164] Furthermore, the application startup module transmits the storage address of the Android installation package of the APP queried from the shortcut combination module to the startup setting module of the object-side Guset, and then the startup setting module obtains the Android installation package corresponding to each storage address through the simulator API, and creates a container to run each Android installation package, completes the startup of multiple APPs, and displays the corresponding interface of each APP (that is, the mobile application interface).

[0165] This embodiment can display the simulator interface, and in response to the shortcut generation operation of the target startup component in the multiple startup components in the simulator interface, the mobile terminal shortcut of the mobile terminal application corresponding to the target startup component is displayed on the interactive desktop. Furthermore, the mobile terminal simulator can be started and run in the background of the desktop operating system. In this case, the main interface of the mobile simulator is not displayed on the interactive desktop of the desktop operating system, that is, the user does not need to start the mobile terminal simulator first, and then start the mobile terminal application from the mobile terminal simulator, so that the process of starting the mobile terminal application can be effectively reduced, making the startup of the mobile terminal application more convenient and improving the user interaction experience. Further, in response to the combination operation of at least two shortcuts, the target combination component can be displayed, and then in response to the triggering operation of the target combination component, the application startup information corresponding to the target combination component can be obtained, and the application startup information can be analyzed. When the analysis result indicates that the types of multiple target applications include mobile terminal application types and local application types, at least one mobile terminal application interface and at least one local application interface indicated by the application startup information can be started. When the analysis result indicates that the types of multiple target applications are all mobile terminal application types, at least two mobile terminal application interfaces indicated by the application startup information can be started. In this way, multiple applications including at least one mobile application can be opened at one time through a target combination component, especially in the scenario of cross-application task execution between mobile applications and local applications. Multiple applications can be opened in a unified manner to maintain the continuity of tasks and reduce the user's interaction process of launching multiple applications for different tasks. Therefore, the operation steps and time cost of launching applications can be effectively reduced, and the user interaction experience can be improved.

[0166] See also Fig.29 , which shows a structural block diagram of an application interaction device 300 provided in an embodiment of the present application. The application interaction device 300 may include a desktop display module 310 and a component display module 320.

[0167] The desktop display module 310 is used to display the interactive desktop. The shortcuts displayed on the interactive desktop include mobile terminal shortcuts and local shortcuts. The mobile terminal shortcuts are used to start the mobile terminal application installed in the mobile terminal simulator.

[0168] A component display module 320, configured to display a target combination component in response to a combination operation performed on at least two shortcuts;

[0169] Among them, the at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target applications corresponding to the at least two shortcuts of the combination.

[0170] In some embodiments, the component display module 320 may include a single category selection unit and a shortcut combination unit.

[0171] A single-category selection unit, configured to display a plurality of target shortcuts in a selected state in response to a selection operation performed on at least two mobile terminal shortcuts;

[0172] The shortcut combination unit is used to display a target combination component in response to a combination operation performed on the multiple target shortcuts.

[0173] In some embodiments, the component display module 320 may further include a multi-category selection unit and a shortcut combination unit.

[0174] A multi-category selection unit, configured to display a plurality of target shortcuts in a selected state in response to a selection operation performed on at least one mobile terminal shortcut and at least one local shortcut;

[0175] The shortcut combination unit is used to display a target combination component in response to a combination operation performed on the multiple target shortcuts.

[0176] In some embodiments, the shortcut combination unit may include an option sub-unit and a component sub-unit.

[0177] An option subunit, for displaying a combined option menu in response to a combined operation on the plurality of target shortcuts;

[0178] The component subunit is used to display a target combination component at a desktop position indicated by the target combination option in response to a selection operation on the target combination option in the combination option menu.

[0179] In some embodiments, the component sub-unit can be specifically used to: in response to a selection operation on a target combination option in the combination option menu, obtain application startup information corresponding to the multiple target shortcuts, and analyze each application startup information separately; when the analysis result indicates that the types of multiple target applications include mobile application types and local application types, merge the application startup information corresponding to the mobile shortcut and the application startup information corresponding to the local shortcut, and create a target combination component based on the merged first merge information to display the target combination component at the desktop position indicated by the target combination option; when the analysis result indicates that the types of multiple target applications are all mobile application types, merge the application startup information corresponding to each mobile shortcut, and create a target combination component based on the merged second merge information to display the target combination component at the desktop position indicated by the target combination option.

[0180] In some embodiments, the application interaction device 300 may further include an information analysis module, a multi-category startup module, and a single-category startup module.

[0181] An information analysis module, configured to obtain application startup information corresponding to the target combination component in response to a trigger operation on the target combination component, and analyze the application startup information;

[0182] A multi-type startup module, used for starting at least one mobile application interface and at least one local application interface indicated by the application startup information when the analysis result indicates that the types of the multiple target applications include a mobile application type and a local application type;

[0183] The single-type startup module is used to start at least two mobile application interfaces indicated by the application startup information when the analysis result indicates that the types of multiple target applications are all mobile application types.

[0184] In some embodiments, the multi-type startup module may include a sequence acquisition unit, a parameter acquisition unit, and a sequential startup unit.

[0185] A sequence acquisition unit, used to acquire the application startup sequence according to the application startup information;

[0186] A parameter acquisition unit, configured to sequentially acquire application startup parameters corresponding to each target application based on the application startup sequence;

[0187] The sequential starting unit is used to start each target application in sequence according to the parameter acquisition order of the application starting parameters, so as to display a mobile application interface corresponding to at least one mobile application and a local application interface corresponding to at least one local application.

[0188] In some embodiments, the application startup parameters include mobile application startup parameters and local application startup parameters, the target application includes a target mobile terminal application and a target local application; the sequential startup unit may include: a sequence determination subunit and a multi-category startup subunit.

[0189] A sequence determination subunit, used to determine the parameter acquisition sequence of the mobile application startup parameters and the local application startup parameters;

[0190] Multiple types of launcher units are used to launch the target mobile application corresponding to each mobile application launch parameter, or the target local application corresponding to each local application launch parameter, in sequence according to the parameter acquisition order, so as to display at least one corresponding mobile application interface and at least one local application interface.

[0191] In some embodiments, the sequential starting unit may further include a theme determination subunit and a theme loading subunit.

[0192] A theme determination subunit, used to determine a mobile application theme corresponding to at least one mobile application interface;

[0193] The theme loading subunit is used to send the mobile application theme to a local application to be loaded in at least one target local application, so that the local application to be loaded loads and displays a theme application interface matching the mobile application theme.

[0194] In some embodiments, the application startup parameters include mobile application startup parameters, and the target application includes a target mobile terminal application; the single-type startup module may include a simulation startup unit and an application startup unit.

[0195] A simulation startup unit, used to start a mobile terminal simulator based on the simulator address in the mobile application startup parameters;

[0196] The application startup unit is used to start the target mobile terminal application corresponding to each application resource identifier in the mobile application startup parameter through the mobile terminal simulator to display the mobile terminal application interface of each target mobile terminal application.

[0197] In some embodiments, the application launching unit may include a parameter analyzing subunit, a moving launching subunit, and an application displaying subunit.

[0198] A parameter analysis subunit, configured to analyze the mobile application startup parameters to obtain a plurality of application resource identifiers and an application startup mode corresponding to each application resource identifier;

[0199] A mobile launch subunit, used to launch a corresponding target mobile terminal application based on each application resource identifier and a corresponding application launch mode;

[0200] The application display subunit is used to display the mobile application interface corresponding to each target mobile application.

[0201] In some embodiments, the mobile launch subunit can be specifically used to: obtain the application installation package corresponding to each application resource identifier; create an application running container according to the application startup method corresponding to each application resource identifier; run the corresponding application installation package in each application running container to start the target mobile application corresponding to each application installation package.

[0202] In some embodiments, the application interaction device 300 may further include a simulation display module and a shortcut display module.

[0203] A simulation display module, used to display a simulator interface, wherein the simulator interface includes startup components corresponding to multiple mobile terminal applications;

[0204] The shortcut display module is used to respond to the shortcut generation operation performed on the target startup component among the multiple startup components, and display the mobile terminal shortcut of the mobile terminal application corresponding to the target startup component on the interactive desktop.

[0205] In some embodiments, the application interaction device 300 may further include a component reorganization module for displaying a reorganized combined component in response to a dragging operation of dragging other shortcuts to a component position corresponding to the target combined component.

[0206] In some embodiments, the application interaction device 300 may further include a menu display module, an application setting module, and a component update module.

[0207] A menu display module, configured to display a context menu corresponding to the target combination component in response to a setting operation performed on the target combination component;

[0208] An application setting module, configured to display an application setting interface in response to a selection operation on an application setting option in the context menu;

[0209] The component update module is used to update the target combination component in response to the removal operation of the target removal application in the removal application setting item of the application setting interface, and display the updated update combination component.

[0210] In some embodiments, the application interaction apparatus 300 may further include a style selection module, an application statistics module, an icon generation module, and an icon replacement module.

[0211] A style selection module, configured to obtain, in response to a selection operation on a display style change option in the context menu, combination start information corresponding to each target combination component on the interactive desktop;

[0212] An application statistics module is used to perform application statistics on the combination startup information corresponding to each target combination component, and determine the distinct application corresponding to each target combination component according to the statistical results;

[0213] An icon generation module, used for generating a combined application icon of a corresponding target combined component based on the distinguished application icon of each distinguished application;

[0214] The icon replacement module is used to display each target composite component after the icon is replaced.

[0215] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices, modules, etc. can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0216] In several embodiments provided in the present application, the coupling between modules may be electrical, mechanical or other forms of coupling.

[0217] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

[0218] This embodiment can display an interactive desktop, and the shortcuts displayed on the interactive desktop may include mobile terminal shortcuts and local shortcuts, and the mobile terminal shortcuts are used to start the mobile terminal application installed in the mobile terminal simulator. Further, in response to the combination operation of at least two shortcuts, a target combination component can be displayed, wherein at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target application corresponding to the at least two shortcuts of the combination. Therefore, by generating a target combination component for multiple shortcuts including at least one mobile terminal shortcut, the target combination component can open multiple applications including at least one mobile terminal application at one time. For scenarios where multiple applications need to be used to perform multiple tasks, especially cross-application scenarios between mobile terminal applications and local applications, it is possible to uniformly open multiple applications, maintain task continuity, and avoid the interaction burden of starting the same application for service objects, thereby effectively reducing the operation steps and time cost of starting multiple applications including at least one mobile terminal application, improving user interaction experience and application interaction efficiency. In addition, by combining multiple shortcuts, only one target combination component is needed on the interactive desktop to represent the startup components of multiple applications, reducing the visual confusion caused by multiple independent shortcuts, helping service objects find the required set of applications more quickly, and improving interaction efficiency while also improving application management efficiency.

[0219] like Fig.30 As shown, the embodiment of the present application also provides a computer device 400, which can be in various forms such as a desktop computer or a laptop computer. The computer device 400 includes a processor 410, a memory 420, a power supply 430 and an input unit 440. The memory 420 stores a computer program. When the computer program is called by the processor 410, the various method steps provided in the above embodiments can be implemented. Those skilled in the art can understand that the structure of the computer device shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0220] The processor 410 may include one or more processing cores. The processor 410 uses various interfaces and lines to connect various parts of the entire battery management system, and executes various functions and processes data of the battery management system, as well as various functions and processes data of the computer device by running or executing instructions, programs, instruction sets or program sets stored in the memory 420, calling the data stored in the memory 420, thereby controlling the computer device as a whole. Optionally, the processor 410 may be implemented in at least one hardware form of digital signal processing (DSP), field programmable gate array (FPGA), and programmable logic array (PLA). The processor 410 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, object interface, and application program, etc.; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communication. It is understandable that the above-mentioned modem may not be integrated into the processor 410, but may be implemented separately through a communication chip.

[0221] The memory 420 may include a random access memory (RAM) or a read-only memory (ROM). The memory 420 may be used to store instructions, programs, instruction sets or program sets. The memory 420 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The data storage area may also store data (such as a phone book and audio and video data) created by the computer device during use. Accordingly, the memory 420 may also include a memory controller to provide the processor 410 with access to the memory 420.

[0222] The power supply 430 can be logically connected to the processor 410 through a power management system, so as to manage charging, discharging, power consumption and other functions through the power management system. The power supply 430 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.

[0223] The input unit 440 may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to object setting and function control.

[0224] Although not shown, the computer device 400 may also include an output unit, a display unit, etc., which are not described in detail herein. Specifically, in the embodiment of the present application, the processor 410 of the computer device will load the executable files corresponding to the processes of one or more computer programs into the memory 420 according to the following instructions, and the processor 410 will run the data stored in the memory 420, such as the phone book and audio and video data, so as to implement the various method steps provided in the aforementioned embodiments.

[0225] like Fig.31 As shown, the embodiment of the present application further provides a computer-readable storage medium 500, in which a computer program 510 is stored. The computer program 510 can be called by a processor of a computer device to execute various method steps provided in the embodiment of the present application.

[0226] The computer readable storage medium may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read-Only Memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium includes a non-volatile computer readable storage medium (Non-Transitory Computer-Readable Storage Medium). The computer readable storage medium 500 has storage space for a computer program that executes any of the method steps in the above embodiments. These computer programs can be read from or written to one or more computer program products. The computer program can be compressed in an appropriate form.

[0227] According to one aspect of the present application, a computer program product is provided, the computer program product comprising a computer program, the computer program being stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device executes various method steps provided in the above embodiments.

[0228] The terms "comprises" and "includes" in the specification of the present application and the above-mentioned drawings and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices. The term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works 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.

[0229] It should be understood that in the present application, "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 objects, 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 objects associated before and after are 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.

[0230] It should be understood that in the description of the embodiments of the present application, 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.

[0231] In the several embodiments provided in the present application, 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.

[0232] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware or in the form of software functional units.

[0233] 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 application 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 application. It should also be understood that the various implementation methods provided in the embodiments of the present application can be arbitrarily combined to achieve different technical effects.

[0234] The above are only preferred embodiments of the present application, and are not intended to limit the present application in any form. Although the present application has been disclosed as above with preferred embodiments, it is not intended to limit the present application. Any technical personnel in the field can make some changes or modify the technical contents disclosed above into equivalent embodiments without departing from the scope of the technical solution of the present application. However, any brief modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present application without departing from the content of the technical solution of the present application are still within the scope of the technical solution of the present application.

Claims

1. An application interaction method, characterized in that: The method comprises: Displaying an interactive desktop, wherein the shortcuts displayed on the interactive desktop include mobile terminal shortcuts and local shortcuts, and the mobile terminal shortcuts are used to start the mobile terminal application installed in the mobile terminal simulator; In response to a combination operation performed on at least two shortcuts, displaying a target combination component; Among them, the at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target applications corresponding to the at least two shortcuts of the combination.

2. The method according to claim 1, characterized in that The step of displaying a target combination component in response to a combination operation performed on at least two shortcuts includes: In response to a selection operation performed on at least two mobile terminal shortcuts, displaying a plurality of target shortcuts in a selected state; In response to a combination operation performed on the plurality of target shortcuts, a target combination component is displayed.

3. The method according to claim 1, characterized in that The step of displaying a target combination component in response to a combination operation performed on at least two shortcuts includes: In response to a selection operation performed on at least one mobile shortcut and at least one local shortcut, displaying a plurality of target shortcuts in a selected state; In response to a combination operation performed on the plurality of target shortcuts, a target combination component is displayed.

4. The method according to claim 2 or 3, characterized in that: The displaying of a target combination component in response to the combination operation performed on the plurality of target shortcuts includes: In response to a combination operation performed on the plurality of target shortcuts, displaying a combination option menu; In response to a selection operation on a target combination option in the combination option menu, a target combination component is displayed at a desktop position indicated by the target combination option.

5. The method according to claim 4, characterized in that In response to the selection operation of the target combination option in the combination option menu, displaying the target combination component at the desktop position indicated by the target combination option includes: In response to a selection operation on a target combination option in the combination option menu, obtaining application startup information corresponding to the plurality of target shortcuts, and analyzing each piece of application startup information respectively; When the analysis result indicates that the types of the multiple target applications include a mobile application type and a local application type, merging the application startup information corresponding to the mobile shortcut and the application startup information corresponding to the local shortcut, and creating a target combination component according to the merged first merged information, so as to display the target combination component at the desktop position indicated by the target combination option; When the analysis result indicates that the types of multiple target applications are all mobile application types, the application startup information corresponding to each mobile shortcut is merged, and a target combination component is created based on the merged second merged information to display the target combination component at the desktop location indicated by the target combination option.

6. The method according to claim 1, characterized in that The method further comprises: In response to a triggering operation on the target combination component, obtaining application startup information corresponding to the target combination component, and analyzing the application startup information; When the analysis result indicates that the types of the multiple target applications include a mobile application type and a local application type, launching at least one mobile application interface and at least one local application interface indicated by the application launch information; When the analysis result indicates that the types of the multiple target applications are all mobile terminal application types, at least two mobile terminal application interfaces indicated by the application startup information are started.

7. The method according to claim 6, characterized in that The starting of at least one mobile application interface and at least one local application interface indicated by the application starting information includes: According to the application startup information, obtaining the application startup sequence; Based on the application startup sequence, sequentially obtain application startup parameters corresponding to each target application; Each target application is started in sequence according to the parameter acquisition sequence of the application startup parameters to display a mobile application interface corresponding to at least one mobile application and a local application interface corresponding to at least one local application.

8. The method according to claim 7, characterized in that The application startup parameters include mobile application startup parameters and local application startup parameters, and the target application includes a target mobile terminal application and a target local application; The method of sequentially starting each target application according to the parameter acquisition sequence of the application startup parameter to display a mobile application interface corresponding to at least one mobile application and a local application interface corresponding to at least one local application includes: Determine the order of obtaining parameters of mobile application startup parameters and local application startup parameters; The target mobile terminal application corresponding to each mobile application startup parameter or the target local application corresponding to each local application startup parameter is started in sequence according to the parameter acquisition order to display the corresponding at least one mobile terminal application interface and at least one local application interface.

9. The method according to claim 8, characterized in that After sequentially starting the target mobile terminal application corresponding to each mobile application startup parameter or the target local application corresponding to each local application startup parameter according to the parameter acquisition order to display the corresponding at least one mobile terminal application interface and at least one local application interface, the method further includes: Determine a mobile application theme corresponding to at least one mobile application interface; The mobile application theme is sent to a local application to be loaded in at least one target local application, so that the local application to be loaded loads and displays a theme application interface matching the mobile application theme.

10. The method according to claim 6, characterized in that The application startup parameters include mobile application startup parameters, and the target application includes a target mobile terminal application; The starting of at least two mobile terminal application interfaces indicated by the application starting information includes: Based on the simulator address in the mobile application startup parameters, start the mobile terminal simulator; The target mobile terminal application corresponding to each application resource identifier in the mobile application startup parameter is started through the mobile terminal simulator to display the mobile terminal application interface of each target mobile terminal application.

11. The method according to claim 10, characterized in that The method of starting the target mobile terminal application corresponding to each application resource identifier in the mobile application startup parameter to display the mobile terminal application interface of each target mobile terminal application includes: Analyze the mobile application startup parameters to obtain multiple application resource identifiers and an application startup method corresponding to each application resource identifier; Based on each application resource identifier and the corresponding application startup method, start the corresponding target mobile application; Display the mobile application interface corresponding to each target mobile application.

12. The method according to claim 11, characterized in that The starting of the corresponding target mobile terminal application based on each application resource identifier and the corresponding application starting method includes: Obtain the application installation package corresponding to each application resource identifier; Create an application running container according to the application startup method corresponding to each application resource identifier; The corresponding application installation package is run in each application running container to start the target mobile terminal application corresponding to each application installation package.

13. The method according to claim 1, characterized in that The method further comprises: Displaying a simulator interface, wherein the simulator interface includes startup components corresponding to multiple mobile terminal applications; In response to a shortcut generation operation performed on a target startup component among the multiple startup components, a mobile terminal shortcut of a mobile terminal application corresponding to the target startup component is displayed on the interactive desktop.

14. The method according to claim 1, characterized in that The method further comprises: In response to a dragging operation of dragging other shortcuts to a component position corresponding to the target combined component, the recombined combined component is displayed.

15. The method according to claim 1, characterized in that The method further comprises: In response to a setting operation performed on the target combination component, displaying a context menu corresponding to the target combination component; In response to a selection operation on an application setting option in the context menu, displaying an application setting interface; In response to a removal operation performed on a target removal application in a removal application setting item of the application setting interface, the target combination component is updated and an updated update combination component is displayed.

16. The method according to claim 15, characterized in that The method further comprises: In response to a selection operation on a display style change option in the context menu, obtaining combination start information corresponding to each target combination component on the interactive desktop; Perform application statistics on the combination startup information corresponding to each target combination component, and determine the distinct application corresponding to each target combination component according to the statistical results; Based on the distinguishing application icon of each distinguishing application, generating a combined application icon of a corresponding target combined component; Displays each target composite component after icon replacement.

17. An application interaction device, characterized in that: The device comprises: A desktop display module, used to display an interactive desktop, wherein the shortcuts displayed on the interactive desktop include mobile terminal shortcuts and local shortcuts, and the mobile terminal shortcuts are used to start the mobile terminal application installed in the mobile terminal simulator; A component display module, configured to display a target combination component in response to a combination operation performed on at least two shortcuts; Among them, the at least two shortcuts include at least one mobile terminal shortcut, and the target combination component is used to uniformly start the target applications corresponding to the at least two shortcuts of the combination.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the application interaction method according to any one of claims 1 to 16 is implemented.

19. A computer device, characterized in that: include: Memory; A processor, wherein a computer program is stored on the memory, and when the computer program is executed by the processor, the application interaction method according to any one of claims 1 to 16 is implemented.

20. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the application interaction method according to any one of claims 1 to 16 is implemented.

Images