CN114691236B - Method, device, equipment and medium for integrating native program and applet - Google Patents
Method, device, equipment and medium for integrating native program and applet Download PDFInfo
- Publication number
- CN114691236B CN114691236B CN202210293530.4A CN202210293530A CN114691236B CN 114691236 B CN114691236 B CN 114691236B CN 202210293530 A CN202210293530 A CN 202210293530A CN 114691236 B CN114691236 B CN 114691236B
- Authority
- CN
- China
- Prior art keywords
- applet
- page
- information
- target
- program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 95
- 230000007774 longterm Effects 0.000 claims abstract description 88
- 230000003068 static effect Effects 0.000 claims abstract description 87
- 230000004044 response Effects 0.000 claims abstract description 27
- 230000006870 function Effects 0.000 claims description 63
- 230000000977 initiatory effect Effects 0.000 claims description 38
- 230000009191 jumping Effects 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 15
- 230000008571 general function Effects 0.000 claims description 8
- 238000012546 transfer Methods 0.000 claims description 5
- 230000003993 interaction Effects 0.000 abstract description 16
- 230000000007 visual effect Effects 0.000 abstract description 14
- 238000012545 processing Methods 0.000 abstract description 7
- 230000001151 other effect Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 21
- 230000000694 effects Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 14
- 230000010354 integration Effects 0.000 description 11
- 238000011161 development Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000000763 evoking effect Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method, a device, equipment and a medium for integrating a native program and an applet, and belongs to the field of data processing. The method comprises the following steps: selecting applet information characterizing 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 a target applet and locally storing the long-term static information; acquiring short-term dynamic information of a target applet, enabling the target applet to run in an applet container according to long-term static information and short-term dynamic information, and switching a display page from a page of a native program to a page of the target applet; and responding to the applet starting input, calling the original program to read long-term static information of the target applet, setting a main task and a root page of the original program as applet containers, and enabling the terminal equipment to display the page of the target applet through the original program. According to the embodiment of the application, the interaction between the applet and the user, the visual experience and other effects can be improved.
Description
Technical Field
The application belongs to the field of data processing, and particularly relates to an integration method, device, equipment and medium of a native program and an applet.
Background
The applet is a lightweight application which can be used without downloading and installing, the development difficulty is lower than that of the original program, and the development difficulty can be reduced and the memory space of the equipment can be saved on the basis of realizing the lightweight function. However, due to the self-characteristics of the applet, the applet has simpler functions, and cannot be compared with the native program in the aspects of interaction with a user, visual experience and the like. That is, the applet is 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, the visual experience and other effects.
In a first aspect, an embodiment of the present application provides a method for integrating a native program and an applet, including: in response to a switching selection input to a page of a native program in the terminal device, selecting applet information characterizing a target applet from an applet list provided by the native program; acquiring long-term static information of a target applet and locally storing the long-term static information; acquiring short-term dynamic information of a target applet, running the target applet in an applet container of a terminal device according to long-term static information and short-term dynamic information of the target applet, and switching a display page from a page of a native program to a page of the target applet; and in response to the 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 applet containers 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: a selection module, configured to select applet information characterizing a target applet from an applet list provided by a native program in response to a switching selection input to a page of the native program in a terminal device; the acquisition module is used for acquiring 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 applet to run in an applet container of the terminal equipment according to the long-term static information and the short-term dynamic information of the target applet, and switching a display page from a page of the original program to a page of the target applet; the control module is also used for responding to the applet starting input, calling the original program to read the long-term static information of the target applet, and setting the main task and the root page of the original program as applet containers so that the terminal equipment displays the page of the target applet through the original 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 the native program with the applet of the first aspect.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the method of integrating the native program and the applet of the first aspect.
The embodiment of the application provides an integrated method, a device, equipment and a medium of a primary program and an applet, wherein a user can carry out switching selection input on a page of the primary program in terminal equipment, the terminal equipment 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 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 primary program is switched into a page of the target applet, and the page of the target applet is displayed by the primary program. Under the condition of restarting the applet in response to the applet starting input, the terminal equipment calls the original program to read the long-term static information, the main task and the root page of the original program are set as applet containers, and the pages of the target applet are displayed through the original program, so that the effect of the applet in the aspects of interaction with a user, visual experience and the like can be consistent or tend to be consistent with the original program, and the effect of the applet in the aspects of interaction with the user, visual experience and the like is improved.
Drawings
In order to more clearly illustrate the technical solution of the embodiments of the present application, the drawings that are needed to be used in the embodiments of the present application will be briefly described, and it is possible for a person skilled in the art to obtain other drawings according to these drawings without inventive effort.
Fig. 1 is a schematic diagram of an application scenario of an integration method of a native program and an applet according to an embodiment of the present application;
FIG. 2 is a flowchart of an embodiment of a method for integrating native programs and applets according to the present application;
FIG. 3 is a flowchart illustrating an example of a page flow for switching from a native program page to an applet page according to an embodiment of the present application;
fig. 4 is a schematic logic architecture diagram of an example in which an original program and an applet coexist in a terminal device according to an embodiment of the present application;
FIG. 5 is a flowchart of an example of a native program restart procedure provided in an embodiment of the present application;
FIG. 6 is a flowchart of another embodiment of a method for integrating native programs with applets according to the application;
FIG. 7 is a flowchart of an example of a procedure for initiating an applet via an applet desktop icon according to an embodiment of the application;
FIG. 8 is a flowchart of a method for integrating native programs with applets according to another embodiment of the application;
FIG. 9 is a flowchart of an example of a procedure for initiating a applet by linking information according to an embodiment of the application;
FIG. 10 is a flowchart of a method for integrating native programs with applets according to another embodiment of the application;
FIG. 11 is a flowchart of an example of a procedure for initiating a applet by pushing information according to an embodiment of the application;
FIG. 12 is a schematic diagram of an embodiment of an integrated device of native and applet provided by the present application;
Fig. 13 is a schematic structural diagram of an embodiment of a terminal device provided by 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 the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings and the detailed embodiments. It should be understood that the particular embodiments described herein are meant to be illustrative of the application only and not 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 application by showing examples of the application.
With the development of network technology, mobile phones, tablet computers, electronic computers and other terminal devices are becoming more and more popular. The user can complete various functions through the terminal equipment, for example, the user can complete various functions such as document processing, payment, instant messaging, image processing and the like through the terminal equipment. Specifically, the terminal device may implement various functions through a native program. But the original program needs to be downloaded and installed, so that the storage space of the terminal equipment is occupied, and the development difficulty is high. In order to achieve the functions more simply, reduce the occupied storage space and the difficulty, the applet is generated. The applet is a lightweight application which can be used without downloading and installing, the development difficulty is lower than that of the original program, and the development difficulty can be reduced and the memory space of the equipment can be saved on the basis of realizing the lightweight function. However, the applet is not required to be downloaded and installed, so that development difficulty is reduced, equipment memory space is saved, the applet functions are simpler, complex functions cannot be realized, and the applet cannot be compared with the original 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 pages of the applet by using the native program. When the display page is switched to the page of the applet, and the applet is started again after the original program is closed, the user does not need to enter the page of the original program first and then enter the page of the applet, and the applet can directly enter the page of the applet through the original program, so that the effect of the applet on the aspects of interaction and visual experience of the user is consistent or tends to be consistent with the effect of the original program, and the effect of the applet on the aspects of interaction and visual experience of the user is improved.
The method for integrating the native program and the applet provided by the embodiment of the application mainly relates to terminal equipment, wherein the native program is installed in the terminal equipment. The terminal device can communicate with a background system, an applet platform and the like of the native program through the gateway so as to realize functions of the native program and the applet. Fig. 1 is a schematic diagram of an application scenario of an integration method of a native program and an applet according to 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. Terminal device 12 may include, but is not limited to, a cell phone, tablet, electronic computer, wearable device, etc. Terminal device 12 may interact with the background system 14 of the native program through gateway 13, and terminal device 12 may also interact with applet platform 15 through gateway 13 to obtain applet information. The operator of the native program may manage, maintain, etc. the background system 14 of the native program via 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 applet developed by himself.
The method, the device, the equipment and the medium for integrating the native program and the applet provided by the application are sequentially described below.
The application provides an integration method of a native program and an applet, which can be applied to terminal equipment, namely, the integration method of the native program and the applet can be executed by the terminal equipment. FIG. 2 is a flowchart of an embodiment of a method for integrating native programs and applets according to the present application. As shown in fig. 2, the method for integrating the program and the applet 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 the terminal device.
The terminal device currently displays a page of the native program. The applet list may be evoked by input to the page of the native program. For example, a human-machine interaction control that invokes an applet list is included on a page of the native program, which when clicked triggers the display of the applet list.
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 applet names, applet version names, applet types, applet graphical indicia, applet page thumbnails, applet introduction description, applet identification, applet supported native version, applet owner identification, applet priority, and the like. The applet types may characterize the functional types of the applet, as may include, but are not limited to, payables, games, shopping, and the like. The applet graphic indicia may be implemented in the applet list as an applet graphic indicia or a uniform resource locator (Uniform Resource Locator, URL) address of the applet graphic indicia, the URL address of the applet graphic indicia being triggered and the applet graphic indicia may be displayed. The applet page thumbnail may be implemented in the applet list as an applet page thumbnail or URL address of the applet page thumbnail, the URL address of the applet page thumbnail is triggered, and the applet page thumbnail may be displayed. The applet identification is used to identify the applet, may be an identification such as the number of the applet, and in some examples, may be an encrypted identification, and is not limited in this regard. The applet-affiliated party identification may be an organization number of the applet developer. The applet priority may be, but is not limited to, a priority established by a party to which the native program belongs or a priority established by a party to which the applet platform belongs; in some examples, applet priorities may be represented by numbers, with larger values representing higher priorities. The applet information allows the user to better understand the applet and facilitate the user's selection.
In some embodiments, the applet list may be obtained prior to performing step S201. In some examples, the applet list may be stored in the terminal device, which may directly retrieve the applet list from itself in case it is required to call up the applet list. In other examples, the terminal device may send an applet acquisition request to a background system of the native program to acquire the applet list from the background system of the native program.
The applet list may include applet information for applets arranged in a recommendation level from high to low. The degree of recommendation may be determined based on function usage 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 further, the recommendation degree of the small program is obtained according to the function use habit of the user.
The function usage information may include one or more of the following: the applet version name, the area to which the applet belongs, the applet priority, applet binding resource information, applet attention, payment information, payment authority information, user personal information.
In the case where the function usage information includes one item of information, the level of recommendation degree can be determined based on the one item of information.
In some examples, the function usage information includes an applet version name, which indicates that the closer the applet is to the native program, the higher the applet recommendation. For example, the recommendation of derived versions of applets for native programs is higher than the recommendation of applets for versions that are not related to native programs.
In some examples, the function usage information includes a region to which the applet belongs, and the closer the current geographic location of the terminal device is to the region to which the applet belongs, the higher the recommendation of the applet. For example, the region to which the applet belongs includes the applet of the current geographic location of the terminal device, which is higher than the recommendation of the applet to which the applet belongs does not include the applet of the current geographic location of the terminal device.
In some examples, the function usage information includes an applet priority, the higher the applet recommendation. For example, the recommendation of an applet with an applet priority of 5 is higher than the recommendation of an applet with an applet priority of 2.
In some examples, the function 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, but is not limited thereto. The applet bound resource information is information related to the applet bound resource, e.g., the applet bound resource information may include the applet bound resource, the frequency with which the applet bound resource is used by the user, the number of applet bound resources, etc. The higher the frequency with which applet bound resources are used by a user, the higher the recommendation of the applet; the greater the number of applet bound resources, the greater the recommendation of the applet. For example, the applet bound resource is a payment card or merchant bound to the applet, the recommendation of the applet matching the applet bound payment card or merchant is higher than the recommendation of the applet not matching the applet bound payment card or merchant; the recommendation degree of the applet with high use frequency of the payment card or the merchant bound with the applet is higher than that of the applet with low use frequency of the payment card or the merchant bound with the applet; the recommendation of the applet with a large number of payment cards or merchants bound to the applet is higher than the recommendation of the applet with a small number of payment cards or merchants bound to the applet.
In some examples, the function usage information includes an applet focus, the higher the applet recommendation. For example, the recommendation of an applet having a high applet interest is higher than the recommendation of an applet having a low applet interest.
In some examples, the function usage information includes payment information. The payment information may be obtained from a payment completion page at the time the user completes the payment, and is not limited herein. The payment information is information related to user payment, and may include a payment card or a payment merchant. For example, if the payment information includes a payment card, the recommendation of an applet that matches the payment card is higher than the recommendation of an applet that does not match the payment card; if the payment information includes a payment merchant, the recommendation of the applet matching the payment merchant is higher than the recommendation of the applet not matching the payment merchant.
In some examples, the function usage information includes payment affiliation information. The payment affiliated institution information may be acquired from a payment details page when the user views the payment details, which is not limited herein. The payment affiliated institution information may characterize the institution affiliated with the payment. For example, the recommendation of an applet matching the payment-affiliated institution information is higher than the recommendation of an applet not matching the payment-affiliated institution information.
In some examples, the function usage information includes user personal information. The recommendation degree of the small program suitable for the personal information of the user can be obtained according to the recommendation degree of the matching of the general user characteristics in the big data and the small program. The recommendation degree of the applet matching with the user personal information is higher than that of the applet not matching with the user personal information. For example, the user personal information includes an age, and the age in the user personal information is 26 years old, and the recommendation degree of the applet matching the age range of 20 to 30 years old is higher than the recommendation degree of the applet matching the age range of 40 to 50 years old.
In the case where the function usage information includes two or more pieces of information, the level of recommendation degree may be determined based on the two or more pieces of information and weights corresponding to the pieces 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 class of applets includes applets that are applet versions of native programs. The applet version of the native program refers to a specific version derived based on the native program, and the applet of the applet version of the native program is a specific version derived based on the native program, for example, the first class applet may include a simple applet of the native program, an applet that retains and strengthens part of the functionality for a specific crowd based on the native program, and the like, but is not limited thereto. Compared with the scheme of realizing the derivative version through the original program, the embodiment of the application realizes the derivative version of the original program through the applet, a user does not need to download the original program of the derivative version, and can switch the corresponding applet of the derivative version according to the own requirement, so that under the condition that the functions of a plurality of versions can be realized, the storage space occupied in the terminal equipment is reduced, and the development difficulty of the applet of the derivative version of the original program can be reduced. In the embodiment of the application, the effect of the small program version of the original program in the aspects of interaction with the user, visual experience and the like can be consistent or tend to be consistent with the effect of the original program, so that the user experience is further improved.
The second class of applets includes applets that are different from the native program's resident party. The native program may also integrate different applets to the party. The terminal device receives an operation input from a user, and can call an applet, which belongs to a different party from the original program, in the original program. The function of the applet, which is different from the native program, may be similar to or different from the native program, and is not limited to this. For example, the native program is an application of the paymate, and the applet list of the native program may include applet information for applets of multiple banks. For another example, the native program is an application of the third paymate, and 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 with the party different from the original program into the applet list, the functions which can be realized by the original program can be further enriched, so that the terminal equipment functions can be realized more flexibly.
For example, the native program is program A1, and the applet list that the native program can provide may include applet information for the simple version applet B1 of program A1, applet information for the elderly version applet B2 of program A1, applet information for applet C1 of Bank1, applet information for applet C2 of Bank2, applet information for the journey code query applet D1 and applet information for merchant shopping applet D2.
The switch select input is used to select one of the applets in the applet list. The target applet inputs the applet selected in the applet list for the switch selection. The switch selection input may be a single click input, a multiple click input, a slide input, or the like, and is not limited thereto.
In step S202, long-term static information of the target applet is acquired and stored locally.
The long-term static information is information that is relatively difficult to change for the applet to take effect over a long period of time, and may include, for example, an applet identification, applet configuration information, applet fixed presentation information, and the like, without limitation. The terminal device may request long-term static information of the target applet from the applet platform.
The long-term static information is stored locally until the next switch selection input selects a different target applet or selects a native program. And after the current switching selection input selects the target applet and under the condition that the next switching selection input does not occur, the long-term static information is always stored locally. And when the next switching selection input is performed after the current switching selection input selects the target applet, if the target applet selected by the next switching selection input is different from the target applet selected by the current switching selection input, deleting the long-term static information of the target applet selected by the current switching selection input locally, and storing the long-term static information of the target applet selected by the next switching selection input locally.
In step S203, short-term dynamic information of the target applet is acquired, the target applet is operated 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. Short-term dynamic information is information that is relatively easy to change in real-time of an applet, for example, the short-term dynamic information may include a policy list, URL addresses of dynamically changing pages, etc., and is not limited herein. The terminal device may request short-term dynamic information of the target applet from the applet platform.
The applet container may be considered the framework of the 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 applet is acquired, the page of the target applet can be obtained together according to the long-term static information and the short-term dynamic information of the target applet, so that the display page of the native program can be switched from the page of the native program to the page of the target applet. Specifically, the page of the native program may be switched to the first page of the target applet.
In step S204, in response to the applet starting input, the main task and the root page of the applet are set as applet containers by calling the applet to read long-term static information of the object applet, so that the terminal device displays the page of the object applet through the applet.
The applet starting input is an input operation for starting the applet, the terminal device receives the applet starting input, invokes the native program, reads the long-term static message of the target applet stored in step S202 through the native program, and sets the main task and the root page of the native program as an applet container, so that the main task is the running target applet after the native program is triggered to be started, the root page, i.e. the first page loaded, is the page of the target applet, and after the native program is invoked to be 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 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 determining whether the applet container is in an open state, it can be determined whether the display page of the native program after the last switch is the applet page or the native program page. If the applet container is in an open state, determining that the display page of the native program after the last switching is the page of the applet, and displaying the applet directly through the native program; if the applet container is not in an open state, it may be determined that the display page of the native program after the last switch is a 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, in order to further achieve the interaction and display effect of the native program-like 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 the address of the pre-page of the target applet. The front page of the applet is a page that is displayed prior to the page of the applet during the applet start-up process, e.g., the front page may include an open page and/or an advertisement page, etc. In some examples, the pre-page may be displayed according to an address of the pre-page before the page is displayed to be switched to the page of the target applet, and the pre-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 executing the step S204, the terminal device may display the front page through the native program according to the address of the front page to further achieve the display effect of the applet 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 invokes program information of the native program from the updated applet list provided by the native program, switch the display page of the native program from the page of the target applet to the page of the native program, and 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 mark, a program page thumbnail, a program introduction description, a program identification, a program affiliated party identification, and the like, which are not limited herein. The applet list may be updated during a switch between a page of the native program and a page of the applet, or during a switch between a page of the applet and a page of the applet, the program information of the native program or applet after the switch is removed from the applet list, and the program information of the native program or applet before the switch is added to the applet list.
In some examples, where the display page of the native program is the page of the target applet, the page of the native program may be asynchronously loaded to enable the display of the page of the native program to be quickly completed if the switch is made from the page of the target applet to the page of the native program.
In the embodiment of the application, a user can perform switching selection input on the page of the original program in the terminal equipment, the terminal equipment responds to the switching selection input to determine the target applet needing to be switched, the long-term static information of the target applet is locally stored, the short-term dynamic information of the target applet is acquired, the target applet is operated in the 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 into the page of the target applet, and the page of the target applet is displayed by the original program. Under the condition of restarting the applet in response to the applet starting input, the terminal equipment calls the original program to read the long-term static information, the main task and the root page of the original program are set as applet containers, and the pages of the target applet are displayed through the original program, so that the effect of the applet in the aspects of interaction with a user, visual experience and the like can be consistent or tend to be consistent with the original program, and the effect of the applet in the aspects of interaction with the user, visual experience and the like is improved. In addition, when the applet list provided by the native program comprises applet information of a plurality of applets, by adopting the method of the embodiment of the application, any one of the applet list can be switched and displayed by calling the native program, so that the effect of coexistence of a plurality of applet native programs in one native program is realized.
In order to more fully describe the method for integrating the native program and the applet in the scheme, the procedure of switching from the page of the native program to the page of the applet when the native program is opened for the first time is described below. FIG. 3 is a flowchart illustrating an example of a page flow for switching from a native program to a applet according to an embodiment of the present application. As shown in fig. 3, the process of switching the page of the native program to the page of the applet may include steps S301 to S317.
In step S301, the terminal device receives a start-up input to 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 the switch selection input.
In step S303, the terminal device acquires and locally saves long-term static information of the target applet.
In step S304, if the user does not pay attention to the target applet, the terminal device adds attention to the target applet.
In step S305, the terminal device acquires the address of the front page of the target applet.
In step S306, the terminal device determines whether the applet container is in an open state. If the applet container is in the open state, jumping to step S308; if the applet container is not in the open state, the process goes 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 login target applet is successful. If the login is successful, jumping to step S311; if the login fails, the process goes to step S309, or prompts the user to log in manually.
In step S311, the terminal device displays the page under loading.
In step S312, the terminal device acquires short-term dynamic information of the object applet.
In step S313, the terminal device determines whether the acquisition of the short-term dynamic information is successful. If the acquisition is successful, jumping to step S315; if the acquisition fails, the process goes to step S314.
In step S314, the terminal device sends out a prompt message to prompt that the short-term dynamic information acquisition fails.
In step S315, the terminal device caches 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 object applet through the native program.
Some of the steps S301 to S317 may be omitted, or the order between the steps may be changed appropriately according to the actual application scenario and operation condition, which is not limited herein.
In the above embodiment, the applet may use general functions of the native program during the operation of the terminal device. The general-purpose functions are functions that are commonly required by the native program and the applet, and may include, for example, 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 are not limited thereto. The applet container may be provided with an application programming interface (Application Programming Interface, API). The API is used for the applet in the applet container to call the generic functions of the native program. That is, the applet may call the generic functions of the native program through the API of the applet container. Therefore, part of the capability of the original program is opened to the applet, so that the difference between the applet and the original program in the function aspect is reduced on the basis of not increasing the development difficulty of the applet, the effect of the applet in the function aspect is improved, and the functions of the applet are more abundant. In the case where the target applet runs in the applet container and needs to execute a general function, the general function of the native program can be called through the API, enriching the function of the target applet.
For example, fig. 4 is a schematic logic architecture diagram of an example in which an original program and an applet coexist in a terminal device according to an embodiment of the present application. As shown in fig. 4, a native program, applet 1, applet 2 and applet 3 can be run in the terminal device. The terminal device has an applet container having an API and a User Interface (UI) component, and general functions of the native program may include an encryption and decryption function, a network request function, a local access function, a User data management function, a hardware capability use function, and other functions. Applet 1, applet 2 and applet 3 can call the general functions of the native program through the API during the running of the applet container.
The manner of applet initiation triggered by applet initiation input is also different in different scenarios, and the method of integrating the native program and the applet will be described below by taking different scenarios as examples.
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 display page of the last opened 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 can call the native program to read the long-term static information of the target applet stored under the condition that the last opened native program is switched to the page of the target applet, and set the main task and the root page of the native program as applet containers, so that the display page of the native program is the first page of the target applet.
In order to more fully describe the method for integrating the native program and the applet in the scheme, 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 according to an embodiment of the present application. As shown in fig. 5, the procedure of restarting the native program may include steps S401 to S415.
In step S401, the terminal device starts a 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 last startup display page of the native program has been switched to the page of the applet. If the original 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 up last time and has been switched to the page of the applet, the process goes to step S405.
Whether the page of the applet switched by the last start of the original program is the page of the target applet can be determined by judging whether the applet container is in an open state or not and whether the page of the applet switched by the last start of the original program is switched to the page of the applet or not can be determined by locally stored long-term static information.
In step S404, the terminal device displays a top page of the native program.
In step S405, the terminal device starts a target applet.
In step S406, the terminal device asynchronously loads the home page of the native program so as to be able to switch quickly when it is necessary to switch back to the page of the native program.
In step S407, the terminal device loads a front page of the target applet.
In step S408, the terminal device determines whether the user login target applet is successful. If the login is successful, jumping to step S409; if the login fails, the process goes to step S405, or the user is prompted to log in manually.
In step S409, the terminal device displays the page under loading.
In step S410, the terminal device acquires short-term dynamic information of the object applet.
In step S411, the terminal device determines whether the acquisition of the short-term dynamic information is successful. If the acquisition is successful, jumping to step S413; if the acquisition fails, the process goes to step S412.
In step S412, the terminal device sends out a prompt message to prompt that the short-term dynamic information acquisition fails.
In step S413, the terminal device caches 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 home page of the target applet through the native program. Specifically, the terminal device may display the first page of the target applet through the native program by setting the main task and the root page of the native program as applet containers.
Some of the steps S401 to S415 may be omitted, or the order between the steps may be changed appropriately according to the actual application scenario and operation condition, which is not limited herein.
In some embodiments, the applet initiation input includes an initiation input to a desktop icon of the applet displayed by the terminal device. The user can create a desktop icon of the applet on the terminal device, and quickly initiate the original program to enter the applet through the desktop icon of the applet. FIG. 6 is a flowchart of another embodiment of a method for integrating native programs with applets according to the present application. The difference between fig. 6 and fig. 2 is that step S204 in fig. 2 may be specifically subdivided into steps S2041a to S2044a in fig. 6, and the method for integrating the native program and the applet shown in fig. 6 may further include step S205 and step S206.
In step S2041a, in response to a start input of a desktop icon of an applet displayed on the terminal device, a jump is made to the relay page.
The launch input to the desktop icon of the applet is used to launch the applet corresponding to the desktop icon. The initiation input may specifically include a click input, a long press input, etc. to the desktop icon, which is not limited herein. When the terminal equipment receives the starting input of the desktop icon of the applet, 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 if the display page of the native program is switched to the page of the applet. The terminal device may jump to the icon generation relay page in response to a desktop icon generation input to the page of the applet, trigger generation and display of the desktop icon of the applet at the terminal device. 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 case where 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 previously switched to the page of the applet can be determined by determining whether the applet container is in an open state.
In step S2043a, in the case where the applet container is in the open state, the jump from the intermediate page to the applet is made, long-term static information of the target applet is read, and the main task and the root page of the applet are set as applet containers.
The applet container is in an open state, indicating that the display page of the native program has been previously switched to the applet page, from which it can be jumped to the native program to invoke the native program to read long-term static information of the target applet that was previously stored locally. The main task and the root page of the native program are set as applet containers in which the target applet is located, so that the terminal device has the capability of displaying the pages of the target applet.
In step S2044a, if the applet corresponding to the desktop icon is the target applet, a page of the target applet is displayed.
And under the condition that the applet corresponding to the desktop icon is the target applet, the terminal equipment can display the page of the target applet through the native program. From the user experience, after the user starts and inputs the desktop icon of the applet, the user opens a display page of the native program, where the display page is a page of the target applet, and specifically, the display page is a top 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 identification of the applet corresponding to the desktop icon is consistent with the applet identification 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, the page of the target applet is jumped 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, and according to the long-term static information and the short-term dynamic information of the applet corresponding to the desktop icon, the applet corresponding to the desktop icon is operated in the applet container, and the main task and the root page of the native program are set as the applet container, and the page of the applet corresponding to the desktop icon may be displayed by the native program, so as to jump from the page of the target applet to the page of the applet corresponding to the desktop icon. The page of the target applet can be used as a transit page which is not explicitly displayed.
In other examples, the terminal device may display the page of the target applet through the native program, then receive a switching input of the user, and obtain long-term static information and short-term dynamic information of the applet corresponding to the desktop icon in response to the switching input, so that the applet corresponding to the desktop icon operates in the applet container, and display the page of the applet corresponding to the desktop icon through the native program, so as to jump from the page of the target applet to the page of the applet corresponding to the desktop icon.
In step S206, when the applet container is not in the open state, the applet corresponding to the desktop icon is loaded from the page skip.
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 native program and the applet in the scheme, the procedure of starting the applet through the desktop icon of the applet is described below. FIG. 7 is a flowchart of an example of a procedure for launching an applet via a desktop icon of the applet, according to an embodiment of the application. As shown in fig. 7, the process of launching the applet through the applet desktop icon may include steps S501 to S516.
In step S501, the terminal device jumps to the relay page in response to a start input to the desktop icon of the applet.
In step S502, the terminal device determines whether the last startup display page of the native program has been switched to the page of the applet. If the original 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 up last time and has been switched to the page of the applet, the process goes to step S504.
Whether the page of the applet switched by the original program is the page of the applet corresponding to the desktop icon can be determined by judging whether the applet container is in an open state or not and whether the page displayed by the original program is switched to the page of the applet or not by locally storing long-term static information.
In step S503, the terminal device loads and runs the applet corresponding to the desktop icon according to the normal applet loading mode.
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, the process goes to step 504, or the user is prompted to log in manually.
In step S506, the terminal device displays the page under loading.
In step S507, the terminal device determines whether the applet corresponding to the desktop icon is a target applet according to the locally stored long-term static information; if the applet corresponding to the desktop icon is the target applet, jumping to step S508; if the applet corresponding to the desktop icon is not the target applet, the process goes to step S510.
By default in this example, if the display page before the native program is switched to the page of the applet, the page of the applet to which the native program was switched before 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 acquisition of the short-term dynamic information is successful. If the acquisition is successful, jumping to step S513; if the acquisition fails, the process goes to step S512.
In step S510, the terminal device acquires 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, the process goes to step S512.
In step S512, the terminal device sends out a prompt message, and the acquisition of the prompt message fails.
In step S513, the terminal device caches 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 first page of the applet corresponding to the desktop icon through the native program. Specifically, the terminal device may display the first page of the applet corresponding to the desktop icon through the native program by setting the main task and the root page of the native program as the applet container.
Some of the steps S501 to S516 may be omitted, or the order between the steps may be changed appropriately according to the actual application scenario and operation condition, which is not limited herein.
In some embodiments, the terminal device may also search for an applet indicated by the search input among applets integrated with the native program in response to the search input to the display page of the native program. It can be determined whether the current display page of the native program has been switched to the page of the applet. If the page is not switched to the page of the applet, loading the applet and operating according to a common applet loading mode. If the page is switched to the small program, starting the small program indicated by the search input, acquiring long-term static information and short-term dynamic information of the small program indicated by the search input, running the small program indicated by the search input in a small program container according to the long-term static information and the short-term dynamic information, and setting the main task of the original 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 original program. The process of loading the applet indicated by the search input and the process of displaying the page of the applet indicated by the search input may refer to steps S408 to S415 in the above embodiments, and will not be described herein.
In some embodiments, the applet initiation input may include an initiation input to the linking information. The user can quickly initiate the original program to enter the applet through the received link information. FIG. 8 is a flowchart of a method for integrating native programs with applets according to another embodiment of the application. The difference between fig. 8 and fig. 2 is that step S204 in fig. 2 may be specifically subdivided into steps S2041b to S2043b in fig. 8, and the method for integrating the native program and the applet shown in fig. 8 may further include step S207 and step S208.
In step S2041b, in response to the start-up input of the link information, the native program is called up, and it is determined whether the applet container is in an open state.
The initiation input to the link information is used to initiate the applet corresponding to the link information. Further, the initiation input to the link information may be used to call up a specified page of the applet indicated by the link information. The linking information may include an external schema link, etc., and is not limited herein. 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, etc., which is not limited herein. The initiation input may specifically include a click input, a long press input, etc. of the link information, which is not limited herein. When the terminal equipment receives the starting input of the link information, the original program is called to judge whether the applet container is in an open state or not. Whether the display page of the native program has been previously switched to the page of the applet can be determined by determining whether the applet container is in an open state.
In step S2042b, long-term static information of the target applet is read with the applet container in an open state, and the main task and root page of the native program are set as applet containers.
The applet container is in an open state, indicating that the native program has been previously switched to the applet's page for display, and the native program may be invoked to read long-term static information of the target applet that was previously stored locally. The main task and the root page of the native program are set as applet containers in which the target applet is located, so that the terminal device has the capability of displaying the pages 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 according to the link information.
In the case where the applet indicated by the link information is the target applet, the terminal device may display a page of the target applet through the native program. Further, since the link information may specifically indicate a designated page in the target applet, the designated page indicated by the link information in the target applet may be opened and displayed by the native program according to the connection information. From the user experience, after the link information is started and input, the user opens a display page of the native program, 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 identification of the applet indicated by the link information is consistent with the applet identification 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 jumped 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 is run 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 are 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. The page of the target applet can be used as a transit page which is not explicitly displayed.
In other examples, the terminal device may display the page of the target applet through the native program, then receive a switching input from the user, and in response to the switching input, obtain long-term static information and short-term dynamic information of the applet indicated by the link information, cause the applet indicated by the link information to run in the applet container, and display the 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 the case where the applet container is not in an open state, the page of the applet indicated by the link information is opened through the browser.
The applet container is not 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 specified page of the applet indicated by the link information can be opened using the browser.
In order to more fully describe the integration method of the native program and the applet in the scheme, the process of starting the applet through the link information is described below. Fig. 9 is a flowchart of an example of a procedure for initiating a applet by link information according to an embodiment of the present application. As shown in fig. 9, the flow of starting the applet by the link information may include steps S601 to S606.
In step S601, the terminal device starts a native program in response to a start-up input of link information.
In step S602, the terminal device loads the native program execution logic.
In step S603, the terminal device determines whether the last startup display page of the native program has been switched to the page of the applet. If the original 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 up last time and has been switched to the page of the applet, the process goes to step S605.
Whether the page of the applet switched by the original program is the page of the applet designated by the link information can be determined by judging whether the applet container is in an open state or not and whether the page displayed by the original program is switched to the page of the applet or not by locally storing long-term static information.
In step S604, the terminal device opens a 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 opens and displays the specified page of the applet indicated by the link information in synchronization.
In some examples, the starting of the applet indicated by the link information in step S605 and the opening and display of the designated page of the applet indicated by the link information can be seen from the relevant contents in steps S504 to S516 in the above-described embodiments. If the applet indicated by the link information is the target applet, the specified page of the applet indicated by the link information can be directly displayed by the native program according to the link information. If the applet indicated by the link information is not the target applet, the applet may jump from the page of the target applet to the specified page of the applet indicated by the link information by the native program.
In step S606, the terminal device asynchronously loads the related information of the native program so as to be quickly switchable when a switch from the page of the applet to the page of the native program is required.
The execution order between step S606 and step S605 is not limited, and the two steps may be performed asynchronously.
Some of the steps S601 to S606 may be omitted, or the order between the steps may be changed appropriately according to the actual application scenario and operation condition, which is not limited herein.
In some embodiments, the target applet initiation input includes an initiation input to push information. The user can quickly initiate the original program to enter the applet through the received push information. FIG. 10 is a flowchart of a method for integrating native programs with applets according to another embodiment of the application. The difference between fig. 10 and fig. 2 is that step S204 in fig. 2 may be specifically subdivided into steps S2041c to S2044c in fig. 10, and the method for integrating the native program and the applet shown in fig. 10 may further include steps S209 to S211.
In step S2041c, in response to the start-up input of the push information, it is determined whether the native program is in the background running state.
The initiation input to the push information is used to initiate an applet indicated by the push information. Further, the initiation input to the push information may be used to call up a specified page of the applet indicated by the push information. The push information may include, but is not limited to, push information in a notification bar, push information in a pop-up window, push information on a lock screen interface, and the like. The initiation input may include, but is not limited to, a click input, a long press input, etc. of the push information. When the terminal device receives a start-up input of the link information, the running state of the native program may be determined. The operating states may include a background operating state and a front end operating state.
In step S2042c, when the native program is in the background running state, the native program is called, and it is determined whether the applet container is in the open state.
The native program is in a background running state, namely the native program is not currently displayed in the terminal equipment, the native program needs to be called up, and whether the applet container is in an open state is judged. Whether the display page of the native program has been switched to the page of the applet or not is judged by judging whether the applet container is in an open state or not.
In step S2043c, long-term static information of the target applet is read with the applet container in an open state, and the main task and root page of the native program are set as applet containers.
The applet container is in an open state, the applet container indicates that the display page of the native program has been switched to the applet page before, and the native program can be called to read long-term static information of the target applet which is stored locally before. The main task and the root page of the native program are set as applet containers in which the target applet is located, so that the terminal device has the capability of displaying the pages 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 a page of the target applet through the native program. Moreover, since the push information may specifically indicate a specified page in the target applet, the specified 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 user experience, after the push information is started and input, the user opens a display page of the native program, wherein the display page is a page of the target applet, and specifically, the display page is a designated page indicated by the push information in the target applet.
In some examples, the determination of whether the applet indicated by the push information is a target applet may be made by whether the applet identification of the applet indicated by the push information is consistent with the applet identification 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 jumped 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, long-term static information and short-term dynamic information of the applet indicated by the push information may be obtained, the applet indicated by the push information is 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. The page of the target applet can be used as a transit page which is not explicitly displayed.
In other examples, the terminal device may display the page of the target applet through the native program, then receive a switching input of the user, and in response to the switching input, obtain long-term static information and short-term dynamic information of the applet indicated by the push information, so that the applet indicated by the link information is operated in the applet container, and display the designated page of the applet indicated by the push information through the native program, so as to jump from the page of the target applet to the designated page of the applet indicated by the push information.
In step S210, when the native program is in the front-end running state, the procedure jumps to the page of the applet indicated by the push information.
The original program is in a front-end running state, namely the original program is currently displayed on the terminal equipment, the original program is not required to be called up any more, and the original program can be directly utilized to jump to a specified page of the applet indicated by the push information.
In step S211, in a case where the applet container is not in an 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, the browser may be utilized to open a designated page of the applet indicated by the push information.
In order to more fully describe the integration method of the native program and the applet in the scheme, the procedure of starting the applet by pushing information is described below. Fig. 11 is a flowchart of an example of a procedure of initiating a applet by pushing information according to an embodiment of the present application. As shown in fig. 11, the procedure of starting the applet by pushing information may include steps S701 to S707.
In step S701, the terminal device determines whether the native program is in a background running state in response to a start-up input of 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, the process goes 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 last startup display page of the native program has been switched to the page of the applet. If the original program is started last time and is not switched to the page of the applet, jumping to step S705; if the original program has been started up last time and has been switched to the page of the applet, the process goes 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 designated page of the applet indicated by the push information.
In some examples, the start of the applet indicated by the push information in step S707, and the opening and display of the designated page of the applet indicated by the push information can be seen from the relevant contents in steps S504 to S516 in the above-described embodiments. If the applet indicated by the push information is the target applet, the specified page of the applet indicated by the push information can be directly displayed by the native program according to the push information. If the applet indicated by the push information is not the target applet, the applet may jump from the page of the target applet to the specified page of the applet indicated by the push information by the native program.
Some of the steps S701 to S707 may be omitted, or the order between the steps may be changed appropriately, depending on the actual application scenario and operation condition, which is not limited herein.
The application also provides a device for integrating the native program and the small program, and the device for integrating the native program and the small program can be arranged in the terminal equipment. FIG. 12 is a schematic diagram of an embodiment of an integrated device for native and applet applications according to the present application. As shown in fig. 12, the native program and applet integration apparatus 800 may include a selection module 801, an acquisition module 802, and a control module 803.
The selection module 801 is operable to select applet information characterizing a target applet in an applet list provided by a 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 acquisition module 802 is also used to acquire short-term dynamic information of the target applet.
The control module 803 may be configured to cause the target applet to run in the applet container of the terminal device and switch the display page from the page of the native program to the page of the target applet based on the long-term static information and the short-term dynamic information of the target applet.
The control module 803 is further configured to, in response to the applet start input, invoke the native program to read long-term static information of the target applet, and set a main task and a root page of the native program as applet containers, so that the terminal device displays the page of the target applet through the native program.
In the embodiment of the application, a user can perform switching selection input on a page of an original program in terminal equipment, the terminal equipment 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 acquired, 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 original program is switched into the page of the target applet, and the page of the target applet is displayed by the original program. Under the condition of restarting the applet in response to the applet starting input, the terminal equipment calls the original program to read the long-term static information, the main task and the root page of the original program are set as applet containers, and the pages of the target applet are displayed through the original program, so that the effect of the applet in the aspects of interaction with a user, visual experience and the like can be consistent or tend to be consistent with the original program, and the effect of the applet in the aspects of interaction with the user, visual experience and the like is improved. In addition, when the applet list provided by the native program comprises applet information of a plurality of applets, by adopting the method of the embodiment of the application, any one of the applet list can be switched and displayed by calling the native program, so that the effect of coexistence of a plurality of applet native programs in one native program is realized.
In some embodiments, the control module 803 may also be used to determine if 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 with the applet container in an open state.
In some embodiments, the obtaining module 802 may be further configured to obtain an address of a leading page of the target applet, so that the terminal device displays the leading 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 applet in the applet container to call the generic functions of the native program.
The control module 803 may also be used to call generic functions of the native program through an API in the event that the target applet is running in the applet container and needs to perform the generic functions.
In some embodiments, the applet initiation input comprises an initiation input to an original program in the terminal device.
In some embodiments, the applet initiation input includes an initiation input to a desktop icon of the applet displayed by the terminal device.
The control module 803 may be configured to: responding to the starting input of the desktop icons of the applets displayed by the terminal equipment, and jumping to a transfer page; judging whether the applet container is in an open state or not; under the condition that the applet container is in an open state, jumping from a middle page to a native program, reading long-term static information of a target applet, and setting a main task and a root page of the native program as the applet container; and if the applet corresponding to the desktop icon is the target applet, controlling the terminal equipment to display the page of the target applet.
In some examples, the control module 803 may be further configured to skip 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 to the linking information.
The control module 803 may be configured to: responding to the starting input of the link information, calling the original program, and judging whether the applet container is in an open state; reading long-term static information of a target applet and setting a main task and a root page of a native program as an applet container under the condition that the applet container is in an open state; and if the applet indicated by the link information is the target applet, opening a page indicated by the link information in the target applet 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 includes an initiation input to push information.
The control module 803 may be configured to: responding to the starting input of the push information, judging whether the original program is in a background running state or not; under the condition that the original program is in a background running state, the original program is called, and whether the applet container is in an open state or not is judged; reading long-term static information of a target applet and setting a main task and a root page of a native program as an applet container under the condition that the applet container is in an open state; if the applet indicated by the pushing information is the target applet, opening a page indicated by the pushing information in the target applet according to the pushing 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 push information if the applet indicated by the push information is not the target applet.
In some examples, the control module 803 may be further configured to jump to a page of the applet indicated by the push information if the native program is in a front-end run state.
In some embodiments, the acquisition module 802 may also be used to acquire an applet list.
The applet list includes applet information for ranking applets from high to low according to recommendation.
The recommendation degree is determined according to function use information of the user, wherein the function use information comprises one or more than two of the following items: the applet version type, the region to which the applet belongs, the applet priority, applet binding resource information, applet attention, payment information, payment authority information, 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 class of applets includes applets of a small programmed version of the native program and the second class of applets includes applets of a different party than the party to which the native program belongs.
The application also provides a terminal device. Fig. 13 is a schematic structural diagram of an embodiment of a terminal device provided by 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 as one or more integrated circuits that implement embodiments of the present application.
Memory 901 may include read-only memory (ROM), random-access memory (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 and applet in embodiments in accordance with 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 the integration of the native program and the applet in the above-described embodiment.
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 to each other via a bus 904, and communicate with each other.
The communication interface 903 is mainly used to implement communication between each module, device, unit, and/or apparatus in the embodiment of the present application. Input devices and/or output devices may also be accessed through communication interface 903.
Bus 904 includes hardware, software, or both, coupling the components of terminal device 900 to one another. By way of example, and not limitation, the bus 904 may include an accelerated graphics port (ACCELERATED GRAPHICS Port, AGP) or other graphics bus, an enhanced industry Standard architecture (Enhanced Industry Standard Architecture, EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry Standard architecture (Industry Standard Architecture, ISA) bus, an Infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a micro channel architecture (Micro Channel Architecture, MCA) bus, a peripheral component interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, a PCI-express (PCI-E) bus, a serial advanced technology attachment (SERIAL ADVANCED Technology Attachment, SATA) bus, a video electronics standards Association local (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 embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect.
The fourth aspect of the present application further provides a computer readable storage medium, on which computer program instructions are stored, where the computer program instructions, when executed by a processor, can implement the method for integrating a native program and an applet in the above embodiment, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted herein. The computer readable storage medium may include a non-transitory computer readable storage medium, such as read-only memory (ROM), random access memory (Random Access Memory RAM), magnetic disk or optical disk, and the like, which are not limited herein.
The application may also provide a computer program product in which instructions, when executed by a processor of a terminal device, cause the terminal device to perform the method of integrating a raw program with an applet in the above embodiments. The details of the foregoing embodiments may be referred to in the description of the foregoing embodiments, and are not described herein.
It should be understood that, in the present specification, each embodiment is described in an incremental manner, and the same or similar parts between the embodiments are all referred to each other, and each embodiment is mainly described in a different point from other embodiments. For an apparatus embodiment, a device embodiment, a computer readable storage medium embodiment, a computer program product embodiment, the relevant points may be found in the description of method embodiments. The application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art will appreciate that various alterations, modifications, and additions may be made, or the order of steps may be altered, after appreciating the spirit of the present application. Also, a detailed description of known method techniques is omitted here 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 being, 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 which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the above-described embodiments are exemplary and not limiting. The different technical features presented in the different embodiments may be combined to advantage. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in view of the drawings, the description, and the claims. In the claims, the term "comprising" does not exclude other means or steps; the word "a" does not exclude a plurality; the terms "first," "second," and the like, are used for designating a name and not for indicating any particular order. Any reference signs in the claims shall not be construed as limiting the scope. The functions of the various elements presented in the claims may be implemented by means of a single hardware or software module. The presence of certain features in different dependent claims does not imply that these features cannot be combined to advantage.
Claims (17)
1. A method for integrating a native program with an applet, comprising:
In response to a switching selection input to a page of an original program in a terminal device, selecting applet information characterizing a target applet from an applet list provided by the original program;
acquiring long-term static information of the target applet and locally storing the long-term static information;
Acquiring short-term dynamic information of the target applet, operating the target applet in an applet container of the terminal equipment according to long-term static information and short-term dynamic information of the target applet, and switching a display page from a page of a native program to a page of the target applet;
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 said calling said native program to read long-term static information of said target applet:
Judging whether the applet container is in an open state;
The reading of the long-term static information of the target applet includes:
and if the applet container is in an open state, reading long-term static information of the target applet.
3. The method of claim 1, further comprising, prior to said obtaining short-term dynamic information of said target applet:
and acquiring the address of the front page of the target applet so that the terminal equipment displays the front page of the target applet before displaying the page of the target applet.
4. The method of claim 1, wherein the applet container is provided with an application programming interface API for an applet in the applet container to call general functions of the native program,
The method further comprises the steps of:
In the case where the target applet runs in the applet container and needs to execute a general function, the general function of the native program is called through the API.
5. The method of claim 1, wherein the applet initiation input comprises an initiation input to the native program in the terminal device.
6. The method of claim 1, wherein the applet initiation input comprises an initiation input to 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, so that the terminal equipment displays the page of the target applet, comprising:
responding to the starting input of the desktop icon of the applet displayed by the terminal equipment, and jumping to a transfer page;
Judging whether the applet container is in an open state or not;
Under the condition that the applet container is in an open state, jumping to the original program from the transfer page, reading long-term static information of the target applet, and setting a main task and a root page of the original program as the applet container;
and if the applet corresponding to the desktop icon is the target applet, displaying a page of the target applet.
7. The method as recited in claim 6, further comprising:
and if the applet corresponding to the desktop icon is not the target applet, jumping from the page of the target applet to the page of the applet corresponding to the desktop icon.
8. The method of claim 1, wherein the applet initiation input comprises an initiation input for linking information,
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, so that the terminal equipment displays the page of the target applet, comprising:
Responding to the starting input of the link information, calling the original program, and judging whether the applet container is in an open state or not;
reading 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 under the condition that the applet container is in an open state;
And if the applet indicated by the link information is the target applet, opening a page indicated by the link information in the target applet according to the link information.
9. The method as recited in claim 8, further comprising:
and if the applet indicated by the link information is not the target applet, jumping from the page of the target applet to the page of the applet indicated by the link information.
10. The method of claim 1, wherein the targeted applet initiation input comprises an initiation input for push information,
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, so that the terminal equipment displays the page of the target applet, comprising:
Responding to the starting input of the push information, and judging whether the original program is in a background running state or not;
under the condition that the native program is in the background running state, calling the native program, and judging whether the applet container is in an open state or not;
reading 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 under the condition that the applet container is in an open state;
and if the applet indicated by the pushing information is the target applet, opening a page indicated by the pushing information in the target applet according to the pushing information.
11. The method as recited in claim 10, further comprising:
And if the applet indicated by the pushing information is not the target applet, jumping from the page of the target applet to the page of the applet indicated by the pushing information.
12. The method as recited in 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 applet indicated by the push information.
13. The method of claim 1, further comprising, prior to selecting the target applet from the applet list provided by the native program:
Obtaining the applet list, wherein the applet list comprises applet information of applets arranged from high to low according to recommendation degree,
The recommendation degree is determined according to function use information of a user, wherein the function use information comprises one or more of the following items: the applet version type, the region to which the applet belongs, the applet priority, applet binding resource information, applet attention, payment information, payment authority information, user personal information.
14. The method of claim 1, wherein the applet list comprises applet information for a first type of applet and/or applet information for a second type of applet,
The first class of applets includes applets of an applet version of the native program, and the second class of applets includes applets of a different party than the native program.
15. An integrated device for native and applet programming, comprising:
A selection module, configured to select applet information characterizing a target applet from an applet list provided by a native program in response to a switching selection input to a page of the native program in a terminal device;
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 applet to run in an applet container of the terminal equipment according to the long-term static information and the short-term dynamic information of the target applet, and switching a display page from a page of a native program to a page of the target applet;
The control module is also used for responding to the applet starting input, calling the original program to read the long-term static information of the target applet, setting the main task and the root page of the original program as the applet container, and enabling the terminal equipment to display the page of the target applet through the original 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 native and applet according to 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 the method of integrating a native program with an applet according to any one of claims 1 to 14.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210293530.4A CN114691236B (en) | 2022-03-24 | 2022-03-24 | Method, device, equipment and medium for integrating native program and applet |
| PCT/CN2022/119712 WO2023178952A1 (en) | 2022-03-24 | 2022-09-19 | Method and apparatus for integrating native program with applet, and device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210293530.4A CN114691236B (en) | 2022-03-24 | 2022-03-24 | Method, device, equipment and medium for integrating native program and applet |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114691236A CN114691236A (en) | 2022-07-01 |
| CN114691236B true CN114691236B (en) | 2024-04-19 |
Family
ID=82140089
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210293530.4A Active CN114691236B (en) | 2022-03-24 | 2022-03-24 | Method, device, equipment and medium for integrating native program and applet |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114691236B (en) |
| WO (1) | WO2023178952A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114691236B (en) * | 2022-03-24 | 2024-04-19 | 中国银联股份有限公司 | Method, device, equipment and medium for integrating native program and applet |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108804158A (en) * | 2018-06-05 | 2018-11-13 | 珠海市魅族科技有限公司 | Application call method, the control method of terminal device, terminal device and computer readable storage medium |
| CN110222263A (en) * | 2019-05-24 | 2019-09-10 | 苏州达家迎信息技术有限公司 | Application maintenance control method, device, server, terminal and storage medium |
| CN111586126A (en) * | 2020-04-28 | 2020-08-25 | 百度在线网络技术（北京）有限公司 | Method, device and equipment for pre-downloading small program and storage medium |
| CN111880701A (en) * | 2020-06-19 | 2020-11-03 | 维沃移动通信有限公司 | Page switching method and device and electronic equipment |
| CN113032703A (en) * | 2021-02-24 | 2021-06-25 | 腾讯科技（深圳）有限公司 | Resource data processing method and device, computer equipment and storage medium |
| CN113190155A (en) * | 2021-04-29 | 2021-07-30 | 上海掌门科技有限公司 | Information processing method, device and storage medium |
| WO2021228143A1 (en) * | 2020-05-15 | 2021-11-18 | 支付宝(杭州)信息技术有限公司 | Mini program startup method, signature method and apparatus, server and medium |
| CN114090118A (en) * | 2021-11-11 | 2022-02-25 | 北京百度网讯科技有限公司 | Method, device and equipment for starting small program and storage medium |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110187913B (en) * | 2019-05-17 | 2023-06-09 | 北京百度网讯科技有限公司 | Method and device for issuing and running applet |
| CN111367581B (en) * | 2020-02-28 | 2024-02-09 | 上海盛付通电子支付服务有限公司 | Method and equipment for providing hosted program |
| CN111782328A (en) * | 2020-07-02 | 2020-10-16 | 支付宝(杭州)信息技术有限公司 | Application processing method and device |
| CN112181510A (en) * | 2020-08-18 | 2021-01-05 | 微民保险代理有限公司 | Applet page data processing method and device, computer equipment and storage medium |
| CN112100481A (en) * | 2020-09-25 | 2020-12-18 | 百度国际科技（深圳）有限公司 | Search method, search device, electronic device, and storage medium |
| CN112084395A (en) * | 2020-09-25 | 2020-12-15 | 百度国际科技（深圳）有限公司 | Search method, search device, electronic device, and storage medium |
| CN112364266A (en) * | 2020-11-11 | 2021-02-12 | 平安科技（深圳）有限公司 | Seamless navigation method, device, electronic equipment and medium for applet and host application |
| CN112269607A (en) * | 2020-11-17 | 2021-01-26 | 北京百度网讯科技有限公司 | Applet control method, system, server and terminal device |
| CN113391854A (en) * | 2021-06-16 | 2021-09-14 | 湖南快乐阳光互动娱乐传媒有限公司 | Communication method and device for host application program and applet |
| CN114691236B (en) * | 2022-03-24 | 2024-04-19 | 中国银联股份有限公司 | Method, device, equipment and medium for integrating native program and applet |
-
2022
- 2022-03-24 CN CN202210293530.4A patent/CN114691236B/en active Active
- 2022-09-19 WO PCT/CN2022/119712 patent/WO2023178952A1/en unknown
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108804158A (en) * | 2018-06-05 | 2018-11-13 | 珠海市魅族科技有限公司 | Application call method, the control method of terminal device, terminal device and computer readable storage medium |
| CN110222263A (en) * | 2019-05-24 | 2019-09-10 | 苏州达家迎信息技术有限公司 | Application maintenance control method, device, server, terminal and storage medium |
| CN111586126A (en) * | 2020-04-28 | 2020-08-25 | 百度在线网络技术（北京）有限公司 | Method, device and equipment for pre-downloading small program and storage medium |
| WO2021228143A1 (en) * | 2020-05-15 | 2021-11-18 | 支付宝(杭州)信息技术有限公司 | Mini program startup method, signature method and apparatus, server and medium |
| CN111880701A (en) * | 2020-06-19 | 2020-11-03 | 维沃移动通信有限公司 | Page switching method and device and electronic equipment |
| CN113032703A (en) * | 2021-02-24 | 2021-06-25 | 腾讯科技（深圳）有限公司 | Resource data processing method and device, computer equipment and storage medium |
| CN113190155A (en) * | 2021-04-29 | 2021-07-30 | 上海掌门科技有限公司 | Information processing method, device and storage medium |
| CN114090118A (en) * | 2021-11-11 | 2022-02-25 | 北京百度网讯科技有限公司 | Method, device and equipment for starting small program and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 微信小程序的用户体验研究;林晓艳;王军峰;王文军;舒炎昕;;工业设计研究;20171031(00);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114691236A (en) | 2022-07-01 |
| WO2023178952A1 (en) | 2023-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108848245B (en) | Screen locking method and mobile terminal | |
| CN106293961B (en) | Text information processing method and device | |
| US20170068527A1 (en) | Device control method and apparatus | |
| CN110704059B (en) | Image processing method, device, electronic equipment and storage medium | |
| CN107193441B (en) | Desktop pendant previewing method and device | |
| CN109922098B (en) | Content sharing method and device for content sharing | |
| CN117390330A (en) | Webpage access method and device | |
| US20170316011A1 (en) | Method and apparatus for searching resource | |
| CN107045546B (en) | Webpage processing method and device and intelligent terminal | |
| CN114691236B (en) | Method, device, equipment and medium for integrating native program and applet | |
| CN110704053A (en) | Method and device for processing style information | |
| WO2017143911A1 (en) | Icon processing method and device for applications | |
| CN107402767B (en) | Method and device for displaying push message | |
| CN105095253A (en) | Webpage display method and webpage display device | |
| CN111159615A (en) | Webpage processing method and device | |
| CN112148395A (en) | Page display method, device, equipment and storage medium | |
| CN108241515B (en) | Application shortcut establishing method and terminal | |
| CN113296841A (en) | Application program processing method, device, equipment and medium | |
| CN105468606B (en) | Webpage saving method and device | |
| CN111596980B (en) | Information processing method and device | |
| CN111695064B (en) | Buried point loading method and device | |
| CN110543265A (en) | Page title bar generation method and device, electronic equipment and storage medium | |
| CN106302821B (en) | Data request method and equipment thereof | |
| CN112667852B (en) | Video-based searching method and device, electronic equipment and storage medium | |
| CN110084065B (en) | Data desensitization method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |