WO2023178952A1

WO2023178952A1 - Method and apparatus for integrating native program with applet, and device and medium

Info

Publication number: WO2023178952A1
Application number: PCT/CN2022/119712
Authority: WO
Inventors: 王钰; 陈卓; 黄河; 谢治民; 徐鑫源; 叶樟源; 黄永生; 周继恩; 李伟; 沈玺; 汤之雄
Original assignee: 中国银联股份有限公司
Priority date: 2022-03-24
Filing date: 2022-09-19
Publication date: 2023-09-28
Also published as: CN114691236A; CN114691236B

Abstract

The present application belongs to the field of data processing. Disclosed are a method and apparatus for integrating a native program with an applet, and a device and a medium. The method comprises: in response to a switching selection input for a page of a native program, selecting, from an applet list provided by the native program, applet information that represents a target applet; acquiring long-term static information of the target applet, and locally storing same; acquiring short-term dynamic information of the target applet, and according to the long-term static information and the short-term dynamic information, making the target applet run in an applet container, and switching a display page from the page of the native program to a page of the target applet; and in response to an applet start input, calling the native program to read the long-term static information of the target applet, and setting a main task and a root page of the native program to be the applet container, such that a terminal device displays the page of the target applet by means of the native program.

Description

Integration methods, devices, equipment and media for native programs and mini programs

Cross-references to related applications

This application claims priority to Chinese patent application 202210293530.4 titled "Integration Method, Device, Equipment and Medium of Native Programs and Mini Programs" submitted on March 24, 2022. The entire content of this application is incorporated herein by reference. middle.

Technical field

This application belongs to the field of data processing, and in particular relates to a method, device, equipment and medium for integrating native programs and applets.

Background technique

Mini programs are lightweight applications that can be used without downloading and installation. The development difficulty is lower than that of native programs. It can reduce the development difficulty and save device memory space on the basis of realizing lightweight functions. However, due to the characteristics of small programs, their functions are relatively simple, and their interaction with users and visual experience cannot be compared with native programs. In other words, mini programs are less effective in terms of interaction with users and visual experience.

Contents of the invention

Embodiments of the present application provide a method, device, equipment and medium for integrating native programs and mini programs, which can improve the interaction between mini programs and users and the visual experience.

In a first aspect, embodiments of the present application provide a method for integrating native programs and mini programs, including: in response to a switching selection input for a page of a native program in a terminal device, selecting a representative target mini program from a list of mini programs provided by the native program. The applet information of the program; obtain the long-term static information of the target applet and save it locally; obtain the short-term dynamic information of the target applet, and make the target applet appear in the applet of the terminal device based on the long-term static information and short-term dynamic information of the target applet. Run in the program container, and switch the display page from the page of the native program to the page of the target applet; in response to the applet startup input, the native program is called to read the long-term static information of the target applet, and the main task and root of the native program are The page is set as an applet container so that the terminal device displays the page of the target applet through the native program.

In the second aspect, embodiments of the present application provide a method for integrating native programs and mini programs, including: a selection module, configured to select input in response to switching selection input of the page of the native program in the terminal device, and select the mini program provided by the native program in the terminal device. Select the small program information that represents the target applet from the list; the acquisition module is used to obtain the long-term static information of the target applet and save it locally; the acquisition module is also used to obtain the short-term dynamic information of the target applet; the control module is used to obtain the target applet's short-term dynamic information based on The long-term static information and short-term dynamic information of the target applet enable the target applet to run in the applet container of the terminal device and switch the display page from the page of the native program to the page of the target applet; the control module is also used to respond to The applet starts the input, calls the native program to read the long-term static information of the target applet, and sets the main task and root page of the native program as the applet container, so that the terminal device displays the page of the target applet through the native program.

In a third aspect, embodiments of the present application provide a terminal device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the integration method of the native program and the applet of the first aspect is implemented.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium. Computer program instructions are stored on the computer-readable storage medium. When the computer program instructions are executed by a processor, the integration method of the native program and the applet of the first aspect is implemented. .

Embodiments of the present application provide a method, device, equipment and medium for integrating native programs and applets. The user can perform switching selection input on the page of the native program in the terminal device, and the terminal device responds to the switching selection input to determine the target applet that needs to be switched. The program saves the long-term static information of the target applet locally, obtains the short-term dynamic information of the target applet, and makes the target applet run in the applet container based on the long-term static information and short-term dynamic information of the target applet. The page of the native program is switched to the page of the target applet, and the page of the target applet is displayed using the native program. When the mini program is restarted in response to the mini program startup input, the terminal device calls the native program to read the long-term static information, sets the main task and root page of the native program as the mini program container, and displays the target mini program through the native program The page enables the mini program to be consistent or consistent with the native program in terms of interaction with the user and visual experience, and improves the interaction between the mini program and the user and the visual experience.

Description of the drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the drawings required to be used in the embodiments of the present application will be briefly introduced below. For those of ordinary skill in the art, without exerting creative efforts, they can also Additional drawings can be obtained from these drawings.

Figure 1 is a schematic diagram of an example of an application scenario of the integration method of native programs and mini programs provided by the embodiment of the present application;

Figure 2 is a flow chart of an embodiment of the integration method of native programs and mini programs provided by this application;

Figure 3 is a flow chart of an example of the process of switching from a native program page to a mini program page provided by an embodiment of the present application;

Figure 4 is a schematic diagram of the logical architecture of an example of coexistence of native programs and applets in a terminal device provided by an embodiment of the present application;

Figure 5 is a flow chart of an example of the native program restart process provided by the embodiment of the present application;

Figure 6 is a flow chart of another embodiment of the integration method of native programs and mini programs provided by this application;

Figure 7 is a flow chart of an example of the process of starting an applet through the desktop icon of the applet provided by the embodiment of the present application;

Figure 8 is a flow chart of another embodiment of the integration method of native programs and mini programs provided by this application;

Figure 9 is a flow chart of an example of the process of starting a mini program through link information provided by the embodiment of the present application;

Figure 10 is a flow chart of yet another embodiment of the integration method of native programs and mini programs provided by this application;

Figure 11 is a flow chart of an example of the process of starting a mini program through push information provided by the embodiment of the present application;

Figure 12 is a schematic structural diagram of an embodiment of an integrated device for native programs and applets provided by this application;

Figure 13 is a schematic structural diagram of an embodiment of the terminal device provided by this application.

Detailed ways

Features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be described in further detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described here are only intended to explain the application, but not to limit the application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.

With the development of network technology, the application of terminal devices such as mobile phones, tablet computers, and electronic computers is becoming more and more common. Users can complete various functions through terminal devices. For example, users can complete various functions such as document processing, payment, instant messaging, and image processing through terminal devices. Specifically, the terminal device can realize various functions through native programs. However, native programs need to be downloaded and installed, occupy a large amount of storage space on the terminal device, and are difficult to develop. In order to implement functions more simply, reduce the storage space occupied, and reduce difficulty, small programs came into being. Mini programs are lightweight applications that can be used without downloading and installation. The development difficulty is lower than that of native programs. It can reduce the development difficulty and save device memory space on the basis of realizing lightweight functions. However, it is precisely because mini programs do not require downloading and installation that while reducing the difficulty of development and saving device memory space, they also make mini programs relatively simple in function and unable to implement more complex functions. In terms of interaction with users and visual experience, etc. Compared to native programs.

Embodiments of the present application provide a method, device, equipment, and medium for integrating native programs and mini programs. The mini program can be selected from the mini program list provided by the native program, and the native program can be used to display the page of the mini program. After the display page has been switched to the page of the mini program and the native program is closed, when the mini program is launched again, the user does not need to enter the page of the native program first and then the page of the mini program. The user can directly enter the page of the mini program through the native program. , thereby making the interaction between the mini program and the user and the visual experience effects consistent or tending to be consistent with the native program effects, and improving the effects of the mini program on the user interaction and visual experience.

