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

Abstract

The present application relates to a sub-application generation method. The method comprises: displaying a sub-application development interface of a first application development platform (S201); on the sub-application development interface, displaying template identifiers of sub-application page templates provided by a second application development platform (S202); in response to an identifier selection operation on a template identifier, displaying a simulator area of the first application development platform and a configuration area of the second application development platform (S203); in the configuration area, displaying a sub-application page template and a plurality of sub-application components provided by the second application development platform (S204); in response to a component selection operation, adding to the sub-application page template a sub-application component selected by the component selection operation (S206); and displaying in the simulator area a simulation interaction page formed by simulating the operation of a sub-application, the simulation interaction page being generated by using the sub-application page template and the sub-application component that has been added to the sub-application page template (S208).

Description

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

[0001] Related applications

[0002] This application claims priority to Chinese patent application number 2024101148014, filed on January 25, 2024, entitled “Sub-application generation method, apparatus, computer device and readable storage medium,” the entire text of which is hereby incorporated by reference. Technical Field

[0003] The present application relates to the field of computer technology, and in particular to a sub-application generation method, apparatus, computer equipment, storage medium, and computer program product. Background Art

[0004] With the development of computer technology, sub-application generation technology has emerged. Users can use this technology to generate sub-applications that meet their needs. For example, merchants on the Internet of Things may need dedicated sub-applications to provide services to consumers. Merchants can generate their own dedicated sub-applications.

[0005] In related technologies, a specific type of sub-application is generally implemented through a specific type of application development platform. The application development platform provides some pre-configured templates, and users can adjust these templates to generate the sub-applications they need.

[0006] 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 sub-application, it needs to be implemented on an application development platform that can develop that type of sub-application, resulting in low sub-application development efficiency. Summary of the Invention

[0007] The present application provides a sub-application generation method, apparatus, computer device, computer-readable storage medium, and computer program product.

[0008] In a first aspect, the present application provides a sub-application generation method, which is executed by a terminal, and the method includes:

[0009] Displaying a sub-application development interface of the first application development platform;

[0010] In the sub-application development interface, a template identifier of the sub-application page template provided by the second application development platform is displayed;

[0011] In response to an identification selection operation on the template identification, displaying a simulator area of ​​the first application development platform and a configuration area for configuring a sub-application of the second application development platform;

[0012] In the configuration area, displaying the sub-application page template and multiple sub-application components provided by the second application development platform;

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

[0014] A simulated interactive page formed by simulating the operation of the sub-application is displayed in the simulator area, where the sub-application is generated using the sub-application page template and the sub-application components added to the sub-application page template.

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

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

[0017] an area display module for displaying, in response to an identification selection operation on the template identification, a simulator area of ​​the first application development platform and a configuration area for configuring a sub-application of the second application development platform; displaying, in the configuration area, the sub-application page template and a plurality of sub-application components provided by the second application development platform;

[0018] an adding 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; and

[0019] The page display module is used to display a simulated interactive page formed by simulating the operation of the sub-application in the simulator area, where the sub-application is generated using the sub-application page template and the sub-application components added to the sub-application page template.

[0020] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the above-mentioned sub-application generation method when executing the computer program.

[0021] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned sub-application generation method when executed by a processor.

[0022] In a fifth aspect, the present application further provides a computer program product, which includes a computer program that implements the above-mentioned sub-application generation method when executed by a processor.

[0023] The details of one or more embodiments of the present application are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the present application will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the conventional technology, the following briefly introduces the drawings required for use in the embodiments or the conventional technology descriptions. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the disclosed drawings without any creative work.

[0025] FIG1 is an application environment diagram of a method for generating a sub-application in one embodiment;

[0026] FIG2 is a schematic diagram of a flow chart of a method for generating a sub-application in one embodiment;

[0027] FIG3 is a schematic diagram of an interface showing a template identifier in a sub-application development interface in one embodiment;

[0028] FIG4 is a schematic diagram of an interface showing a simulator area and a configuration area in the same interface in another embodiment;

[0029] FIG5 is a schematic diagram of an interface showing a simulator area and a configuration area in different interfaces, respectively, according to another embodiment;

[0030] FIG6 is a schematic diagram of an interface showing a toolbar area, a simulator area, and a configuration area in one embodiment;

[0031] FIG7 is a schematic diagram of an interface in which a second application debugging interface is overlaid on a native debugging area in one embodiment;

[0032] FIG8 is a schematic diagram of an interface showing a template identifier on a project list page of a developer tool according to an embodiment;

[0033] FIG9 is a schematic diagram of an interface for project creation logic customized by a third-party service provider in one embodiment;

[0034] FIG10 is a schematic diagram of scanning a QR code corresponding to a mini-program with a mobile phone to display the mini-program page on the mobile phone in one embodiment;

[0035] FIG11 is a sequence diagram of creating a mini-program project in one embodiment;

[0036] FIG12 is a schematic diagram of a first application debugging interface generated by an embedded rendering method in one embodiment;

[0037] FIG13 is a sequence diagram of the developer tool generating a mini-program after creating a mini-program project in one embodiment;

[0038] FIG14 is a structural block diagram of a sub-application generating device according to an embodiment;

[0039] FIG15 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

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

[0042] Intelligent Traffic System (ITS), also known as Intelligent Transportation System, is an effective and integrated application of advanced science and technology (information technology, computer technology, data communication technology, sensor technology, electronic control technology, automatic control theory, operations research, artificial intelligence, etc.) to transportation, service control and vehicle manufacturing, strengthening the connection between vehicles, roads and users, thereby forming an integrated transportation system that ensures safety, improves efficiency, improves the environment and saves energy. Or;

[0043] Intelligent Vehicle Infrastructure Cooperative Systems (IVICS), also known as VICS, are a development direction of Intelligent Transportation Systems (ITS). IVICS utilizes advanced wireless communications and next-generation internet technologies to implement dynamic, real-time information exchange between vehicles and roads. Based on the collection and integration of dynamic traffic information across time and space, IVICS conducts active vehicle safety control and collaborative road management. This fully realizes effective coordination between people, vehicles, and roads, ensuring traffic safety and improving traffic efficiency, thereby creating a safe, efficient, and environmentally friendly road transportation system.

[0044] The sub-application generation method provided in an embodiment of the present application can be applied to the application environment shown in Figure 1 . Terminal 102 communicates with server 104 via a network. A data storage system can store data that server 104 needs to process. The data storage system can be integrated with server 104, or located in the cloud or on another server. Terminal 102 displays a sub-application development interface for a first application development platform. Within the sub-application development interface, a template identifier for a sub-application page template provided by a second application development platform is displayed. The page template and its template identifier can be stored in server 104. In response to an identifier selection operation for the template identifier, terminal 102 displays a simulator area for the first application development platform and a configuration area for configuring a sub-application for 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 server 104. In response to a component selection operation for selecting from the multiple sub-application components, terminal 102 adds the sub-application component selected in the component selection operation to the sub-application page template. The terminal 102 displays a simulated interactive page formed by simulating the running of a sub-application in the simulator area. The sub-application is generated using the sub-application page template and the sub-application components added to the sub-application page template.

[0045] Terminal 102 may include, but is not limited to, various desktop computers, laptops, smartphones, tablet computers, IoT devices, and portable wearable devices. IoT devices may include smart speakers, smart TVs, smart air conditioners, and smart car devices. Portable wearable devices may include smart watches, smart bracelets, and head-mounted devices. Server 104 may be implemented as a standalone server or a server cluster consisting of multiple servers.

[0046] In one embodiment, as shown in FIG2 , a sub-application generation method is provided, which is described by taking the method applied to the terminal in FIG1 as an example, including the following steps:

[0047] Step S201: displaying a sub-application development interface of a first application development platform.

[0048] Step S202: Displaying the template identifier of the sub-application page template provided by the second application development platform in the sub-application development interface.

[0049] The 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.

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

[0051] A sub-application page template is a page that allows for editing and arranging. Developers can implement sub-application functionality within this sub-application page template. A template identifier is used to identify a sub-application page template. Specifically, the template identifier can be at least a portion of the sub-application page template, a thumbnail of the sub-application page template, or the sub-application page template's name or number, but is not limited to these.

[0052] A sub-application is an application that cannot run independently and requires the help of other applications to run. In other words, the sub-application runs within the parent application.

[0053] A sub-application may refer to an installation-free application, that is, an application that can be used without downloading and installing. Such an application is usually run as a sub-program in a client, and the client is called a parent application.

[0054] 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 these.

[0055] This sub-application can also be a cloud application, which is an application that runs in the cloud. Cloud applications are applications that interact between the terminal and the cloud. Cloud applications operate by using the powerful computing power of the cloud simulator to encode the running process into audio and video streams, which are transmitted to the terminal over the network to enable interaction with the user.

