Sub-application generation method and device, computer equipment and readable storage medium

Abstract

The invention relates to a sub-application generation method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: displaying a sub-application development interface of a first application development platform, and displaying a template identifier of a sub-application page template provided by a second application development platform on the sub-application development interface; in response to an identifier selection operation on the template identifier, displaying a simulator area of the first application development platform and a configuration area provided by the second application development platform, the configuration area displaying a sub-application page template and a plurality of sub-application components provided by the second application development platform; in response to the component selection operation, adding the sub-application component selected by the component selection operation into the sub-application page template; and in response to a simulation trigger event for the simulator area, displaying a simulation interaction page of the sub-application in the simulator area, the simulation interaction page being generated based on the sub-application page template and the added sub-application component. By adopting the method, the sub-application development efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and particularly to a method, device, computer device, storage medium, and computer program product for generating sub-applications. Background Art

[0002] With the development of computer technology, sub-application generation technology has emerged, and users can generate sub-applications that meet their own needs through sub-application generation technology. For example, for merchants on the Internet of Things, exclusive sub-applications are required to provide services for consumers, and merchants can generate their own exclusive sub-applications.

[0003] In the related art, specific types of sub-applications are generally implemented through specific types of application development platforms. The application development platform provides some pre-configured templates, and users can adjust these templates to generate the sub-applications they need.

[0004] However, since different application development platforms can only provide development services for certain types of sub-applications, when a user needs to generate a certain type of sub-application, it needs to be implemented on an application development platform that can develop this type of sub-application, resulting in low development efficiency of sub-applications. Summary of the Invention

[0005] Based on this, it is necessary to provide a method, device, computer device, computer-readable storage medium, and computer program product for generating sub-applications that can improve development efficiency for the above technical problems.

[0006] In a first aspect, the present application provides a method for generating sub-applications. The method includes:

[0007] Display the sub-application development interface of the first application development platform, and display the template identifiers of the sub-application page templates provided by the second application development platform on the sub-application development interface;

[0008] In response to an identifier selection operation on the template identifier, display the simulator area of the first application development platform and the configuration area provided by the second application development platform. The configuration area displays the sub-application page template and a plurality of sub-application components provided by the second application development platform;

[0009] In response to a component selection operation for selecting among the plurality of sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template;

[0010] In response to a simulation trigger event for the simulator area, display a simulated interaction page of the sub-application in the simulator area. The simulated interaction page is generated based on the sub-application page template and the sub-application components already added to the sub-application page template.

[0011] In a second aspect, the present application also provides a sub-application generation device. The device includes:

[0012] An interface display module, configured to display a sub-application development interface of a first application development platform, and display a template identifier of a sub-application page template provided by a second application development platform on the sub-application development interface;

[0013] A region display module, configured to, in response to an identifier selection operation on the template identifier, display an emulator region of the first application development platform and a configuration region provided by the second application development platform. The configuration region displays the sub-application page template and a plurality of sub-application components provided by the second application development platform;

[0014] An addition module, configured to, in response to a component selection operation of selecting among the plurality of sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template;

[0015] A page display module, configured to, in response to a simulation trigger event for the emulator region, display a simulation interaction page of the sub-application in the emulator region. The simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template.

[0016] In one embodiment, the region display module is further configured to, in response to an identifier selection operation on the template identifier, display a first application debugging interface. The first application debugging interface includes an emulator region provided by the first application development platform and a configuration region provided by the second application development platform.

[0017] In one embodiment, the first application debugging interface further includes a toolbar region provided by the first application development platform; the page display module is further configured to display an emulator trigger control in the toolbar region; and in response to a trigger operation on the emulator trigger control, display a simulation interaction page of the sub-application in the emulator region.

[0018] In one embodiment, a preview control is displayed in the toolbar region; the device further includes:

[0019] A graphic code display module, configured to, in response to a trigger operation on the preview control, display a first graphic code of the sub-application in the emulator region, so that when the first graphic code is scanned, the mother application of the terminal that scans the first graphic code runs the sub-application and displays a preview interaction page of the sub-application.

[0020] In one embodiment, a real device debugging control is displayed in the toolbar region; the device further includes:

[0021] A graphic code display module, which is used to respond to a triggering operation on the real machine debugging control, and display a second graphic code of the sub-application in the emulator area, so that when the second graphic code is scanned, the mother application of the terminal that scans the second graphic code runs the sub-application, and displays the interaction page of the sub-application and the running log of the sub-application.

[0022] In one embodiment, the area display module is further configured to respond to an identification selection operation on the template identifier, display the emulator area of the first application development platform, and display a second application debugging interface covering the emulator area; wherein, the second application debugging interface includes a configuration area provided by the second application development platform, and an interaction area other than the configuration area, and operations in the interaction area can act on the emulator area.

[0023] In one embodiment, the area display module is further configured to respond to an identification selection operation on the template identifier, and obtain a template plugin provided by a second application development platform bound to the template identifier;

[0024] Determine the plugin configuration file of the template plugin, determine the interface rendering method based on the plugin configuration file; according to the interface rendering method, display the emulator area of the first application development platform and the configuration area provided by the second application development platform.

[0025] In one embodiment, when the interface rendering method is embedded rendering, the area display module is further configured to display a first application debugging interface of the first application development platform, and the first application debugging interface includes the emulator area of the first application development platform and the configuration area provided by the second application development platform; when the interface rendering method is overlay rendering, display the emulator area of the first application development platform, and display a second application debugging interface covering the emulator area, and the second application debugging interface includes the configuration area provided by the second application development platform.

[0026] In one embodiment, the device further includes:

[0027] A generation module, which is used to, when the interface rendering method is embedded rendering, obtain the first layout information of the emulator area of the first application development platform; based on the first layout information of the emulator area, determine the second layout information of the configuration area provided by the second application development platform; based on the second layout information and the first layout information, generate the first application debugging interface of the first application development platform.

[0028] In one embodiment, the device further includes:

[0029] A generation module, configured to, when the interface rendering method is overlay rendering, obtain first layout information of the emulator area of the first application development platform; determine second layout information of the configuration area provided by the second application development platform based on the first layout information of the emulator area; obtain a second application debugging interface provided by the second application development platform based on the second layout information and the first layout information, where the second application debugging interface includes the configuration area and an interaction area; display the second application debugging interface, and display the emulator area covered by the interaction area of the second application debugging interface, and the layout of the emulator area is displayed in the interaction area.

[0030] In one embodiment, the device further includes:

[0031] An adjustment module, configured to, when detecting a first preset operation in the configuration area, adjust the view hierarchy of the second application debugging interface to be higher than that of the emulator area, so that after the view hierarchy is adjusted, operations on the configuration area can act on the configuration area;

[0032] When detecting a second preset operation in the interaction area, adjust the view hierarchy of the second application debugging interface to be lower than that of the emulator area, so that after the view hierarchy is adjusted, operations on the interaction area can act on the emulator area.

[0033] In one embodiment, the device further includes:

[0034] A project creation module, configured to run a project creation script built in the template plugin to obtain a sub-application project identifier; create a sub-application development project locally on the first application development platform based on the sub-application project identifier; generate an emulator area of the first application development platform and a configuration area provided by the second application development platform based on the sub-application development project.

[0035] In one embodiment, the device further includes:

[0036] A sub-application code acquisition module, configured to obtain sub-application code from the second application development platform based on the template plugin, where the sub-application code is generated based on the sub-application page template and sub-application components already added in the sub-application page template; store the sub-application code locally and run it to obtain a simulated interaction page of the sub-application.

[0037] In one embodiment, the interface display module is further configured to display at least one platform identifier of a second application development platform in the sub-application development interface; in response to an identifier selection operation of selecting an identifier from the at least one platform identifier, display a template identifier associated with the selected platform identifier in the sub-application development interface, where the template identifier is used to identify a sub-application page template provided by the second application development platform corresponding to the selected platform identifier.

[0038] In one embodiment, the interface display module is further configured to display a template category trigger control in the sub-application development interface; in response to a trigger operation on the template category trigger control, display at least one candidate template category in the sub-application development interface; in response to an identifier selection operation of selecting an identifier from the at least one platform identifier and a category selection operation of selecting a category from the at least one candidate template category, display a template identifier that belongs to the selected template category and is associated with the selected platform identifier in the sub-application development interface.

[0039] In one embodiment, the interface display module is further configured to display a platform category trigger control in the sub-application development interface; in response to a trigger operation on the platform category trigger control, display at least one platform category in the sub-application development interface; in response to a category selection operation of selecting a category from the at least one platform category, display platform identifiers of at least one second application development platform that belongs to the selected platform category in the sub-application development interface.

[0040] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0041] Display a sub-application development interface of a first application development platform, and display a template identifier of a sub-application page template provided by a second application development platform in the sub-application development interface;

[0042] In response to an identifier selection operation on the template identifier, display a simulator area of the first application development platform and a configuration area provided by the second application development platform. The configuration area displays the sub-application page template and a plurality of sub-application components provided by the second application development platform;

[0043] In response to a component selection operation of selecting a component from the plurality of sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template;

[0044] In response to a simulation trigger event for the simulator area, a simulation interaction page of the sub-application is displayed in the simulator area, and the simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template.

[0045] Fourthly, the present application also provides a computer-readable storage medium. On the computer-readable storage medium, there is a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0046] Display the sub-application development interface of the first application development platform, and display the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface;

[0047] In response to an identifier selection operation on the template identifier, display the simulator area of the first application development platform and the configuration area provided by the second application development platform. In the configuration area, the sub-application page template and multiple sub-application components provided by the second application development platform are displayed;

[0048] In response to a component selection operation of selecting among the multiple sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template;

[0049] In response to a simulation trigger event for the simulator area, a simulation interaction page of the sub-application is displayed in the simulator area, and the simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template.

[0050] Fifthly, the present application also provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0051] Display the sub-application development interface of the first application development platform, and display the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface;

[0052] In response to an identifier selection operation on the template identifier, display the simulator area of the first application development platform and the configuration area provided by the second application development platform. In the configuration area, the sub-application page template and multiple sub-application components provided by the second application development platform are displayed;

[0053] In response to a component selection operation of selecting among the multiple sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template;

[0054] In response to a simulation trigger event for the simulator area, a simulation interaction page of the sub-application is displayed in the simulator area, and the simulation interaction page is generated based on the sub-application page template and the sub-application components already added in the sub-application page template.

[0055] The above-mentioned sub-application generation method, device, computer device, storage medium, and computer program product display the sub-application development interface of the first application development platform to display the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface of the first application development platform, which can combine the first application development platform and the second application development platform, enabling users to select and use the page template provided by the second application development platform in the first application development platform to realize the generation of sub-applications. In response to the identifier selection operation on the template identifier, the simulator area of the first application development platform and the configuration area provided by the second application development platform are displayed. The configuration area provided by the second application development platform displays the sub-application page template provided by the second application development platform and multiple sub-application components provided by the second application development platform. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, enabling users to freely call the page templates and components of the third-party application development platform. In response to the component selection operation of selecting among multiple sub-application components, the sub-application component selected by the component selection operation is added to the sub-application page template. In response to the simulation trigger event for the simulator area, a simulation interaction page of the sub-application is displayed in the simulator area, and the simulation interaction page is generated based on the sub-application page template and the sub-application components already added in the sub-application page template. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, thereby expanding the development function of the sub-application through the first application development platform. Moreover, by visually selecting components to generate sub-applications, users do not need to write code, enabling users who do not understand code to also generate customized sub-applications, making the development of sub-applications simpler, and thus improving the development efficiency of sub-applications. Description of the Drawings

[0056] Figure 1 It is an application environment diagram of the sub-application generation method in an embodiment;

