CN114691236A

CN114691236A - Method, device, equipment and medium for integrating native program and applet

Info

Publication number: CN114691236A
Application number: CN202210293530.4A
Authority: CN
Inventors: 王钰; 陈卓; 黄河; 谢治民; 徐鑫源; 叶樟源; 黄永生; 周继恩; 李伟; 沈玺; 汤之雄
Original assignee: China Unionpay Co Ltd
Current assignee: China Unionpay Co Ltd
Priority date: 2022-03-24
Filing date: 2022-03-24
Publication date: 2022-07-01
Anticipated expiration: 2042-03-24
Also published as: CN114691236B; WO2023178952A1

Abstract

The application discloses a method, a device, equipment and a medium for integrating a native program and an applet, belonging to the field of data processing. The method comprises the following steps: selecting applet information representing a target applet in an applet list provided by the native program in response to a switch selection input to a page of the native program; acquiring long-term static information of the target small program and storing the long-term static information locally; acquiring short-term dynamic information of a target small program, enabling the target small program to run in a small program container according to the long-term static information and the short-term dynamic information, and switching a display page from a page of a native program to a page of the target small program; and responding to the applet starting input, calling the native program to read the long-term static information of the target applet, setting the main task and the root page of the native program as an applet container, and enabling the terminal equipment to display the page of the target applet through the native program. According to the method and the device, the effects of interaction between the small program and the user, visual experience and the like can be improved.

Description

Method, device, equipment and medium for integrating native program and applet

Technical Field

The present application relates to the field of data processing, and in particular, to a method, an apparatus, a device, and a medium for integrating a native program and an applet.

Background

The small program is a light-weight application which can be used without downloading and installing, the development difficulty is lower than that of the original program, the development difficulty can be reduced on the basis of realizing light-weight functions, and the memory space of equipment can be saved. However, due to the characteristics of the applet, the function of the applet is simple, and the functions of the applet cannot be compared with those of the native program in terms of interaction with a user, visual experience and the like. That is, applets are less effective in terms of interaction with the user, visual experience, and the like.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a medium for integrating a native program and an applet, which can improve the interaction between the applet and a user and the effect in the aspects of visual experience and the like.

In a first aspect, an embodiment of the present application provides an integration method of a native program and an applet, including: selecting the small program information representing the target small program from a small program list provided by the original program in response to the switching selection input of the page of the original program in the terminal equipment; acquiring long-term static information of the target small program and storing the long-term static information locally; acquiring short-term dynamic information of a target small program, enabling the target small program to run in a small program container of terminal equipment according to the long-term static information and the short-term dynamic information of the target small program, and switching a display page from a page of a native program to a page of the target small program; and responding to the applet starting input, calling the native program to read the long-term static information of the target applet, and setting the main task and the root page of the native program as an applet container so that the terminal equipment displays the page of the target applet through the native program.

In a second aspect, an embodiment of the present application provides an integrated device of a native program and an applet, including: the selecting module is used for responding to the switching selection input of the page of the original program in the terminal equipment and selecting the small program information representing the target small program in the small program list provided by the original program; the acquisition module is used for acquiring the long-term static information of the target applet and locally storing the long-term static information; the acquisition module is also used for acquiring short-term dynamic information of the target applet; the control module is used for enabling the target small program to run in a small program container of the terminal equipment according to the long-term static information and the short-term dynamic information of the target small program and switching a display page from a native program page to a target small program page; the control module is also used for responding to the applet starting input, calling the native program to read the long-term static information of the target applet, and setting the main task and the root page of the native program as an applet container so that the terminal device can display the page of the target applet through the native program.

In a third aspect, an embodiment of the present application provides a terminal device, including: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the method of integrating native programs with applets of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, on which computer program instructions are stored, and when executed by a processor, the computer program instructions implement the method for integrating a native program and an applet according to the first aspect.

The embodiment of the application provides a method, a device, equipment and a medium for integrating a native program and an applet, wherein a user can perform switching selection input on a page of a native program in a terminal device, the terminal device responds to the switching selection input to determine a target applet to be switched, long-term static information of the target applet is stored locally, short-term dynamic information of the target applet is obtained, the target applet is operated in an applet container according to the long-term static information and the 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 by the native program. Under the condition of responding to the small program starting input and restarting the small program, the terminal device calls the original program to read the long-term static information, sets the main task and the root page of the original program as a small program container, and displays the page of the target small program through the original program, so that the effect of the small program in the aspects of interaction with a user, visual experience and the like can be consistent or nearly consistent with that of the original program, and the effect of the small program in the aspects of interaction with the user, visual experience and the like is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram of an example of an application scenario of an integration method of a native program and an applet, provided by an embodiment of the present application;

FIG. 2 is a flow chart of an embodiment of a method for integrating native programs with applets as provided herein;

FIG. 3 is a flowchart of an example of a process of switching from a native program page to an applet page according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram illustrating an exemplary logical architecture of a terminal device in which an original program and an applet coexist according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of an example of a restart procedure of a native program according to an embodiment of the present application;

FIG. 6 is a flow chart of another embodiment of a method for integrating native programs with applets as provided herein;

fig. 7 is a flowchart of an example of a process of starting an applet through a desktop icon of the applet according to an embodiment of the present application;

FIG. 8 is a flow chart of yet another embodiment of a method for integrating native programs with applets as provided herein;

fig. 9 is a flowchart of an example of initiating an applet process by link information according to an embodiment of the present application;

FIG. 10 is a flow chart of yet another embodiment of a method for integrating native programs with applets as provided herein;

fig. 11 is a flowchart of an example of a process of initiating an applet by pushing information according to an embodiment of the present application;

FIG. 12 is a block diagram illustrating an embodiment of an integrated native program and applet device provided herein;

fig. 13 is a schematic structural diagram of an embodiment of a terminal device provided in the present application.

Detailed Description

Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative only and are not intended to be limiting. 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 the 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. The user can complete various functions through the terminal device, for example, the user can complete various functions such as document processing, payment, instant messaging, image processing and the like through the terminal device. Specifically, the terminal device may implement various functions by a native program. However, the native program needs to be downloaded and installed, occupies a large storage space of the terminal device, and is difficult to develop. In order to realize functions more simply, reduce occupied storage space and reduce difficulty, small programs are produced. The small program is a light-weight application which can be used without downloading and installing, the development difficulty is lower than that of the original program, the development difficulty can be reduced on the basis of realizing light-weight functions, and the memory space of equipment can be saved. However, just because the applet does not need to be downloaded and installed, the applet has simpler functions and cannot realize more complex functions while reducing the development difficulty and saving the memory space of the device, and the applet cannot be compared with the native program in the aspects of interaction with a user, visual experience and the like.