The integration method of native programs and small programs provided by the embodiments of this application mainly involves terminal devices, and native programs are installed in the terminal devices. The terminal device can communicate with the background system of the native program, the mini program platform, etc. through the gateway to realize the functions of the native program and the mini program. FIG. 1 is a schematic diagram of an example of an application scenario of the integration method of native programs and mini programs provided by the embodiment of the present application. As shown in Figure 1, the user 11 can operate the terminal device 12, and the terminal device 12 has native programs installed. The terminal device 12 may include a mobile phone, a tablet computer, an electronic computer, a wearable device, etc., which is not limited here. The terminal device 12 can communicate and interact with the background system 14 of the native program through the gateway 13, and the terminal device 12 can also communicate and interact with the applet platform 15 through the gateway 13 to obtain applet information. The operator of the native program can manage and maintain the backend system 14 of the native program through the management system 16 . Users of the mini program platform 15 can upload the developed mini programs to the mini program platform 15 and manage and maintain the mini programs they have developed.

The integration methods, devices, equipment and media of native programs and mini programs provided by this application will be described in sequence below.

This application provides an integration method of native programs and mini programs, which can be applied to terminal devices, that is, the integration method of native programs and mini programs can be executed by terminal devices. Figure 2 is a flow chart of an embodiment of the integration method of native programs and mini programs provided by this application. As shown in Figure 2, the program and applet integration method may include steps S201 to S204.

In step S201, in response to a switching selection input to the page of the native program in the terminal device, applet information representing the target applet is selected from the applet list provided by the native program.

The terminal device currently displays the page of the native program. By inputting the page of the native program, the mini program list can be evoked. For example, the page of the native program includes a human-computer interaction control that evokes a list of mini-programs. When the human-computer interaction control is clicked, the display of the mini-program list is triggered.

The applet list may include applet information for at least one applet. Mini program information can characterize the mini program. For example, the mini program information may include the mini program name, the mini program version name, the mini program type, the mini program graphic logo, the mini program page thumbnail, the mini program introduction, the mini program logo, the native program version supported by the mini program, the mini program One or more of the following information: owner identification, mini program priority, etc. The mini program type can represent the function type of the mini program, such as payment type, game type, shopping type, etc., which is not limited here. The mini program graphic logo can be implemented as the mini program graphic logo or the Uniform Resource Locator (URL) address of the mini program graphic logo in the mini program list. When the URL address of the mini program graphic logo is triggered, the mini program graphic can be displayed. logo. The mini program page thumbnail can be implemented as the mini program page thumbnail or the URL address of the mini program page thumbnail in the mini program list. When the URL address of the mini program page thumbnail is triggered, the mini program page thumbnail can be displayed. The applet identifier is used to identify the applet, and can be an identifier such as the number of the applet. In some examples, the applet identifier can be an encryption identifier, which is not limited here. The mini program owner identifier can be the organization number of the mini program developer. The priority of the mini program can be the priority set by the owner of the native program or the priority set by the owner of the mini program platform, which is not limited here; in some examples, the priority of the mini program can be represented by a number, and the value of the number is higher. The larger the value, the higher the priority. Mini Program information allows users to better understand Mini Programs and facilitates users to make choices.

In some embodiments, before performing step S201, the applet list may be obtained. In some examples, the applet list can be stored in the terminal device. When the applet list needs to be called up, the terminal device can directly obtain the applet list from itself. In other examples, the terminal device may send an applet acquisition request to the background system of the native program to obtain the applet list from the background system of the native program.

The mini program list may include mini program information of the mini programs arranged in descending order of recommendation. Recommendation can be determined based on the user's function usage information. Function usage information includes information related to users' use of native program functions and information related to users' use of mini program functions. Based on the function usage information, the user's function usage can be profiled to obtain the user's function usage habits, and then based on the user's function usage habits, the recommendation degree of the mini program can be obtained.

Function usage information may include one or more of the following: mini program version name, mini program region, mini program priority, mini program binding resource information, mini program attention volume, payment information, payment institution information, user personal information information.

When the function usage information includes one piece of information, the level of recommendation can be determined based on this piece of information.

In some examples, the function usage information includes a mini program version name. The mini program version name indicates that the closer the mini program is to the native program, the higher the recommendation of the mini program. For example, the recommendation degree of a mini program that is a derivative of a native program is higher than that of a mini program that has nothing to do with the native program.

In some examples, the function usage information includes the region where the mini program belongs. The closer the current geographical location of the terminal device is to the region where the mini program belongs, the higher the recommendation degree of the mini program. For example, the recommendation degree of a Mini Program whose region includes the current geographical location of the terminal device is higher than the recommendation degree of an Mini Program whose region does not include the current geographical location of the terminal device.

In some examples, the function usage information includes the applet priority. The higher the applet priority, the higher the applet recommendation. For example, the recommendation degree of a mini program with a mini program priority of 5 is higher than the recommendation degree of a mini program with a mini program priority of 2.

In some examples, the function usage information includes applet binding resource information. Mini program binding resource information can be obtained from the resource binding completion page when the user completes resource binding, which is not limited here. Mini program binding resource information is information related to mini program binding resources. For example, mini program binding resource information may include mini program binding resources, the frequency of mini program binding resources being used by users, the number of mini program binding resources, etc. . The more frequently the resources bound to a mini program are used by users, the higher the recommendation degree of the mini program; the greater the number of resources bound to a mini program, the higher the recommendation degree of the mini program. For example, the resource bound to the mini program is a payment card or merchant bound to the mini program. The recommendation degree of the mini program matching the payment card or merchant bound to the mini program is higher than that of the payment card or merchant not bound to the mini program. The recommendation degree of the matching mini program; the recommendation degree of the mini program with high usage frequency of the payment card or merchant bound to the mini program is higher than the recommendation degree of the mini program with low usage frequency of the payment card or merchant bound to the mini program; and The recommendation degree of a Mini Program with a large number of payment cards or merchants bound to the Mini Program is higher than that of a Mini Program with a small number of payment cards or merchants bound to the Mini Program.

In some examples, the function usage information includes the number of followers of the mini program. The higher the number of followers of the mini program, the higher the recommendation degree of the mini program. For example, the recommendation degree of a mini program with a high number of mini program followers is higher than the recommendation degree of a mini program with a low number of mini program followers.

In some examples, feature usage information includes payment information. The payment information can be obtained from the payment completion page when the user completes the payment, which is not limited here. Payment information is information related to user payment, and payment information may include payment cards or payment merchants. For example, if the payment information includes a payment card, the recommendation degree of the mini program that matches the payment card is higher than the recommendation degree of the mini program that does not match the payment card; if the payment information includes a payment merchant, the recommendation degree of the mini program that matches the payment merchant is higher. degree, higher than the recommendation degree of mini programs that do not match the payment merchant.

In some examples, the function usage information includes payment affiliation information. The payment institution information can be obtained from the payment details page when the user views the payment details, and is not limited here. The payment institution information may represent the institution to which the payment belongs. For example, the recommendation degree of a mini program that matches the payment institution information is higher than the recommendation degree of a mini program that does not match the payment institution information.

In some examples, feature usage information includes user personal information. Based on the recommendation degree matching the common user characteristics in big data with the mini program, the recommendation degree of the mini program suitable for the user's personal information can be obtained. The recommendation degree of the mini program that matches the user's personal information is higher than the recommendation degree of the mini program that does not match the user's personal information. For example, if the user's personal information includes age, and the age in the user's personal information is 26, then the recommendation degree of a mini program matching the age group of 20 to 30 years old is higher than the recommendation degree of a mini program matching the age group of 40 to 50 years old. .

When the function usage information includes two or more pieces of information, the degree of recommendation can be determined based on the two or more pieces of information and the weight corresponding to each piece of information.