[0057] Figure 2 It is a flowchart of the sub-application generation method in an embodiment;

[0058] Figure 3 It is an interface diagram of displaying the template identifier in the sub-application development interface in an embodiment;

[0059] Figure 4 It is an interface diagram of displaying the simulator area and the configuration area in the same interface in another embodiment;

[0060] Figure 5 Schematic diagram of separately displaying the simulator area and the configuration area in different interfaces in another embodiment;

[0061] Figure 6 Schematic diagram of an interface showing the toolbar area, the simulator area, and the configuration area in one embodiment;

[0062] Figure 7 Schematic diagram of an interface where the second application debugging interface covers the native debugging area in one embodiment;

[0063] Figure 8 Schematic diagram of an interface where the project list page of the developer tool displays the template identifier in one embodiment;

[0064] Figure 9 Schematic diagram of the project creation logic customized by a third-party service provider in one embodiment;

[0065] Figure 10 Schematic diagram of scanning the QR code corresponding to the mini program by a mobile phone to display the mini program page in the mobile phone in one embodiment;

[0066] Figure 11 Sequence diagram of creating a mini program project in one embodiment;

[0067] Figure 12 Schematic diagram of the first application debugging interface generated by the embedded rendering method in one embodiment;

[0068] Figure 13 Sequence diagram of the developer tool generating a mini program after creating a mini program project in one embodiment;

[0069] Figure 14 Block diagram of the sub-application generation device in one embodiment;

[0070] Figure 15 Internal structure diagram of a computer device in one embodiment. Detailed implementation manners

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

[0072] The sub-application generation method provided by the embodiments of this application can be applied to the generation of various types of sub-applications and can be used in various scenarios such as cloud technology, artificial intelligence, intelligent transportation, and assisted driving. For example, for a navigation sub-application, the generated sub-application is used to provide navigation functions for users. The sub-application generation method provided by this application is at least related to the following technologies: intelligent transportation systems, intelligent vehicle-road collaborative systems, computer vision technologies, etc.

[0073] An Intelligent Traffic System (ITS), also known as an Intelligent Transportation System, is an integrated transportation system that effectively combines advanced scientific and technological means (information technology, computer technology, data communication technology, sensor technology, electronic control technology, automatic control theory, operations research, artificial intelligence, etc.) in transportation, service control, and vehicle manufacturing to strengthen the connection among vehicles, roads, and users, thereby forming a comprehensive transportation system that ensures safety, improves efficiency, enhances the environment, and saves energy. Or;

[0074] An Intelligent Vehicle Infrastructure Cooperative Systems (IVICS), abbreviated as a vehicle-road collaborative system, is a development direction of an Intelligent Traffic System (ITS). A vehicle-road collaborative system uses advanced wireless communication and new-generation Internet technologies to comprehensively implement dynamic real-time information interaction between vehicles and between vehicles and roads, and based on the collection and fusion of full-time and full-space dynamic traffic information, it conducts active vehicle safety control and road collaborative management, fully realizing the effective collaboration of people, vehicles, and roads, ensuring traffic safety, improving traffic efficiency, and thus forming a safe, efficient, and environmentally friendly road traffic system.

[0075] The sub-application generation method provided by the embodiments of this application can be applied, for example, to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or can be placed on the cloud or other servers. The terminal 102 displays the sub-application development interface of the first application development platform, and the template identifier of the sub-application page template provided by the second application development platform is displayed on the sub-application development interface. The page template and the template identifier of the page template can be stored in the server 104. In response to the identifier selection operation on the template identifier, the terminal 102 displays the simulator area of the first application development platform and the configuration area provided by the second application development platform. The configuration area displays the sub-application page template and multiple sub-application components provided by the second application development platform. The multiple sub-application components can be stored in the server 104. In response to the component selection operation of selecting in the multiple sub-application components, the terminal 102 adds the sub-application component selected by the component selection operation to the sub-application page template. In response to the simulation trigger event for the simulator area, the terminal 102 displays the simulation interaction page of the sub-application in the simulator area. The simulation interaction page is generated based on the sub-application page template and the sub-application components already added to the sub-application page template.

[0076] Among them, the terminal 102 can be, but is not limited to, various desktop computers, laptop computers, smart phones, tablet computers, Internet of Things devices, and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0077] In one embodiment, as Figure 2 shown, a method for generating a sub-application is provided. Taking the terminal in Figure 1 as an example, the method includes the following steps:

[0078] Step S202, display the sub-application development interface of the first application development platform, and display the template identifier of the sub-application page template provided by the second application development platform on the sub-application development interface.

[0079] Among them, the first application development platform refers to a platform that provides development services for sub-applications. The first application development platform refers to a tool for assisting developers in developing and debugging sub-applications.

[0080] The second application development platform is also a platform that provides development services for sub-applications. The second application development platform is different from the first application development platform.

[0081] A sub - application page template refers to a page that allows for arrangement and editing. Developers can implement the editing of sub - application functions on this sub - application page template. The template identifier is used to identify the sub - application page template. Specifically, the template identifier can be at least a part of the content of the sub - application page template, it can be a thumbnail of the sub - application page template, or the name, number, etc. of the sub - application page template, but is not limited to this.

[0082] A sub - application refers to an application that cannot run independently and needs to rely on other applications to run, that is, the sub - application runs within the parent application.

[0083] A sub - application can refer to an application program that does not require installation, that is, an application program that can be used without downloading and installation. Such application programs usually run as sub - programs in the client, and this client is called the parent application.

[0084] Sub - applications include, but are not limited to, instant messaging applications, short - video applications, long - video applications, game applications, music sharing applications, shopping and selling applications, UGC (User Generated Content) applications, various intelligent recognition applications, etc., but are not limited to this.

[0085] This sub - application can also be a cloud application. A cloud application refers to an application that runs in the cloud. A cloud application refers to an application that interacts between the terminal and the cloud. The running mode of a cloud application is to encode the running process as an audio - video stream through the powerful computing power of the cloud simulator and transmit it to the terminal through the network to achieve interaction with users.

[0086] The cloud refers to the cloud server, also known as the cloud computing server. A cloud server is based on a large - scale distributed computing system, and integrates computer resources through virtualization technology to provide services for Internet infrastructure. The network that provides resources is called the "cloud". The resources in the "cloud" seem to be infinitely expandable to users, and can be obtained at any time, used on demand, expanded at any time, and paid according to usage. Cloud computing is a computing model that distributes computing tasks on a resource pool composed of a large number of computers, enabling various application systems to obtain computing power, storage space, and information services according to needs.

[0087] In this embodiment, the first application development platform can also be a sub - application or a parent application. The second application development platform can also be a sub - application or a parent application.

[0088] Specifically, the user can log in to the first application development platform running on the terminal through the application development account. The terminal displays the sub - application development interface of the first application development platform, and at least one template identifier is displayed on the sub - application development interface. Each template identifier is used to identify a sub - application page template, and the sub - application page template is provided by the second application development platform. For example Figure 3As shown, multiple template identifiers 304 provided by the second application development platform 302 are displayed in the sub-application development interface 300.

[0089] In this embodiment, the number of sub-application page templates can be set as needed. The sub-application page template can be a blank page or a page with some components pre-configured.

[0090] Step S204: In response to an identifier selection operation on the template identifier, display the simulator area of the first application development platform and the configuration area provided by the second application development platform. The configuration area displays the sub-application page template and multiple sub-application components provided by the second application development platform.

[0091] Among them, the identifier selection operation is a preset operation on the template identifier. Detecting the identifier selection operation will trigger the selection of the corresponding template identifier. The identifier selection operation can specifically be a touch operation, a cursor operation, a button operation, or a voice operation. The touch operation can be a touch click operation, a touch press operation, or a touch slide operation. The touch operation can be a single-point touch operation or a multi-point touch operation; the cursor operation can be an operation of controlling the cursor to click or an operation of controlling the cursor to press; the button operation can be a virtual button operation or a physical button operation, etc.

[0092] The simulator area is a display area provided by the first application development platform for debugging the generated sub-application. The simulator area can be a pop-up window, a floating layer, an independent interface, or a partial area in an independent interface.

[0093] The configuration area is a display area provided by the second application development platform for displaying the sub-application page template and multiple sub-application components. The configuration area can be a pop-up window, a floating layer, an independent interface, or a partial area in an independent interface.

[0094] Specifically, the terminal, in response to the developer's identifier selection operation on the template identifier, determines the template identifier selected by the identifier selection operation, and feeds back to the second application development platform through the first application development platform the template identifier selected by the identifier selection operation. The second application development platform determines the sub-application page template identified by the fed-back template identifier based on the fed-back template identifier.

[0095] The terminal displays the simulator area of the first application development platform and displays the configuration area provided by the second application development platform. The configuration area displays the sub-application page template identified by the selected template identifier, as well as multiple sub-application components provided by the second application development platform.

[0096] In this embodiment, the terminal can display the simulator area and the configuration area on the same screen. Displaying the simulator area and the configuration area on the same screen can be to display the simulator area and the configuration area in the same interface, such as Figure 4As shown. It can also be that the simulator area and the configuration area are respectively displayed in two interfaces on the same screen, such as Figure 5 As shown.

[0097] In this embodiment, the terminal responds to the developer's identification selection operation on the template identifier, displays the simulator area in the second application development platform, jumps from the first application development platform to the second application development platform, and displays the configuration area in the second application development platform. The configuration area displays the sub-application page template identified by the selected template identifier, as well as multiple sub-application components provided by the second application development platform.

[0098] In this embodiment, in response to the identification selection operation on the template identifier, the sub-application page template represented by the template identifier selected by the identification selection operation is displayed in the sub-application development interface. In response to the completion event of the selection of the template identifier, the simulator area and the configuration area are displayed.

[0099] Step S206, in response to the component selection operation of selecting among multiple sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template.

[0100] Specifically, the terminal displays multiple available sub-application components and the sub-application page template identified by the selected template identifier in the configuration area. The developer can select the components to be used among the multiple sub-application components and add the selected components to the sub-application page template. The terminal receives the component selection operation of the developer selecting among the multiple sub-application components, determines the sub-application component selected by the component selection operation, and adds the sub-application component to the sub-application page template.

[0101] In this embodiment, the component selection operation includes but is not limited to long press, click, slide, move, and multi-touch operations. Adding the component to the sub-application page template means copying the sub-application component selected by the developer from the component library interface to the sub-application page template.

[0102] For example, the developer can select the sub-application components to be used among the multiple sub-application components and move the sub-application components to be used to the sub-application page template. The terminal detects the movement operation of the developer on the sub-application component, determines the movement trajectory corresponding to the movement operation, and moves the sub-application component to the sub-application page template according to the movement trajectory.

[0103] Step S208, in response to the simulation trigger event for the simulator area, display the simulation interaction page of the sub-application in the simulator area, and the simulation interaction page is generated based on the sub-application page template and the sub-application components already added to the sub-application page template.

[0104] Among them, the simulated trigger event is an event used to trigger the debugging of the sub-application. The simulated trigger event can specifically be a touch operation, a cursor operation, a key operation, or a voice operation.

[0105] The simulator area is the display area where the sub-application runs on the parent application through simulation by the simulator. The simulator is provided by the first application development platform and can simulate the operation of the parent application on the sub-application.

[0106] In this embodiment, the simulated interaction page of the sub-application is generated based on the native code of the page template and the components already added in the page template. The native code is generated by the second application development platform.

[0107] Specifically, in response to the simulated trigger event for the simulator area, the terminal displays the simulated interaction page of the sub-application in the simulator area. The simulated interaction page is generated based on the sub-application page template and the sub-application components already added in the sub-application page template.