The embodiment of the application provides a method, a device, equipment and a medium for integrating a native program and an applet, which can select the applet from an applet list provided by the native program and display a page of the applet by using the native program. When the display page is switched to the page of the small program, and the small program is started again after the original program is closed, the user does not need to enter the page of the original program firstly and then enter the page of the small program, and the user can directly enter the page of the small program through the original program, so that the interaction and visual experience effects of the small program and the user are consistent or tend to be consistent with the effect of the original program, and the interaction and visual experience effects of the small program in the user are improved.

The method for integrating the native program and the applet provided by the embodiment of the application mainly relates to terminal equipment, and the native program is installed in the terminal equipment. The terminal device can communicate with a background system of the native program, an applet platform and the like through the gateway so as to realize the functions of the native program and the applet. Fig. 1 is a schematic diagram of an example of an application scenario of an integration method of a native program and an applet, provided by an embodiment of the present application. As shown in fig. 1, a user 11 can operate a terminal device 12, and a native program is installed in the terminal device 12. The terminal device 12 may include, but is not limited to, a mobile phone, a tablet computer, an electronic computer, a wearable device, etc. The terminal device 12 can be in communication interaction with the background system 14 of the native program through the gateway 13, and the terminal device 12 can also be in communication interaction with the applet platform 15 through the gateway 13 to obtain the applet information. The operator of the native program can manage, maintain, etc. the backend system 14 of the native program through the management system 16. The user of the applet platform 15 can upload the developed applet to the applet platform 15 and manage and maintain the developed applet.

The integration method, apparatus, device and medium of native program and applet provided in the present application will be described in turn.

The application provides an integration method of a native program and an applet, which can be applied to a terminal device, namely the integration method of the native program and the applet can be executed by the terminal device. Fig. 2 is a flowchart of an embodiment of a method for integrating a native program and an applet provided in the present application. As shown in fig. 2, the program and applet integrating method may include steps S201 to S204.

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

The terminal device currently displays the page of the native program. The applet list may be invoked by entry of a page of the native program. For example, a native program page includes a human-machine interaction control on it that invokes a list of applets, which when clicked triggers the list of applets to be displayed.

The applet list may include applet information for at least one applet. The applet information may characterize the applet. For example, the applet information may include one or more of an applet name, an applet version name, an applet type, an applet graphic flag, an applet page thumbnail, an applet introduction description, an applet identifier, a native program version supported by the applet, an applet owner identifier, an applet priority, and the like. The applet type may characterize the functional type of the applet and may include, without limitation, a pay class, a game class, a shopping class, etc. The applet graphic identifier may be implemented in the applet list as an applet graphic identifier or as a Uniform Resource Locator (URL) address of the applet graphic identifier, and the URL address of the applet graphic identifier may be triggered to display the applet graphic identifier. The small program page thumbnail can be realized in the small program list as the small program page thumbnail or the URL address of the small program page thumbnail, and the URL address of the small program page thumbnail is triggered to display the small program page thumbnail. The applet identifier is used to identify the applet, and may be an identifier such as a number of the applet, and in some examples, the applet identifier may be an encrypted identifier, which is not limited herein. The identity to which the applet belongs may be the organization number of the applet developer. The applet priority may be a priority established by the native program or the applet platform, and is not limited herein; in some examples, applet priorities may be represented by numbers, with a larger value of a number representing a higher priority. The applet information may allow the user to better understand the applet for the user's selection.

In some embodiments, the applet list may be acquired before performing step S201. In some examples, the applet list may be stored in the terminal device, which may be obtained directly from the terminal device itself in case the applet list needs to be invoked. In other examples, the terminal device may send an applet obtain request to a backend system of the native program to obtain an applet list from the backend system of the native program.

The applet list may include applet information for the applets arranged from high to low in recommendation. The recommendation degree may be determined according to the function use information of the user. The function use information includes information related to the use of the native program function by the user and information related to the use of the applet function by the user. According to the function use information, the function use of the user can be portrayed, the function use habit of the user is obtained, and the recommendation degree of the small program is further obtained according to the function use habit of the user.

The function usage information may include one or more of the following: the system comprises an applet version name, an applet region, an applet priority, applet binding resource information, an applet attention amount, payment information, payment mechanism information and user personal information.

In the case where the function usage information includes one item of information, the level of the recommendation degree may be determined based on this item of information.

In some examples, the function usage information includes an applet version name indicating that the closer the applet is related to the native program, the higher the recommendation level of the applet. For example, a derivative version of a native program may have a higher recommendation for an applet than a version of the applet that is unrelated to the native program.

In some examples, the function usage information includes a region to which the applet belongs, and the recommendation degree of the applet is higher the closer the current geographical location of the terminal device is to the region to which the applet belongs. For example, the recommendation degree of the applet that the area to which the applet belongs includes the current geographical position of the terminal device is higher than the recommendation degree of the applet that the area to which the applet belongs does not include the current geographical position of the terminal device.

In some examples, the functionality usage information includes applet priorities, the higher the applet priority, the higher the recommendation of the applet. For example, the recommendation level of the applet with the applet priority level 5 is higher than the recommendation level of the applet with the applet priority level 2.

In some examples, the functionality usage information includes applet binding resource information. The applet binding resource information may be obtained from the resource binding completion page when the user completes the resource binding, which is not limited herein. The applet binding resource information is information related to the applet binding resource, and for example, the applet binding resource information may include the applet binding resource, the frequency of the applet binding resource used by the user, the number of the applet binding resource, and the like. The higher the frequency of the applet binding resources used by the user is, the higher the recommendation degree of the applet is; the greater the number of bound resources of the applet, the higher the recommendation level of the applet. For example, the applet binding resource is a payment card or a merchant bound with the applet, and the recommendation degree of the applet matched with the payment card or the merchant bound with the applet is higher than that of the applet not matched with the payment card or the merchant bound with the applet; the recommendation degree of the small program with high use frequency of the payment card or the merchant bound with the small program is higher than that of the small program with low use frequency of the payment card or the merchant bound with the small program; the recommendation degree of the small program with the large number of the payment cards or the merchants bound with the small program is higher than that of the small program with the small number of the payment cards or the merchants bound with the small program.

In some examples, the function usage information includes an applet focus amount, the higher the recommendation level of the applet. For example, the recommendation degree of an applet with a high applet attention amount is higher than the recommendation degree of an applet with a low applet attention amount.

In some examples, the functional usage information includes payment information. The payment information may be acquired from the payment completion page when the user completes the payment, which is not limited herein. The payment information is related to user payment, and the payment information may include a payment card or a payment merchant. For example, if the payment information includes a payment card, the recommendation degree of the applet matched with the payment card is higher than that of the applet not matched with the payment card; if the payment information comprises the payment merchant, the recommendation degree of the small program matched with the payment merchant is higher than that of the small program not matched with the payment merchant.

In some examples, the functional usage information includes payment affiliate information. The payment affiliate information may be obtained from the payment details page when the user views the payment details, and is not limited herein. The payment affiliate information may characterize the affiliate to which the payment pertains. For example, the recommendation degree of the applet that matches the payment-affiliated institution information is higher than the recommendation degree of the applet that does not match the payment-affiliated institution information.