In some embodiments, the applet list may include applet information for a first type of applet and/or applet information for a second type of applet.

The first category of mini programs includes mini programs that are mini-programmed versions of native programs. The mini-programmed version of a native program refers to a specific version derived from a native program. The mini-programmed version of a native program is a specific version of a mini program derived from a native program. For example, the first type of mini-program may include a native program. Simple version of the program, mini programs based on native programs that retain and enhance some functions for specific groups of people, etc. are not limited here. Compared with the solution of implementing a derivative version through a native program, the embodiment of the present application implements a derivative version of the native program through a mini program. Users do not need to download the derivative version of the native program and can switch to the corresponding derivative version of the mini program according to their own needs. When multiple versions of functions can be implemented, the storage space occupied in the terminal device is reduced, and the applet can also reduce the difficulty of developing derivative versions of the native program. In the embodiments of this application, the effects of the mini-programmed version of the native program on user interaction and visual experience can be consistent or similar to those of the native program, thereby further improving the user experience.

The second category of mini programs includes mini programs that are owned by a different party than the original program. Native programs can also integrate mini programs from different owners. The terminal device receives the user's operation input and can evoke a mini program in the native program whose owner is different from the owner of the native program. The functions of mini programs whose owners are different from those of the native program can be similar to the functions of the native program, or they can be different from the functions of the native program, which is not limited here. For example, the native program is an application of a payment platform, and the mini program list of the native program may include mini program information of multiple banks' mini programs. For another example, if the native program is an application of a third payment platform, the mini program list of the native program may include the itinerary code to query the mini program information of the mini program. By adding the mini program information of the mini program whose owner is different from the native program in the mini program list, the functions that can be realized with the help of the native program can be further enriched, making the terminal device function implementation more flexible.

For example, if the native program is program A1, the list of mini programs that the native program can provide may include the mini program information of the simplified version of the program A1, mini program B1, the mini program information of the senior version of the program A1, B2, and the mini program C1 of Bank1. The applet information of Bank2, the applet information of Bank2, the applet information of itinerary code query applet D1 and the applet information of merchant shopping applet D2.

The toggle selection input is used to select an applet in the list of applets. The target applet is the applet selected in the applet list for the toggle selection input. The switching selection input can be single click input, multiple click input, sliding input, etc., which is not limited here.

In step S202, long-term static information of the target applet is obtained and saved locally.

Long-term static information is information that is effective for a long time in a mini program and is relatively difficult to change. For example, long-term static information may include the mini program identifier, configuration information of the mini program, fixed display information of the mini program, etc., which is not limited here. The terminal device can request long-term static information of the target applet from the applet platform.

Save long-term static information locally until the next time you switch the selection input to select a different target applet or select a native program. After this switching selection input selects the target applet and the next switching selection input does not occur, long-term static information is always saved locally. After the current switching selection input selects the target applet and the next switching selection input occurs, if the target applet selected by the next switching selection input is different from the target applet selected by this switching selection input, it will be deleted locally. The long-term static information of the target applet selected by the input selection of this switch is saved locally, and the long-term static information of the target applet selected by the input selection of the next switch is saved locally.

In step S203, obtain the short-term dynamic information of the target applet, make the target applet run in the applet container of the terminal device based on the long-term static information and short-term dynamic information of the target applet, and change the display page from the page of the native program Switch to the page of the target applet.

The operation of the target applet also requires the acquisition of short-term dynamic information of the target applet. Short-term dynamic information is real-time information of a mini program that is relatively easy to change. For example, short-term dynamic information may include policy lists, URL addresses of dynamically changing pages, etc., which is not limited here. The terminal device can request short-term dynamic information of the target applet from the applet platform.

The applet container can be regarded as the framework of the applet. Long-term static information and short-term dynamic information work together to enable the mini program to run in the mini program container. After obtaining the short-term dynamic information of the target applet, the page of the target applet can be obtained based on the long-term static information and short-term dynamic information of the target applet, so that the display page of the native program can be switched from the page of the native program to the page of the target applet. page. Specifically, the page of the native program can be switched to the homepage of the target applet.

In step S204, in response to the applet startup input, the native program is called to read the long-term static information of the target applet, and the main task and root page of the native program are set as the applet container, so that the terminal device displays the target applet through the native program. program page.

The applet startup input is an input operation used to start the applet. The terminal device receives the applet startup input, calls the native program, reads the long-term static message of the target applet saved in step S202 through the native program, and saves the main program of the native program. The task and root page are set as mini program containers, so that after the native program is triggered and opened, the main task is to run the target mini program. The root page, that is, the first page loaded is the page of the target mini program, so that after the native program is called and opened, the terminal The device directly displays the page of the target applet.

In some embodiments, before calling the native program to read the long-term static information of the target applet, the terminal device may determine whether the applet container is open. When the display page of the native program is switched from the page of the native program to the page of the mini program, the mini program container needs to be opened so that the mini program can run. By determining whether the mini program container is open, it can be determined whether the displayed page of the native program after the latest switch is the page of the mini program or the page of the native program. If the applet container is open, it can be determined that the display page of the native program after the latest switch is the page of the applet, which means that the applet can be displayed directly through the native program; if the applet container is not open, it can be determined The displayed page of the native program after the latest switch is the page of the native program. If the applet container is open, read the long-term static information of the target applet.

In some embodiments, in order to further realize native program-like interaction and display effects of the mini program, before obtaining the short-term dynamic information of the target mini program, the address of the front page of the target mini program can be obtained, so that the terminal device Display the front page of the target applet before displaying the page of the target applet. The terminal device can request the mini program platform to obtain the address of the front page of the target mini program. The front page of a mini program is a page that is displayed before the page of the mini program during the startup process of the mini program. For example, the front page may include an opening page and/or an advertising page, etc. In some examples, the front page can be displayed according to the address of the front page before the display page is switched to the page of the target applet. The front page can fill in the gap that may occur when the page of the native program is switched to the page of the target applet. Shows blank. In other examples, after obtaining the address of the front page of the target applet, before performing the above step S204, the terminal device can display the page of the target applet through the native program according to the address of the front page. Front page to further realize the display effect of mini program native program.

In some embodiments, if the user needs to switch from the page of the target applet back to the page of the native program, the user can perform a switching selection input on the page of the target applet, and the terminal device calls the native program from the terminal device in response to the switching selection input. Select the program information of the native program from the updated list of mini programs provided, and switch the display page of the native program from the page of the target mini program to the page of the native program. Specifically, switch from the page of the target mini program to the home page of the native program. .

The updated applet list can include program information for native programs. Program information may include one or more of program name, program version, program type, program graphic logo, program page thumbnail, program introduction description, program logo, program owner logo and other information, which is not limited here. During the process of switching between the page of the native program and the page of the mini program, or during the process of switching between the page of the mini program and the page of the mini program, the mini program list can be updated, and the switched native program The program information or the applet information of the applet is eliminated from the applet list, and the program information of the native program or the applet information of the applet before switching is added to the applet list.

In some examples, when the display page of the native program is the page of the target applet, the page of the native program can be loaded asynchronously to quickly switch from the page of the target applet to the page of the native program. Complete the display of the native program page.

In the embodiment of the present application, the user can perform switching selection input on the page of the native program in the terminal device, and the terminal device responds to the switching selection input to determine the target applet that needs to be switched, and saves the long-term static information of the target applet locally. And obtain the short-term dynamic information of the target applet, based on the long-term static information and short-term dynamic information of the target applet, make the target applet run in the applet container, switch from the page of the native program to the page of the target applet, and use the native program Display the page of the target applet. When the mini program is restarted in response to the mini program startup input, the terminal device calls the native program to read the long-term static information, sets the main task and root page of the native program as the mini program container, and displays the target mini program through the native program The page enables the mini program to be consistent or consistent with the native program in terms of interaction with the user and visual experience, and improves the interaction between the mini program and the user and the visual experience. Moreover, in the case where the mini program list provided by the native program includes the mini program information of multiple mini programs, the method of the embodiment of the present application can be used to call the native program to switch and display any one of the mini program lists, thereby realizing a native program. The effect of coexistence of multiple small program-like native programs in the program.