[0108] In this embodiment, the sub-application is generated by the second application development platform. The second application development platform generates the sub-application based on the sub-application page template and the sub-application components already added in the sub-application page template in the configuration interface. In response to the simulated trigger event for the simulator area, the terminal loads and runs the sub-application on the first application development platform through the simulator, so as to display the simulated interaction page of the sub-application in the simulator area.

[0109] In this embodiment, the sub-application development interface of the first application development platform is displayed, and the template identifier of the sub-application page template provided by the second application development platform is displayed in the sub-application development interface of the first application development platform, which can combine the first application development platform and the second application development platform, enabling users to select and use the page template provided by the second application development platform on the first application development platform to generate sub-applications. In response to the identifier selection operation on the template identifier, the simulator area of the first application development platform and the configuration area provided by the second application development platform are displayed. The configuration area provided by the second application development platform displays the sub-application page template provided by the second application development platform and multiple sub-application components provided by the second application development platform. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, allowing users to freely call the page templates and components of the third-party application development platform. In response to the component selection operation of selecting among multiple sub-application components, the sub-application component selected by the component selection operation is added to the sub-application page template. In response to the simulation trigger event for the simulator area, the simulation interaction page of the sub-application is displayed in the simulator area. The simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, thereby expanding the development function of the sub-application through the first application development platform. Moreover, by visually selecting components to generate sub-applications, users do not need to write code, enabling users who do not understand code to also generate customized sub-applications, making the development of sub-applications simpler, and thus improving the development efficiency of sub-applications.

[0110] In one embodiment, in response to the identifier selection operation on the template identifier, displaying the simulator area of the first application development platform and the configuration area provided by the second application development platform includes:

[0111] In response to the identifier selection operation on the template identifier, the first application debugging interface is displayed. The first application debugging interface includes the simulator area provided by the first application development platform and the configuration area provided by the second application development platform.

[0112] Specifically, the terminal, in response to the developer's identifier selection operation on the template identifier, determines the template identifier selected by the identifier selection operation and determines the sub-application page template represented by the selected template identifier. The template identifier and the sub-application page template are provided by the second application development platform.

[0113] The terminal displays a first application debugging interface provided by the first application development platform. The first application debugging interface includes an emulator area provided by the first application development platform and a configuration area provided by the second application development platform. The terminal displays a sub-application page template provided by the second application development platform in the configuration area and also displays a plurality of sub-application components provided by the second application development platform.

[0114] Developers can select components from the multiple sub-application components displayed in the configuration area to add the sub-application components selected by the component selection operation to the sub-application page template. Through the second application development platform, a sub-application is generated based on the sub-application page template and the sub-application components already added to the sub-application page template.

[0115] In response to a simulation trigger event by the developer for the emulator area, a simulation interaction page of the sub-application is displayed in the emulator area.

[0116] In this embodiment, in response to an identification selection operation on the template identification, the first application debugging interface provided by the first application development platform is displayed, so that the emulator area provided by the first application development platform and the configuration area provided by the second application development platform can be simultaneously displayed in the first application debugging interface. This enables the sub-application configured by the developer in the configuration area to run in the emulator area. Developers can configure and debug the sub-application in the same interface, making the development of the sub-application simpler and conducive to improving the user experience.

[0117] In one embodiment, the first application debugging interface further includes a toolbar area provided by the first application development platform; in response to a simulation trigger event for the emulator area, displaying a simulation interaction page of the sub-application in the emulator area includes:

[0118] Displaying an emulator trigger control in the toolbar area; in response to a trigger operation on the emulator trigger control, displaying a simulation interaction page of the sub-application in the emulator area.

[0119] Among them, the emulator trigger control is an interactive element displayed in the toolbar area and available for user operation. An interactive element is a visual element. A visual element refers to an element that can be displayed and is visible to the human eye for conveying information. The manifestation forms of interactive elements are diverse. For example, it can be at least one of a control, an image, text, an identification, a link, or an animation file, but not limited to this. A control can be a button, a text box, a radio box, or an option group.

[0120] The emulator trigger control is a control used to trigger the display of a simulation interaction page of the sub-application in the emulator area. The simulation interaction page refers to the interaction page of the sub-application displayed in the emulator area when simulating the operation of the sub-application.

[0121] The first application debugging interface further includes a toolbar area provided by the first application development platform, and a simulator trigger control is displayed in the toolbar area.

[0122] Specifically, in response to an identification selection operation on a template identifier, the terminal displays a first application debugging interface including a toolbar area, a simulator area, and a configuration area. Among them, the toolbar area and the simulator area are provided by the first application development platform, and the configuration area is provided by the second application development platform.

[0123] A simulator trigger control is displayed in the toolbar area. When a developer triggers the simulator trigger control, the running environment of the sub-application can be simulated through the simulator of the first application development platform, so as to run the sub-application generated based on the sub-application page template and the added components in the configuration area, and then the simulated interaction page of the sub-application is displayed in the simulator area.

[0124] In one embodiment, the developer can perform interaction operations on the simulated interaction page to test the generated sub-application.

[0125] In this embodiment, the toolbar area and the simulator area provided by the first application development platform, and the configuration area provided by the second application development platform can be displayed in the first application debugging interface of the first application development platform, so that the developer can directly use the functions of other development platforms in the first application development platform, and the functions used can still be implemented by other development platforms. Therefore, the services provided by the second application development platform can be combined into the first application development platform, greatly improving the sub-application development ability of the first application development platform.

[0126] In one embodiment, a preview control is displayed in the toolbar area; the method further includes:

[0127] In response to a trigger operation on the preview control, a first graphic code of the sub-application is displayed in the simulator area, so that when the first graphic code is scanned, the mother application of the terminal that scans the first graphic code runs the sub-application and displays the preview interaction page of the sub-application.

[0128] Specifically, a preview control is displayed in the toolbar area, and the preview control is used to trigger the preview of the interaction page of the sub-application.

[0129] In response to a component selection operation in which a developer selects among multiple sub-application components, the sub-application components selected by the component selection operation are added to the sub-application page template. The terminal generates a sub-application based on the sub-application page template and the sub-application components already added to the sub-application page template through the second application development platform.

[0130] The terminal generates a first graphic code of a sub - application through a first application development platform. When the developer triggers the preview control displayed in the toolbar area, the terminal, in response to the triggering operation on the preview control, displays the first graphic code of the sub - application in the emulator area.

[0131] The developer can scan the first graphic code through the parent application of another terminal to run the sub - application through the parent application of the terminal that scans the first graphic code and display the preview interaction page of the sub - application. The preview interaction page refers to the page of the sub - application in the preview state.

[0132] In this embodiment, the preview interaction page does not support interaction operations, that is, the preview interaction page can only be viewed and cannot be operated.

[0133] In this embodiment, in response to the triggering operation on the preview control, the first graphic code of the sub - application is displayed in the emulator area so that when the first graphic code is scanned, the sub - application runs through the parent application of the terminal that scans the first graphic code and the preview interaction page of the sub - application is displayed, enabling the generated sub - application to run and be previewed on other terminals, thus ensuring that the sub - application can run on a real device and the running effect of the sub - application on the real device can be presented.

[0134] In one embodiment, a real - device debugging control is displayed in the toolbar area; the method further includes:

[0135] In response to the triggering operation on the real - device debugging control, a second graphic code of the sub - application is displayed in the emulator area so that when the second graphic code is scanned, the sub - application runs through the parent application of the terminal that scans the second graphic code and the interaction page and the running log of the sub - application are displayed.

[0136] Specifically, a real - device debugging control is displayed in the toolbar area. The terminal, in response to the component selection operation where the developer selects among multiple sub - application components, adds the sub - application components selected by the component selection operation to the sub - application page template. The terminal, through a second application development platform, generates a sub - application based on the sub - application page template and the sub - application components already added to the sub - application page template.

[0137] The terminal generates a second graphic code of the sub - application through the first application development platform. When the developer triggers the real - device debugging control displayed in the toolbar area, the terminal, in response to the developer's triggering operation on the real - device debugging control, displays the second graphic code of the sub - application in the emulator area.

[0138] The developer can scan the second graphic code through the parent application of another terminal to run the sub - application through the parent application of the terminal that scans the second graphic code and display the interaction page of the sub - application. This interaction page supports interaction operations, and the developer can operate on this interaction page to test the relevant functions in the interaction page.

[0139] Moreover, the running logs of the sub - application are also displayed through the parent application of the terminal that scans the second QR code, enabling developers to test the relevant functions of the generated sub - application on a real device and view the running logs of the sub - application.

[0140] In this embodiment, when the parent application of the terminal that scans the second QR code runs the sub - application and displays the interaction page of the sub - application, developers can perform interaction operations on the interaction page and generate operation records based on the interaction operations, thereby generating the running logs of the sub - application.

[0141] In this embodiment, in response to the triggering operation on the real - device debugging control, the second QR code of the sub - application is displayed in the emulator area. When the second QR code is scanned, the parent application of the terminal that scans the second QR code runs the sub - application, enabling the sub - application to run on the real device to present the running effect of the sub - application on the real device. Moreover, by displaying the interaction page and the running logs of the sub - application, the relevant functions of the sub - application can be tested on the real device, and it is convenient for developers to directly view the running logs of the sub - application on the real device, thereby improving the debugging efficiency of the sub - application.

[0142] In one embodiment, as Figure 6 shown, the toolbar area 602 displays the emulator trigger control 604, the preview control 606, and the real - device debugging control 608. After developers add them to the sub - application page template 612 in the configuration area 610, they can trigger the emulator trigger control 604 to display the simulated interaction page 616 of the sub - application in the emulator area 614.

[0143] When developers trigger the preview control, the first QR code of the sub - application is displayed in the emulator area. When the first QR code is scanned, the parent application of the terminal that scans the first QR code runs the sub - application and displays the preview interaction page of the sub - application. When developers trigger the real - device debugging control, the second QR code of the sub - application is displayed in the emulator area. When the second QR code is scanned, the parent application of the terminal that scans the second QR code runs the sub - application and displays the interaction page and the running logs of the sub - application.

[0144] In one embodiment, in response to the identification selection operation on the template identification, the emulator area of the first application development platform and the configuration area provided by the second application development platform are displayed, including:

[0145] In response to the identification selection operation on the template identification, the emulator area of the first application development platform is displayed, and the second application debugging interface covering the emulator area is also displayed; wherein, the second application debugging interface includes the configuration area provided by the second application development platform and the interaction area other than the configuration area, and the operations in the interaction area can act on the emulator area.

[0146] Specifically, in response to the developer's identification selection operation on the template identifier, the terminal determines the template identifier selected by the identification selection operation and determines the sub-application page template represented by the selected template identifier. The template identifier and the sub-application page template are provided by the second application development platform.

[0147] The terminal displays the simulator area of the first application development platform and displays the second application debugging interface covering the simulator area. The second application debugging interface is provided by the second application development platform.

[0148] The second application debugging interface includes a configuration area provided by the second application development platform. The terminal displays the sub-application page template provided by the second application development platform in this configuration area and displays multiple sub-application components provided by the second application development platform.

[0149] The area in the second application debugging interface and the area other than the configuration area serves as the interaction area. Since the second application debugging interface covers the simulator area, when the developer wants to operate on the simulator area, it can be achieved through the operation on the interaction area. That is, the operation of the developer in the interaction area can act on the simulator area.

[0150] In this embodiment, the interaction area covers the simulator area provided by the first application development platform. The simulator area is at the lower layer of the interaction area and can be displayed through the interaction area. For example, the interaction area is a transparent area. When the interaction area covers the simulator area, the simulator area can be displayed through the interaction area, enabling the operation of the developer in the interaction area to act on the corresponding position of the simulator area.