In some examples, the function usage information includes user personal information. The recommendation degree of the small programs suitable for the personal information of the user can be obtained according to the recommendation degree of the common user characteristics in the big data matched with the small programs. The recommendation degree of the small program matched with the personal information of the user is higher than that of the small program not matched with the personal information of the user. For example, the user personal information includes an age, and if the age in the user personal information is 26 years, the recommendation degree of the applet matching the age group of 20 to 30 years is higher than that of the applet matching the age group of 40 to 50 years.

When the function use information includes two or more items of information, the level of the recommendation level can be determined based on the two or more items of information and the weight corresponding to each item of information.

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

The first type of applet includes an applet that is a small programmed version of the native program. The applet of the applet refers to the specific version derived based on the applet, and the applet of the applet is the applet derived based on the specific version of the applet, for example, the first applet may include a simple applet of the applet, an applet that reserves and reinforces partial functions for a specific group based on the applet, and the like, which is not limited herein. Compared with the scheme of realizing the derivative version through the native program, the derivative version of the native program is realized through the applet in the embodiment of the application, a user does not need to download the native program of the derivative version, the applet of the corresponding derivative version can be switched according to the self requirement, under the condition that the functions of multiple versions can be realized, the occupied storage space in the terminal equipment is reduced, and the development difficulty of the derivative version of the native program can also be reduced by the applet. In the embodiment of the application, the interaction between the small programming version of the native program and the user and the effect in the aspects of visual experience and the like can be consistent or nearly consistent with the effect of the native program, so that the user experience is further improved.

The second class of applets includes applets that have a different party than the native program. Native programs may also integrate different applets of their own. The terminal equipment receives the operation input of the user, and can call out the small program of which the party belongs to the original program and is different from the party belonging to the original program. The functions of the applet, which belongs to a different party from the native program, may be similar to or different from the functions of the native program, and are not limited herein. For example, the native program is an application of a payment platform, and the applet list of the native program may include applet information for applets of multiple banks. For another example, where the native program is an application of a third payment platform, the applet list of the native program may include applet information for the run code query applet. By adding the applet information of the applet of which the side is different from that of the original program into the applet list, the functions which can be realized by the original program can be further enriched, so that the functions of the terminal equipment are more flexibly realized.

For example, the native program is program a1, and the list of applets that the native program can provide can include applet information of applet B1 of program a1, applet information of applet B2 of program a1, applet information of applet C1 of Bank1, applet information of applet C2 of Bank2, applet information of applet D1 of Bank2, and applet information of merchant shopping applet D2.

The switch selection input is used to select an applet in the applet list. The target applet selects an applet selected in the applet list for the handover selection input. The switching selection input may be a single click input, a multi-click input, a slide input, etc., and is not limited thereto.

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

The long-term static information is information that is relatively hard to change for long-term effectiveness of the applet, for example, the long-term static information may include an applet identifier, configuration information of the applet, fixed presentation information of the applet, and the like, which is not limited herein. The terminal device may request long-term static information of the target applet from the applet platform.

And storing the long-term static information locally until the next switching selection input selects a different target small program or a native program. And after the target applet is selected and input in the switching selection, and under the condition that the next switching selection input does not occur, the long-term static information is always stored locally. And after the target applet is selected and input by the current switching selection and under the condition that 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 the current switching selection input, locally deleting the long-term static information of the target applet selected by the current switching selection input, and locally storing the long-term static information of the target applet selected by the next switching selection input.

In step S203, short-term dynamic information of the target applet is acquired, the target applet is caused to run in the applet container of the terminal device according to the long-term static information and the short-term dynamic information of the target applet, and the display page is switched from the page of the native program to the page of the target applet.

The running of the target applet also requires the acquisition of short-term dynamic information of the target applet. The short-term dynamic information is real-time information of the applet that is relatively easy to change, for example, the short-term dynamic information may include a policy list, a URL address of a dynamically changing page, and the like, and is not limited herein. The terminal device may request short-term dynamic information of the target applet from the applet platform.

An applet container can be viewed as the framework of an applet. The long-term static information and the short-term dynamic information work together to enable the applet to run in the applet container. After the short-term dynamic information of the target small program is obtained, the page of the target small program can be obtained together according to the long-term static information and the short-term dynamic information of the target small program, and therefore the display page of the native program can be switched from the page of the native program to the page of the target small program. Specifically, a page may be switched from the native program to the first page of the target applet.

In step S204, in response to the applet start 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 an applet container, so that the terminal device displays the page of the target applet through the native program.

The applet starting input is an input operation for starting the applet, the terminal device receives the applet starting input, calls the native program, reads the long-term static message of the target applet stored in step S202 through the native program, and sets a main task and a root page of the native program as an applet container, so that the main task is to run the target applet after the native program is triggered and started, the root page, i.e., a first loaded page, is a page of the target applet, and after the native program is called and opened, the terminal device directly displays the page of the target applet.

In some embodiments, the terminal device may determine whether the applet container is in an open state before invoking the native program to read the long-term static information of the target applet. In the case where the display page of the native program is switched from the page of the native program to the page of the applet, the applet container needs to be opened to enable the applet to run. By judging whether the applet container is in an open state or not, whether the display page of the native program is the applet page or the native program page after the last switching can be judged. If the small program container is in an open state, determining that the display page of the original program after the last switching is the page of the small program, and the situation that the small program can be directly displayed through the original program is the situation; if the applet container is not in the open state, it may be determined that the displayed page of the native program after the last switch is the page of the native program. And if the applet container is in an open state, reading long-term static information of the target applet.

In some embodiments, to further achieve the interaction and display effect of the native-like program of the applet, the address of the front page of the target applet may be acquired before the short-term dynamic information of the target applet is acquired, so that the terminal device displays the front page of the target applet before displaying the page of the target applet. The terminal device may request the applet platform to obtain an address of a front page of the target applet. The front page of the applet is a page displayed before the page of the applet during the startup of the applet, for example, the front page may include an open screen page and/or an advertisement page, etc. In some examples, the leading page may be displayed according to an address of the leading page before the display page is switched to the page of the target applet, and the leading page may fill in a display blank that may be generated during the switching of the page of the native program to the page of the target applet. In other examples, after the address of the front page of the target applet is obtained, before the terminal device displays the page of the target applet through the native program in step S204, the front page may be displayed through the native program according to the address of the front page, so as to further achieve the display effect of the applet-type native program.

In some embodiments, if the user needs to switch back from the page of the target applet to the page of the native program, the user may make a switch selection input to the page of the target applet, in response to which the terminal device selects program information of the native program from an updated applet list provided by the terminal device invoking the native program, and switches the display page of the native program from the page of the target applet to the page of the native program, in particular, from the page of the target applet to the first page of the native program.