[0056] The cloud refers to cloud servers, also known as cloud servers. Cloud servers are based on large-scale distributed computing systems that integrate computer resources through virtualization technology to provide internet infrastructure services. The network that provides these resources is called the "cloud." To users, these resources appear infinitely scalable, readily accessible, usable on demand, and scalable at any time, with a pay-per-use policy. Cloud computing is a computing model that distributes computing tasks across a resource pool composed of numerous computers, enabling various application systems to access computing power, storage space, and information services as needed.

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

[0058] Specifically, a user can log in to a first application development platform running on a terminal using an application development account. The terminal displays a sub-application development interface of the first application development platform. The sub-application development interface displays at least one template identifier, each of which identifies a sub-application page template provided by a second application development platform. As shown in FIG3 , sub-application development interface 300 displays multiple template identifiers 304 provided by a second application development platform 302.

[0059] 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.

[0060] Step S203 : In response to the selection operation on the template identifier, a simulator area of ​​the first application development platform and a configuration area for configuring a sub-application of the second application development platform are displayed.

[0061] Step S204: In the configuration area, a sub-application page template and multiple sub-application components provided by the second application development platform are displayed.

[0062] The identifier selection operation is a preset operation that acts 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 key 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-touch operation or a multi-touch operation. The cursor operation can be an operation that controls the cursor to click or to press. The key operation can be a virtual key operation or a physical key operation, etc.

[0063] 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.

[0064] 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.

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

[0066] The terminal displays a simulator area of ​​the first application development platform and a configuration area for configuring a sub-application of the second application development platform. The configuration area displays a sub-application page template identified by the selected template identifier and multiple sub-application components provided by the second application development platform.

[0067] 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 done by displaying the simulator area and the configuration area on the same interface, as shown in Figure 4. Alternatively, the simulator area and the configuration area can be displayed separately on two interfaces on the same screen, as shown in Figure 5.

[0068] In this embodiment, in response to the developer's selection of the template identifier, the terminal displays a simulator area in the second application development platform, jumps from the first application development platform to the second application development platform, and displays a configuration area in the second application development platform. The configuration area displays the sub-application page template identified by the selected template identifier and multiple sub-application components provided by the second application development platform.

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

[0070] Step S206 : In response to a component selection operation of selecting from a plurality of sub-application components, the sub-application component selected by the component selection operation is added to the sub-application page template.

[0071] 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 component they want to use from the multiple sub-application components and add the selected component to the sub-application page template. The terminal receives the developer's component selection operation to select from 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.

[0072] In this embodiment, the component selection operation includes but is not limited to long press, click, slide, move and multi-touch operations. Adding a 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.

[0073] For example, a developer can select a desired sub-application component from multiple sub-application components and move it to a sub-application page template. The terminal detects the developer's move operation on the sub-application component, determines the movement trajectory corresponding to the move operation, and moves the sub-application component to the sub-application page template according to the movement trajectory.

[0074] Step S208 : Displaying a simulated interactive page formed by simulating the running of a sub-application in the simulator area. The sub-application is generated by using the sub-application page template and the sub-application components added to the sub-application page template.

[0075] Among them, the terminal can display a simulated interactive page formed by simulating the operation of the sub-application in the simulator area in response to a simulation trigger event. The simulation trigger event is an event used to trigger the debugging of the sub-application. The simulation trigger event can specifically be a touch operation, a cursor operation, a key operation or a voice operation. The terminal can also display the simulated interactive page formed by the operation of the simulated sub-application in the simulator area in real time. The terminal can also display the simulated interactive page formed by the operation of the simulated sub-application in the simulator area whenever a change occurs in the configuration area, wherein the change can be at least one of adding a sub-application component, deleting a sub-application component, replacing a sub-application component, adjusting the properties of a sub-application component or adjusting the layout of a sub-application component.

[0076] The simulator area is a display area where a child application is simulated to run on a parent application through the simulator. The simulator is provided by the first application development platform and can simulate the parent application running on the child application.

[0077] In this embodiment, the simulated interactive page of the sub-application is generated based on the native code of the page template and the components added to the page template, and the native code is generated by the second application development platform.

[0078] Specifically, in response to a simulation trigger event for the simulator area, the terminal displays 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 component added to the sub-application page template.

[0079] 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 in the configuration interface and the sub-application components added to the sub-application page template. In response to the simulation trigger event for the simulator area, the terminal loads and runs the sub-application on the first application development platform via the simulator, thereby displaying the simulated interaction page of the sub-application in the simulator area.

[0080] 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 on the sub-application development interface of the first application development platform. This can combine the first application development platform and the second application development platform, allowing users to select the page template provided by the second application development platform to generate a sub-application on the first application development platform. In response to the identifier selection operation of the template identifier, the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform are displayed. The configuration area for configuring the sub-application of 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 page templates and components of third-party application development platforms. In response to a component selection operation for selecting from 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 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 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 functions of the sub-application through the first application development platform. In addition, by generating sub-applications through visual component selection, there is no need for users to write code, so that users who do not understand code can also generate customized sub-applications, making the development of sub-applications simpler, thereby improving the development efficiency of sub-applications.

[0081] In one embodiment, in response to an identification selection operation on a template identification, a simulator area of ​​a first application development platform and a configuration area for configuring a sub-application of a second application development platform are displayed, including:

[0082] In response to the selection operation of the template identifier, a first application debugging interface is displayed; a simulator area provided by the first application development platform and a configuration area for configuring a sub-application of the second application development platform are displayed on the first application debugging interface.

[0083] Specifically, in response to the developer's selection operation on the template identifier, the terminal 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.

[0084] The terminal displays a first application debugging interface provided by the first application development platform. The first application debugging interface includes a simulator area provided by the first application development platform and a configuration area for configuring a sub-application of the second application development platform. The terminal displays a sub-application page template provided by the second application development platform in the configuration area, along with multiple sub-application components provided by the second application development platform.

[0085] Developers can select components from 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, and generate a sub-application based on the sub-application page template and the sub-application components added to the sub-application page template through the second application development platform.

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

[0087] In this embodiment, in response to the identification selection operation of the template identification, the 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 for configuring the sub-application of the second application development platform can be displayed simultaneously in the first application debugging interface, so that the sub-application configured by the developer in the configuration area can run in the simulator area, and 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.

[0088] In one embodiment, the first application debugging interface further includes a toolbar area provided by the first application development platform; and the simulator area displays a simulated interactive page formed by simulating the sub-application running, including:

[0089] The simulator trigger control is displayed in the toolbar area; in response to the triggering operation of the simulator trigger control, a simulated interaction page formed by the running of the simulated sub-application is displayed in the simulator area.

[0090] The simulator trigger control is an interactive element displayed in the toolbar area and accessible to users. An interactive element is a visual element. A visual element is an element that can be displayed and seen by the human eye to convey information. Interactive elements can take various forms, including, but not limited to, at least one of a control, image, text, logo, link, or animation file. A control can be a button, fill-in-the-blank box, radio button, or option group.

[0091] The simulator trigger control is used to trigger the display of a sub-app's simulated interactive page in the simulator area. The simulated interactive page refers to the sub-app's interactive page displayed in the simulator area when the simulated sub-app is running.

[0092] The first application debugging interface also includes a toolbar area provided by the first application development platform, and the toolbar area displays a simulator trigger control.

[0093] Specifically, in response to the selection operation of the template identifier, the terminal displays a first application debugging interface including a toolbar area, a simulator area, and a configuration area, wherein 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.

[0094] The toolbar area displays a simulator trigger control. When the developer triggers the simulator trigger control, the operating environment of the sub-application can be simulated through the simulator of the first application development platform, thereby running the sub-application generated based on the sub-application page template in the configuration area and the added components, and displaying the simulated interaction page of the sub-application in the simulator area.

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

[0096] In this embodiment, the toolbar area and simulator area provided by the first application development platform, as well as the configuration area for configuring the sub-application of the second application development platform can be displayed in the first application debugging interface of the first application development platform, so that developers 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, so that the services provided by the second application development platform can be combined with the first application development platform, greatly improving the sub-application development capabilities of the first application development platform.

[0097] In one embodiment, the toolbar area displays a preview control; the method further includes:

[0098] In response to the triggering operation of the preview control, the first graphic code of the sub-application is displayed in the simulator area. The first graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application and display the preview interaction page of the sub-application.

[0099] Specifically, the toolbar area displays a preview control, which is used to trigger a preview of the interactive page of the sub-application.

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

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

[0102] Developers can scan the first graphic code through a parent application running on another terminal to run the sub-application through the parent application running on the scanning terminal that scanned the first graphic code and display a preview interaction page of the sub-application. The preview interaction page refers to the page of the sub-application in the preview state.

[0103] In this embodiment, the preview interaction page does not support interactive operations, that is, the preview interaction page can only be viewed but not operated.