[0151] In this embodiment, as Figure 7 shown, in response to the identification selection operation on the template identifier, the native debugging area of the first application development platform is displayed, and the second application debugging interface covering the native debugging area is displayed. Among them, the native debugging area includes the simulator area and the toolbar area of the first application development platform; the second application debugging interface includes the configuration area provided by the second application development platform and the interaction area other than the configuration area. The operation in the interaction area can act on the native debugging area. The interaction area covers the native debugging area of the first application development platform. The native debugging area is at the lower layer of the interaction area and can be displayed through the interaction area, enabling the operation of the developer in the interaction area to act on the corresponding position of the native debugging area.

[0152] In this embodiment, in response to an identification selection operation on a template identifier, the simulator area of the first application development platform is displayed, and a second application debugging interface covering the simulator area is displayed. The second application debugging interface includes a configuration area provided by the second application development platform and an interaction area other than the configuration area, so that the display freedom of the configuration area is higher. Operations in the interaction area can act on the simulator area, enabling operations on the simulator area from the interaction area, and enabling configuration in the configuration area and operations on the simulator area to be realized on the same interface, effectively expanding the functions of the first application development platform, making the interface display more flexible, and meeting the needs of different users.

[0153] In one embodiment, in response to an identification selection operation on a template identifier, displaying the simulator area of the first application development platform and the configuration area provided by the second application development platform includes:

[0154] In response to an identification selection operation on a template identifier, obtain a template plugin provided by the second application development platform bound to the template identifier; determine the plugin configuration file of the template plugin, and determine the interface rendering method based on the plugin configuration file; according to the interface rendering method, display the simulator area of the first application development platform and the configuration area provided by the second application development platform.

[0155] Among them, the interface rendering methods include embedded rendering and overlay rendering. Embedded rendering means that the configuration area provided by the second application development platform is embedded in the first application debugging interface of the first application development platform. That is, embedded rendering means that the configuration area provided by the second application development platform and the simulator area of the first application development platform are both embedded in the first application debugging interface of the first application development platform.

[0156] When the first application development platform provides a toolbar area, this embedded rendering means that the configuration area provided by the second application development platform, the toolbar area, and the simulator area of the first application development platform are all embedded in the first application debugging interface of the first application development platform.

[0157] Overlay rendering means that the second application debugging interface provided by the second application development platform covers the simulator area provided by the first application development platform, and the second application debugging interface includes a configuration area.

[0158] When the first application development platform provides a toolbar area, this overlay rendering means that the second application debugging interface provided by the second application development platform covers the simulator area and the toolbar area provided by the first application development platform.

[0159] The template plugin is a program written according to a certain specification of the application programming interface. The template plugin is defined and written by the first application development platform.

[0160] Specifically, in response to the developer's identification selection operation on the template identifier, the terminal determines the template identifier selected by the identification selection operation and determines the template plugin provided by the second application development platform bound to the template identifier. The terminal determines the plugin configuration file of the template plugin, and the interface rendering method provided by the second application development platform is defined in the plugin configuration file. The terminal determines the interface rendering method from the plugin configuration file, and the terminal performs interface rendering according to the interface rendering method to obtain the simulator area of the first application development platform and the configuration area provided by the second application development platform. The terminal displays the simulator area of the first application development platform and the configuration area provided by the second application development platform.

[0161] In this embodiment, in response to the identification selection operation on the template identifier, the template plugin provided by the second application development platform bound to the template identifier is obtained, so as to determine the interface rendering method based on the plugin configuration file of the template plugin, so that the simulator area of the first application development platform and the configuration area provided by the second application development platform can be automatically rendered according to the interface rendering method defined by the second application development platform.

[0162] In one embodiment, displaying the simulator area of the first application development platform and the configuration area provided by the second application development platform according to the interface rendering method includes:

[0163] When the interface rendering method is embedded rendering, display the first application debugging interface of the first application development platform, and the first application debugging interface includes the simulator area of the first application development platform and the configuration area provided by the second application development platform; when the interface rendering method is overlay rendering, display the simulator area of the first application development platform, and display the second application debugging interface provided by the first application development platform covering the simulator area, and the second application debugging interface includes the configuration area provided by the second application development platform.

[0164] Specifically, when the interface rendering method is embedded rendering, the terminal generates the first application debugging interface of the first application development platform, and displays the simulator area of the first application development platform and the configuration area provided by the second application development platform in the first application debugging interface. Further, the first application debugging interface includes the simulator area and the toolbar area of the first application development platform, and the configuration area provided by the second application development platform.

[0165] When the interface rendering method is overlay rendering, the terminal displays the simulator area of the first application development platform, and displays the second application debugging interface provided by the first application development platform covering the simulator area. The second application debugging interface includes the configuration area provided by the second application development platform. Further, the second application debugging interface covers the simulator area and the toolbar area of the first application development platform.

[0166] In this embodiment, when the interface rendering method is embedded rendering, the first application debugging interface of the first application development platform is displayed. The first application debugging interface includes the native debugging area of the first application development platform and the configuration area provided by the second application development platform. The native debugging area includes the emulator area and the toolbar area. When the interface rendering method is overlay rendering, the native debugging area of the first application development platform is displayed, and the second application debugging interface overlaid on the native debugging area is displayed. The second application debugging interface includes the configuration area provided by the second application development platform.

[0167] In this embodiment, two interface rendering methods defined by the second application development platform are provided, so that the emulator area and the configuration area can be automatically rendered in the first application development platform according to the interface rendering methods defined by the second application development platform. When the interface rendering method is embedded rendering, the emulator area of the first application development platform and the configuration area provided by the second application development platform are rendered and displayed in the same interface, which is convenient for developers to configure the page and view the interaction page of the sub-application formed by the configuration at the same time. When the interface rendering method is overlay rendering, the emulator area of the first application development platform is displayed, and the second application debugging interface overlaid on the emulator area is displayed. The second application debugging interface includes the configuration area provided by the second application development platform, so that the display freedom of the configuration area is higher, the content in the configuration area can be displayed more completely, and it is convenient for developers to operate.

[0168] In one embodiment, the method further includes:

[0169] When the interface rendering method is embedded rendering, obtain the first layout information of the emulator area of the first application development platform; based on the first layout information of the emulator area, determine the second layout information of the configuration area provided by the second application development platform; based on the second layout information and the first layout information, generate the first application debugging interface of the first application development platform.

[0170] The first layout information refers to the information related to the layout of the emulator area of the first application development platform, including the display position, display size, etc. of the emulator area. The second layout information refers to the information related to the layout of the configuration area provided by the second application development platform, including the display position, display size, etc. of the configuration area.

[0171] Specifically, when the interface rendering method is embedded rendering, the terminal can obtain the first layout information of the emulator area provided by the first application development platform. The terminal can obtain the original layout information of the configuration area provided by the second application development platform from the second application development platform, and determine the second layout information of the configuration area based on the first layout information of the emulator area and the original layout information.

[0172] Among them, the original layout information of the configuration area refers to the layout information of the configuration area provided by the second application development platform. The second layout information of the configuration area is the layout information formed after adjusting the original layout information based on the first layout information.

[0173] The terminal generates a first application debugging interface for the first application development platform based on the second layout information and the first layout information.

[0174] In this embodiment, the terminal sends the second layout information and the first layout information to the first server corresponding to the first application development platform. Through the first server, a first application debugging interface for the first application development platform is generated based on the second layout information and the first layout information.

[0175] In this embodiment, the terminal sends the first layout information and the original layout information to the first server corresponding to the first application development platform. Through the first server, the original layout information is adjusted based on the first layout information to obtain the second layout information. Through the first server, a first application debugging interface is generated based on the second layout information and the first layout information.

[0176] In one embodiment, when the interface rendering method is embedded rendering, the first layout information of the simulator area and the third layout information of the toolbar area of the first application development platform are obtained; based on the first layout information of the simulator area and the third layout information of the toolbar area, the second layout information of the configuration area provided by the second application development platform is determined; based on the first layout information, the second layout information, and the third layout information, a first application debugging interface for the first application development platform is generated, so that the first application debugging interface can accommodate the simulator area, the toolbar area, and the configuration area.

[0177] Furthermore, the terminal sends the first layout information, the second layout information, and the third layout information to the first server corresponding to the first application development platform. Through the first server, a first application debugging interface for the first application development platform is generated based on the first layout information, the second layout information, and the third layout information.

[0178] In this embodiment, when the interface rendering method is embedded rendering, the first layout information of the simulator area of the first application development platform is obtained, and based on the first layout information of the simulator area, the second layout information of the configuration area provided by the second application development platform is determined, so that a first application debugging interface that can embed the simulator area and the configuration area is accurately generated based on the second layout information and the first layout information.

[0179] In one embodiment, when the interface rendering method is overlay rendering, the simulator area of the first application development platform is displayed, and a second application debugging interface overlaid on the simulator area is displayed, including:

[0180] When the interface rendering method is overlay rendering, obtain the first layout information of the emulator area of the first application development platform; based on the first layout information of the emulator area, determine the second layout information of the configuration area provided by the second application development platform; based on the second layout information and the first layout information, obtain the second application debugging interface provided by the second application development platform, and the second application debugging interface includes a configuration area and an interaction area; display the second application debugging interface, and display the emulator area covered by the interaction area of the second application debugging interface, and the layout of the emulator area is displayed in the interaction area.

[0181] Specifically, when the interface rendering method is overlay rendering, the terminal obtains the first layout information of the emulator area of the first application development platform. The terminal can obtain the original layout information of the configuration area provided by the second application development platform from the second application development platform, and based on the first layout information of the emulator area and the original layout information, determine the second layout information of the configuration area. The terminal can send the second layout information and the first layout information to the second server corresponding to the second application development platform, and the second server generates the second application debugging interface of the second application development platform based on the second layout information and the first layout information. The second application debugging interface includes a configuration area and an interaction area other than the configuration area.

[0182] The terminal displays the second application debugging interface, and displays the emulator area covered by the interaction area of the second application debugging interface, and the layout of the emulator area is displayed through the interaction area. That is, the emulator area is below the interaction area and can be displayed through the interaction area.

[0183] In this embodiment, when the interface rendering method is overlay rendering, displaying the emulator area of the first application development platform and displaying the second application debugging interface covering the emulator area includes:

[0184] When the interface rendering method is overlay rendering, send the first layout information of the emulator area of the first application development platform to the second server corresponding to the second application development platform; the first layout information is used to instruct the second server to determine the second layout information of the configuration area and generate the second application debugging interface based on the second layout information and the first layout information;

[0185] Display the emulator area of the first application development platform and display the second application debugging interface covering the emulator area. The emulator area is below the interaction area and is displayed through the interaction area.

[0186] In one embodiment, the developer can operate in the configuration area of the second application debugging interface so that the operations performed can directly act on the configuration area. The developer can operate in the interaction area of the second application debugging interface so that the operations performed can act on the emulator area.

[0187] In this embodiment, when the interface rendering method is overlay rendering, obtain the first layout information of the emulator area of the first application development platform. Based on the first layout information of the emulator area, determine the second layout information of the configuration area provided by the second application development platform. Based on the second layout information and the first layout information, obtain a second application debugging interface including the configuration area and the interaction area. Thus, when the second application debugging interface and the emulator area are displayed, the emulator area covered by the interaction area of the second application debugging interface can be displayed through this interaction area, enabling developers to see the displayed simulated interaction page in the covered emulator area.

[0188] In one embodiment, the method further includes:

[0189] When a first preset operation in the configuration area is detected, adjust the view hierarchy of the second application debugging interface to be higher than that of the emulator area, so that after the view hierarchy is adjusted, operations on the configuration area can act on the configuration area; when a second preset operation in the interaction area is detected, adjust the view hierarchy of the second application debugging interface to be lower than that of the emulator area, so that after the view hierarchy is adjusted, operations on the interaction area can act on the emulator area.