In order to more comprehensively explain the integration method of the native program and the mini program in this solution, the process of opening the native program for the first time and switching from the page of the native program to the page of the mini program is explained below. FIG. 3 is a flowchart of an example of the process of switching from a native program page to a mini program page provided by an embodiment of the present application. As shown in Figure 3, the process of switching the page of the native program to the page of the applet may include steps S301 to step S317.

In step S301, the terminal device receives a startup input for the native program and displays the homepage of the native program.

In step S302, the terminal device determines the target applet in response to the switching selection input.

In step S303, the terminal device obtains and locally saves the long-term static information of the target applet.

In step S304, if the user does not pay attention to the target applet, the terminal device adds attention to the target applet.

In step S305, the terminal device obtains the address of the front page of the target applet.

In step S306, the terminal device determines whether the applet container is in an open state. If the applet container is open, jump to step S308; if the applet container is not open, jump to step S307.

In step S307, the terminal device closes the tasks related to the applet in the native program and jumps to step S308.

In step S308, the terminal device returns to the home page of the native program.

In step S309, the terminal device opens the applet container and starts the target applet.

In step S310, the terminal device determines whether the user's login to the target applet is successful. If the login is successful, jump to step S311; if the login fails, jump to step S309, or prompt the user to log in manually.

In step S311, the terminal device displays the loading page.

In step S312, the terminal device obtains short-term dynamic information of the target applet.

In step S313, the terminal device determines whether the short-term dynamic information is successfully obtained. If the acquisition is successful, jump to step S315; if the acquisition fails, jump to step S314.

In step S314, the terminal device sends a prompt message indicating that the short-term dynamic information acquisition failed.

In step S315, the terminal device caches short-term dynamic information.

In step S316, the terminal device loads the target applet and runs the target applet in the applet container.

In step S317, the terminal device displays the homepage of the target applet through a native program.

Depending on the actual application scenario and operating conditions, some of the above-mentioned steps S301 to S317 may be omitted, or the order of the steps may be appropriately changed, which is not limited here.

In the above embodiment, the applet can use the common functions of the native program while the terminal device is running. General functions are functions that are required by native programs and mini programs. For example, general functions may include encryption functions, decryption functions, network request functions, local access functions, user data management functions, terminal device hardware capability usage functions, etc. One or more items are not limited here. The applet container can be provided with an application programming interface (Application Programming Interface, API). This API is used by the applet in the applet container to call the common functions of the native program. In other words, the mini program can call the common functions of the native program through the API of the mini program container. This opens up some capabilities of native programs to mini programs, thereby reducing the functional gap between mini programs and native programs without increasing the difficulty of mini program development, improving the functional effects of mini programs, and making mini programs more functional. The functions are richer. When the target applet runs in the applet container and needs to perform common functions, the common functions of the native program can be called through the API to enrich the functions of the target applet.

For example, FIG. 4 is a schematic logical architecture diagram of an example of coexistence of native programs and applets in a terminal device provided by an embodiment of the present application. As shown in Figure 4, native programs, mini programs 1, mini programs 2, and mini programs 3 can be run on the terminal device. The terminal device has a mini program container, and the mini program container has API and user interface (UI) components. The common functions of the native program can include encryption and decryption functions, network request functions, local access functions, user data management functions, and hardware capabilities. Usage functions and other features. Mini Program 1, Mini Program 2, and Mini Program 3 can call the common functions of native programs through APIs while the Mini Program container is running.

In different scenarios, the methods of starting the mini program triggered by the mini program startup input are also different. The following uses different scenarios as examples to illustrate the integration method of native programs and mini programs.

In some embodiments, the applet startup input includes a startup input to a native program in the terminal device. When the current native program has been closed and the display page of the last time the native program was opened is finally switched to the page of the target applet, if the native program is started again through the startup input of the native program, the terminal device will call the native program to read the last time The long-term static information of the target applet is saved when the native program is opened and switched to the target applet page, and the main task and root page of the native program are set as the applet container, so that the display page of the native program is the homepage of the target applet. .

In order to more comprehensively explain the integration method of the native program and the mini program in this solution, the following describes the process of restarting the native program after the display page of the native program is switched to the page of the target mini program. FIG. 5 is a flow chart of an example of a native program restart process provided by an embodiment of the present application. As shown in FIG. 5 , the process of restarting the native program may include steps S401 to S415.

In step S401, the terminal device starts the native program in response to the user's input to start the native program.

In step S402, the terminal device loads native program running logic.

In step S403, the terminal device determines whether the display page of the last startup of the native program has been switched to the page of the applet. If the native program has not switched to the page of the mini program when it was launched last time, jump to step S404; if the native program has been switched to the page of the mini program when it was launched last time, jump to step S405.

Among them, you can determine whether the applet container is open to determine whether the display page of the native program has been switched to the page of the applet when it was last started. You can also determine the applet page that the native program was switched to when it was last started through the long-term static information saved locally. Whether the page of the program is the page of the target applet.

In step S404, the terminal device displays the home page of the native program.

In step S405, the terminal device starts the target applet.

In step S406, the terminal device asynchronously loads the home page of the native program so that it can be quickly switched when it is necessary to switch back to the page of the native program.

In step S407, the terminal device loads the front page of the target applet.

In step S408, the terminal device determines whether the user's login to the target applet is successful. If the login is successful, jump to step S409; if the login fails, jump to step S405, or prompt the user to log in manually.

In step S409, the terminal device displays the loading page.

In step S410, the terminal device obtains short-term dynamic information of the target applet.

In step S411, the terminal device determines whether the short-term dynamic information is successfully obtained. If the acquisition is successful, jump to step S413; if the acquisition fails, jump to step S412.

In step S412, the terminal device sends a prompt message indicating that the acquisition of short-term dynamic information failed.

In step S413, the terminal device caches short-term dynamic information.

In step S414, the terminal device loads the target applet and runs the target applet in the applet container.

In step S415, the terminal device displays the homepage of the target applet through a native program. Specifically, the terminal device can display the homepage of the target applet through the native program by setting the main task and root page of the native program as the applet container.

Depending on the actual application scenario and operating conditions, some of the above-mentioned steps S401 to S415 may be omitted, or the order of the steps may be appropriately changed, which is not limited here.

In some embodiments, the applet startup input includes a startup input to a desktop icon of the applet displayed by the terminal device. Users can create a desktop icon for the mini program on the terminal device, and quickly call up the native program and enter the mini program through the desktop icon of the mini program. Figure 6 is a flow chart of another embodiment of the integration method of native programs and mini programs provided by this application. The difference between Figure 6 and Figure 2 is that step S204 in Figure 2 can be specifically refined into steps S2041a to step S2044a in Figure 6 . The integration method of native programs and mini programs shown in Figure 6 can also include step S205 and step S206.

In step S2041a, in response to a startup input to the desktop icon of the applet displayed on the terminal device, jump to the transfer page.

The startup input to the desktop icon of the applet is used to launch the applet corresponding to the desktop icon. The startup input may specifically include click input on desktop icons, long press input, etc., which is not limited here. When the terminal device receives the startup input for the desktop icon of the applet, the terminal device will first jump to the transfer page, and then jump to other pages from the transfer page. The transfer page can be a transparent page and not displayed explicitly.

The desktop icon of the mini program can be generated when the display page of the native program is switched to the page of the mini program. The terminal device can respond to the desktop icon generation input of the applet page, jump to the icon generation transfer page, trigger the generation and display of the desktop icon of the applet on the terminal device. The icon generation transfer page can be an H5 page or other types of pages, which is not limited here.