[0104] In this embodiment, in response to the triggering operation of the preview control, the first graphic code of the sub-application is displayed in the simulator area, so that when the first graphic code is scanned, the sub-application is run by the parent application running on the scanning terminal that scans the first graphic code, and the preview interaction page of the sub-application is displayed. The generated sub-application can be run and previewed on other terminals, thereby ensuring that the sub-application can be run on a real machine and that the running effect of the sub-application on the real machine can be presented.

[0105] In one embodiment, the toolbar area displays a real-device debugging control; the method further includes:

[0106] In response to the triggering operation of the real machine debugging control, the second graphic code of the sub-application is displayed in the simulator area. The second graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application, and display the interaction page of the sub-application and the operation log of the sub-application.

[0107] Specifically, the toolbar area displays a real-device debugging control. In response to a component selection operation in which the developer selects from among multiple sub-application components, the terminal adds the sub-application component selected in the component selection operation to the sub-application page template. The terminal generates a sub-application based on the sub-application page template and the sub-application components added to the sub-application page template via the second application development platform.

[0108] The terminal generates a second graphic code of the sub-application through the first application development platform. When the developer triggers the real machine debugging control displayed in the toolbar area, the terminal responds to the developer's triggering operation of the real machine debugging control and displays the second graphic code of the sub-application in the simulator area.

[0109] Developers can scan the second graphic code through a parent application running on another terminal to launch the child application through the parent application running on the scanning terminal that scanned the second graphic code, and display the child application's interactive page. The interactive page supports interactive operations, and developers can operate on the interactive page to test related functions within the interactive page.

[0110] In addition, the running log of the sub-application is displayed on the parent application running on the scanning terminal that scans the second graphic code, so that the developer can test the relevant functions of the generated sub-application in a real device and view the running log of the sub-application.

[0111] In this embodiment, the parent application running on the scanning terminal that scans the second graphic code runs the sub-application and displays the interactive page of the sub-application. The developer can perform interactive operations on the interactive page and generate operation records based on the interactive operations, thereby generating a running log of the sub-application.

[0112] In this embodiment, in response to triggering a real-device debugging control, a second graphical code of the sub-application is displayed in the simulator area. When the second graphical code is scanned, the parent application running on the scanning terminal that scanned the second graphical code runs the sub-application, enabling the sub-application to run on the real device, thereby presenting the sub-application's running effect on the real device. Furthermore, the sub-application's interactive page and running log are displayed, enabling testing of the sub-application's related functions on the real device and facilitating developers to directly view the sub-application's running log on the real device, thereby improving sub-application debugging efficiency.

[0113] In one embodiment, as shown in FIG6 , toolbar area 602 displays simulator trigger controls 604, preview controls 606, and real-device debugging controls 608. After the developer adds configuration area 610 to the sub-application page template 612, they can trigger simulator trigger controls 604, and display the sub-application's simulated interaction page 616 in simulator area 614.

[0114] When the developer triggers the preview control, the first graphic code of the sub-application is displayed in the simulator area. The first graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application and display the preview interaction page of the sub-application.

[0115] When the developer triggers the real device debugging control, the second graphic code of the sub-application is displayed in the simulator area. The second graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application and display the sub-application's interactive page and the sub-application's running log.

[0116] In one embodiment, in response to an identification selection operation on a template identification, a simulator area of ​​a first application development platform and a configuration area for configuring a sub-application of a second application development platform are displayed, including:

[0117] In response to the identification selection operation of the template identification, the simulator area of ​​the first application development platform is displayed, and the second application debugging interface is displayed overlying the simulator area; wherein the second application debugging interface includes a configuration area for configuring the sub-application of the second application development platform, and an interactive area other than the configuration area, and operations in the interactive area can act on the simulator area.

[0118] Specifically, in response to the developer's selection operation on the template identifier, the terminal 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.

[0119] The terminal displays the simulator area of ​​the first application development platform and displays a second application debugging interface overlaid on the simulator area. The second application debugging interface is provided by the second application development platform.

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

[0121] The second application debugging interface and the area outside the configuration area are used as the interactive area. Because the second application debugging interface is overlaid on the simulator area, developers can operate the simulator area by operating in the interactive area. In other words, the developer's operations in the interactive area will be applied to the simulator area.

[0122] In this embodiment, the interactive area is overlaid on the simulator area provided by the first application development platform. The simulator area is located below the interactive area and can be displayed through the interactive area. For example, the interactive area is a transparent area, and the interactive area is overlaid on the simulator area. The simulator area can then be displayed through the interactive area, so that the developer's operations in the interactive area can be applied to the corresponding position in the simulator area.

[0123] In this embodiment, as shown in FIG7 , in response to the selection operation of the template identifier, 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 native debugging area includes the simulator area and the toolbar area of ​​the first application development platform; the second application debugging interface includes a configuration area for configuring the sub-application of the second application development platform, and an interactive area other than the configuration area. Operations in the interactive area can act on the native debugging area. The interactive area is overlaid on the native debugging area of ​​the first application development platform. The native debugging area is in the lower layer of the interactive area and can be displayed through the interactive area, so that the developer's operations in the interactive area can act on the corresponding position of the native debugging area.

[0124] In this embodiment, in response to an operation to select a template identifier, the simulator area of ​​the first application development platform is displayed, and a second application debugging interface is displayed overlying the simulator area. The second application debugging interface includes a configuration area for configuring sub-applications of the second application development platform, as well as an interactive area in addition to the configuration area, allowing for greater display freedom in the configuration area. Operations in the interactive area can be applied to the simulator area, making it possible to operate the simulator area from the interactive area. Configurations in the configuration area and operations on the simulator area can be implemented on the same interface, effectively expanding the functionality of the first application development platform and making the interface display more flexible to meet the needs of different users.

[0125] In one embodiment, in response to an identification selection operation on a template identification, a simulator area of ​​a first application development platform and a configuration area for configuring a sub-application of a second application development platform are displayed, including:

[0126] In response to an identification selection operation on a template identifier, a template plug-in provided by a second application development platform bound to the template identifier is obtained; a plug-in configuration file of the template plug-in is determined, and an interface rendering mode is determined based on the plug-in configuration file; according to the interface rendering mode, a simulator area of ​​the first application development platform and a configuration area for configuring a sub-application of the second application development platform are displayed.

[0127] Interface rendering methods include embedded rendering and overlay rendering. Embedded rendering refers to the configuration area for configuring the sub-application of the second application development platform, which is embedded in the first application debugging interface of the first application development platform. In other words, embedded rendering means that the configuration area for configuring the sub-application of 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.

[0128] When the first application development platform provides a toolbar area, the embedded rendering represents the configuration area and toolbar area for configuring the sub-application of the second application development platform, and the simulator area of ​​the first application development platform, all of which are embedded in the first application debugging interface of the first application development platform.

[0129] Overlay rendering refers to a second application debugging interface provided by the second application development platform, which covers the simulator area provided by the first application development platform, and the second application debugging interface includes a configuration area.

[0130] When the first application development platform provides a toolbar area, the overlay rendering represents a second application debugging interface provided by the second application development platform, covering the simulator area and the toolbar area provided by the first application development platform.

[0131] The template plug-in is a program written in accordance with a certain standard application program interface. The template plug-in is defined and written by the first application development platform.

[0132] Specifically, in response to the developer's identification selection operation on the template identification, the terminal determines the template identification selected by the identification selection operation, and determines the template plug-in provided by the second application development platform bound to the template identification. The terminal determines the plug-in configuration file of the template plug-in, which defines the interface rendering method provided by the second application development platform. The terminal determines the interface rendering method from the plug-in configuration file, and the terminal performs interface rendering according to the interface rendering method, obtaining the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform. The terminal displays the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform.

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

[0134] In one embodiment, displaying the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform according to the interface rendering method includes:

[0135] When the interface rendering mode is embedded rendering, the first application debugging interface of the first application development platform is displayed, and the first application debugging interface includes the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform; when the interface rendering mode is overlay rendering, the simulator area of ​​the first application development platform is displayed, and the second application debugging interface covering the simulator area is displayed, and the second application debugging interface includes the configuration area for configuring the sub-application of the second application development platform.

[0136] Specifically, when the interface rendering mode is embedded rendering, the terminal generates a first application debugging interface for the first application development platform, displaying a simulator area for the first application development platform and a configuration area for configuring sub-applications of the second application development platform. Furthermore, the first application debugging interface includes a simulator area and a toolbar area for the first application development platform, as well as a configuration area for configuring sub-applications of the second application development platform.

[0137] When the interface rendering mode is overlay rendering, the terminal displays the simulator area of ​​the first application development platform and displays a second application debugging interface provided by the first application development platform overlaid on the simulator area. The second application debugging interface includes a configuration area for configuring sub-applications of the second application development platform. Furthermore, the second application debugging interface overlays the simulator area and toolbar area of ​​the first application development platform.