[0190] Specifically, when the interface rendering method is overlay rendering, display the second application debugging interface and display the emulator area covered by the interaction area of the second application debugging interface. The terminal can detect the operations of the developer. When an operation in the configuration area is detected and this operation is the first preset operation, indicating that the developer needs to perform relevant configuration operations in the configuration area, the terminal adjusts the view hierarchy of the second application debugging interface to be higher than that of the emulator area. When the view hierarchy of the second application debugging interface is higher than that of the emulator area, the operations of the developer in the configuration area can directly act on the configuration area.

[0191] When the view hierarchy of the second application debugging interface is lower than that of the emulator area, the operations of the developer in the interaction area of the second application debugging interface can act on the emulator area.

[0192] When an operation in the interaction area is detected and this operation is the second preset operation, indicating that the developer wants to perform relevant operations on the emulator area, the terminal adjusts the view hierarchy of the second application debugging interface to be lower than that of the emulator area. After adjusting the view hierarchy of the emulator area, in response to the operations of the developer in the interaction area, apply this operation to the emulator area.

[0193] Further, after adjusting the view hierarchy of the simulator area, in response to an operation by the developer in the interaction area, determine the interaction position of the operation in the interaction area, determine the corresponding position of the interaction position in the simulator area, and apply the operation to the corresponding position in the simulator area. For example, there is a control A in the simulator area, and the developer can see the control A in the simulator area on the interaction area. The developer clicks on position a on the interaction area, and this position a is the position of the control A in the simulator area that the developer sees in the interaction area. Then the terminal applies the click operation to the control A in the simulator area and executes the function corresponding to the control A.

[0194] In this embodiment, the method further includes:

[0195] When detecting a first preset operation in the configuration area, adjust the view hierarchy of the second application debugging interface to be higher than the view hierarchy of the native debugging area, so that after the view hierarchy is adjusted, the operation on the configuration area can act on the configuration area; when detecting a second preset operation in the interaction area, adjust the view hierarchy of the second application debugging interface to be lower than the view hierarchy of the native debugging area, so that after the view hierarchy is adjusted, the operation on the interaction area can act on the native debugging area. The native debugging area includes a simulator area and a toolbar area.

[0196] For example, in order for the developer to operate the native debugging area and the configuration area simultaneously, when the mouse moves to the configuration area, the view hierarchy of the second application debugging interface will automatically be moved to the top layer. At this time, the plugin needs to detect the mouse event by itself. When the mouse moves into the interaction area, call the preset interface provided by the first application development platform to lower the view hierarchy of the second application debugging interface, so that the operation event in the interaction area can penetrate the interaction area and thus act on the native debugging area, so that the developer can also normally click on the relevant controls in the native debugging area.

[0197] In this embodiment, when detecting a first preset operation in the configuration area, it means that the developer needs to perform relevant configuration operations in the configuration area, then adjust the view hierarchy of the second application debugging interface to be higher than the view hierarchy of the simulator area, so that after the view hierarchy is adjusted, the developer can directly perform operations in the configuration area. When detecting a second preset operation in the interaction area, it means that the developer wants to perform relevant operations on the simulator area, then adjust the view hierarchy of the second application debugging interface to be lower than the view hierarchy of the simulator area, so that after the view hierarchy is adjusted, the operation of the developer on the interaction area can act on the simulator area, so that in the case where the second application debugging interface covers the simulator area, the developer can still normally use the functions of the simulator area.

[0198] In one embodiment, the method further includes:

[0199] Run the project creation script built into the template plugin to obtain the sub-application project identifier; based on the sub-application project identifier, create a sub-application development project locally on the first application development platform; based on the sub-application development project, generate the simulator area of the first application development platform and the configuration area provided by the second application development platform.

[0200] Specifically, the terminal responds to the developer's identification selection operation on the template identifier, determines the template identifier selected by the identification selection operation, and determines the template plugin provided by the second application development platform bound to the template identifier. The terminal determines the project creation script built into the template plugin, loads and runs the project creation script, and obtains the sub-application project identifier. The terminal automatically creates a sub-application development project locally on the first application development platform based on the sub-application project identifier. After creation, the simulator area of the first application development platform and the configuration area provided by the second application development platform can be generated.

[0201] The terminal determines the interface rendering method based on the plugin configuration file, and displays the simulator area and the configuration area according to the interface rendering method.

[0202] In this embodiment, a project creation area is displayed on the sub-application development interface. The terminal automatically creates a sub-application development project locally on the first application development platform based on the sub-application project identifier, generates the project information of the sub-application development project, and automatically fills the generated project information into the project creation area.

[0203] In this embodiment, running the project creation script built into the template plugin can obtain the sub-application project identifier. Based on the sub-application project identifier, a sub-application development project is created locally on the first application development platform, so that the function of using the custom project creation logic of the second application development platform can be provided on the first application development platform. Thus, based on the sub-application development project, the simulator area of the first application development platform and the configuration area provided by the second application development platform are generated, realizing the combination of the debugging function of the first application development platform and the configuration function of the second application development platform.

[0204] In one embodiment, the method further includes:

[0205] Based on the template plugin, obtain the sub-application code from the second application development platform. The sub-application code is generated based on the sub-application page template and the sub-application components already added in the sub-application page template; store the sub-application code locally and run it to obtain the simulated interaction page of the sub-application.

[0206] Specifically, the second application development platform generates the sub-application code based on the sub-application page template and the sub-application components already added in the sub-application page template. The terminal obtains the sub-application code based on the template plugin provided by the second application development platform.

[0207] The terminal stores the sub-application code in the local area of the first application development platform and runs the sub-application code stored locally, thereby generating a sub-application and a simulated interaction page of the sub-application. The terminal responds to a simulated trigger event for the simulator area and displays the simulated interaction page of the sub-application in the simulator area.

[0208] In this embodiment, in response to a trigger operation on the simulator trigger control in the toolbar area, the terminal runs the sub-application code stored locally through the simulator of the first application development platform, obtains the sub-application and the simulated interaction page of the sub-application, and displays the simulated interaction page of the sub-application in the simulator area.

[0209] In this embodiment, when the developer adjusts the added components in the sub-application page template in the configuration area, the second application development platform generates updated sub-application code based on the added components in the adjusted sub-application page template. The terminal obtains the updated sub-application code through the template plugin to update the sub-application code stored locally in the first application development platform, thereby displaying the simulated interaction page of the updated sub-application in the simulator area.

[0210] In this embodiment, obtaining the sub-application code from the second application development platform based on the template plugin includes:

[0211] Invoking a preset interface provided by the first application development platform; through the preset interface, obtaining the sub-application code from the second application development platform based on the template plugin.

[0212] In this embodiment, the second application development platform can generate sub-application code based on the sub-application page template and the added sub-application components in the sub-application page template, enabling the developer to use the page template and components defined by the second application development platform in the first application development platform, and still being able to use the original generation logic of the second application development platform to generate sub-application code without modifying the generation logic of the sub-application code. The sub-application code can be obtained from the second application development platform through the template plugin, stored locally in the first application development platform and run to obtain the simulated interaction page of the sub-application, thereby effectively expanding the development capabilities of the first application development platform based on the template plugin and enabling the first application development platform to be compatible with the development logics of different development platforms.

[0213] In one embodiment, displaying the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface includes:

[0214] Display at least one platform identifier of a second application development platform in the sub-application development interface; in response to a selected identifier operation of selecting from at least one platform identifier, in the sub-application development interface, display a template identifier associated with the selected platform identifier, where the template identifier is used to identify the sub-application page template provided by the second application development platform of the selected platform identifier.

[0215] Among them, the platform identifier is used to identify the second application development platform. The platform identifier is associated with the template identifier to indicate that the sub-application page template represented by the template identifier is provided by the second application development platform represented by the platform identifier. That is, the template identifier of the sub-application page template provided by the second application development platform is associated with the platform identifier of the second application development platform.

[0216] Specifically, the terminal displays at least one platform identifier of a second application development platform in the sub-application development interface. The developer can select from at least one platform identifier of the second application development platform. The terminal, in response to the developer's selected identifier operation, determines the platform identifier selected by the selected identifier operation. The terminal determines the second application development platform represented by the platform identifier, and obtains the template identifier of the sub-application page template provided by the second application development platform. The terminal displays the obtained template identifier in the sub-application development interface.

[0217] In this embodiment, the terminal obtains the template identifier of the sub-application page template from the second application development platform identified by the platform identifier through the first application development platform.

[0218] In this embodiment, the terminal displays a platform selection trigger control in the sub-application development interface. In response to the developer's trigger operation on the platform selection trigger control, at least one platform identifier of a second application development platform is displayed in the sub-application development interface.

[0219] In this embodiment, at least one platform identifier of a second application development platform is displayed in the sub-application development interface, so that at least one third-party application development platform can be provided for the developer to select, enabling the developer to directly use the page templates and components provided by other application development platforms in the first application development platform to generate sub-applications. In response to a selected identifier operation of selecting from at least one platform identifier, in the sub-application development interface, a template identifier associated with the selected platform identifier is displayed, and the template identifier is used to identify the sub-application page template provided by the second application development platform of the selected platform identifier, so that the page template provided by the second application development platform selected by the user can be displayed for the user to select to meet the different needs of the user.

[0220] In one embodiment, the method further includes:

[0221] Display a template category trigger control on the sub-application development interface; in response to a trigger operation on the template category trigger control, display at least one candidate template category on the sub-application development interface;

[0222] In response to an identification selection operation of selecting from at least one platform identification, on the sub-application development interface, display a template identification associated with the selected platform identification, including:

[0223] In response to an identification selection operation of selecting from at least one platform identification and a category selection operation of selecting from at least one candidate template category, on the sub-application development interface, display a template identification that belongs to the selected template category and is associated with the selected platform identification.

[0224] Among them, the candidate template category refers to the category of the sub-application page template, and different types of sub-applications can be generated through different types of sub-application page templates.

[0225] Specifically, the terminal displays at least one platform identification of a second application development platform on the sub-application development interface, and displays a template category trigger control on the sub-application development interface. The developer can select from at least one platform identification of the second application development platform, and the terminal, in response to the developer's identification selection operation, determines the platform identification selected by the identification selection operation, and determines the second application development platform represented by the platform identification.

[0226] The developer can trigger the template category trigger control, and the terminal, in response to the developer's trigger operation on the template category trigger control, displays at least one candidate template category on the sub-application development interface.

[0227] The developer can select at least one category from the displayed candidate template categories, and the terminal, in response to the developer's category selection operation, obtains each template identification belonging to the target template category selected by the category selection operation from the second application development platform.

[0228] In this embodiment, the method further includes: displaying on the configuration area a plurality of sub-application components bound to the sub-application page template and the template category to which the sub-application page template belongs, and the plurality of sub-application components are provided by the second application development platform.

[0229] In this embodiment, displaying a template category trigger control on the sub-application development interface and, in response to a trigger operation on the template category trigger control, displaying at least one candidate template category on the sub-application development interface can provide developers on the first application development platform with the types of page templates of other development platforms, making the classification of page templates of other development platforms more refined, enabling developers to flexibly select the corresponding template types according to the types of sub-applications they need to generate, and thus displaying the page templates of other development platforms under this type for developers to flexibly select.

[0230] In one embodiment, at least one platform identifier of a second application development platform is displayed on a sub-application development interface, including:

[0231] A platform category trigger control is displayed on the sub-application development interface; in response to a trigger operation on the platform category trigger control, at least one platform category is displayed on the sub-application development interface; in response to a category selection operation of selecting within at least one platform category, on the sub-application development interface, platform identifiers of at least one second application development platform belonging to the selected platform category are displayed.