In step S2042a, it is determined whether the applet container is in an open state.

When the display page of the native program is switched to the page of the mini program, the mini program container will be opened. When the display page of the native program is switched to the page of the native program, the applet container will be closed. You can determine whether the display page of the native program has been switched to the page of the mini program before by determining whether the mini program container is open.

In step S2043a, when the applet container is open, jump from the transfer page to the native program, read the long-term static information of the target applet, and set the main task and root page of the native program as the applet container.

The applet container is open, which means that the display page of the native program has been switched to the page of the applet before. You can jump from the transfer page to the native program to call the native program to read the long-term static information of the target applet that was previously saved locally. . Set the main task and root page of the native program as a mini program container, and the mini program container is the target mini program, so that the terminal device has the ability to display the page of the target mini program.

In step S2044a, if the applet corresponding to the desktop icon is the target applet, the page of the target applet is displayed.

When the applet corresponding to the desktop icon is the target applet, the terminal device can display the page of the target applet through the native program. From the perspective of user experience, after the user enters the startup input for the desktop icon of the mini program, what opens is the display page of the native program, and the display page is the page of the target mini program. Specifically, the display page is the homepage of the target mini program.

In some examples, whether the applet corresponding to the desktop icon is the target applet can be determined by whether the applet ID of the applet corresponding to the desktop icon is consistent with the applet ID previously stored locally in long-term static information.

In step S205, if the applet corresponding to the desktop icon is not the target applet, jump from the page of the target applet to the page of the applet corresponding to the desktop icon.

In some examples, if the applet corresponding to the desktop icon is not the target applet, the long-term static information and short-term dynamic information of the applet corresponding to the desktop icon can be obtained. According to the long-term static information and short-term dynamic information of the applet corresponding to the desktop icon, Let the applet corresponding to the desktop icon run in the applet container. The main task and root page of the native program have been set as the applet container. The page of the applet corresponding to the desktop icon can be displayed through the native program to jump from the page of the target applet. Go to the page of the applet corresponding to the desktop icon. Among them, the page of the target applet can be used as a transfer page that is not displayed explicitly.

In other examples, the terminal device can first display the page of the target applet through a native program, and then receive the user's switching input. In response to the switching input, the terminal device can obtain the long-term static information and short-term dynamic information of the applet corresponding to the desktop icon, so that Run the applet corresponding to the desktop icon in the applet container, and display the page of the applet corresponding to the desktop icon through the native program, so as to jump from the page of the target applet to the page of the applet corresponding to the desktop icon.

In step S206, when the applet container is not in an open state, the applet corresponding to the desktop icon is jumped from the transfer page and loaded.

The applet container is not open, which means that the display page of the native program has been switched to the page of the native program before. In this case, the applet can be loaded and run according to the ordinary applet loading method.

In order to more comprehensively explain the integration method of native programs and mini programs in this solution, the process of starting the mini program through the desktop icon of the mini program is explained below. FIG. 7 is a flowchart of an example of the process of starting an applet through the desktop icon of the applet provided by the embodiment of the present application. As shown in Figure 7, the process of starting the applet through the desktop icon of the applet may include steps S501 to S516.

In step S501, the terminal device jumps to the transfer page in response to the startup input of the desktop icon of the applet.

In step S502, the terminal device determines whether the display page of the last startup of the native program has been switched to the page of the applet. If the native program has not switched to the page of the mini program when it was launched last time, jump to step S503; if the native program has been switched to the page of the mini program when it was launched last time, jump to step S504.

Among them, you can determine whether the applet container is open to determine whether the display page of the native program has been switched to the page of the applet when it was last started. You can also determine the applet page that the native program was switched to when it was last started through the long-term static information saved locally. Whether the page of the program is the page of the applet corresponding to the desktop icon.

In step S503, the terminal device loads the applet corresponding to the desktop icon according to the ordinary applet loading method and runs it.

In step S504, the terminal device starts the applet corresponding to the desktop icon.

In step S505, the terminal device determines whether the user's login to the applet corresponding to the desktop icon is successful. If the login is successful, jump to step S506; if the login fails, jump to step 504, or prompt the user to log in manually.

In step S506, the terminal device displays the loading page.

In step S507, the terminal device determines whether the applet corresponding to the desktop icon is the target applet based on the locally stored long-term static information; if the applet corresponding to the desktop icon is the target applet, jump to step S508; if the applet corresponding to the desktop icon is the target applet, The applet is not the target applet, jump to step S510.

By default in this example, if the display page of the native program is switched to the page of the mini program, the page of the mini program that the native program was previously switched to is the page of the target mini program.

In step S508, the terminal device obtains short-term dynamic information of the applet corresponding to the desktop icon.

In step S509, the terminal device determines whether the short-term dynamic information is successfully obtained. If the acquisition is successful, jump to step S513; if the acquisition fails, jump to step S512.

In step S510, the terminal device obtains long-term static information and short-term dynamic information of the applet corresponding to the desktop icon.

In step S511, the terminal device determines whether the long-term static information and short-term dynamic information are successfully obtained. If the acquisition is successful, jump to step S514; if the acquisition fails, jump to step S512.

In step S512, the terminal device sends a prompt message indicating that the information acquisition fails.

In step S513, the terminal device caches short-term dynamic information.

In step S514, the terminal device locally stores long-term dynamic information and caches short-term dynamic information.

In step S515, the terminal device loads the applet corresponding to the desktop icon and runs the applet corresponding to the desktop icon in the applet container.

In step S516, the terminal device displays the home page of the applet corresponding to the desktop icon through a native program. Specifically, the terminal device can display the home page of the applet corresponding to the desktop icon through the native program by setting the main task and root page of the native program as the applet container.

Depending on the actual application scenario and operating conditions, some of the above steps S501 to S516 may be omitted, or the order of the steps may be appropriately changed, which is not limited here.

In some embodiments, the terminal device may also, in response to a search input to the display page of the native program, look for the applet indicated by the search input in the applet integrated with the native program. It can determine whether the current display page of the native program has been switched to the page of the mini program. If the page of the mini program is not switched, the mini program will be loaded and run according to the normal mini program loading method. If the page has been switched to the applet, start the applet indicated by the search input, obtain the long-term static information and short-term dynamic information of the applet indicated by the search input, and run the search in the applet container based on the long-term static information and short-term dynamic information. Input the applet indicated by the input, and set the main task of the native program as the applet container, so that the terminal device can display a page for searching the applet indicated by the input through the native program. The process of loading the applet indicated by the search input and the process of displaying the page of the applet indicated by the search input may refer to steps S408 to S415 in the above embodiment, and will not be described again here.

In some embodiments, the applet activation input may include activation input for link information. Users can quickly call up the native program and enter the mini program through the received link information. Figure 8 is a flow chart of another embodiment of the integration method of native programs and mini programs provided by this application. The difference between Figure 8 and Figure 2 is that step S204 in Figure 2 can be specifically refined into steps S2041b to S2043b in Figure 8 . The integration method of native programs and mini programs shown in Figure 8 can also include step S207 and step S208.

In step S2041b, in response to the startup input of the link information, the native program is called up to determine whether the applet container is in an open state.

The startup input of the link information is used to start the applet corresponding to the link information. Further, the startup input of the link information can be used to call up the specified page of the applet indicated by the link information. Link information may include external scheme links, etc., which is not limited here. The link information may include the URL address of the specified page of the applet indicated by the link information. The link information can be carried in text messages, multimedia messages, instant messaging messages, etc., and is not limited here. The startup input may specifically include click input, long press input, etc. for link information, which is not limited here. When the terminal device receives the startup input of the link information, it will call the native program to determine whether the applet container is open. You can determine whether the display page of the native program has been switched to the page of the mini program before by determining whether the mini program container is open.