[0138] In this embodiment, when the interface rendering mode is embedded rendering, the first application debugging interface of the first application development platform is displayed. The first application debugging interface includes a native debugging area of ​​the first application development platform and a configuration area for configuring sub-applications of the second application development platform. The native debugging area includes a simulator area and a toolbar area. When the interface rendering mode is overlay rendering, the native debugging area of ​​the first application development platform is displayed, and the second application debugging interface overlaying the native debugging area is displayed. The second application debugging interface includes a configuration area for configuring sub-applications of the second application development platform.

[0139] In this embodiment, two interface rendering methods defined by the second application development platform are provided, so that the simulator area and the configuration area can be automatically rendered in the first application development platform 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 for configuring the sub-application of the second application development platform are rendered and displayed in the same interface, which is convenient for developers to view the interactive page of the sub-application formed by the configuration while performing page configuration. When the interface rendering method is overlay rendering, 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 the configuration area for configuring the sub-application of the second application development platform, which makes the display freedom of the configuration area higher and can more completely display the content in the configuration area, which is convenient for developers to operate.

[0140] In one embodiment, the method further comprises:

[0141] When the interface rendering mode is embedded rendering, obtain the first layout information of the simulator area of ​​the first application development platform; based on the first layout information of the simulator area, determine the second layout information of the configuration area for configuring the sub-application of 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.

[0142] The first layout information refers to information related to the layout of the simulator area of ​​the first application development platform, including the display position and size of the simulator area. The second layout information refers to information related to the layout of the configuration area used to configure the sub-application of the second application development platform, including the display position and size of the configuration area.

[0143] Specifically, when the interface rendering mode is embedded rendering, the terminal can obtain first layout information of the simulator area provided by the first application development platform. The terminal can obtain original layout information of the configuration area used to configure the sub-application of the second application development platform from the second application development platform, and determine second layout information of the configuration area based on the first layout information of the simulator area and the original layout information.

[0144] The original layout information of the configuration area refers to the layout information of the configuration area used to configure the sub-application of the second application development platform. The second layout information of the configuration area is the layout information formed by adjusting the original layout information based on the first layout information.

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

[0146] 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. The first server generates a first application debugging interface of the first application development platform based on the second layout information and the first layout information.

[0147] In this embodiment, the terminal sends the first layout information and the original layout information to a first server corresponding to the first application development platform. The first server adjusts the original layout information based on the first layout information to obtain the second layout information. The first server generates a first application debugging interface based on the second layout information and the first layout information.

[0148] In one of the embodiments, when the interface rendering mode 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 for configuring the sub-application of the second application development platform is determined; based on the first layout information, the second layout information and the third layout information, the first application debugging interface of 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.

[0149] Furthermore, the terminal sends the first layout information, the second layout information, and the third layout information to a first server corresponding to the first application development platform, and generates a first application debugging interface of the first application development platform based on the first layout information, the second layout information, and the third layout information.

[0150] In this embodiment, when the interface rendering mode 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 for configuring the sub-application of the second application development platform is determined, so that based on the second layout information and the first layout information, the first application debugging interface that can embed the simulator area and the configuration area is accurately generated.

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

[0152] When the interface rendering mode is overlay rendering, obtain the first layout information of the simulator area of ​​the first application development platform; based on the first layout information of the simulator area, determine the second layout information of the configuration area for configuring the sub-application of 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, the second application debugging interface includes a configuration area and an interactive area; display the second application debugging interface, and display the simulator area covered by the interactive area of ​​the second application debugging interface, and the interactive area shows the layout of the simulator area.

[0153] Specifically, when the interface rendering mode is overlay rendering, the terminal obtains the first layout information of the simulator area of ​​the first application development platform. The terminal can obtain the original layout information of the configuration area used to configure the sub-application of 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 and the original layout information of the simulator 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 can generate a 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 interactive area other than the configuration area.

[0154] The terminal displays the second application debugging interface and displays the simulator area covered by the interactive area of ​​the second application debugging interface, and displays the layout of the simulator area through the interactive area. That is, the simulator area is below the interactive area and can be displayed through the interactive area.

[0155] In this embodiment, when the interface rendering mode is overlay rendering, the simulator area of ​​the first application development platform is displayed, and the second application debugging interface overlaid on the simulator area is displayed, including:

[0156] When the interface rendering mode is overlay rendering, first layout information of the simulator area of ​​the first application development platform is sent to the second server corresponding to the second application development platform; the first layout information is used to instruct the second server to determine second layout information of the configuration area, and generate a second application debugging interface based on the second layout information and the first layout information;

[0157] The simulator area of ​​the first application development platform is displayed, and the second application debugging interface covering the simulator area is displayed. The simulator area is located below the interactive area and is displayed through the interactive area.

[0158] In one embodiment, the developer can operate in the configuration area of ​​the second application debugging interface so that the operation can be directly applied to the configuration area. The developer can operate in the interaction area of ​​the second application debugging interface so that the operation can be applied to the simulator area.

[0159] In this embodiment, when the interface rendering mode is overlay 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 for configuring the sub-application of the second application development platform is determined, and based on the second layout information and the first layout information, the second application debugging interface including the configuration area and the interaction area is obtained, so that 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 the developer can see the displayed simulated interaction page in the covered simulator area.

[0160] In one embodiment, the method also includes: when a first preset operation is detected within the configuration area, adjusting the view level of the second application debugging interface to be higher than the view level of the simulator area, and the second application debugging interface after the view level adjustment is used to respond to the operation on the configuration area through the configuration area.

[0161] In one embodiment, the method further includes: when a second preset operation acting on the interactive area is detected, adjusting the view level of the second application debugging interface to be lower than the view level of the simulator area, and after the view level adjustment, the simulator area is used to respond to operations targeting the interactive area.

[0162] Specifically, when the interface rendering mode is overlay rendering, the second application debugging interface is displayed, and the simulator area covered by the interactive area of ​​the second application debugging interface is displayed. The terminal can detect the developer's operation. When an operation in the configuration area is detected, and the 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 level of the second application debugging interface to a level higher than the view level of the simulator area. When the view level of the second application debugging interface is higher than the view level of the simulator area, the developer's operations in the configuration area can directly affect the configuration area.

[0163] When the view level of the second application debugging interface is lower than the view level of the simulator area, the developer's operations in the interactive area in the second application debugging interface can be applied to the simulator area.

[0164] When an operation is detected in the interactive area, and the operation is a second preset operation, indicating that the developer wants to perform a related operation on the simulator area, the terminal adjusts the view level of the second application debugging interface to be lower than the view level of the simulator area. After adjusting the view level of the simulator area, in response to the developer's operation in the interactive area, the operation is applied to the simulator area.

[0165] Furthermore, after adjusting the view hierarchy of the simulator area, in response to the developer's operation in the interactive area, the interaction position of the operation in the interactive area is determined, the corresponding position of the interaction position in the simulator area is determined, and the operation is applied 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 in the interactive area. The developer clicks position a in the interactive area, and the position a is the position of the control A seen by the developer in the interactive 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.

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

[0167] When a first preset operation is detected in the configuration area, the view level of the second application debugging interface is adjusted to be higher than the view level of the native debugging area, so that operations on the configuration area can be applied to the configuration area after the view level adjustment; when a second preset operation is detected in the interactive area, the view level of the second application debugging interface is adjusted to be lower than the view level of the native debugging area, so that operations on the interactive area can be applied to the native debugging area after the view level adjustment. The original debugging area includes the simulator area and the toolbar area.

[0168] For example, to allow developers to operate the native debugging area and the configuration area simultaneously, the view level of the second application debugging interface is automatically moved to the top layer when the mouse moves to the configuration area. At this time, the plug-in needs to detect mouse events on its own. When the mouse moves into the interactive area, it calls the preset interface provided by the first application development platform to lower the view level of the second application debugging interface, allowing operation events in the interactive area to penetrate the interactive area and act on the native debugging area, so that developers can also click on the relevant controls in the native debugging area normally.

[0169] 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 level of the second application debugging interface is adjusted to a level higher than the view level of the simulator area, so that after the view level is adjusted, the developer can directly perform operations in the configuration area. When a second preset operation acting in the interactive area is detected, indicating that the developer wants to perform relevant operations on the simulator area, the view level of the second application debugging interface is adjusted to a level lower than the view level of the simulator area, so that after the view level is adjusted, the developer's operations on the interactive area can act on the simulator area, so that when the second application debugging interface covers the simulator area, the developer can still use the functions of the simulator area normally. This embodiment further improves the efficiency of generating sub-applications by automatically adjusting the view level to adapt to the developer's operations.

[0170] In one embodiment, the method further comprises:

[0171] Run the project creation script built into the template plug-in 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 a simulator area for the first application development platform and a configuration area for configuring the sub-application of the second application development platform.