[0232] Wherein, the platform category refers to the category of the second application development platform. Different categories of application development platforms can generate different categories of sub-applications. For example, a map application development platform can generate map-type sub-applications, and a voting application development platform can generate voting-type sub-applications.

[0233] Specifically, the terminal displays a sub-application development interface of a first application development platform, and a platform category trigger control is displayed on the sub-application development interface. Developers can trigger this control to view different types of second application development platforms. The terminal, in response to a trigger operation on the platform category trigger control, displays at least one platform category on the sub-application development interface, and developers can select at least one category from the displayed platform categories. The terminal, in response to a category selection operation of a developer selecting within at least one platform category, determines the platform category selected by the category selection operation, and determines the platform identifiers of each second application development platform belonging to this platform category. The terminal displays, on the sub-application development interface, platform identifiers of at least one second application development platform belonging to the selected platform category.

[0234] In this embodiment, the first application development platform displays platform categories of different categories of second application development platforms on the interface for developers to select, enabling the invocation of different categories of second application development platforms on the first application development platform, enabling the combination of different categories of second application development platforms into the first application development platform, providing developers with more comprehensive development functions, enabling developers to implement the generation of any type of sub-application through the first application development platform without using a specific type of application development platform to generate, and being able to improve the flexibility and convenience of sub-application development.

[0235] In one embodiment, a method for generating a sub-application is provided, which is applied to a terminal and includes:

[0236] Display a sub-application development interface of a first application development platform, and display at least one platform identifier of a second application development platform and a template category trigger control on the sub-application development interface.

[0237] Next, in response to a trigger operation on the template category trigger control, at least one candidate template category is displayed on the sub-application development interface.

[0238] Further, in response to an identification selection operation for selecting an identification in at least one platform identification and a category selection operation in at least one candidate template category, on the sub-application development interface, a template identification belonging to the selected template category and associated with the selected platform identification is displayed. The template identification is used to identify a sub-application page template provided by the second application development platform of the selected platform identification.

[0239] Next, in response to an identification selection operation on the template identification, a template plugin bound to the template identification associated with the selected platform identification is determined, a plugin configuration file of the template plugin is determined, and an interface rendering method is determined based on the plugin configuration file.

[0240] Optionally, when the interface rendering method is embedded rendering, a first application debugging interface is displayed. The first application debugging interface includes a simulator area provided by the first application development platform, a toolbar area provided by the first application development platform, and a configuration area provided by the second application development platform. In the configuration area, a sub-application page template and a plurality of sub-application components provided by the second application development platform are displayed. In the toolbar area, a simulator trigger control, a preview control, and a real device debugging control are displayed.

[0241] Optionally, when the interface rendering method is overlay rendering, a native debugging area of the first application development platform is displayed, and a second application debugging interface overlaid on the native debugging area is displayed. The second application debugging interface includes a configuration area provided by the second application development platform and an interaction area other than the configuration area. Operations in the interaction area can act on the native debugging area, and the native debugging area includes a toolbar area and a simulator area.

[0242] Next, in response to a component selection operation for selecting a sub-application component among a plurality of sub-application components, the sub-application component selected by the component selection operation is added to the sub-application page template.

[0243] Further, in response to a trigger operation on the simulator trigger control, a simulated interaction page of the sub-application is displayed in the simulator area. The simulated interaction page is generated based on the sub-application page template and the sub-application components already added to the sub-application page template.

[0244] Further, in response to a trigger operation on the preview control, a first graphic code of the sub-application is displayed in the simulator area. When the first graphic code is scanned, the mother application of the terminal that scans the first graphic code runs the sub-application, and a preview interaction page of the sub-application is displayed.

[0245] Further, in response to a triggering operation on the real device debugging control, a second graphic code of the sub-application is displayed in the emulator area, so that when the second graphic code is scanned, the parent application of the terminal that scans the second graphic code runs the sub-application, and the interaction page and the running log of the sub-application are displayed.

[0246] In this embodiment, the sub-application development interface of the first application development platform is displayed to show multiple platform identifiers of the second application development platform and various candidate template categories in the sub-application development interface of the first application development platform, so that multiple selectable other application development platforms and various types of selectable page templates are provided in the first application development platform, thereby enabling the combination of the first application development platform and the second application development platform, and allowing users to select and use the page templates provided by the second application development platform in the first application development platform to generate sub-applications. After the developer selects the required second application development platform and the sub-application page template provided by the second application development platform, the interface rendering method can be determined through the template plug-in bound to the template identifier, so as to determine the display method of the interface.

[0247] When the interface rendering method is embedded rendering, the emulator area of the first application development platform and the configuration area provided by the second application development platform are rendered and displayed in the same interface, which is convenient for developers to perform page configuration while viewing the interaction page of the sub-application formed by the configuration. When the interface rendering method is overlay rendering, the emulator area of the first application development platform is displayed, and the second application debugging interface covering the emulator area is displayed. The second application debugging interface includes the configuration area provided by the second application development platform, so that the display freedom of the configuration area is higher, the content in the configuration area can be more completely displayed, and it is convenient for developers to operate.

[0248] The configuration area provided by the second application development platform displays the sub-application page templates provided by the second application development platform and multiple sub-application components provided by the second application development platform. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, enabling users to freely call the page templates and components of the third-party application development platform. In response to a component selection operation for selecting among multiple sub-application components, the selected sub-application component is added to the sub-application page template. In response to a simulation trigger event for the simulator area, a simulation interaction page of the sub-application is displayed in the simulator area. This simulation interaction page is generated based on the sub-application page template and the sub-application components already added to the sub-application page template. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, thereby expanding the development function of the sub-application through the first application development platform. Moreover, by visually selecting components to generate a sub-application, there is no need for users to write code, enabling users who do not understand code to also generate customized sub-applications, making the development of sub-applications simpler and thus improving the development efficiency of sub-applications.

[0249] In one embodiment, an application scenario of a sub-application generation method is provided, and the processing procedure is as follows:

[0250] The first application development platform can be a developer tool, and the second application development platform can be a third-party service provider. A third-party service provider refers to other development tools other than developer tools. A sub-application is a mini-program.

[0251] As Figure 8 shown, the template identifier of the third-party service provider is added to the project list page of the developer tool, and this template identifier is displayed as part of the sub-application page template. The project list page is the sub-application development interface. When the developer clicks on the template identifier, the sub-application page template identified by the clicked template identifier is displayed in the sub-application development interface.

[0252] After the developer selects the template identifier and clicks the OK control to complete the selection, it enters the project creation logic customized by the third-party service provider, as Figure 9 shown.

[0253] After successfully creating the project, it will enter the first application debugging interface, as shown above Figure 6 shown. This interface is mainly divided into three parts. On the left is the simulator area, and on the top is the toolbar area, which are all native functions of the developer tool. On the right is the interface customized by the third-party service provider, that is, the configuration area.

[0254] After selecting relevant components in the configuration area on the right, developers can directly debug the mini-program API (Application Programming Interface) in the simulator area on the left. The API is a preset interface, which is a set of predefined functions. The purpose is to provide the application and developers with the ability to access a set of routines based on a certain software or hardware, without the need to access the source code or understand the details of the internal working mechanism.

[0255] At the same time, developers can use the real device debugging function in the toolbar area to remotely debug the mini-program. Specifically, clicking the save control in the toolbar area will display the mini-program in the simulator area, or clicking the "Simulator" control will also display the mini-program in the simulator area. Clicking the preview control in the toolbar area will display the QR code corresponding to the mini-program in the simulator area. Scanning the QR code with a mobile phone will display the mini-program on the mobile phone, as Figure 10 shown. Clicking the real device debugging control in the toolbar area will display the QR code corresponding to the mini-program in the simulator area. Scanning the QR code with a mobile phone will display the mini-program and the running log of the mini-program on the mobile phone.

[0256] On the technical side, as Figure 11 shown, taking the example that the developer clicks the template identifier provided by the map application building platform on the project list page, the developer tool will first read the template plugin provided by the third-party service provider bound to the template identifier, load and run the project creation script built into the template plugin to create a project ID, and finally return a project ID to the developer tool. The developer tool uses this project ID to actually create a mini-program project. After that, the third-party service provider can continue to use this project ID for its own permission verification and other logics.

[0257] After creating the project, it will enter the application debugging interface, which includes a native debugging area and a configuration area customized by the third-party service provider's template plugin.

[0258] The application debugging interface is an interface rendered according to the interface rendering method. The interface rendering method can be embedded rendering or overlay rendering. Then the application debugging interface can be the first application debugging interface generated according to the embedded rendering method, or the second application debugging interface generated according to the overlay rendering method. Among them, embedded rendering means that the configuration area provided by the second application development platform is directly embedded in the first application debugging interface of the first application development platform, as Figure 12 shown.

[0259] Overlay rendering means that the entire webview covers the native debugging area, that is, the second application debugging interface provided by the second application development platform covers the simulator area and the toolbar area provided by the first application development platform, as described aboveFigure 7 As shown. Overlay rendering means that the interface of the plugin directly overlays the entire window of the tool through the webview, providing higher freedom for the plugin display function.

[0260] However, if the template plugin selects the overlay rendering method, the template plugin needs to obtain the layout information of the emulator area and the layout information of the toolbar area through the API provided by the tool, and reserve blank transparent areas in the webview so that the emulator area and the toolbar area can be displayed in the transparent areas.

[0261] At the same time, in order for developers to operate the native debugging area and the configuration area in the second application debugging interface simultaneously, when the developer tool's mouse moves to the configuration area, it will automatically move the view hierarchy of the second application debugging interface to the top layer. The template plugin needs to detect the mouse operation event by itself. When the mouse moves to the area other than the configuration area in the second application debugging interface, it calls the preset interface provided by the developer tool to lower the view hierarchy of the second application debugging interface, so that the operation event can penetrate the second application debugging interface and act on the native debugging area, enabling developers to also click on the relevant buttons in the native debugging area normally.

[0262] In order for users to be able to use the real device debugging function of the developer tool normally, the template plugin must pass the newly generated applet code after the developer's operation to the developer tool, as Figure 13 shown. After the developer enters the project created by the template, the developer tool will match the corresponding template plugin according to the template used by the project, and decide whether to use embedded rendering or overlay rendering according to the template plugin configuration file. The template plugin pulls the relevant information of the project ID and the generated applet code from the background of the third-party service provider's template plugin according to the project ID. The background of the third-party service provider's template plugin is the second server corresponding to the second application development platform. The template plugin passes the applet code to the developer tool through the API provided by the developer tool. After the developer tool obtains the applet code, it writes it into the local cache directory, and then starts a series of initializations, including compiling the applet code, etc. After the initialization is successful, it returns the result of the successful initialization to the target plugin. After the initialization is successful, developers can perform any operations in the application debugging interface, such as using the real device debugging function provided by the developer tool, or updating the applet configuration in the configuration area. After the developer updates the service configuration, the template plugin will regenerate the applet code and send the differentiated code to the developer tool side through the API provided by the developer. The developer tool synchronizes the code files to be updated to the corresponding file content in the local cache directory, and then recompiles the code to trigger the update of the emulator content, and the emulator area displays the latest applet content.

[0263] This embodiment provides a general method for generating sub-applications, enabling third-party service providers to integrate their services with developer tools, allowing developers to simultaneously use third-party services and capabilities such as the simulator and real-device debugging remote breakpoint debugging of developer tools, thus improving the development efficiency and experience of developers. The implementation of this solution enables third-party service providers to expand without the need to develop a complete set of mini-program debugging solutions. They only need to simply develop a template plugin based on the interfaces provided by the developer tools, which can meet the needs of third-party service providers to expand the mini-program development capabilities, while retaining the original debugging experience of the mini-program developer tools and effectively improving the overall development efficiency.