The updated applet list may include program information for the native program. The program information may include one or more of a program name, a program version, a program type, a program graphic flag, a program page thumbnail, a program introduction description, a program identifier, a program affiliated party identifier, and the like, and is not limited herein. In the process of switching between the page of the native program and the page of the applet, or in the process of switching between the page of the applet and the page of the applet, the applet list may be updated, the program information of the native program or the applet after the switching is eliminated from the applet list, and the program information of the native program or the applet before the switching is added to the applet list.

In some examples, where the display page of the native program is a page of the target applet, the page of the native program may be asynchronously loaded to enable display of the page of the native program to be quickly completed if the page of the target applet is switched to the page of the native program.

In the embodiment of the application, a user can perform switching selection input on a page of an original program in a terminal device, the terminal device responds to the switching selection input to determine a target applet needing to be switched, long-term static information of the target applet is stored locally, short-term dynamic information of the target applet is obtained, the target applet is enabled to run in an applet container according to the long-term static information and the short-term dynamic information of the target applet, the page of the original program is switched to the page of the target applet, and the page of the target applet is displayed by the original program. Under the condition of responding to the small program starting input and restarting the small program, the terminal device calls the original program to read the long-term static information, sets the main task and the root page of the original program as a small program container, and displays the page of the target small program through the original program, so that the effect of the small program in the aspects of interaction with a user, visual experience and the like can be consistent or nearly consistent with that of the original program, and the effect of the small program in the aspects of interaction with the user, visual experience and the like is improved. Moreover, when the applet list provided by the native program includes the applet information of a plurality of applets, by using the method of the embodiment of the application, the native program can be called to switch and display any one of the applet lists, and the effect of coexistence of a plurality of applet-type native programs in one native program is achieved.

In order to more fully describe the method for integrating the original program and the applet in this embodiment, a process of opening the original program for the first time and switching from the page of the original program to the page of the applet will be described below. Fig. 3 is a flowchart of an example of a process of switching from a native program page to an applet page according to an embodiment of the present disclosure. As shown in fig. 3, the process of switching the page of the native program into the page of the applet may include steps S301 to S317.

In step S301, the terminal device receives a start input for the native program, and displays a top page of the native program.

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

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

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

In step S305, the terminal device acquires the address of the leading 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 in the open state, jumping to step S308; if the applet container is not in the open state, go to step S307.

In step S307, the terminal device closes the task 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 has successfully logged in to the target applet. If the login is successful, jumping to step S311; if the login fails, the process goes to step S309, or the user is prompted to log in manually.

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

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

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

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

In step S315, the terminal device buffers the 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 home page of the target applet by the native program.

Some steps from step S301 to step S317 may be omitted, or the order between the steps may be changed as appropriate, according to the actual application scenario and operation situation, and is not limited herein.

In the above embodiment, the applet may use a general function of the native program in the course of the terminal device running. The general-purpose function is a function that is commonly required by the native program and the applet, for example, the general-purpose function may include one or more of an encryption function, a decryption function, a network request function, a local access function, a user data management function, a hardware capability use function of the terminal device, and the like, and is not limited herein. The applet container may be provided with an Application Programming Interface (API). The API is used for the applet in the applet container to call the generic function of the native program. That is, the applet can call the general-purpose function of the native program through the API of the applet container. Therefore, partial capability of the original program is opened to the small program, so that on the basis of not increasing the difficulty of developing the small program, the difference of the effect of the small program and the original program in the aspect of functions is reduced, the effect of the small program in the aspect of functions is improved, and the functions of the small program are richer. Under the condition that the target small program runs in the small program container and needs to execute the general function, the general function of the original program can be called through the API, and the function of the target small program is enriched.

For example, fig. 4 is a schematic logical architecture diagram of an example of coexistence of an original program and an applet in a terminal device according to an embodiment of the present disclosure. As shown in fig. 4, a native program, applet 1, applet 2 and applet 3 may be run in the terminal device. The terminal device has an applet container having an API and a User Interface (UI) component, and the generic functions of the native application may include an encryption/decryption function, a network request function, a local access function, a User data management function, a hardware capability use function, and other functions. The applet 1, the applet 2 and the applet 3 can call general functions of the native program through the API during the operation of the applet container.

In different scenarios, the manner of starting the applet triggered by the applet start input is also different, and the integration method of the native program and the applet will be described below by taking different scenarios as an example.

In some embodiments, the applet initiation input comprises an initiation input to an original program in the terminal device. When the current native program is closed and the last opened display page of the native program is finally switched to the page of the target applet, if the native program is started again through the starting input of the native program, the terminal device calls the native program to read the long-term static information of the target applet saved under the condition that the last opened native program is switched to the page of the target applet, and sets the main task and the root page of the native program as an applet container, so that the display page of the native program is the first page of the target applet.

In order to more fully describe the integration method of the native program and the applet in this embodiment, a process of restarting the native program after the display page of the native program is switched to the page of the target applet is described below. Fig. 5 is a flowchart of an example of a native program restart procedure provided in an embodiment of the present application. As shown in fig. 5, the flow of the native program restart may include steps S401 to S415.

In step S401, the terminal device starts the native program in response to a start input of the native program by the user.

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

In step S403, the terminal device determines whether the native program last started up display page has been switched to a page of the applet. If the native program is started last time and is not switched to the page of the applet, jumping to step S404; if the native program has been started the page switched to the applet last time, go to step S405.

Whether the page of the small program switched by the original program started last time is the page of the target small program can be determined through judging whether the small program container is in an open state or not and through locally stored long-term static information.

In step S404, the terminal device displays the top 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 the switching can be performed quickly when the page of the native program needs to be switched back.

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

In step S408, the terminal device determines whether the user has succeeded in logging in the target applet. If the login is successful, jumping to step S409; if the login fails, jumping to step S405, or prompting the user to log in manually.

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

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

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

In step S412, the terminal device sends a prompt message to prompt that the short-term dynamic information acquisition fails.

In step S413, the terminal device buffers the 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 top page of the target applet by the native program. Specifically, the terminal device may display a home page of the target applet by the native program by setting a main task and a root page of the native program as an applet container.

Some steps from step S401 to step S415 may be omitted, or the order between the steps may be changed as appropriate, according to the actual application scenario and the operation situation, and is not limited herein.

In some embodiments, the applet launch input comprises a launch input to a desktop icon of the applet displayed by the terminal device. The user can create a desktop icon of the small program on the terminal equipment, and the original program is quickly called to enter the small program through the desktop icon of the small program. Fig. 6 is a flowchart of another embodiment of a method for integrating a native program with an applet provided in the present application. Fig. 6 is different from fig. 2 in that step S204 in fig. 2 can be specifically subdivided into step S2041a to step S2044a in fig. 6, and the method for integrating the native program and the applet shown in fig. 6 can further include step S205 and step S206.

In step S2041a, in response to a start input to the desktop icon of the applet displayed by the terminal device, a jump is made to the transit page.