[0172] Specifically, in response to the developer's selection operation on the template identifier, the terminal determines the template identifier selected by the selection operation and identifies the template plug-in provided by the second application development platform to which the template identifier is bound. The terminal determines the project creation script built into the template plug-in, loads and runs the project creation script, and obtains the sub-application project identifier. Based on the sub-application project identifier, the terminal automatically creates the sub-application development project locally on the first application development platform. Once the sub-application project is created, a simulator area for the first application development platform and a configuration area for configuring the sub-application of the second application development platform are generated.

[0173] The terminal determines the interface rendering mode based on the plug-in configuration file, and displays the simulator area and configuration area according to the interface rendering mode.

[0174] 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 project information for the sub-application development project, and automatically fills the generated project information into the project creation area.

[0175] In this embodiment, the project creation script built into the template plug-in is run to obtain a sub-application project identifier, and based on the sub-application project identifier, a sub-application development project is created locally on the first application development platform, thereby enabling the first application development platform to provide the function of using the custom project creation logic of the second application development platform, and based on the sub-application development project, a simulator area of ​​the first application development platform and a configuration area for configuring the sub-application of the second application development platform are generated, thereby realizing the combination of the debugging function of the first application development platform and the configuration function of the second application development platform.

[0176] In one embodiment, the method further comprises:

[0177] Based on the template plug-in, the sub-application code is obtained from the second application development platform. The sub-application code is generated based on the sub-application page template and the sub-application components added to the sub-application page template; the sub-application code is stored locally and run to obtain a simulated interactive page of the sub-application.

[0178] Specifically, the second application development platform generates the sub-application code based on the sub-application page template and the sub-application component added to the sub-application page template, and the terminal obtains the sub-application code based on the template plug-in provided by the second application development platform.

[0179] The terminal stores the sub-application code locally on the first application development platform and runs the sub-application code stored locally to generate a simulated interaction page between the sub-applications. In response to a simulation trigger event for the simulator area, the terminal displays the simulated interaction page of the sub-application in the simulator area.

[0180] In this embodiment, in response to the trigger operation of 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 simulated interaction page between the sub-application and the sub-application, and displays the simulated interaction page of the sub-application in the simulator area.

[0181] In this embodiment, when a developer adjusts the added components in a 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 plug-in to update the sub-application code locally stored on the first application development platform, thereby displaying the updated sub-application's simulated interaction page in the simulator area.

[0182] In this embodiment, based on the template plug-in, the sub-application code is obtained from the second application development platform, including:

[0183] Call the preset interface provided by the first application development platform; obtain the sub-application code from the second application development platform based on the template plug-in through the preset interface.

[0184] 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 added to the sub-application page template, allowing developers to use the page templates and components defined by the second application development platform in the first application development platform, while still using the second application development platform's original generation logic to generate sub-application code without modifying the sub-application code generation logic. The sub-application code can be obtained from the second application development platform through a template plug-in, stored locally on the first application development platform, and run to obtain a simulated interactive page for the sub-application. This effectively expands the development capabilities of the first application development platform based on the template plug-in, making the first application development platform compatible with the development logic of different development platforms.

[0185] In one embodiment, the template identifier of the sub-application page template provided by the second application development platform is displayed on the sub-application development interface, including:

[0186] The platform identifier of at least one second application development platform is displayed on the sub-application development interface; in response to an identifier selection operation of selecting at least one platform identifier, a template identifier associated with the selected platform identifier is displayed on 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 of the selected platform identifier.

[0187] 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.

[0188] Specifically, the terminal displays the platform identifier of at least one second application development platform on the sub-application development interface. The developer can select from the at least one second application development platform platform identifier. In response to the developer's identifier selection operation, the terminal determines the platform identifier selected by the identifier selection 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 on the sub-application development interface.

[0189] 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.

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

[0191] In this embodiment, the platform identifier of at least one second application development platform is displayed on the sub-application development interface, thereby providing at least one third-party application development platform for developer selection. This allows developers to directly generate sub-applications on the first application development platform using page templates and components provided by other application development platforms. In response to an identifier selection operation performed by selecting from at least one platform identifier, the sub-application development interface displays a template identifier associated with the selected platform identifier. The template identifier is used to identify a sub-application page template provided by the second application development platform associated with the selected platform identifier. This allows page templates provided by the user-selected second application development platform to be displayed for user selection, thereby meeting the user's diverse needs.

[0192] In one embodiment, the method further comprises:

[0193] Displaying a template category trigger control on the sub-application development interface; in response to a triggering operation on the template category trigger control, displaying at least one candidate template category on the sub-application development interface;

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

[0195] In response to an identifier selection operation of selecting from at least one platform identifier and a category selection operation of selecting from at least one candidate template category, template identifiers belonging to the selected template category and associated with the selected platform identifier are displayed in the sub-application development interface.

[0196] The candidate template category refers to the category of the sub-application page template. Different types of sub-applications can be generated by different types of sub-application page templates.

[0197] Specifically, the terminal displays the platform identifier of at least one 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 the platform identifiers of the at least one second application development platform. In response to the developer's identifier selection operation, the terminal determines the platform identifier selected by the identifier selection operation and determines the second application development platform represented by the platform identifier.

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

[0199] The developer may select at least one category from the displayed candidate template categories. In response to the developer's category selection operation, the terminal obtains from the second application development platform template identifiers belonging to the target template category selected by the category selection operation.

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

[0201] In this embodiment, a template category trigger control is displayed in the sub-application development interface. In response to the triggering operation of the template category trigger control, at least one candidate template category is displayed in the sub-application development interface. The types of page templates of other development platforms can be provided to developers in the first application development platform, so that the classification of page templates of other development platforms is more refined, so that developers can flexibly select the corresponding template type according to the type of sub-application they need to generate, thereby displaying the page templates of other development platforms under this type for developers to flexibly select.

[0202] In one embodiment, displaying the platform identifier of at least one second application development platform on the sub-application development interface includes:

[0203] 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 from at least one platform category, a platform identifier of at least one second application development platform belonging to the selected platform category is displayed on the sub-application development interface.

[0204] The platform category refers to the category of the second application development platform. Different application development platforms can generate different sub-applications. For example, a map application development platform can generate map sub-applications, while a voting application development platform can generate voting sub-applications.

[0205] Specifically, the terminal displays the sub-application development interface of the first application development platform, and displays a platform category trigger control in the sub-application development interface. The developer can trigger the control to view different types of second application development platforms. In response to the triggering operation of the platform category trigger control, the terminal displays at least one platform category in the sub-application development interface, and the developer can select at least one category from the displayed platform categories. In response to the category selection operation of the developer selecting from at least one platform category, the terminal determines the platform category selected by the category selection operation and determines the platform identifier of each second application development platform belonging to the platform category. The terminal displays the platform identifier of at least one second application development platform belonging to the selected platform category in the sub-application development interface.

[0206] In this embodiment, the first application development platform displays the platform categories of different categories of second application development platforms on the interface for developers to choose from, so that different categories of second application development platforms can be called on the first application development platform, and different categories of second application development platforms can be integrated into the first application development platform, providing developers with more comprehensive development functions, so that no matter what type of sub-application the developer needs to generate, it can be implemented through the first application development platform without using a specific type of application development platform to generate it, which can improve the flexibility and convenience of sub-application development.

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

[0208] A sub-application development interface of the first application development platform is displayed, and a platform identifier and a template category trigger control of at least one second application development platform are displayed on the sub-application development interface.

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

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

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

[0212] Optionally, when the interface rendering mode is embedded rendering, the first application debugging interface is displayed, and the first application debugging interface includes a simulator area provided by the first application development platform and a toolbar area provided by the first application development platform, and a configuration area for configuring a sub-application of the second application development platform; the configuration area displays a sub-application page template and multiple sub-application components provided by the second application development platform; the toolbar area displays a simulator trigger control, a preview control, and a real device debugging control;

[0213] Optionally, when the interface rendering mode is overlay rendering, the native debugging area of ​​the first application development platform is displayed, and the second application debugging interface is displayed overlaying the native debugging area; the second application debugging interface includes a configuration area for configuring the sub-application of the second application development platform, and an interactive area other than the configuration area. Operations in the interactive area can act on the native debugging area, and the native debugging area includes a toolbar area and a simulator area.

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

[0215] Furthermore, 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, where the simulated interaction page is generated based on the sub-application page template and the sub-application components added to the sub-application page template.

[0216] Furthermore, in response to the triggering operation of the preview control, the first graphic code of the sub-application is displayed in the simulator area, and the first graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application and display the preview interaction page of the sub-application.

[0217] Furthermore, in response to the triggering operation of the real machine debugging control, a second graphic code of the sub-application is displayed in the simulator area. The second graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application, and display the interaction page of the sub-application and the operation log of the sub-application.