In step S2042b, when the applet container is open, the long-term static information of the target applet is read, and the main task and root page of the native program are set as the applet container.

The applet container is open, which means that the display page of the native program has been switched to the page of the applet. The native program can be called to read the long-term static information of the target applet that was previously saved locally. Set the main task and root page of the native program as a mini program container, and the mini program container is the target mini program, so that the terminal device has the ability to display the page of the target mini program.

In step S2043b, if the applet indicated by the link information is the target applet, the page indicated by the link information in the target applet is opened according to the link information.

When the applet indicated by the link information is the target applet, the terminal device can display the page of the target applet through the native program. Moreover, since the link information can specifically indicate the specified page in the target applet, the specified page indicated by the link information in the target applet can be opened and displayed through the native program according to the connection information. From the perspective of user experience, after the user inputs the link information, what opens is the display page of the native program, and the display page is the page of the target applet. Specifically, the display page is the designation indicated by the link information in the target applet. page.

In some examples, whether the applet indicated by the link information is the target applet can be determined by whether the applet ID of the applet indicated by the link information is consistent with the applet ID previously stored locally in long-term static information.

In step S207, if the applet indicated by the link information is not the target applet, jump from the page of the target applet to the page of the applet indicated by the link information.

In some examples, if the applet indicated by the link information is not the target applet, the long-term static information and short-term dynamic information of the applet indicated by the link information can be obtained. According to the long-term static information and short-term dynamic information of the applet indicated by the link information, Make the applet indicated by the link information run in the applet container. The main task and root page of the native program have been set as the applet container. The page of the applet indicated by the link information can be displayed through the native program to jump from the page of the target applet. Go to the page of the applet indicated by the link information. Among them, the page of the target applet can be used as a transfer page that is not displayed explicitly.

In other examples, the terminal device can first display the page of the target applet through a native program, then receive the user's switching input, and in response to the switching input, obtain the long-term static information and short-term dynamic information of the applet indicated by the link information, so that The applet indicated by the link information is run in the applet container, and the specified page of the applet indicated by the link information is displayed through the native program, so as to jump from the page of the target applet to the specified page of the applet indicated by the link information.

In step S208, when the applet container is not in an open state, the page of the applet indicated by the link information is opened through the browser.

The applet container is not open, which means that the display page of the native program has been switched to the page of the native program before. In this case, the browser can be used to open the specified page of the applet indicated by the link information.

In order to more comprehensively explain the integration method of native programs and mini programs in this solution, the process of starting the mini program through link information is explained below. Figure 9 is a flow chart of an example of the process of starting a mini program through link information provided by the embodiment of the present application. As shown in Figure 9, the process of starting the applet through link information may include steps S601 to S606.

In step S601, the terminal device starts the native program in response to the startup input of the link information.

In step S602, the terminal device loads native program running logic.

In step S603, the terminal device determines whether the display page of the last startup of the native program has been switched to the page of the applet. If the native program has not switched to the page of the mini program when it was launched last time, jump to step S604; if the native program has been switched to the page of the mini program when it was launched last time, jump to step S605.

Among them, you can determine whether the applet container is open to determine whether the display page of the native program has been switched to the page of the applet when it was last started. You can also determine the applet page that the native program was switched to when it was last started through the long-term static information saved locally. Whether the page of the program is the page of the applet specified by the link information.

In step S604, the terminal device opens the page of the applet indicated by the link information through the browser.

In step S605, the terminal device starts the applet indicated by the link information, and synchronously opens and displays the designated page of the applet indicated by the link information.

In some examples, for the startup of the applet indicated by the link information in step S605 and the opening and display of the specified page of the applet indicated by the link information, please refer to the relevant content in steps S504 to step S516 in the above embodiment. If the applet indicated by the link information is the target applet, the specified page of the applet indicated by the link information can be directly displayed through the native program according to the link information. If the applet indicated by the link information is not the target applet, the native program can be used to jump from the page of the target applet to the specified page of the applet indicated by the link information.

In step S606, the terminal device asynchronously loads the relevant information of the native program so that it can be quickly switched when it is necessary to switch from the page of the applet to the page of the native program.

The execution order between step S606 and step S605 is not limited here, and the two steps can be performed asynchronously.

Depending on the actual application scenario and operating conditions, some of the above-mentioned steps S601 to S606 may be omitted, or the order of the steps may be appropriately changed, which is not limited here.

In some embodiments, the target applet activation input includes activation input for push information. Users can quickly launch the native program and enter the mini program through the received push information. Figure 10 is a flow chart of yet another embodiment of the integration method of native programs and mini programs provided by this application. The difference between Figure 10 and Figure 2 is that step S204 in Figure 2 can be specifically refined into steps S2041c to S2044c in Figure 10 . The integration method of native programs and applets shown in Figure 10 can also include step S209 Go to step S211.

In step S2041c, in response to the startup input of the push information, it is determined whether the native program is running in the background.

The launch input for push information is used to launch the applet indicated by the push information. Further, the startup input of the push information can be used to call up the specified page of the applet indicated by the push information. Push information may include push information in the notification bar, push information in pop-up windows, push information on the lock screen interface, etc., and is not limited here. The startup input may include click input for push information, long press input, etc., which is not limited here. When the terminal device receives startup input for link information, the running status of the native program can be determined. Running status can include background running status and front-end running status.

In step S2042c, when the native program is running in the background, the native program is called up to determine whether the applet container is open.

The native program is running in the background, that is, the native program is not currently displayed on the terminal device. You need to call up the native program to determine whether the mini program container is open. By determining whether the mini program container is open, it is possible to determine whether the display page of the native program has been switched to the mini program page before.

In step S2043c, when the applet container is open, the long-term static information of the target applet is read, and the main task and root page of the native program are set as the applet container.

The applet container is open. The applet container is open, which means that the display page of the native program has been switched to the page of the applet before. The native program can be called to read the long-term static information of the target applet that was previously saved locally. Set the main task and root page of the native program as a mini program container, and the mini program container is the target mini program, so that the terminal device has the ability to display the page of the target mini program.

In step S2044c, if the applet indicated by the push information is the target applet, the page indicated by the push information in the target applet is opened according to the push information.

When the applet indicated by the push information is the target applet, the terminal device can display the page of the target applet through the native program. Moreover, since the push information can specifically indicate the specified page in the target applet, the specified page indicated by the push information in the target applet can be opened and displayed through the native program according to the connection information. From the perspective of user experience, after the user inputs the push information, he or she opens the display page of the native program, and the display page is the page of the target applet. Specifically, the display page is the designation indicated by the push information in the target applet. page.

In some examples, whether the applet indicated by the push information is the target applet can be determined by whether the applet ID of the applet indicated by the push information is consistent with the applet ID previously stored locally in long-term static information.

In step S209, if the applet indicated by the push information is not the target applet, jump from the page of the target applet to the page of the applet indicated by the push information.

In some examples, if the applet indicated by the push information is not the target applet, the long-term static information and short-term dynamic information of the applet indicated by the push information can be obtained. According to the long-term static information and short-term dynamic information of the applet indicated by the push information, Make the applet indicated by the push information run in the applet container. The main task and root page of the native program have been set as the applet container. The page of the applet indicated by the push information can be displayed through the native program to jump from the page of the target applet. Go to the page of the applet indicated by the push message. Among them, the page of the target applet can be used as a transfer page that is not displayed explicitly.

In other examples, the terminal device can first display the page of the target applet through a native program, then receive the user's switching input, and in response to the switching input, obtain the long-term static information and short-term dynamic information of the applet indicated by the push information, so that The applet indicated by the link information is run in the applet container, and the specified page of the applet indicated by the push information is displayed through the native program, so as to jump from the page of the target applet to the specified page of the applet indicated by the push information.

In step S210, when the native program is in the front-end running state, jump to the page of the applet indicated by the push information.