And starting the small program corresponding to the desktop icon by starting the input of the desktop icon of the small program. The start input may specifically include a click input, a long-press input, and the like for the desktop icon, which is not limited herein. When the terminal equipment receives the starting input of the desktop icon of the small program, the terminal equipment jumps to the transfer page first and then jumps to other pages from the transfer page. The transit page may be a transparent page and not explicitly displayed.

The desktop icon of the applet may be generated in a case where the display page of the native program is switched to the page of the applet. The terminal equipment can respond to desktop icon generation input of the page of the applet, jump to the icon generation transfer page, trigger generation and display the desktop icon of the applet on the terminal equipment. The icon generation relay page may be an H5 page or other type of page, and is not limited herein.

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

In the case where the display page of the native program is switched to the page of the applet, the applet container is opened. In the event that the display page of the native program is switched to the page of the native program, the applet container is closed. Whether the display page of the native program has been switched to the page of the applet before can be determined by determining whether the applet container is in an open state.

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

The small program container is in an open state, which indicates that the display page of the original program is switched to the page of the small program before, and the small program container can jump from the transfer page to the original program so as to call the original program to read the long-term static information of the target small program which is stored locally before. Setting the main task and the root page of the native program as an applet container, wherein the applet container is a target applet, so that the terminal equipment has the capability of displaying the page of the target applet.

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

And under the condition that the small program corresponding to the desktop icon is the target small program, the terminal equipment can display the page of the target small program through the native program. From the aspect of user experience, after a user starts and inputs a desktop icon of an applet, a display page of a native program is opened, and the display page is a page of a target applet, specifically, the display page is a home page of the target applet.

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

In step S205, if the applet corresponding to the desktop icon is not the target applet, a jump is made 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 the short-term dynamic information of the applet corresponding to the desktop icon may be obtained, the applet corresponding to the desktop icon may be run in the applet container according to the long-term static information and the short-term dynamic information of the applet corresponding to the desktop icon, the main task and the root page of the native program have been set as the applet container, and the applet page corresponding to the desktop icon may be displayed through the native program so as to jump from the applet page corresponding to the target applet to the applet page corresponding to the desktop icon. Wherein, the page of the target small program can be used as a transfer page which is not displayed explicitly.

In other examples, the terminal device may display a page of the target applet through the native program, then receive a switching input of the user, obtain long-term static information and short-term dynamic information of the applet corresponding to the desktop icon in response to the switching input, enable the applet corresponding to the desktop icon to run in the applet container, and display the page of the applet corresponding to the desktop icon through the native program 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 the open state, the applet corresponding to the desktop icon is jump-loaded from the middle page.

The applet container is not in an open state, indicating that the display page of the native program has been previously switched to the page of the native program. In this case, the applet can be loaded and run in the normal applet loading manner.

In order to more fully describe the integration method of the original program and the applet in the present embodiment, a process of starting the applet through the desktop icon of the applet will be described below. Fig. 7 is a flowchart of an example of a process of starting an applet through a desktop icon of the applet according to an embodiment of the present application. As shown in fig. 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 relay page in response to a start input of the desktop icon of the applet.

In step S502, the terminal device determines whether the native program last start-up display page has been switched to the page of the applet. If the native program is started last time and is not switched to the page of the applet, jumping to step S503; if the native program has been started the page switched to the applet last time, go to step S504.

Whether the page of the small program switched by the last start of the original program is the page of the small program corresponding to the desktop icon can be determined through judging whether the small program container is in the open state or not and through locally stored long-term static information.

In step S503, the terminal device loads and runs the applet corresponding to the desktop icon according to a normal applet loading manner.

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

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

In step S506, the terminal device displays the page under load.

In step S507, the terminal device determines whether the applet corresponding to the desktop icon is the target applet according to the locally stored long-term static information; if the small program corresponding to the desktop icon is the target small program, jumping to step S508; if the applet corresponding to the desktop icon is not the target applet, go to step S510.

In this example, it is default that if the display page before the native program is switched to the page of the applet, the page of the applet switched to before the native program is the page of the target applet.

In step S508, the terminal device acquires 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 acquired. If the acquisition is successful, jumping to step S513; if the acquisition fails, go 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 acquisition of the long-term static information and the short-term dynamic information is successful. If the acquisition is successful, jumping to step S514; if the acquisition fails, go to step S512.

In step S512, the terminal device sends a prompt message, and the prompt message fails to be acquired.

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

In step S514, the terminal device locally stores the long-term dynamic information and caches the 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 the native program. Specifically, the terminal device may display a home page of the applet corresponding to the desktop icon through the native program by setting a main task and a root page of the native program as an applet container.

Some steps from step S501 to step S516 may be omitted, or the order between the steps may be changed as appropriate, according to the actual application scenario and the operation situation, and is not limited herein.

In some embodiments, the terminal device may further search for an applet indicated by the search input in an applet integrated with the native program in response to the search input to the display page of the native program. It may be determined whether the native program's current display page has been switched to the applet's page. And if the page is not switched to be the page of the small program, loading the small program according to a common small program loading mode and running. And if the page is switched to the small program page, starting the small program indicated by the search input, acquiring the long-term static information and the short-term dynamic information of the small program indicated by the search input, operating the small program indicated by the search input in the small program container according to the long-term static information and the short-term dynamic information, and setting the main task of the native program as the small program container so that the terminal equipment can display the page of the small program indicated by the search 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 refer to steps S408 to S415 in the above embodiments, which are not described herein again.

In some embodiments, the applet initiation input may include an initiation input for the link information. The user can quickly invoke the native program into the applet through the received link information. Fig. 8 is a flowchart of another embodiment of a method for integrating a native program with an applet. Fig. 8 is different from fig. 2 in that step S204 in fig. 2 can be specifically detailed as step S2041b to step S2043b in fig. 8, and the method for integrating the native program and the applet shown in fig. 8 can further include step S207 and step S208.

In step S2041b, in response to the start input to the link information, the native program is invoked, and it is determined whether or not the applet container is in the open state.

The start input to the link information is used to start the applet corresponding to the link information. Further, the launch input to the link information may be used to invoke a designated page of the applet indicated by the link information. The link information may include an external scheme link, etc., and is not limited thereto. The link information may include a URL address of a specified page of the applet indicated by the link information. The link information may be carried in a short message, a multimedia message, an instant messaging message, and the like, which is not limited herein. The start input may specifically include a click input, a long-press input, and the like for the link information, and is not limited herein. When the terminal equipment receives the starting input of the link information, the native program is called to judge whether the small program container is in an opening state. Whether the display page of the native program has been switched to the page of the applet before can be determined by determining whether the applet container is in an open state.

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

The small program container is in an open state, which indicates that the display page of the native program is switched to the page of the small program before, and the native program can be called to read the long-term static information of the target small program which is stored locally before. Setting the main task and the root page of the native program as an applet container, wherein the applet container is a target applet, so that the terminal equipment has the capability of displaying the page of the target applet.

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 based on the link information.