[0218] In this embodiment, the sub-application development interface of the first application development platform is displayed, and the platform identifiers of multiple second application development platforms and multiple candidate template categories are displayed on the sub-application development interface of the first application development platform. This provides multiple selectable other application development platforms and multiple selectable page template types in the first application development platform, thereby enabling the first application development platform and the second application development platform to be combined, allowing users to choose to use the page template provided by the second application development platform to generate sub-applications on the first application development platform. After the developer selects the desired second application development platform and the sub-application page template provided by the second application development platform, the template plug-in bound to the template identifier can be used to determine the interface rendering method, thereby determining the interface display method.

[0219] When the interface rendering mode is embedded rendering, the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform are rendered and displayed in the same interface, making it easy for developers to view the interactive pages of the sub-application formed by the configuration while performing page configuration. When the interface rendering mode is overlay rendering, the simulator area of ​​the first application development platform is displayed, and the second application debugging interface overlaid on the simulator area is displayed. The second application debugging interface includes the configuration area for configuring the sub-application of the second application development platform, which allows for greater display freedom of the configuration area and can more completely display the content in the configuration area, facilitating developer operation.

[0220] The configuration area for configuring a sub-application on the second application development platform displays a sub-application page template 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 page templates and components from third-party application development platforms. In response to a component selection operation in which a selection is made 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 in the simulator area, a simulated interaction page for the sub-application is displayed in the simulator area. This simulated 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 functionality of the sub-application through the first application development platform. Furthermore, by generating a sub-application through visual component selection, the user does not need to write code, allowing users who do not understand code to generate customized sub-applications, making sub-application development simpler and improving sub-application development efficiency.

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

[0222] 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 development tools other than developer tools. A sub-application is a mini-program.

[0223] As shown in Figure 8, the project list page in the developer tools adds a template identifier for a third-party service provider. This identifier is displayed as part of the sub-app page template. The project list page is the sub-app development interface. When a developer clicks a template identifier, the sub-app page template identified by the template identifier is displayed in the sub-app development interface.

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

[0225] After successfully creating the project, you will enter the first application debugging interface, as shown in Figure 6. This interface is mainly divided into three parts: the simulator area on the left and the toolbar area above, which are all native functions of the developer tools. The right side is the interface customized by the third-party service provider, namely the configuration area.

[0226] After developers select relevant components in the configuration area on the right, they can directly debug the applet API (Application Programming Interface) in the simulator area on the left. API is a preset interface, which is a set of predefined functions. Its purpose is to provide applications and developers with the ability to access a set of routines based on certain software or hardware without accessing the source code or understanding the details of the internal working mechanism.

[0227] At the same time, developers can use the real-device debugging function in the toolbar area to remotely debug the mini program. Specifically, click the Save control in the toolbar area to display the mini program in the simulator area, or click the "Simulator" control to display the mini program in the simulator area. Click the Preview control in the toolbar area to display the QR code corresponding to the mini program in the simulator area. Scan the QR code with your phone to display the mini program on your phone, as shown in Figure 10. Click the real-device debugging control in the toolbar area to display the QR code corresponding to the mini program in the simulator area. Scan the QR code with your phone to display the mini program and the mini program's running log on your phone.

[0228] On the technical side, as shown in Figure 11, for example, if a developer clicks on a template identifier provided by the map application building platform on the project list page, the developer tool will first read the template plug-in provided by the third-party service provider associated with the template identifier, load and run the project creation script built into the template plug-in to create a project ID, and ultimately return a project ID to the developer tool. The developer tool then uses this project ID to actually create a mini program project. The third-party service provider can then continue to use this project ID for its own permission verification and other logic.

[0229] After creating the project, you will enter the application debugging interface, which includes the native debugging area and the customized configuration area of ​​the third-party service provider template plug-in.

[0230] The application debugging interface is an interface rendered using an interface rendering method. The interface rendering method can be embedded rendering or overlay rendering. The application debugging interface can be a first application debugging interface generated using the embedded rendering method, or a second application debugging interface generated using the overlay rendering method. Embedded rendering refers to a configuration area for configuring sub-applications of the second application development platform, which is directly embedded within the first application debugging interface of the first application development platform, as shown in Figure 12.

[0231] Overlay rendering means that the entire webview is overlaid on the native debugging area. This means that the second application debugging interface provided by the second application development platform covers the simulator area and toolbar area provided by the first application development platform, as shown in Figure 7. Overlay rendering directly overlays the plug-in interface on the entire tool window through the webview, providing greater flexibility in plug-in display functions.

[0232] However, if the template plug-in chooses the overlay rendering method, the template plug-in needs to obtain the layout information of the simulator area and the toolbar area through the API provided by the tool, and reserve a blank transparent area in the webview so that the simulator area and toolbar area can be displayed in the transparent area.

[0233] At the same time, to allow developers to operate simultaneously in the native debugging area and the configuration area in the second application debugging interface, the developer tools automatically move the view hierarchy of the second application debugging interface to the top when the mouse moves over the configuration area. The template plug-in needs to detect mouse operation events and, when the mouse moves over any area of ​​the second application debugging interface other than the configuration area, call the preset interface provided by the developer tools to lower the view hierarchy of the second application debugging interface. This allows operation events to penetrate the second application debugging interface and act on the native debugging area, allowing developers to click the relevant buttons in the native debugging area normally.

[0234] To enable the developer tools' on-device debugging capabilities, the template plugin must pass the newly generated mini-program code to the developer tools, as shown in Figure 13. After the developer enters the project created by the template, the developer tools match the project's template with the corresponding template plugin and determine whether to use embedded or overlay rendering based on the template plugin's configuration file. The template plugin retrieves project ID information and the generated mini-program code from the third-party service provider's template plugin backend, which is the second server corresponding to the second application development platform. The template plugin passes the mini-program code to the developer tools via the developer tools' API. After receiving the mini-program code, the developer tools write it to a local cache directory and then perform a series of initialization steps, including compiling the mini-program code. Upon successful initialization, the result is returned to the target plugin. After successful initialization, the developer can perform any operations in the application debugging interface, such as using the developer tools' on-device debugging capabilities or updating the mini-program configuration in the configuration area. After the developer updates the service configuration, the template plugin regenerates the mini-program code and sends the differentiated code to the developer tools via the developer tools' API. The developer tool synchronizes the code files that need to be updated to the corresponding file contents in the local cache directory, then recompiles the code, triggering an update of the simulator content. The simulator area displays the latest mini-program content.

[0235] This embodiment provides a general sub-application generation method that allows third-party service providers to combine their services with developer tools, allowing developers to simultaneously use third-party services and the developer tools' simulator and real-device debugging, remote breakpoint debugging, and other capabilities, thereby improving developer development efficiency and experience. The implementation of this solution eliminates the need for third-party service providers to develop a complete set of mini-program debugging solutions. Instead, they can simply develop a template plug-in based on the interface provided by the developer tools to achieve expansion. This simultaneously meets the needs of third-party service providers to expand mini-program development capabilities while retaining the original debugging experience of the mini-program developer tools, effectively improving overall development efficiency.

[0236] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0237] Based on the same inventive concept, embodiments of the present application also provide a sub-application generation device for implementing the sub-application generation method involved above. The implementation solution provided by this device is similar to the implementation solution described in the above method. Therefore, the specific limitations in one or more sub-application generation device embodiments provided below can be found in the above limitations on the sub-application generation method and will not be repeated here.

[0238] In one embodiment, as shown in FIG14 , a sub-application generating device 1400 is provided, comprising: an interface display module 1402 , an area display module 1404 , an adding module 1406 , and a page display module 1408 , wherein:

[0239] The interface display module 1402 is used to display the sub-application development interface of the first application development platform; in the sub-application development interface, the template identifier of the sub-application page template provided by the second application development platform is displayed.

[0240] The area display module 1404 is used to display the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform in response to the identification selection operation of the template identification; in the configuration area, the sub-application page template and multiple sub-application components provided by the second application development platform are displayed.

[0241] The adding module 1406 is configured to, in response to a component selection operation of selecting from a plurality of sub-application components, add the sub-application component selected by the component selection operation to the sub-application page template.

[0242] The page display module 1408 is used to display the simulated interactive page formed by simulating the running of the sub-application in the simulator area. The simulated interactive page is generated by using the sub-application page template and the sub-application components added to the sub-application page template.

[0243] In this embodiment, a sub-application development interface of the first application development platform is displayed, and a template identifier of a sub-application page template provided by the second application development platform is displayed on the sub-application development interface of the first application development platform. This allows the first application development platform and the second application development platform to be combined, allowing users to select the page template provided by the second application development platform to generate a sub-application on the first application development platform. In response to the selection operation of the template identifier, a simulator area of ​​the first application development platform and a configuration area for configuring the sub-application of the second application development platform are displayed. The configuration area 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 page templates and components of third-party application development platforms. In response to a component selection operation for selecting from 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 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 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 functions of the sub-application through the first application development platform. In addition, by generating sub-applications through visual component selection, there is no need for users to write code, so that users who do not understand code can also generate customized sub-applications, making the development of sub-applications simpler, thereby improving the development efficiency of sub-applications.