[0264] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0265] Based on the same inventive concept, an embodiment of the present application also provides a sub-application generation device for implementing the above-mentioned sub-application generation method. The solution provided by this device for solving problems is similar to the solution described in the above method. Therefore, the specific limitations in one or more embodiments of the sub-application generation device provided below can refer to the limitations on the sub-application generation method in the above text and will not be repeated here.

[0266] In one embodiment, as Figure 14 shown, a sub-application generation device 1400 is provided, including: an interface display module 1402, a region display module 1404, an addition module 1406, and a page display module 1408, where:

[0267] The interface display module 1402 is configured to display the sub-application development interface of the first application development platform, and display the template identifier of the sub-application page template provided by the second application development platform on the sub-application development interface.

[0268] The region display module 1404 is configured to, in response to an identification selection operation on the template identifier, display the simulator region of the first application development platform and the configuration region provided by the second application development platform. The configuration region displays the sub-application page template and multiple sub-application components provided by the second application development platform.

[0269] An adding module 1406 is configured to add the sub-application component selected by the component selection operation to the sub-application page template in response to a component selection operation for selecting among multiple sub-application components.

[0270] A page display module 1408 is configured to display a simulation interaction page of the sub-application in the simulator area in response to a simulation trigger event for the simulator area, where the simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template.

[0271] In this embodiment, by displaying the sub-application development interface of the first application development platform to show the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface of the first application development platform, the first application development platform and the second application development platform can be combined, enabling a user to select and use the page template provided by the second application development platform in the first application development platform to implement the generation of the sub-application. In response to an identifier selection operation on the template identifier, the simulator area of the first application development platform and the configuration area provided by the second application development platform are displayed. The configuration area provided by the second application development platform shows the sub-application page template provided by the second application development platform and multiple sub-application components provided by the second application development platform. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, allowing the user to freely call the page templates and components of the third-party application development platform. In response to a component selection operation for selecting among multiple sub-application components, the sub-application component selected by the component selection operation is added to the sub-application page template. In response to a simulation trigger event for the simulator area, a simulation interaction page of the sub-application is displayed in the simulator area. The simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template. These page templates and components are provided by the second application development platform and are decoupled from the first application development platform itself, thereby expanding the development function of the sub-application through the first application development platform. Moreover, by visually selecting components to generate the sub-application, there is no need for the user to write code, enabling a user who does not understand code to also generate a customized sub-application, making the development of the sub-application simpler and thus improving the development efficiency of the sub-application.

[0272] In one embodiment, the area display module 1404 is further configured to display a first application debugging interface in response to an identifier selection operation on the template identifier. The first application debugging interface includes a simulator area provided by the first application development platform and a configuration area provided by the second application development platform.

[0273] In this embodiment, in response to an identification selection operation on a template identifier, a first application debugging interface provided by the first application development platform is displayed, so that the simulator area provided by the first application development platform and the configuration area provided by the second application development platform can be simultaneously displayed in the first application debugging interface, enabling a developer to configure a sub-application obtained in the configuration area to run in the simulator area. The developer can configure and debug the sub-application in the same interface, making the development of the sub-application simpler and conducive to improving the user experience.

[0274] In one embodiment, the first application debugging interface further includes a toolbar area provided by the first application development platform; the page display module 1408 is further configured to display a simulator trigger control in the toolbar area; in response to a trigger operation on the simulator trigger control, a simulated interaction page of the sub-application is displayed in the simulator area.

[0275] In this embodiment, the toolbar area and the simulator area provided by the first application development platform, as well as the configuration area provided by the second application development platform, can be displayed in the first application debugging interface of the first application development platform, enabling a developer to directly use the functions of other development platforms in the first application development platform, and the functions used can still be implemented by other development platforms. Thus, the services provided by the second application development platform can be combined into the first application development platform, greatly enhancing the sub-application development ability of the first application development platform.

[0276] In one embodiment, a preview control is displayed in the toolbar area; the device further includes:

[0277] A graphic code display module, configured to, in response to a trigger operation on the preview control, display a first graphic code of the sub-application in the simulator area, so that when the first graphic code is scanned, the mother application of the terminal that scans the first graphic code runs the sub-application and displays a preview interaction page of the sub-application.

[0278] In this embodiment, in response to a trigger operation on the preview control, a first graphic code of the sub-application is displayed in the simulator area, so that when the first graphic code is scanned, the mother application of the terminal that scans the first graphic code runs the sub-application and displays a preview interaction page of the sub-application, enabling the generated sub-application to be run and previewed on other terminals, thereby ensuring that the sub-application can be run on a real device and the running effect of the sub-application on the real device can be presented.

[0279] In one embodiment, a real device debugging control is displayed in the toolbar area; the device further includes:

[0280] The graphic code display module is used to respond to the triggering operation on the real machine debugging control, and display the second graphic code of the sub-application in the simulator area, so that when the second graphic code is scanned, the mother application of the terminal that scans the second graphic code runs the sub-application, and displays the interaction page of the sub-application and the running log of the sub-application.

[0281] In this embodiment, in response to the triggering operation on the real machine debugging control, the second graphic code of the sub-application is displayed in the simulator area, so that when the second graphic code is scanned, the mother application of the terminal that scans the second graphic code runs the sub-application, and the operation of the sub-application on the real machine can be realized to present the running effect of the sub-application on the real machine. Moreover, by displaying the interaction page of the sub-application and the running log of the sub-application, the relevant functions of the sub-application can be tested on the real machine, and it is convenient for developers to directly view the running log of the sub-application on the real machine, thereby improving the debugging efficiency of the sub-application.

[0282] In one embodiment, the area display module 1404 is further used to respond to the identification selection operation on the template identification, display the simulator area of the first application development platform, and display the second application debugging interface covering the simulator area; wherein, the second application debugging interface includes a configuration area provided by the second application development platform and an interaction area other than the configuration area, and the operations in the interaction area can act on the simulator area.

[0283] In this embodiment, in response to the identification selection operation on the template identification, the simulator area of the first application development platform is displayed, and the second application debugging interface covering the simulator area is displayed. The second application debugging interface includes a configuration area provided by the second application development platform and an interaction area other than the configuration area, so that the display freedom of the configuration area is higher. The operations in the interaction area can act on the simulator area, so that the simulator area can be operated from the interaction area, and the configuration in the configuration area and the operation on the simulator area can be realized on the same interface, effectively expanding the functions of the first application development platform, making the interface display more flexible and meeting the needs of different users.

[0284] In one embodiment, the area display module 1404 is further used to respond to the identification selection operation on the template identification, obtain the template plug-in provided by the second application development platform bound to the template identification; determine the plug-in configuration file of the template plug-in, and determine the interface rendering method based on the plug-in configuration file; according to the interface rendering method, display the simulator area of the first application development platform and the configuration area provided by the second application development platform.

[0285] In this embodiment, in response to an identification selection operation on a template identifier, a template plugin provided by a second application development platform bound to the template identifier is obtained, and an interface rendering method is determined based on the plugin configuration file of the template plugin, so that the simulator area of the first application development platform and the configuration area provided by the second application development platform can be automatically rendered according to the interface rendering method defined by the second application development platform.

[0286] In one embodiment, the area display module 1404 is further configured to display a first application debugging interface of the first application development platform when the interface rendering method is embedded rendering. The first application debugging interface includes a simulator area of the first application development platform and a configuration area provided by the second application development platform; when the interface rendering method is overlay rendering, display the simulator area of the first application development platform, and display a second application debugging interface overlaid on the simulator area. The second application debugging interface includes a configuration area provided by the second application development platform.

[0287] In this embodiment, two interface rendering methods defined by the second application development platform are provided, so that in the first application development platform, the simulator area and the configuration area can be automatically rendered according to the interface rendering method defined by the second application development platform. When the interface rendering method is embedded rendering, the simulator area of the first application development platform and the configuration area provided by the second application development platform are rendered and displayed in the same interface, which is convenient for developers to configure the page and view the interaction page of the sub-application formed by the configuration at the same time. When the interface rendering method is overlay rendering, the simulator area of the first application development platform is displayed, and a second application debugging interface overlaid on the simulator area is displayed. The second application debugging interface includes a configuration area provided by the second application development platform, so that the display freedom of the configuration area is higher, the content in the configuration area can be displayed more completely, and it is convenient for developers to operate.

[0288] In one embodiment, the device further includes:

[0289] A generation module, configured to obtain first layout information of the simulator area of the first application development platform when the interface rendering method is embedded rendering; determine second layout information of the configuration area provided by the second application development platform based on the first layout information of the simulator area; and generate a first application debugging interface of the first application development platform based on the second layout information and the first layout information.

[0290] In this embodiment, when the interface rendering method is embedded rendering, the first layout information of the simulator area of the first application development platform is obtained, and the second layout information of the configuration area provided by the second application development platform is determined based on the first layout information of the simulator area, so that based on the second layout information and the first layout information, a first application debugging interface that can embed the simulator area and the configuration area is accurately generated.

[0291] In one embodiment, the device further comprises:

[0292] A generation module, configured to, when the interface rendering mode is overlay rendering, obtain first layout information of a simulator area of a first application development platform; determine second layout information of a configuration area provided by a second application development platform based on the first layout information of the simulator area; obtain a second application debugging interface provided by the second application development platform based on the second layout information and the first layout information, where the second application debugging interface includes a configuration area and an interaction area; display the second application debugging interface, and display the simulator area covered by the interaction area of the second application debugging interface, and the layout of the simulator area is displayed in the interaction area.

[0293] In this embodiment, when the interface rendering mode is overlay rendering, first layout information of a simulator area of a first application development platform is obtained, second layout information of a configuration area provided by a second application development platform is determined based on the first layout information of the simulator area, and a second application debugging interface including a configuration area and an interaction area is obtained based on the second layout information and the first layout information. Therefore, when the second application debugging interface and the simulator area are displayed, the simulator area covered by the interaction area of the second application debugging interface can be displayed through the interaction area, so that a developer can see a displayed simulation interaction page in the covered simulator area.

[0294] In one embodiment, the device further comprises:

[0295] An adjustment module, configured to, when a first preset operation in the configuration area is detected, adjust the view level of the second application debugging interface to be higher than that of the simulator area, so that after the view level is adjusted, an operation on the configuration area can act on the configuration area; when a second preset operation in the interaction area is detected, adjust the view level of the second application debugging interface to be lower than that of the simulator area, so that after the view level is adjusted, an operation on the interaction area can act on the simulator area.

[0296] In this embodiment, when a first preset operation in the configuration area is detected, indicating that the developer needs to perform relevant configuration operations in the configuration area, the view hierarchy of the second application debugging interface is adjusted to be higher than that of the simulator area, so that after the view hierarchy is adjusted, the developer can directly operate in the configuration area. When a second preset operation in the interaction area is detected, indicating that the developer wants to perform relevant operations on the simulator area, the view hierarchy of the second application debugging interface is adjusted to be lower than that of the simulator area, so that after the view hierarchy is adjusted, the operations of the developer on the interaction area can act on the simulator area, enabling the developer to still use the functions of the simulator area normally when the second application debugging interface covers the simulator area.

[0297] In one embodiment, the device further includes:

[0298] A project creation module, configured to run a project creation script built in the template plugin to obtain a sub-application project identifier; based on the sub-application project identifier, create a sub-application development project locally on the first application development platform; and based on the sub-application development project, generate a simulator area of the first application development platform and a configuration area provided by the second application development platform.