In the case where the applet indicated by the link information is the target applet, the terminal device may display the page of the target applet by the native program. Moreover, since the link information may specifically indicate a specified page in the target applet, the specified page indicated by the link information in the target applet may be opened and displayed by the native program according to the link information. From the aspect of user experience, after the user performs the start input on the link information, a display page of the native program is opened, and the display page is a page of the target applet, specifically, the display page is a specified page indicated by the link information in the target applet.

In some examples, whether the applet indicated by the link information is the target applet may be determined by whether the applet identifier of the applet indicated by the link information coincides with the applet identifier previously stored in the local long-term static information.

In step S207, if the applet indicated by the link information is not the target applet, the page of the target applet is skipped 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 the short-term dynamic information of the applet indicated by the link information may be acquired, the applet indicated by the link information may be operated in the applet container according to the long-term static information and the short-term dynamic information of the applet indicated by the link information, the main task and the root page of the native program may have been set as the applet container, and the page of the applet indicated by the link information may be displayed by the native program to jump from the page of the target applet to the page of the applet indicated by the link information. Wherein, the page of the target small program can be used as a transfer page which is not displayed explicitly.

In other examples, the terminal device may display a page of the target applet through the native program, receive a switching input of the user, acquire long-term static information and short-term dynamic information of the applet indicated by the link information in response to the switching input, cause the applet indicated by the link information to run in the applet container, and display a designated page of the applet indicated by the link information through the native program to jump from the page of the target applet to the designated page of the applet indicated by the link information.

In step S208, in a case where the applet container is not in the open state, the page of the applet indicated by the link information is opened by the browser.

The applet container is not in an open state, indicating that the display page of the native program has been previously switched to the page of the native program. In this case, a specified page of the applet indicated by the link information may be opened using the browser.

In order to more fully describe the integration method of the original program and the applet in the present embodiment, the process of starting the applet through the link information is described below. Fig. 9 is a flowchart of an example of initiating an applet process through link information according to an embodiment of the present application. As shown in fig. 9, the flow of starting an applet by link information may include steps S601 to S606.

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

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

In step S603, the terminal device determines whether the native program last start-up display page has been switched to the page of the applet. If the native program is started last time and is not switched to the page of the applet, jumping to step S604; if the native program has been started the page switched to the applet last time, go to step S605.

Whether the page of the small program switched by the last start of the original program is the page of the small program specified by the link information can be determined through judging whether the small program container is in an open state or not and through locally stored long-term static information.

In step S604, the terminal apparatus 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, the starting of the applet indicated by the link information and the opening and displaying of the designated page of the applet indicated by the link information in step S605 may refer to the related contents in steps S504 to S516 in the above embodiments. If the applet indicated by the link information is the target applet, the designated page of the applet indicated by the link information can be directly displayed by the native program according to the link information. If the small program indicated by the link information is not the target small program, jumping from the page of the target small program to the specified page of the small program indicated by the link information through the native program.

In step S606, the terminal device asynchronously loads the related information of the native program, so that the switching can be performed quickly when the page of the native program needs to be switched from the page of the applet.

The execution sequence between step S606 and step S605 is not limited, and the two steps may be performed asynchronously.

Depending on the actual application scenario and the operation situation, some steps from step S601 to step S606 may be omitted, or the order between the steps may be changed as appropriate, and is not limited herein.

In some embodiments, the target applet initiation input comprises an initiation input to push information. The user can quickly call up the native program to enter the applet through the received push information. FIG. 10 is a flowchart illustrating a method for integrating a native program with an applet according to still another embodiment of the present disclosure. Fig. 10 is different from fig. 2 in that step S204 in fig. 2 can be specifically subdivided into step S2041c to step S2044c in fig. 10, and the method for integrating the native program and the applet shown in fig. 10 can further include step S209 to step S211.

In step S2041c, in response to a start input for the push information, it is determined whether the native program is in a background running state.

The start input to the push information is used to start the applet indicated by the push information. Further, the initiation input of the push information may be used to invoke a designated page of the applet indicated by the push information. The push information may include push information in a notification bar, push information in a popup, push information on a lock screen interface, and the like, which are not limited herein. The start input may include, but is not limited to, a click input, a long press input, etc. of the pushed information. When the terminal device receives a start input for the link information, the operating state of the native program may be determined. The running states may include a background running state and a front-end running state.

In step S2042c, when the native program is in the background operation state, the native program is invoked to determine whether or not the applet container is in the open state.

The native program is in a background running state, namely the native program is not displayed on the terminal equipment at present, and the native program needs to be called up to judge whether the small program container is in an open state. And judging whether the display page of the native program is switched to the page of the applet before by judging whether the applet container is in an open state.

In step S2043c, in the case where the applet container is in the open state, 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 small program container is in an open state, the small program container is in the open state, the small program container represents that the display page of the native program is switched to the page of the small program before, and the native program can be called to read the long-term static information of the target small program which is stored locally before. Setting the main task and the root page of the native program as an applet container, wherein the applet container is a target applet, so that the terminal equipment has the capability of displaying the page of the target applet.

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.

In the case where the applet indicated by the push information is the target applet, the terminal device may display the page of the target applet through the native program. Moreover, since the push information may specifically indicate a specific page in the target applet, the specific page indicated by the push information in the target applet may be opened and displayed by the native program according to the connection information. From the aspect of user experience, after the user starts and inputs the push information, a display page of the native program is opened, and the display page is a page of the target applet, specifically, the display page is a specified page indicated by the push information in the target applet.

In some examples, whether the applet indicated by the push information is the target applet may be determined by whether the applet identifier of the applet indicated by the push information coincides with the applet identifier previously stored in the local long-term static information.

In step S209, if the applet indicated by the push information is not the target applet, the page of the target applet is skipped 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 the short-term dynamic information of the applet indicated by the push information may be acquired, the applet indicated by the push information may be run in the applet container according to the long-term static information and the short-term dynamic information of the applet indicated by the push information, the main task and the root page of the native program have been set as the applet container, and the page of the applet indicated by the push information may be displayed by the native program to jump from the page of the target applet to the page of the applet indicated by the push information. Wherein, the page of the target small program can be used as a transfer page which is not displayed explicitly.

In other examples, the terminal device may display a page of the target applet through the native program, then receive a switching input of the user, obtain, in response to the switching input, long-term static information and short-term dynamic information of the applet indicated by the push information, enable the applet indicated by the link information to run in the applet container, and display, through the native program, a specified page of the applet indicated by the push information to jump from the page of the target applet to the specified page of the applet indicated by the push information.

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

The native program is in a front-end running state, namely the native program is displayed on the terminal equipment at present, the native program does not need to be called up, and the native program can be directly used for jumping to a designated page of the small program indicated by the push information.