[0244] In one embodiment, the area display module 1404 is also used to display the first application debugging interface in response to the identification selection operation of the template identification; and display the simulator area provided by the first application development platform and the configuration area for configuring the sub-application of the second application development platform on the first application debugging interface.

[0245] In this embodiment, in response to the identification selection operation of the template identification, the 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 for configuring the sub-application of the second application development platform can be displayed simultaneously in the first application debugging interface, so that the sub-application configured by the developer in the configuration area can run in the simulator area, and 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.

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

[0247] In this embodiment, the toolbar area and simulator area provided by the first application development platform, as well as the configuration area for configuring the sub-application of the second application development platform can be displayed in the first application debugging interface of the first application development platform, so that developers 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, so that the services provided by the second application development platform can be combined with the first application development platform, greatly improving the sub-application development capabilities of the first application development platform.

[0248] In one embodiment, the toolbar area displays a preview control; the apparatus further comprises:

[0249] The graphic code display module is used to display the first graphic code of the sub-application in the simulator area in response to the triggering operation of the preview control. The first graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application and display the preview interaction page of the sub-application.

[0250] In this embodiment, in response to the triggering operation of the preview control, the first graphic code of the sub-application is displayed in the simulator area, so that when the first graphic code is scanned, the sub-application is run by the parent application running on the scanning terminal that scans the first graphic code, and the preview interaction page of the sub-application is displayed. The generated sub-application can be run and previewed on other terminals, thereby ensuring that the sub-application can be run on a real machine and that the running effect of the sub-application on the real machine can be presented.

[0251] In one embodiment, the toolbar area displays real-device debugging controls; the apparatus further comprises:

[0252] The graphic code display module is used to display the second graphic code of the sub-application in the simulator area in response to the trigger operation of the real machine debugging control. The second graphic code is used for scanning by the parent application running on the scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application and display the interaction page of the sub-application and the operation log of the sub-application.

[0253] In this embodiment, in response to triggering a real-device debugging control, a second graphical code of the sub-application is displayed in the simulator area. When the second graphical code is scanned, the parent application running on the scanning terminal that scanned the second graphical code runs the sub-application, enabling the sub-application to run on the real device, thereby presenting the sub-application's running effect on the real device. Furthermore, the sub-application's interactive page and running log are displayed, enabling testing of the sub-application's related functions on the real device and facilitating developers to directly view the sub-application's running log on the real device, thereby improving sub-application debugging efficiency.

[0254] In one embodiment, the area display module 1404 is also used to display the simulator area of ​​the first application development platform in response to the identification selection operation of the template identification, and to display the second application debugging interface overlaid on the simulator area; wherein the second application debugging interface includes a configuration area for configuring the sub-application of the second application development platform, and an interactive area other than the configuration area, and operations in the interactive area can act on the simulator area.

[0255] In this embodiment, in response to an operation to select a template identifier, the simulator area of ​​the first application development platform is displayed, and a second application debugging interface is displayed overlying the simulator area. The second application debugging interface includes a configuration area for configuring sub-applications of the second application development platform, as well as an interactive area in addition to the configuration area, allowing for greater display freedom in the configuration area. Operations in the interactive area can be applied to the simulator area, making it possible to operate the simulator area from the interactive area. Configurations in the configuration area and operations on the simulator area can be implemented on the same interface, effectively expanding the functionality of the first application development platform and making the interface display more flexible to meet the needs of different users.

[0256] In one embodiment, the area display module 1404 is also used to obtain a template plug-in provided by the second application development platform bound to the template identifier in response to an identifier selection operation on the template identifier; determine a plug-in configuration file of the template plug-in, and determine an interface rendering method based on the plug-in configuration file; and display the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform according to the interface rendering method.

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

[0258] In one embodiment, the area display module 1404 is also used to display the first application debugging interface of the first application development platform when the interface rendering mode is embedded rendering, and the first application debugging interface includes the simulator area of ​​the first application development platform and the configuration area for configuring the sub-application of the second application development platform; when the interface rendering mode is overlay rendering, the simulator area of ​​the first application development platform is displayed, and the second application debugging interface covering the simulator area is displayed, and the second application debugging interface includes the configuration area for configuring the sub-application of the second application development platform.

[0259] In this embodiment, two interface rendering methods defined by the second application development platform are provided, so that the simulator area and the configuration area can be automatically rendered in the first application development platform 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 for configuring the sub-application of the second application development platform are rendered and displayed in the same interface, which is convenient for developers to view the interactive page of the sub-application formed by the configuration while performing page configuration. When the interface rendering method is overlay rendering, 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 the configuration area for configuring the sub-application of the second application development platform, which makes the display freedom of the configuration area higher and can more completely display the content in the configuration area, which is convenient for developers to operate.

[0260] In one embodiment, the apparatus further comprises:

[0261] A generation module is used to obtain first layout information of the simulator area of ​​the first application development platform when the interface rendering mode is embedded rendering; based on the first layout information of the simulator area, determine second layout information of the configuration area for configuring the sub-application of the second application development platform; based on the second layout information and the first layout information, generate a first application debugging interface of the first application development platform.

[0262] In this embodiment, when the interface rendering mode 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 for configuring the sub-application of the second application development platform is determined, so that based on the second layout information and the first layout information, the first application debugging interface that can embed the simulator area and the configuration area is accurately generated.

[0263] In one embodiment, the apparatus further comprises:

[0264] A generation module is used to obtain first layout information of the simulator area of ​​the first application development platform when the interface rendering mode is overlay rendering; based on the first layout information of the simulator area, determine second layout information of the configuration area for configuring the sub-application of the second application development platform; based on the second layout information and the first layout information, obtain a second application debugging interface provided by the second application development platform, the second application debugging interface including a configuration area and an interactive area; display the second application debugging interface, and display the simulator area covered by the interactive area of ​​the second application debugging interface, the interactive area showing the layout of the simulator area.

[0265] In this embodiment, when the interface rendering mode is overlay 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 for configuring the sub-application of the second application development platform is determined, and based on the second layout information and the first layout information, the second application debugging interface including the configuration area and the interaction area is obtained, so that 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 the developer can see the displayed simulated interaction page in the covered simulator area.

[0266] In one embodiment, the apparatus further comprises:

[0267] The adjustment module is used to adjust the view level of the second application debugging interface to be higher than the view level of the simulator area when a first preset operation is detected in the configuration area. The second application debugging interface after the view level adjustment is used to respond to operations on the configuration area through the configuration area.

[0268] The adjustment module can be used to adjust the view level of the second application debugging interface to a level lower than the view level of the simulator area when a second preset operation acting on the interactive area is detected. After the view level is adjusted, the simulator area is used to respond to operations targeting the interactive area.

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

[0270] In one embodiment, the apparatus further comprises:

[0271] The project creation module is used to run the project creation script built into the template plug-in 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 for configuring the sub-application of the second application development platform.

[0272] In this embodiment, the project creation script built into the template plug-in is run to obtain a sub-application project identifier, and based on the sub-application project identifier, a sub-application development project is created locally on the first application development platform, thereby enabling the first application development platform to provide the function of using the custom project creation logic of the second application development platform, and based on the sub-application development project, a simulator area of ​​the first application development platform and a configuration area for configuring the sub-application of the second application development platform are generated, thereby realizing the combination of the debugging function of the first application development platform and the configuration function of the second application development platform.

[0273] In one embodiment, the apparatus further comprises:

[0274] The sub-application code acquisition module is used to obtain the sub-application code from the second application development platform based on the template plug-in. The sub-application code is generated based on the sub-application page template and the sub-application components added to the sub-application page template; the sub-application code is stored locally and run to obtain the simulated interactive page of the sub-application.

[0275] 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 added to the sub-application page template, allowing developers to use the page templates and components defined by the second application development platform in the first application development platform, while still using the second application development platform's original generation logic to generate sub-application code without modifying the sub-application code generation logic. The sub-application code can be obtained from the second application development platform through a template plug-in, stored locally on the first application development platform, and run to obtain a simulated interactive page for the sub-application. This effectively expands the development capabilities of the first application development platform based on the template plug-in, making the first application development platform compatible with the development logic of different development platforms.

[0276] In one embodiment, the interface display module 1402 is also used to display the platform identifier of at least one second application development platform in the sub-application development interface; in response to an identifier selection operation of selecting 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 of the selected platform identifier.

[0277] In this embodiment, the platform identifier of at least one second application development platform is displayed on the sub-application development interface, thereby providing at least one third-party application development platform for developer selection. This allows developers to directly generate sub-applications on the first application development platform using page templates and components provided by other application development platforms. In response to an identifier selection operation performed by selecting from at least one platform identifier, the sub-application development interface displays a template identifier associated with the selected platform identifier. The template identifier is used to identify a sub-application page template provided by the second application development platform associated with the selected platform identifier. This allows page templates provided by the user-selected second application development platform to be displayed for user selection, thereby meeting the user's diverse needs.