The native program is in the front-end running state, that is, the native program is currently displayed on the terminal device. There is no need to call up the native program. You can directly use the native program to jump to the specified page of the mini program indicated by the push information.

In step S211, when the applet container is not in an open state, the browser is used to open the page of the applet indicated by the push information.

The applet container is not open, which means that the display page of the native program has been switched to the page of the native program before. In this case, the browser can be used to open the specified page of the applet indicated by the push information.

In order to more comprehensively explain the integration method of native programs and mini programs in this solution, the process of launching mini programs through push information is explained below. Figure 11 is a flowchart of an example of the process of starting a mini program through push information provided by the embodiment of the present application. As shown in Figure 11, the process of starting the applet by pushing information may include steps S701 to S707.

In step S701, the terminal device determines whether the native program is running in the background in response to the startup input of the push information. If the native program is in the background running state, jump to step S703; if the native program is in the front-end running state, jump to step S702.

In step S702, the terminal device jumps to the designated page of the applet indicated by the push information in the native program.

In step S703, the terminal device enters the native program running logic.

In step S704, the terminal device determines whether the display page of the last startup of the native program has been switched to the page of the applet. If the native program was not switched to the page of the mini program when it was launched last time, jump to step S705; if the native program was switched to the page of the mini program when it was launched last time, jump to step S707.

In step S705, the terminal device opens the page of the applet indicated by the push information through the browser.

In step S706, the terminal device loads the home page of the native program.

In step S707, the terminal device starts the applet indicated by the push information, opens and displays the designated page of the applet indicated by the push information.

In some examples, the startup of the applet indicated by the push information in step S707 and the opening and display of the specified page of the applet indicated by the push information may refer to the relevant content in steps S504 to step S516 in the above embodiment. If the applet indicated by the push information is the target applet, the specified page of the applet indicated by the push information can be directly displayed through the native program according to the push information. If the applet indicated by the push information is not the target applet, you can use the native program to jump from the page of the target applet to the specified page of the applet indicated by the push information.

Depending on the actual application scenario and operating conditions, some of the above-mentioned steps S701 to S707 may be omitted, or the order of the steps may be appropriately changed, which is not limited here.

This application also provides an integration device of native programs and mini programs, which can be installed in a terminal device. FIG. 12 is a schematic structural diagram of an embodiment of an integrated device for native programs and applets provided by this application. As shown in FIG. 12 , the device 800 for integrating native programs and small programs may include a selection module 801 , an acquisition module 802 and a control module 803 .

The selection module 801 may be configured to select applet information representing the target applet from the applet list provided by the native program in response to a switching selection input to a page of the native program in the terminal device.

The acquisition module 802 can be used to acquire long-term static information of the target applet and save it locally.

The acquisition module 802 is also used to acquire short-term dynamic information of the target applet.

The control module 803 can be used to make the target applet run in the applet container of the terminal device based on the long-term static information and short-term dynamic information of the target applet, and switch the display page from the page of the native program to the page of the target applet.

The control module 803 is also used to respond to the applet startup input, call the native program to read the long-term static information of the target applet, and set the main task and root page of the native program as the applet container, so that the terminal device displays the target through the native program Mini program page.

In the embodiment of the present application, in the embodiment of the present application, the user can perform switching selection input on the page of the native program in the terminal device. The terminal device responds to the switching selection input to determine the target applet that needs to be switched, and changes the target applet to the page of the native program. The long-term static information is saved locally, and the short-term dynamic information of the target applet is obtained. Based on the long-term static information and short-term dynamic information of the target applet, the target applet is run in the applet container, and the page of the native program is switched to the target applet. The page of the program uses the native program to display the page of the target applet. When the mini program is restarted in response to the mini program startup input, the terminal device calls the native program to read the long-term static information, sets the main task and root page of the native program as the mini program container, and displays the target mini program through the native program The page enables the mini program to be consistent or consistent with the native program in terms of interaction with the user and visual experience, and improves the interaction between the mini program and the user and the visual experience. Moreover, in the case where the mini program list provided by the native program includes the mini program information of multiple mini programs, the method of the embodiment of the present application can be used to call the native program to switch and display any one of the mini program lists, thereby realizing a native program. The effect of coexistence of multiple small program-like native programs in the program.

In some embodiments, the control module 803 may also be used to determine whether the applet container is open.

The control module 803 may be used to read long-term static information of the target applet when the applet container is in an open state.

In some embodiments, the obtaining module 802 may also be used to obtain the address of the front page of the target applet, so that the terminal device displays the front page of the target applet before displaying the page of the target applet.

In some embodiments, the applet container is provided with an application programming interface API, which is used by the applet in the applet container to call common functions of the native program.

The control module 803 can also be used to call the common function of the native program through the API when the target applet runs in the applet container and needs to perform a common function.

In some embodiments, the applet startup input includes a startup input to a native program in the terminal device.

In some embodiments, the applet startup input includes a startup input to a desktop icon of the applet displayed on the terminal device.

The control module 803 may be used to: jump to the transfer page in response to the startup input of the desktop icon of the applet displayed on the terminal device; determine whether the applet container is in an open state; when the applet container is in an open state, transfer from The page jumps to the native program, reads the long-term static information of the target applet, and sets the main task and root page of the native program as the applet container; if the applet corresponding to the desktop icon is the target applet, control the terminal device to display the target applet. program page.

In some examples, the control module 803 can also be used to jump from the page of the target applet to the page of the applet corresponding to the desktop icon when the applet corresponding to the desktop icon is not the target applet.

In some embodiments, the applet activation input includes activation input for link information.

The control module 803 can be used to: respond to the startup input of the link information, call up the native program, and determine whether the applet container is in the open state; when the applet container is in the open state, read the long-term static information of the target applet, Set the main task and root page of the native program as the applet container; if the applet indicated by the link information is the target applet, open the page indicated by the link information in the target applet based on the link information.

In some examples, the control module 803 may also be configured to jump from the page of the target applet to the page of the applet indicated by the link information when the applet indicated by the link information is not the target applet.

In some embodiments, the target applet activation input includes activation input for push information.

The control module 803 can be used to: respond to the startup input of the push information, determine whether the native program is in the background running state; when the native program is in the background running state, call up the native program, and determine whether the applet container is in the open state; When the mini program container is open, read the long-term static information of the target mini program, and set the main task and root page of the native program as the mini program container; if the mini program indicated by the push information is the target mini program, according to the push Information, open the page indicated by the push information in the target applet.

In some examples, the control module 803 may also be configured to jump from the page of the target applet to the page of the applet indicated by the push information when the applet indicated by the push information is not the target applet.

In some examples, the control module 803 can also be used to jump to the page of the applet indicated by the push information when the native program is in the front-end running state.

In some embodiments, the obtaining module 802 can also be used to obtain the applet list.

The mini program list includes mini program information arranged from high to low in terms of recommendation.

Recommendation is determined based on the user's function usage information, which includes one or more of the following: mini program version type, mini program region, mini program priority, mini program binding resource information, mini program attention, payment Information, payment institution information, and user personal information.

In some examples, the applet list includes applet information of the first type of applet and/or applet information of the second type of applet. The first category of mini programs includes mini programs that are mini-programmed versions of native programs, and the second category of mini programs includes mini programs that are owned by a different party than the original program.

This application also provides a terminal device. Figure 13 is a schematic structural diagram of an embodiment of the terminal device provided by this application. As shown in Figure 13, the terminal device 900 includes a memory 901, a processor 902, and a computer program stored on the memory 901 and executable on the processor 902.

In some examples, the above-mentioned processor 902 may include a central processing unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.

The memory 901 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk storage media device, optical storage media device, flash memory device, electrical, optical or other physical/tangible devices Memory storage device. Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to perform operations described with reference to the integration of native programs and applets according to embodiments of the present application.

The processor 902 reads the executable program code stored in the memory 901 to run the computer program corresponding to the executable program code, so as to realize the integration of the native program and the applet in the above embodiment.