In step S211, if the applet container is not in the open state, the page of the applet indicated by the push information is opened by the browser.

The applet container is not in an open state, indicating that the display page of the native program has been previously switched to the page of the native program. In this case, a specified page of the applet indicated by the push information can be opened using the browser.

In order to more fully describe the integration method of the original program and the applet in this embodiment, a process of starting the applet by pushing information is described below. Fig. 11 is a flowchart of an example of a process of initiating an applet by pushing information according to an embodiment of the present application. As shown in fig. 11, the flow of launching an applet by pushing information may include steps S701 to S707.

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

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

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

In step S704, the terminal device determines whether the native program last started up display page has been switched to a page of the applet. If the native program is started last time and is not switched to the page of the applet, jumping to step S705; if the native program has been started the page switched to the applet last time, go to step S707.

In step S705, the terminal device opens a 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, and opens and displays a specified page of the applet indicated by the push information.

In some examples, the starting of the applet indicated by the push information and the opening and displaying of the designated page of the applet indicated by the push information in step S707 can be referred to the relevant contents in steps S504 to S516 in the above embodiments. If the applet indicated by the push information is the target applet, the designated page of the applet indicated by the push information can be directly displayed through the native program according to the push information. If the small program indicated by the push information is not the target small program, jumping from the page of the target small program to the specified page of the small program indicated by the push information through the native program.

Some steps from step S701 to step S707 may be omitted, or the order between the steps may be changed as appropriate, according to the actual application scenario and the operation situation, and is not limited herein.

The application also provides an integrated device of the native program and the small program, and the integrated device of the native program and the small program can be arranged in the terminal equipment. FIG. 12 is a block diagram illustrating an embodiment of an integrated device of native programs and applets provided in the present application. As shown in fig. 12, the integrated native program and applet apparatus 800 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 characterizing a target applet from a list of applets provided by the native program in response to a switch selection input to a page of the native program in the terminal device.

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

The obtaining module 802 is also configured to obtain short-term dynamic information of the target applet.

The control module 803 may be configured to enable the target applet to run in the applet container of the terminal device according to the long-term static information and the 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 further configured to, in response to the applet starting input, invoke the native program to read the long-term static information of the target applet, and set the main task and the root page of the native program as an applet container, so that the terminal device displays the page of the target applet through the native program.

In this embodiment, a user may perform a switching selection input on a page of an original program in a terminal device, the terminal device determines a target applet to be switched in response to the switching selection input, locally stores long-term static information of the target applet, acquires short-term dynamic information of the target applet, and causes the target applet to run in an applet container according to the long-term static information and the short-term dynamic information of the target applet, switches the page of the original program to the page of the target applet, and displays the page of the target applet by using the original program. Under the condition that the small program is restarted in response to the small program starting input, the terminal equipment calls the original program to read the long-term static information, sets the main task and the root page of the original program as a small program container, and displays the page of the target small program through the original program, so that the effects of the small program in the aspects of interaction with a user, visual experience and the like can be consistent or tend to be consistent with those of the original program, and the effects of the small program in the aspects of interaction with the user, visual experience and the like are improved. Moreover, when the applet list provided by the native program includes the applet information of a plurality of applets, by using the method of the embodiment of the application, the native program can be called to switch and display any one of the applet lists, and the effect of coexistence of a plurality of applet-type native programs in one native program is achieved.

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

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

In some embodiments, the obtaining module 802 may be further configured to obtain an address of a 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 for the applets in the applet container to call general functions of the native application.

The control module 803 may also be used to call the generic function of the native program through the API in the case where the target applet is running in the applet container and needs to perform the generic function.

In some embodiments, the applet initiation input comprises an initiation input to an original program in the terminal device.

In some embodiments, the applet launch input comprises a launch input to a desktop icon of the applet displayed by the terminal device.

The control module 803 may be used to: responding to the starting input of the desktop icon of the small program displayed by the terminal equipment, and jumping to a transfer page; judging whether the small program container is in an open state or not; under the condition that the small program container is in an open state, jumping from the middle transfer page to the original program, reading long-term static information of the target small program, and setting a main task and a root page of the original program as the small program container; and if the small program corresponding to the desktop icon is the target small program, controlling the terminal equipment to display the page of the target small program.

In some examples, the control module 803 may be further configured to jump from the page of the target applet to the page of the applet corresponding to the desktop icon if the applet corresponding to the desktop icon is not the target applet

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

The control module 803 may be used to: responding to the starting input of the link information, calling up an original program, and judging whether the small program container is in an opening state; under the condition that the small program container is in an open state, reading long-term static information of a target small program, and setting a main task and a root page of a native program as the small program container; and if the small program indicated by the link information is the target small program, opening the page indicated by the link information in the target small program according to the link information.

In some examples, the control module 803 may be further operable to jump from the page of the target applet to the page of the applet indicated by the link information in the event that the applet indicated by the link information is not the target applet.

In some embodiments, the target applet initiation input comprises an initiation input to push information.

The control module 803 may be used to: responding to the starting input of the push information, and judging whether the native program is in a background running state; under the condition that the native program is in a background running state, calling the native program and judging whether the small program container is in an open state or not; under the condition that the small program container is in an open state, reading long-term static information of a target small program, and setting a main task and a root page of a native program as the small program container; and if the applet indicated by the push information is the target applet, opening a page indicated by the push information in the target applet according to the push information.

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

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

In some embodiments, the obtaining module 802 may also be used to obtain a list of applets.

The applet list includes applet information for arranging the applets from high to low in recommendation.

The recommendation degree is determined according to the function use information of the user, and the function use information comprises one or more than two of the following items: the method comprises the steps of small program version type, small program region, small program priority, small program binding resource information, small program attention amount, payment information, payment belonging mechanism information and user personal information.

In some examples, the applet list includes applet information for the first type of applet and/or applet information for the second type of applet. The first type of applet includes an applet that is a small programmed version of the native program, and the second type of applet includes an applet that has a different party than the native program.

The application also provides a terminal device. Fig. 13 is a schematic structural diagram of an embodiment of a terminal device provided in the present application. As shown in fig. 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 one example, the 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 the embodiments of the present Application.

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

The processor 902 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 901 for realizing integration of the native program and the applet in the above-described embodiments.

In some examples, terminal device 900 can also include a communication interface 903 and a bus 904. As shown in fig. 13, the memory 901, the processor 902, and the communication interface 903 are connected via a bus 904 to complete communication therebetween.

The communication interface 903 is mainly used for implementing communication between modules, apparatuses, units and/or devices in this embodiment of the application. Input devices and/or output devices are also accessible through communication interface 903.

Bus 904 comprises hardware, software, or both coupling the components of terminal device 900 to each other. By way of example, and not limitation, 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), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) Bus, an InfiniBand interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a Micro Channel Architecture (MCA) Bus, a Peripheral Component Interconnect (PCI) Bus, a PCI Express (PCI-E) Bus, a Serial Advanced Technology Attachment (SATA) Bus, a Video Electronics Standards Association Local Bus (VLB) Bus, or other suitable Bus, or a combination of two or more of these. Bus 904 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the application, any suitable buses or interconnects are contemplated by the application.