[0299] In this embodiment, running the project creation script built in the template plugin can obtain the sub-application project identifier. Based on the sub-application project identifier, a sub-application development project is created locally on the first application development platform, so that the function of using the custom project creation logic of the second application development platform can be provided on the first application development platform. Then, based on the sub-application development project, a simulator area of the first application development platform and a configuration area provided by the second application development platform are generated, realizing the combination of the debugging function of the first application development platform and the configuration function of the second application development platform.

[0300] In one embodiment, the device further includes:

[0301] A sub-application code acquisition module, configured to obtain sub-application code from the second application development platform based on the template plugin. The sub-application code is generated based on a sub-application page template and sub-application components already added to the sub-application page template; store the sub-application code locally and run it to obtain a simulated interaction page of the sub-application.

[0302] In this embodiment, the second application development platform can generate sub-application code based on the sub-application page template and the sub-application components already added in the sub-application page template, enabling developers to use the page templates and components defined by the second application development platform in the first application development platform, and still being able to use the original generation logic of the second application development platform to generate sub-application code without modifying the generation logic of the sub-application code. The sub-application code can be obtained from the second application development platform through a template plug-in, stored locally in the first application development platform and run to obtain a simulated interaction page of the sub-application, thereby effectively expanding the development capabilities of the first application development platform based on the template plug-in and enabling the first application development platform to be compatible with the development logics of different development platforms.

[0303] In one embodiment, the interface display module 1402 is further configured to display at least one platform identifier of the second application development platform in the sub-application development interface; in response to an identifier selection operation of selecting in at least one platform identifier, display a template identifier associated with the selected platform identifier in the sub-application development interface, where the template identifier is used to identify the sub-application page template provided by the second application development platform with the selected platform identifier.

[0304] In this embodiment, displaying at least one platform identifier of the second application development platform in the sub-application development interface can provide at least one third-party application development platform for developers to choose from, enabling developers to directly use the page templates and components provided by other application development platforms in the first application development platform to generate sub-applications. In response to an identifier selection operation of selecting in at least one platform identifier, a template identifier associated with the selected platform identifier is displayed in the sub-application development interface, and the template identifier is used to identify the sub-application page template provided by the second application development platform with the selected platform identifier, so that the page template provided by the second application development platform selected by the user can be displayed for the user to choose from to meet the different needs of the user.

[0305] In one embodiment, the interface display module 1402 is further configured to display a template category trigger control in the sub-application development interface; in response to a trigger operation on the template category trigger control, display at least one candidate template category in the sub-application development interface; in response to an identifier selection operation of selecting in at least one platform identifier and a category selection operation of selecting in at least one candidate template category, display a template identifier that belongs to the selected template category and is associated with the selected platform identifier in the sub-application development interface.

[0306] In this embodiment, a template category trigger control is displayed on the sub-application development interface. In response to a trigger operation on the template category trigger control, at least one candidate template category is displayed on the sub-application development interface, which can provide developers with the types of page templates of other development platforms in the first application development platform, making the classification of page templates of other development platforms more refined, so that developers can flexibly select the corresponding template type according to the type of sub-application they need to generate, and then display the page templates of other development platforms under this type for developers to flexibly select.

[0307] In one embodiment, the interface display module 1402 is further configured to display a platform category trigger control on the sub-application development interface; in response to a trigger operation on the platform category trigger control, display at least one platform category on the sub-application development interface; in response to a category selection operation of selecting from at least one platform category, display the platform identifiers of at least one second application development platform belonging to the selected platform category on the sub-application development interface.

[0308] In this embodiment, the first application development platform displays the platform categories of different types of second application development platforms on the interface for developers to select, enabling the call of different types of second application development platforms to be realized in the first application development platform, combining different types of second application development platforms into the first application development platform, providing developers with more comprehensive development functions, enabling developers to implement any type of sub-application they need through the first application development platform without using a specific type of application development platform to generate, and improving the flexibility and convenience of sub-application development.

[0309] Each module in the above sub-application generation device can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules.

[0310] In one embodiment, a computer device is provided. The computer device can be a terminal, and its internal structure diagram can be as Figure 15As shown in the figure. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a sub-application generation method. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0311] Those skilled in the art can understand that Figure 15 the structure shown in the figure is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0312] In one embodiment, a computer device is further provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented.

[0313] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0314] In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0315] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions.

[0316] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

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

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

Claims

1. A method for generating a sub-application, characterized in that, The method includes: Display a sub-application development interface of a first application development platform, and display a template identifier of a sub-application page template provided by the second application development platform on the sub-application development interface; In response to an identifier selection operation on the template identifier, display a simulator area of the first application development platform and a configuration area provided by the second application development platform. The configuration area displays the sub-application page template and a plurality of sub-application components provided by the second application development platform; In response to a component selection operation for selecting among the plurality of sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template; In response to a simulation trigger event for the simulator area, display a simulation interaction page of the sub-application in the simulator area, where the simulation interaction page is generated based on the sub-application page template and the sub-application components already added to the sub-application page template; 2. The method according to claim 1, characterized in that The step of, in response to an identifier selection operation on the template identifier, displaying the simulator area of the first application development platform and the configuration area provided by the second application development platform includes: In response to an identifier selection operation on the template identifier, display a first application debugging interface, where the first application debugging interface includes the simulator area provided by the first application development platform and the configuration area provided by the second application development platform; 3. The method according to claim 2, wherein The first application debugging interface further includes a toolbar area provided by the first application development platform; The step of, in response to a simulation trigger event for the simulator area, displaying a simulation interaction page of the sub-application in the simulator area includes: Display a simulator trigger control in the toolbar area; In response to a trigger operation on the simulator trigger control, display a simulation interaction page of the sub-application in the simulator area; 4. The method according to claim 3, wherein The toolbar area displays a preview control; the method further includes: In response to a trigger operation on the preview control, display a first graphic code of the sub-application in the simulator area, so that when the first graphic code is scanned, the mother application of the terminal that scans the first graphic code runs the sub-application and displays a preview interaction page of the sub-application; 5. The method according to claim 3, wherein The toolbar area displays a real device debugging control; the method further includes: In response to a trigger operation on the real device debugging control, display a second graphic code of the sub-application in the simulator area, so that when the second graphic code is scanned, the mother application of the terminal that scans the second graphic code runs the sub-application and displays an interaction page of the sub-application and a running log of the sub-application; 6. The method according to claim 1, characterized in that, The step of, in response to an identifier selection operation on the template identifier, displaying the simulator area of the first application development platform and the configuration area provided by the second application development platform includes: In response to an identifier selection operation on the template identifier, display the simulator area of the first application development platform and display a second application debugging interface covering the simulator area; Among them, the second application debugging interface includes a configuration area provided by the second application development platform and an interaction area other than the configuration area. Operations in the interaction area can act on the simulator area.

7. The method according to claim 1, characterized in that The displaying of the simulator area of the first application development platform and the configuration area provided by the second application development platform in response to an identification selection operation on the template identification includes: In response to an identification selection operation on the template identification, obtaining a template plugin provided by a second application development platform bound to the template identification; Determining a plugin configuration file of the template plugin, and determining an interface rendering method based on the plugin configuration file; Displaying the simulator area of the first application development platform and the configuration area provided by the second application development platform according to the interface rendering method.

8. The method according to claim 7, characterized in that The displaying of the simulator area of the first application development platform and the configuration area provided by the second application development platform according to the interface rendering method includes: When the interface rendering method is embedded rendering, displaying a first application debugging interface of the first application development platform, where the first application debugging interface includes the simulator area of the first application development platform and the configuration area provided by the second application development platform; When the interface rendering method is overlay rendering, displaying the simulator area of the first application development platform and displaying a second application debugging interface overlaid on the simulator area, where the second application debugging interface includes the configuration area provided by the second application development platform.

9. The method according to claim 8, wherein The method further includes: When the interface rendering method is embedded rendering, obtaining first layout information of the simulator area of the first application development platform; Based on the first layout information of the simulator area, determining second layout information of the configuration area provided by the second application development platform; Generating a first application debugging interface of the first application development platform based on the second layout information and the first layout information.

10. The method according to claim 8, characterized in that, The when the interface rendering method is overlay rendering, displaying the simulator area of the first application development platform and displaying a second application debugging interface overlaid on the simulator area includes: When the interface rendering method is overlay rendering, obtaining first layout information of the simulator area of the first application development platform; Based on the first layout information of the simulator area, determining second layout information of the configuration area provided by the second application development platform; Based on the second layout information and the first layout information, obtaining a second application debugging interface provided by the second application development platform, where the second application debugging interface includes the configuration area and the interaction area; Displaying the second application debugging interface and displaying the simulator area covered by the interaction area of the second application debugging interface, where the layout of the simulator area is shown in the interaction area.

11. The method according to claim 10, wherein The method further includes: When a first preset operation within the configuration area is detected, adjust the view hierarchy of the second application debugging interface to be higher than the view hierarchy of the emulator area, so that after the view hierarchy is adjusted, the operation on the configuration area can act on the configuration area; When a second preset operation acting on the interaction area is detected, adjust the view hierarchy of the second application debugging interface to be lower than the view hierarchy of the emulator area, so that after the view hierarchy is adjusted, the operation on the interaction area can act on the emulator area.

12. The method according to claim 7, characterized in that, The method further includes: Run the project creation script built in the template plugin to obtain a sub-application project identifier; Based on the sub-application project identifier, create a sub-application development project locally on the first application development platform; Based on the sub-application development project, generate the emulator area of the first application development platform and the configuration area provided by the second application development platform.

13. The method according to claim 7, characterized in that, The method further includes: Based on the template plugin, obtain sub-application code from the second application development platform, where the sub-application code is generated based on the sub-application page template and the sub-application components already added in the sub-application page template; Store the sub-application code locally and run it to obtain a simulated interaction page of the sub-application.

14. The method according to any one of claims 1 to 13, characterized in that The displaying the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface includes: Display at least one platform identifier of the second application development platform in the sub-application development interface; In response to an identifier selection operation of selecting in the at least one platform identifier, in the sub-application development interface, display the template identifier associated with the selected platform identifier, where the template identifier is used to identify the sub-application page template provided by the second application development platform of the selected platform identifier.

15. The method according to claim 14, wherein The method further includes: Display a template category trigger control in the sub-application development interface; In response to a trigger operation on the template category trigger control, display at least one candidate template category in the sub-application development interface; The responding to an identifier selection operation of selecting in the at least one platform identifier and displaying the template identifier associated with the selected platform identifier in the sub-application development interface includes: In response to an identifier selection operation of selecting in the at least one platform identifier and a category selection operation of selecting in the at least one candidate template category, in the sub-application development interface, display the template identifier that belongs to the selected template category and is associated with the selected platform identifier.

16. The method according to claim 14, wherein The displaying at least one platform identifier of the second application development platform in the sub-application development interface includes: Display a platform category trigger control in the sub-application development interface; In response to a trigger operation on the platform category trigger control, display at least one platform category in the sub-application development interface; In response to a category selection operation of selecting in the at least one platform category, in the sub-application development interface, display at least one platform identifier of the second application development platform that belongs to the selected platform category.

17. A sub-application generation device, characterized in that The device includes: An interface display module, configured to display a sub-application development interface of a first application development platform, and display a template identifier of a sub-application page template provided by a second application development platform on the sub-application development interface; A region display module, configured to, in response to an identifier selection operation on the template identifier, display a simulator region of the first application development platform and a configuration region provided by the second application development platform, where the configuration region displays the sub-application page template and a plurality of sub-application components provided by the second application development platform; An addition module, configured to, in response to a component selection operation of selecting from the plurality of sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template; A page display module, configured to, in response to a simulation trigger event for the simulator region, display a simulation interaction page of the sub-application in the simulator region, where the simulation interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template.

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

19. A computer-readable storage medium, on which a computer program is stored, characterized in that, When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

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

Images