In some examples, the terminal device 900 may also include a communication interface 903 and a bus 904. Among them, as shown in Figure 13, the memory 901, the processor 902, and the communication interface 903 are connected through the bus 904 and complete communication with each other.

The communication interface 903 is mainly used to implement communication between modules, devices, units and/or equipment in the embodiments of this application. Input devices and/or output devices may also be accessed through the communication interface 903.

Bus 904 includes hardware, software, or both, coupling the components of terminal device 900 to each other. By way of example, but not limitation, the bus 904 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industry Standard Architecture (ISA) bus, infinite bandwidth interconnect, low pin count (LPC) bus, memory bus, Micro Channel architecture Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association part ( Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these. Where appropriate, bus 904 may include one or more buses. Although the embodiments of this application describe and illustrate a specific bus, this application contemplates any suitable bus or interconnection.

The fourth aspect of the present application also provides a computer-readable storage medium. The computer-readable storage medium stores computer program instructions. When the computer program instructions are executed by the processor, the native program and the applet in the above embodiment can be realized. Integrated methods can achieve the same technical effect. To avoid duplication, they will not be described again here. Among them, the above-mentioned computer-readable storage media may include non-transitory computer-readable storage media, such as read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), magnetic disks or optical disks etc. are not limited here.

The present application can also provide a computer program product. When instructions in the computer program product are executed by a processor of a terminal device, the terminal device causes the terminal device to execute the integration method of the native program and the applet in the above embodiment. For specific details, please refer to the relevant descriptions in the above embodiments and will not be described again here.

It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. place. For apparatus embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments, relevant information may be found in the description of the method embodiments. This application is not limited to the specific steps and structures described above and illustrated in the drawings. Those skilled in the art can make various changes, modifications and additions, or change the order between steps after understanding the spirit of the present application. Also, for the sake of brevity, detailed descriptions of known method techniques are omitted here.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that execution of the instructions via the processor of the computer or other programmable data processing apparatus enables Implementation of the functions/actions specified in one or more blocks of a flowchart and/or block diagram. Such a processor may be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It will also be understood that each block in the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can also be implemented by special purpose hardware that performs the specified functions or actions, or can be implemented by special purpose hardware and A combination of computer instructions.

Those skilled in the art should understand that the above embodiments are illustrative rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other modified embodiments of the disclosed embodiments based on studying the drawings, description and claims. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to indicate names rather than to indicate any specific order. . Any reference signs in the claims shall not be construed as limiting the scope. The functions of several parts appearing in the claims may be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

An integration method of native programs and mini programs, including:

In response to a switching selection input to the page of the native program in the terminal device, select the applet information representing the target applet from the applet list provided by the native program;

Obtain the long-term static information of the target applet and save it locally;

Obtain the short-term dynamic information of the target applet, make the target applet run in the applet container of the terminal device according to the long-term static information and short-term dynamic information of the target applet, and change the display page from the native The page of the program is switched to the page of the target applet;

In response to the applet startup input, the native program is called to read the long-term static information of the target applet, and the main task and root page of the native program are set as the applet container, so that the terminal device passes The native program displays the page of the target applet.
The method according to claim 1, before calling the native program to read the long-term static information of the target applet, further comprising:

Determine whether the applet container is open;

The reading of long-term static information of the target applet includes:

If the applet container is open, read the long-term static information of the target applet.
The method according to claim 1, before obtaining the short-term dynamic information of the target applet, further comprising:

Obtain the address of the front page of the target applet, so that the terminal device displays the front page of the target applet before displaying the page of the target applet.
The method according to claim 1, wherein the applet container is provided with an application programming interface API, and the API is used for the applet in the applet container to call the general functions of the native program,

The method also includes:

When the target applet runs in the applet container and needs to perform a general function, the general function of the native program is called through the API.
The method according to claim 1, wherein the applet startup input includes a startup input to the native program in the terminal device.
The method according to claim 1, wherein the applet startup input includes a startup input to the desktop icon of the applet displayed by the terminal device,

In response to the applet startup input, the native program is called to read the long-term static information of the target applet, and the main task and root page of the native program are set as the applet container, so that the terminal The device displays the page of the target applet, including:

In response to a startup input to the desktop icon of the applet displayed on the terminal device, jump to the transfer page;

Determine whether the applet container is open;

When the applet container is open, jump from the transfer page to the native program, read the long-term static information of the target applet, and set the main task and root page of the native program. Be the applet container;

If the applet corresponding to the desktop icon is the target applet, display the page of the target applet.
The method of claim 1, further comprising:

If the applet corresponding to the desktop icon is not the target applet, jump from the page of the target applet to the page of the applet corresponding to the desktop icon.
The method according to claim 1, wherein the applet startup input includes a startup input for link information,

In response to the applet startup input, the native program is called to read the long-term static information of the target applet, and the main task and root page of the native program are set as the applet container, so that the terminal The device displays the page of the target applet, including:

In response to the startup input of the link information, call up the native program and determine whether the applet container is in an open state;

When the applet container is in an open state, read the long-term static information of the target applet, and set the main task and root page of the native program as the applet container;

If the applet indicated by the link information is the target applet, open the page indicated by the link information in the target applet according to the link information.
The method of claim 8, further comprising:

If the applet indicated by the link information is not the target applet, jump from the page of the target applet to the page of the applet indicated by the link information.
The method according to claim 1, wherein the target applet startup input includes a startup input for push information,

In response to the applet startup input, the native program is called to read the long-term static information of the target applet, and the main task and root page of the native program are set as the applet container, so that the terminal The device displays the page of the target applet, including:

In response to the startup input of the push information, determine whether the native program is running in the background;

When the native program is in the background running state, call up the native program and determine whether the applet container is in an open state;

When the applet container is in an open state, read the long-term static information of the target applet, and set the main task and root page of the native program as the applet container;

If the applet indicated by the push information is the target applet, open the page indicated by the push information in the target applet according to the push information.
The method of claim 10, further comprising:

If the applet indicated by the push information is not the target applet, jump from the page of the target applet to the page of the applet indicated by the push information.
The method of claim 10, further comprising:

When the native program is in the front-end running state, jump to the page of the mini program indicated by the push information.
The method according to claim 1, before selecting the target applet from the applet list provided by the native program, further comprising:

Obtain the mini program list, which includes mini program information arranged from high to low in terms of recommendation,

The recommendation degree is determined based on the user's function usage information, which includes one or more of the following: mini program version type, mini program region, mini program priority, mini program binding resource information, mini program Number of followers, payment information, payment institution information, and user personal information.
The method according to claim 1, wherein the applet list includes applet information of the first type of applet and/or applet information of the second type of applet,

The first type of small program includes a small program that is a mini-programmed version of the native program, and the second type of small program includes a small program whose owner is different from the owner of the original program.
An integrated device for native programs and mini programs, including:

A selection module configured to select applet information representing the target applet from the applet list provided by the native program in response to the switching selection input of the page of the native program in the terminal device;

The acquisition module is used to obtain the long-term static information of the target applet and save it locally;

The acquisition module is also used to acquire short-term dynamic information of the target applet;

A control module configured to make the target applet run in the applet container of the terminal device based on the long-term static information and short-term dynamic information of the target applet, and switch the display page from the native program page to the target applet. Describe the page of the target applet;

The control module is also configured to respond to the applet startup input, call the native program to read the long-term static information of the target applet, and set the main task and root page of the native program as the applet container, So that the terminal device displays the page of the target applet through the native program.
A terminal device includes: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the integration method of the native program and the applet as described in any one of claims 1 to 14 is implemented.
A computer-readable storage medium. Computer program instructions are stored on the computer-readable storage medium. When the computer program instructions are executed by a processor, the native program and applet as described in any one of claims 1 to 14 are implemented. Integrated approach to the program.