The fourth aspect of the present application further provides a computer-readable storage medium, where computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the method for integrating a native program and an applet in the foregoing embodiments can be implemented, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, which is not limited herein.

The present application may also provide a computer program product, where instructions in the computer program product, when executed by a processor of a terminal device, cause the terminal device to execute the method for integrating a native program and an applet in the above embodiments. For details, reference may be made to the related descriptions in the above embodiments, which are not repeated herein.

It should be clear that the embodiments in this specification are described in a progressive manner, and the same or similar parts in the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. For apparatus embodiments, device embodiments, computer-readable storage medium embodiments, computer program product embodiments, reference may be made in relation to the description of the method embodiments. The present application is not limited to the particular steps and structures described above and shown in the drawings. Those skilled in the art may make various changes, modifications and additions or change the order between the steps after appreciating the spirit of the present application. Also, a detailed description of known process techniques is omitted herein for the sake of brevity.

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 the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware for performing the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It will be appreciated by persons skilled in the art that the above embodiments are illustrative and not restrictive. Different features which are present in different embodiments may be combined to advantage. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art upon studying the drawings, the specification, and the claims. In the claims, the term "comprising" does not exclude other means or steps; the word "a" or "an" does not exclude a plurality; the terms "first" and "second" are used to denote a name and not to denote any particular order. Any reference signs in the claims shall not be construed as limiting the scope. The functions of the various parts appearing in the claims may be implemented by a single hardware or software module. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims

1. A method for integrating a native program with an applet, comprising:

responding to a switching selection input of a page of a primary program in a terminal device, and selecting small program information representing a target small program from a small program list provided by the primary program;

acquiring long-term static information of the target applet and storing the long-term static information locally;

acquiring short-term dynamic information of the target small program, enabling the target small program to run in a small program container of the terminal equipment according to the long-term static information and the short-term dynamic information of the target small program, and switching a display page from a page of a native program to a page of the target small program;

and responding to an applet starting input, calling the native program to read long-term static information of the target applet, and setting a main task and a root page of the native program as the applet container so that the terminal equipment displays the page of the target applet through the native program.

2. The method of claim 1, further comprising, prior to the invoking the native program to read long-term static information of the target applet:

judging whether the small program container is in an open state or not;

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

and if the applet container is in an open state, reading the long-term static information of the target applet.

3. The method of claim 1, prior to said obtaining short term dynamic information of the target applet, further comprising:

and acquiring the address of the front page of the target small program, so that the terminal equipment displays the front page of the target small program before displaying the page of the target small program.

4. The method according to claim 1, wherein the applet container is provided with an application programming interface API for an applet in the applet container to call a general function of the native program,

the method further comprises the following steps:

calling a generic function of the native program through the API in the event that the target applet runs in the applet container and the generic function needs to be performed.

5. The method of claim 1, wherein the applet launching input comprises a launching input for the native application in the terminal device.

6. The method of claim 1, wherein the applet launching input comprises a launching input of a desktop icon of an applet displayed by the terminal device,

the responding to the applet starting input, calling the native program to read the long-term static information of the target applet, setting the main task and the root page of the native program as the applet container, and enabling the terminal device to display the page of the target applet comprises the following steps:

responding to the starting input of the desktop icon of the small program displayed by the terminal equipment, and jumping to a transfer page;

judging whether the small program container is in an open state or not;

under the condition that the small program container is in an open state, jumping from the transfer page to the original program, reading long-term static information of the target small program, and setting a main task and a root page of the original program as the small program container;

and if the small program corresponding to the desktop icon is the target small program, displaying the page of the target small program.

7. The method of claim 1, further comprising:

and if the small program corresponding to the desktop icon is not the target small program, jumping from the page of the target small program to the page of the small program corresponding to the desktop icon.

8. The method of claim 1, wherein the applet initiation input comprises an initiation input for link information,

in response to the starting input of the link information, calling the native program and judging whether the small program container is in an open state;

under the condition that the small program container is in an open state, reading long-term static information of the target small program, and setting a main task and a root page of the native program as the small program container;

and if the small program indicated by the link information is the target small program, opening a page indicated by the link information in the target small program according to the link information.

9. The method of claim 8, further comprising:

and if the small program indicated by the link information is not the target small program, jumping from the page of the target small program to the page of the small program indicated by the link information.

10. The method of claim 1, wherein the target applet initiation input comprises an initiation input to push information,

responding to the starting input of the push information, and judging whether the native program is in a background running state;

under the condition that the native program is in the background running state, calling the native program, and judging whether the small program container is in an open state;

and if the small program indicated by the push information is the target small program, opening a page indicated by the push information in the target small program according to the push information.

11. The method of claim 10, further comprising:

and if the small program indicated by the push information is not the target small program, jumping from the page of the target small program to the page of the small program indicated by the push information.

12. The method of claim 10, further comprising:

and under the condition that the native program is in a front-end running state, jumping to a page of the small program indicated by the push information.

13. The method of claim 1, further comprising, prior to selecting a target applet from the list of applets provided by the native program:

acquiring the applet list, wherein the applet list comprises applet information of applets arranged from high recommendation degree to low recommendation degree,

the recommendation degree is determined according to function use information of a user, and the function use information comprises one or more than two of the following items: the method comprises the steps of small program version type, small program region, small program priority, small program binding resource information, small program attention amount, payment information, payment belonging mechanism information and user personal information.

14. The method according to claim 1, wherein the applet list comprises applet information of the applets of the first type and/or applet information of the applets of the second type,

the first type of applet includes an applet that is a small programmed version of the native applet, and the second type of applet includes an applet that has a different owner than the owner of the native applet.

15. An integrated native program and applet device, comprising:

the selecting module is used for responding to the switching selection input of the page of the original program in the terminal equipment and selecting the small program information representing the target small program in the small program list provided by the original program;

the acquisition module is used for acquiring the long-term static information of the target applet and locally storing the long-term static information;

the acquisition module is further used for acquiring short-term dynamic information of the target applet;

the control module is used for enabling the target small program to run in a small program container of the terminal equipment according to the long-term static information and the short-term dynamic information of the target small program and switching a display page from a page of a native program to a page of the target small program;

the control module is further used for responding to an applet starting input, calling the native program to read the long-term static information of the target applet, and setting the main task and the root page of the native program as the applet container so that the terminal device can display the page of the target applet through the native program.

16. A terminal device, comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a method of integrating a native program with an applet as claimed in any one of claims 1 to 14.

17. A computer-readable storage medium, characterized in that it has stored thereon computer program instructions which, when executed by a processor, implement a method of integration of a native program with an applet as claimed in any one of claims 1 to 14.