[0278] In one embodiment, the interface display module 1402 is also used to display a template category trigger control in the sub-application development interface; in response to a triggering operation on the template category trigger control, at least one candidate template category is displayed in the sub-application development interface; in response to an identifier selection operation of selecting from at least one platform identifier and a category selection operation of selecting from at least one candidate template category, a template identifier belonging to the selected template category and associated with the selected platform identifier is displayed in the sub-application development interface.

[0279] In this embodiment, a template category trigger control is displayed in the sub-application development interface. In response to the triggering operation of the template category trigger control, at least one candidate template category is displayed in the sub-application development interface. The types of page templates of other development platforms can be provided to developers in the first application development platform, so that the classification of page templates of other development platforms is more refined, so that developers can flexibly select the corresponding template type according to the type of sub-application they need to generate, thereby displaying the page templates of other development platforms under this type for developers to flexibly select.

[0280] In one embodiment, the interface display module 1402 is also used 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, at least one platform category is displayed in the sub-application development interface; in response to a category selection operation of selecting at least one platform category, the platform identifier of at least one second application development platform belonging to the selected platform category is displayed in the sub-application development interface.

[0281] In this embodiment, the first application development platform displays the platform categories of different categories of second application development platforms on the interface for developers to choose from, so that different categories of second application development platforms can be called on the first application development platform, and different categories of second application development platforms can be integrated into the first application development platform, providing developers with more comprehensive development functions, so that no matter what type of sub-application the developer needs to generate, it can be implemented through the first application development platform without using a specific type of application development platform to generate it, which can improve the flexibility and convenience of sub-application development.

[0282] Each module in the above-mentioned sub-application generation device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0283] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be shown in Figure 15. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. 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 a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via wired or wireless communication, and the wireless communication may be implemented via Wi-Fi, a mobile cellular network, NFC (near field communication), or other technologies. When executed by the processor, the computer program implements a sub-application generation method. The display unit of the computer device is used to form a visually visible image, and 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, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse, etc.

[0284] Those skilled in the art will understand that the structure shown in FIG15 is merely a block diagram of a portion of the structure 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 shown in the figure, or combine certain components, or have a different arrangement of components.

[0285] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

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

[0287] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0288] 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 used 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 must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0289] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and 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-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may 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). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0290] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, 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, they should be considered to be within the scope of this specification.

[0291] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A method for generating a sub-application, which is executed by a terminal, and the method includes: Displaying a sub-application development interface of a first application development platform; In the sub-application development interface, displaying a template identifier of a sub-application page template provided by a second application development platform; In response to an identifier selection operation on the template identifier, displaying an emulator area of the first application development platform and a configuration area for configuring the sub-application of the second application development platform; In the configuration area, displaying 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 of selecting among the plurality of sub-application components, adding the sub-application component selected by the component selection operation to the sub-application page template; And Displaying in the emulator area a simulated interaction page formed by simulating the operation of the sub-application, where the sub-application is generated by using the sub-application page template and the sub-application components added to the sub-application page template.

2. The method according to claim 1, where the displaying the emulator area of the first application development platform and the configuration area for configuring the sub-application of the second application development platform in response to an identifier selection operation on the template identifier includes: In response to an identifier selection operation on the template identifier, displaying a first application debugging interface; In the first application debugging interface, displaying the emulator area provided by the first application development platform and the configuration area for configuring the sub-application of the second application development platform.

3. According to the method described in claim 2, the first application debugging interface further displays a toolbar area provided by the first application development platform; The displaying in the emulator area a simulated interaction page formed by simulating the operation of the sub-application includes: Displaying an emulator trigger control in the toolbar area; In response to a trigger operation on the emulator trigger control, displaying in the emulator area a simulated interaction page formed by simulating the operation of the sub-application.

4. The method according to claim 3, where a preview control is displayed in the toolbar area; the method further includes: In response to a trigger operation on the preview control, displaying a first graphic code of the sub-application in the emulator area, where the first graphic code is used for being scanned by a parent application running on a scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application, and displaying a preview interaction page of the sub-application.

5. The method according to claim 3 or 4, where a real device debugging control is displayed in the toolbar area; the method further includes: In response to a trigger operation on the real device debugging control, displaying a second graphic code of the sub-application in the emulator area, where the second graphic code is used for being scanned by a parent application running on a scanning terminal to instruct the parent application running on the scanning terminal to run the sub-application, and displaying an interaction page of the sub-application and a running log of the sub-application.

6. The method according to any one of claims 1 to 5, where the displaying the emulator area of the first application development platform and the configuration area for configuring the sub-application of the second application development platform in response to an identifier selection operation on the template identifier includes: In response to an identification selection operation on the template identification, display the simulator area of the first application development platform and display a second application debugging interface overlaid on the simulator area; Wherein, the second application debugging interface includes a configuration area for configuring sub-applications of the second application development platform and an interaction area other than the configuration area, and operations triggered in the interaction area act on the simulator area.

7. The method according to any one of claims 1 to 6, wherein the step of, in response to an identification selection operation on the template identification, displaying the simulator area of the first application development platform and a configuration area for configuring sub-applications of the second application development platform includes: In response to an identification selection operation on the template identification, obtain a template plugin provided by the second application development platform bound to the template identification; 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 a configuration area for configuring sub-applications of the second application development platform.

8. The method according to claim 7, wherein the step of, according to the interface rendering method, displaying the simulator area of the first application development platform and a configuration area for configuring sub-applications of the second application development platform includes: 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 a configuration area for configuring sub-applications of the second application development platform.

9. The method according to claim 7 or 8, wherein the step of, according to the interface rendering method, displaying the simulator area of the first application development platform and a configuration area for configuring sub-applications of the second application development platform includes: 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, and the second application debugging interface includes a configuration area for configuring sub-applications of the second application development platform.

10. The method according to claim 8 or 9, further comprising: When the interface rendering method is embedded rendering, obtain first layout information of the simulator area of the first application development platform; Based on the first layout information of the simulator area, determine second layout information of a configuration area for configuring sub-applications of 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.

11. The method according to claim 9, wherein the step of, 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, obtain first layout information of the simulator area of the first application development platform; Determine second layout information for configuring the configuration area of the sub-application of the 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 the configuration area and the 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 shown in the interaction area.

12. The method according to claim 11, the method further includes: When detecting a first preset operation within the configuration area, adjust the view hierarchy of the second application debugging interface to be higher than the view hierarchy of the simulator area. After the view hierarchy adjustment, the second application debugging interface is used to respond to operations on the configuration area through the configuration area.

13. The method according to claim 11 or 12, the method further includes: When detecting a second preset operation acting on the interaction area, adjust the view hierarchy of the second application debugging interface to be lower than the view hierarchy of the simulator area. After the view hierarchy adjustment, the simulator area is used to respond to operations on the interaction area.

14. The method according to any one of claims 7 to 13, the method further includes: Run the 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 a simulator area of the first application development platform and a configuration area for configuring the sub-application of the second application development platform based on the sub-application development project.

15. The method according to any one of claims 7 to 14, the method further includes: 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 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.

16. The method according to any one of claims 1 to 15, in the sub-application development interface, displaying the template identifier of the sub-application page template provided by the second application development platform 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, display, in the sub-application development interface, 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.

17. The method according to claim 15, 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; In response to an identification selection operation for selecting among the at least one platform identification, in the sub-application development interface, display a template identification associated with the selected platform identification, including: In response to an identification selection operation for selecting among the at least one platform identification and a category selection operation for selecting among the at least one candidate template category, in the sub-application development interface, display a template identification that belongs to the selected template category and is associated with the selected platform identification.

18. The method according to claim 16, wherein the displaying, in the sub-application development interface, of the platform identifications of at least one second application development platform 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 for selecting among the at least one platform category, in the sub-application development interface, display the platform identifications of at least one second application development platform that belongs to the selected platform category.

19. A sub-application generation device, the device includes: An interface display module, configured to display a sub-application development interface of a first application development platform; In the sub-application development interface, display a template identification of a sub-application page template provided by a second application development platform; A region display module, configured to, in response to an identification selection operation for the template identification, display an emulator region of the first application development platform and a configuration region for configuring the sub-application of the second application development platform; In the configuration region, display 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 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; And A page display module, configured to display a simulated interaction page formed by simulating the operation of the sub-application in the emulator region, where the simulated interaction page is generated using the sub-application page template and the sub-application components already added to the sub-application page template.

20. A computer device, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, implements the steps of the method according to any one of claims 1 to 18.

21. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the method according to any one of claims 1 to 18.

22. A computer program product, including a computer program, and when the computer program is executed by a processor, implements the steps of the method according to any one of claims 1 to 18.

Images