CN113282363A - Method and device for optimizing hybrid APP - Google Patents
Method and device for optimizing hybrid APP Download PDFInfo
- Publication number
- CN113282363A CN113282363A CN202110579235.0A CN202110579235A CN113282363A CN 113282363 A CN113282363 A CN 113282363A CN 202110579235 A CN202110579235 A CN 202110579235A CN 113282363 A CN113282363 A CN 113282363A
- Authority
- CN
- China
- Prior art keywords
- webapp
- instruction
- interactive
- closing
- webview
- 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.)
- Pending
Links
Images
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/451—Execution arrangements for user interfaces
-
- 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
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- 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/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5022—Mechanisms to release resources
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)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a method and a device for optimizing hybrid APP, which are used for shortening the response time of Web application in the hybrid APP. The method provided by the embodiment of the invention comprises the following steps: receiving a starting instruction, and opening a main interface of the native APP based on the starting instruction; if a non-closing interactive instruction for the WebAPP is detected on the main interface, calling Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface; if a closing instruction of the WebAPP is detected, calling a native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP; and if the non-closing interactive instruction for the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the detected non-closing interactive instruction for the WebAPP.
Description
Technical Field
The invention relates to the technical field of computer program application, in particular to a method and a device for optimizing hybrid APP (application).
Background
In the era of mobile internet, along with the explosive increase of sales of smart terminals, mobile internet has enabled each user to enjoy more mobile and personalized internet experience. Due to the convenience of development and maintenance of intelligent terminal hybrid APP, hybrid development modes are increasingly adopted for intelligent terminal APP.
The hybrid development App (hybrid App) is that a lightweight browser (WebView) is embedded in a native App, and part of native functions are developed by changing into Html 5, so that the functions can be dynamically updated without upgrading the App, and can be simultaneously run on the Android or iOS App, so that the user experience is better, and the developed resources can be saved.
However, when the Web application is loaded, the current hybrid APP optimizes the time for the client to open the Web application by reducing the initialization time of the webview, and although the optimization method reduces the initialization time of the webview, the optimization method still does not significantly shorten the response time of the Web application.
Disclosure of Invention
The embodiment of the invention provides a method and a device for optimizing hybrid APP, which are used for shortening the response time of Web application in the hybrid APP.
A first aspect of an embodiment of the present application provides a method for optimizing a hybrid APP, where the hybrid APP includes a native APP and a WebAPP, and the WebAPP is embedded in Webview, and the method includes:
receiving a starting instruction, and opening a main interface of the native APP based on the starting instruction;
if a non-closing interactive instruction for the WebAPP is detected on the main interface, calling the Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface;
if a closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP;
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
Preferably, before performing the caching operation on the page stack in the Webview and the static resource in the WebAPP, the method further includes:
judging whether the number of the page stacks is greater than 1;
if so, deleting the page stack to a last page stack, and executing cache operation on the last page stack and the static resources in the WebAPP;
if not, triggering a step of executing cache operation on the page stack in the Webview and the static resource in the WebAPP.
Preferably, if the non-close interactive instruction for the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the detected non-close interactive instruction for the WebAPP again includes:
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction of the WebAPP detected again.
Preferably, before invoking the Webview based on the non-close interaction instruction and loading the interaction interface corresponding to the non-close interaction instruction, the method further includes:
acquiring a user identification code and user authority;
judging whether the authority triggers the non-closing interactive instruction or not according to the user identification code and the user authority;
and if so, triggering the step of calling the Webview based on the non-closing interactive instruction and loading the interactive interface corresponding to the non-closing interactive instruction if the non-closing interactive instruction for the WebAPP is detected on the main interface.
Preferably, if a close instruction for the WebAPP is detected, calling the native APP to intercept the close instruction, and performing a cache operation on a page stack in the Webview and a static resource in the WebAPP, including:
if the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and executing cache operation on the user identification code and the user authority, the page stack in the Webview and the static resource in the WebAPP.
Preferably, the method further comprises:
and if a closing instruction of the main interface is detected, calling the native APP to destroy the Webview, and completing resource recovery.
A second aspect of the embodiments of the present application provides an apparatus for optimizing hybrid APP, including:
the receiving unit is used for receiving a starting instruction and opening a main interface of the native APP based on the starting instruction;
a loading unit, configured to, when a non-close interaction instruction for the WebAPP is detected on the main interface, call the Webview based on the non-close interaction instruction, and load an interaction interface corresponding to the non-close interaction instruction, where, in a process of loading the interaction interface, at least a step of loading a static resource in the WebAPP is included;
the cache unit is used for calling the native APP to intercept the closing instruction when the closing instruction of the WebAPP is detected, executing cache operation on a page stack in the Webview and a static resource in the WebAPP, and then jumping to a main interface of the native APP;
and the skipping unit is used for controlling the native APP to call the interactive interface in the page stack and skipping from the interactive interface in the page stack to a target interactive interface corresponding to the again detected non-closing interactive instruction of the WebAPP if the non-closing interactive instruction of the WebAPP is detected on the main interface again.
Preferably, the apparatus further comprises:
the first judging unit is used for judging whether the number of the page stacks in the Webview is greater than 1 or not before caching is performed on the page stacks in the Webview and the static resources in the WebAPP;
the first execution unit is used for deleting the page stack to the last page stack and executing cache operation on the last page stack and the static resource in the WebAPP when the number of the page stacks is larger than 1;
and the second execution unit is used for triggering the step of executing cache operation on the page stack in the Webview and the static resource in the WebAPP when the number of the page stacks is not more than 1.
Preferably, the jumping unit is specifically configured to:
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction of the WebAPP detected again.
Preferably, the apparatus further comprises:
the acquisition unit is used for acquiring a user identification code and user rights before calling the Webview based on the non-closing interactive instruction and loading an interactive interface corresponding to the non-closing interactive instruction;
the second judging unit is used for judging whether the permission triggers the non-closing interactive instruction or not according to the user identification code and the user permission;
and the triggering unit is used for triggering the step of calling the Webview based on the non-closing interactive instruction and loading the interactive interface corresponding to the non-closing interactive instruction if the non-closing interactive instruction for the WebAPP is detected on the main interface when the interactive instruction is triggered by the permission.
Preferably, the cache unit is specifically configured to:
if the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and executing cache operation on the user identification code and the user authority, the page stack in the Webview and the static resource in the WebAPP.
Preferably, the apparatus further comprises:
and the recovery unit is used for calling the native APP to destroy the Webview to complete resource recovery if a closing instruction of the main interface is detected.
A third aspect of the embodiments of the present application provides a computer apparatus, including a processor, where the processor is configured to implement the method for optimizing hybrid APP provided in the first aspect of the embodiments of the present application when executing a computer program stored in a memory.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is used, when being executed by a processor, to implement the method for optimizing hybrid APP provided in the first aspect of the embodiments of the present application.
According to the technical scheme, the embodiment of the invention has the following advantages:
in the embodiment of the application, a starting instruction is received, and a main interface of the native APP is opened based on the starting instruction; if a non-closing interactive instruction for the WebAPP is detected on the main interface, calling the Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface; if a closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP; and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
According to the method and the device, when a closing instruction of the Web application is executed, the native APP is called to intercept the closing instruction, cache operation is performed on at least one interactive interface and the static resources in the WebAPP, and when a non-closing interactive instruction (namely a response instruction of the Web application) of the WebAPP is detected on the main interface again, the previous cached interactive interface can be jumped to the target interactive interface, and the cached interactive interface contains the static resources in the WebAPP, so that when the target interactive interface is loaded, the loading time of the static resources in the WebAPP is reduced, and the response time of the Web application is shortened.
Drawings
FIG. 1 is a schematic diagram of an embodiment of a method for optimizing hybrid APP in the embodiment of the present application;
FIG. 2 is a schematic diagram of another embodiment of a method for optimizing hybrid APP in the embodiment of the present application;
FIG. 3 is a schematic diagram of another embodiment of a method for optimizing hybrid APP in the embodiment of the present application;
FIG. 4 is a schematic diagram of another embodiment of a method for optimizing hybrid APP in the embodiment of the present application;
fig. 5 is a schematic diagram of an embodiment of an apparatus for optimizing hybrid APP in the embodiment of the present application.
Detailed Description
The embodiment of the invention provides a method and a device for optimizing hybrid APP, which are used for shortening the response time of Web application in the hybrid APP.
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For the sake of understanding, the terms used in the present application will be described below, and their meanings will be continued in the following description, and will not be described in detail later.
Native APP: native APP is built for use on a particular device and its operating system, so it can use device-specific hardware and software. Native APP development programs can provide optimized performance and take full advantage of the latest technologies such as GPS, as compared to network applications or mobile cloud applications developed to be common across multiple systems.
Static resources: generally refers to files sent by a server to a client, such as js, css, pictures, audio, etc., as is common.
webview: the browser is a webkit-based engine, can analyze DOM elements and display a control of an html page, has the same principle as a browser to display the page, and can be regarded as a browser.
API: an API (application programming Interface) is a predefined function that is intended to provide applications and developers the ability to access a set of routines based on certain software or hardware, without accessing source code or understanding the details of internal working mechanisms.
Based on the existing hybrid APP, when the Web application is loaded, the response time of the Web application is not yet obviously shortened.
For convenience of understanding, the method for optimizing hybrid APP in the embodiment of the present application is described below, and referring to fig. 1, an embodiment of the method for optimizing hybrid APP in the embodiment of the present application includes:
101. receiving a starting instruction, and opening a main interface of the native APP based on the starting instruction;
the method can be executed based on a controller or a processor for controlling the hybrid APP, and specifically, when receiving a start instruction, an execution main body (the controller or the processor for controlling the hybrid APP) opens a main interface of the native APP based on the start instruction.
102. If a non-closing interactive instruction for the WebAPP is detected on the main interface, calling the Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface;
and if the execution subject detects a non-closing interactive instruction for the WebAPP on the main interface, namely the execution subject detects that the interactive instruction is a non-closing instruction on the main interface, calling Webview based on the interactive instruction and loading an interactive interface corresponding to the interactive instruction. It should be noted that the interactive instruction herein includes one or more interactive interfaces, and when a plurality of interactive instructions are detected, a plurality of interactive interfaces are overlappingly loaded based on the plurality of interactive instructions, and the overlappingly loading herein refers to overlaying a first interactive page with a second interactive page when the second interactive page is loaded.
It should be noted that, when the Webview loads the first interactive interface, static resources of the web application, such as js (javascript), css (Cascading Style Sheets), pictures, audio, and the like, need to be loaded first, so in the embodiment of the present application, the executing main body at least includes a step of loading the static resources in the WebAPP in the process of loading the interactive interface.
103. If a closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP;
different from the prior art, when a closing instruction of the WebAPP is detected, closing operation is directly executed on the interactive interface, when the closing instruction of the WebAPP is detected, the native APP is called to intercept the corresponding closing instruction, cache operation is executed on a page stack in the Webview and a static resource in the WebAPP, and after the cache operation is completed, the main interface of the native APP is jumped to.
It should be noted that, when the embodiment includes multiple interaction interfaces, the Webview correspondingly includes multiple page stacks, and cache operations need to be performed on the multiple page stacks in the Webview and the static resources in the WebAPP, and after the cache operations are completed, a jump is made to the main interface of the native APP.
Specifically, when jumping to the main interface of the native APP, the pre-stored script file may be called through the API interface, and the main interface of the native APP is jumped to through the script file.
104. And if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
After jumping to the main interface of the native APP in step 103, if a non-close interaction instruction to the WebAPP is detected on the main interface again, controlling the native APP to call an interaction interface corresponding to the page stack in the cache, and jumping from the interaction interface to a target interaction interface corresponding to the interaction execution detected again.
Because the page stack in the Webview and the static resources in the WebAPP are cached in step 103, the embodiment of the present application may directly invoke the static resources in the WebAPP in the local cache when the interactive instruction based on the non-close control on the main interface is detected again, so that the cached static resources in the WebAPP may be reused when the interactive interface in the WebAPP is not loaded for the first time, thereby reducing the time for loading the static resources in the WebAPP, and shortening the response time of the Web application in the hybrid APP.
Based on the embodiment described in fig. 1, if the Webview includes multiple page stacks in step 102, fig. 1 needs to cache the multiple page stacks and static resources in the WebAPP, which may cause that, in the process of jumping from the interactive interfaces corresponding to the multiple page stacks to the target interactive interface in step 104, a user may see multiple previously cached interactive interfaces, so that the jumping process is not smooth enough, thereby reducing user experience.
Based on this problem, in the embodiment of the present application, before performing the caching operation on the page stack in the Webview and the static resource in the WebAPP in step 103, the following steps may be performed, please refer to fig. 2, where another embodiment of the method for optimizing a hybrid APP in the embodiment of the present application includes:
201. judging whether the number of page stacks in the Webview is larger than 1, if so, executing the step 202, and if not, executing the step 203;
before performing caching operation on the page stacks in the Webview and the static resources in the WebAPP, the execution main body can also judge the number of the page stacks in the Webview, judge whether the number of the page stacks is greater than 1, if so, execute step 202, and if not, execute step 203.
202. Deleting the page stacks to the last page stack, executing cache operation on the last page stack and static resources in the WebAPP, and then jumping to a main interface of the native APP;
when the number of page stacks in Webview is larger than 1, deleting the page stacks to the last page stack, executing caching operation on the last page stack and the static resource in WebAPP, and then jumping to a main interface of a primary APP;
203. triggering a step of executing cache operation on a page stack in the Webview and a static resource in the WebAPP;
and when the number of the page stacks in the Webview is not more than 1, namely the number of the page stacks in the Webview is equal to 1, performing caching operation on the page stacks in the Webview and the static resources in the WebAPP.
204. And if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
After the step 203 jumps to the main interface of the native APP, if the non-close interaction instruction to the WebAPP on the main interface is detected again, the native APP is controlled to call the interaction interface corresponding to the last page stack in the cache, and jumps to the target interaction interface corresponding to the interaction execution detected again from the interaction interface.
According to the method and the device for achieving the webpage interface cache, when the Webview comprises the plurality of page stacks, the plurality of page stacks in the Webview are emptied to the last page stack, so that cache operation is only performed on the interactive interface corresponding to the last page stack and the static resources in the WebAPP, and therefore when the interactive instruction based on the non-closed control on the main interface is detected again, the interactive interface corresponding to the last page stack can be jumped to the target interactive interface, on one hand, the step of reloading the static resources in the WebAPP can be saved, the response time of the WebAPP is shortened, on the other hand, the interactive interface corresponding to the last page stack can be jumped to the target interactive interface, smooth transition from the main interface to the target interactive interface is completed, and user experience is improved.
Based on the embodiment described in fig. 1, before invoking the Webview based on the non-close interaction instruction in the step 102 and loading the interaction interface corresponding to the non-close interaction instruction, the following steps may also be performed, please refer to fig. 3, where another embodiment of the method for optimizing hybrid APP in the embodiment of the present application includes:
301. acquiring a user identification code and user authority;
in some hybrid APPs, in order to protect the user rights, the user identification code and the user rights need to be obtained, and step 302 is executed according to the user identification code and the user rights.
302. And judging whether the non-closing interactive instruction is triggered by the authority according to the user identification code and the user authority, if so, executing step 303, and if not, executing step 309.
When the user identification code and the user permission are obtained, whether the user identification code and the user permission have the permission to trigger an interactive instruction based on a non-closing control on the main interface is further judged, if yes, step 303 is executed, and if not, step 309 is executed.
303. Triggering the step of calling the Webview based on the non-closing interactive instruction and loading an interactive interface corresponding to the non-closing interactive instruction if the non-closing interactive instruction for the WebAPP is detected on the main interface;
the description of the specific content of this step is similar to that of step 102, and is not repeated here.
304. If the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and judging whether the number of page stacks in the Webview is greater than 1, if so, executing a step 305, and if not, executing a step 307;
if the execution subject detects a closing instruction of the WebAPP, calling the native APP to intercept the closing instruction, and meanwhile, judging whether the number of page stacks in the Webview is greater than 1, if so, executing a step 305, otherwise, executing a step 307;
305. deleting the page stack to a last page stack, executing cache operation on the user identification code and the user authority, the last page stack and static resources in the WebAPP, and then jumping to a main interface of the native APP;
if the number of the page stacks in the Webview is larger than 1, deleting the page stacks in the Webview to the last page stack, executing cache operation on the user identification code and the user authority, the last page stack and the static resources in the WebAPP, and then jumping to the main interface of the native APP.
Because the caching operation is executed on the user identification code and the user permission, the last page stack and the static resource in the WebAPP in the embodiment of the application, the user identification code and the user permission in the cache and the static resource in the WebAPP can be called when the interaction interface corresponding to the interaction instruction based on the non-closing control on the main interface is loaded again, and therefore when the interaction interface is loaded again, the time for loading the user identification code and the user permission and the static resource in the WebAPP is reduced, and the response time of the WebAPP is shortened.
306. If the non-closing interactive instruction for the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction for the WebAPP detected again;
after jumping to the primary interface of the native APP in step 305, if an interactive instruction based on the non-close control on the primary interface (i.e., a non-close interactive instruction to the WebAPP) is detected again, controlling the native APP to call the interactive interface corresponding to the last page stack in the cache, and jumping from the interactive interface to a target interactive interface corresponding to the re-detected interactive execution.
Because step 305 clears the plurality of page stacks in the Webview to the last page stack when the plurality of page stacks are included in the Webview, so that only the interactive interface corresponding to the last page stack and the static resources in the WebAPP are cached, when the interactive instruction based on the non-closed control on the main interface is detected again, the interactive interface corresponding to the last page stack can be jumped to the target interactive interface, on one hand, steps of reloading the user identification code and the user permission and the static resources in the WebAPP can be saved, the response time of the WebAPP is shortened, on the other hand, the interactive interface corresponding to the last page stack can be jumped to the target interactive interface, the smooth transition from the main interface to the target interactive interface is completed, and the user experience is improved.
307. Executing cache operation on the user identification code, the user authority, the page stack in the Webview and the static resource in the WebAPP, and then jumping to the main interface of the native APP;
if the number of the page stacks in the Webview is not more than 1 (namely equal to 1), directly executing cache operation on the user identification code and the user authority, the page stacks in the Webview and the static resources in the WebAPP, and then jumping to a main interface of the native APP;
308. if the non-closing interactive instruction for the WebAPP is detected on the main interface again, controlling the native APP to call an interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the detected non-closing interactive instruction for the WebAPP;
after jumping to the main interface of the native APP in step 308, if an interactive instruction based on the non-close control on the main interface (i.e., a non-close interactive instruction to the webAPP) is detected again, the native APP is controlled to call the interactive interface corresponding to the page stack in the cache, and jump from the interactive interface to a target interactive interface corresponding to the re-detected interactive execution.
309. Other processes are performed.
After the user identification code and the user permission are obtained, if it is further judged that the user identification code and the user permission cannot trigger an interactive instruction based on a non-closed control on the main interface, other processes are executed, such as sending a prompt message to prompt the user that the user does not have the permission, or requiring the user to re-verify the user identification code and the user permission, and the like, and specific limitations are not provided here.
According to the embodiment of the application, the user identification code and the user permission need to be verified, so that after the user identification code and the user permission are checked to be cached by the execution main body after entering the interactive interface, the page stack in the Webview and the static resource in the WebAPP are cached, the time for loading the user identification code and the user permission and the static resource in the WebAPP is shortened when the WebAPP is loaded again, and the response time of the WebAPP is shortened.
Furthermore, when a plurality of page stacks exist in Webview, the page stacks are deleted to the last page stack, so that when the interaction instruction based on the non-closed control on the main interface is detected again, the native APP is controlled to call the interaction interface corresponding to the last page stack, the interaction interface corresponding to the last page stack jumps to the target interaction interface, smooth transition from the main interface to the target interaction interface is completed, and user experience is improved.
Based on the embodiments described in fig. 1 to fig. 3, when a close instruction for the native APP main interface is detected, the following steps may be further performed, please refer to fig. 4, another embodiment of the method for optimizing hybrid APP in the embodiment of the present application includes:
401. and if a closing instruction of the main interface is detected, calling the native APP to destroy the Webview, and completing resource recovery.
If a closing instruction of the primary APP main interface is detected, calling the primary APP to destroy the Webview, namely clearing the cached user identification code, user permission and/or the page stack in the Webview and the static resource in the WebAPP in the original cache, thereby completing the recovery of the storage space.
With reference to fig. 5, the method in the embodiment of the present application is described above, and the following describes an apparatus for optimizing hybrid APP in the embodiment of the present application, where an embodiment of an apparatus for optimizing hybrid APP in the embodiment of the present application includes:
a receiving unit 501, configured to receive a start instruction, and open a main interface of the native APP based on the start instruction;
a loading unit 502, configured to, when a non-close interaction instruction for the WebAPP is detected on the main interface, invoke the Webview based on the non-close interaction instruction, and load an interaction interface corresponding to the non-close interaction instruction, where in a process of loading the interaction interface, at least a step of loading a static resource in the WebAPP is included;
the caching unit 503 is configured to, when a closing instruction for the WebAPP is detected, invoke the native APP to intercept the closing instruction, perform caching operation on a page stack in the Webview and a static resource in the WebAPP, and then jump to a main interface of the native APP;
a skipping unit 504, configured to control the native APP to invoke the interactive interface in the page stack if the non-close interactive instruction for the WebAPP is detected on the main interface again, and skip from the interactive interface in the page stack to a target interactive interface corresponding to the non-close interactive instruction for the WebAPP detected again.
Preferably, the apparatus further comprises:
a first determining unit 505, configured to determine whether the number of page stacks in the Webview is greater than 1 before performing a caching operation on the page stacks and the static resources in the WebAPP;
a first executing unit 506, configured to delete the page stack to a last page stack when the number of the page stacks is greater than 1, and execute a caching operation on the last page stack and a static resource in the WebAPP;
a second executing unit 507, configured to trigger a step of performing a caching operation on the page stack in the Webview and the static resource in the WebAPP when the number of the page stacks is not greater than 1.
Preferably, the jumping unit 504 is specifically configured to:
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction of the WebAPP detected again.
Preferably, the apparatus further comprises:
an obtaining unit 508, configured to obtain a user identification code and a user right before invoking the Webview based on the non-close interaction instruction and loading an interaction interface corresponding to the non-close interaction instruction;
a second determining unit 509, configured to determine whether the non-close interaction instruction is triggered by an authority according to the user identification code and the user authority;
and a triggering unit 510, configured to trigger, when an interactive instruction is triggered with permission, a step of calling the Webview based on the non-close interactive instruction and loading an interactive interface corresponding to the non-close interactive instruction if the non-close interactive instruction for the WebAPP is detected on the main interface.
Preferably, the cache unit 503 is specifically configured to:
if the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and executing cache operation on the user identification code and the user authority, the page stack in the Webview and the static resource in the WebAPP.
Preferably, the apparatus further comprises:
and the recovery unit 511 is configured to invoke the native APP to destroy the Webview if a closing instruction for the main interface is detected, so as to complete resource recovery.
It should be noted that the functions of the above units are similar to those described in fig. 1 to 4, and are not described again here.
In the embodiment of the application, a receiving unit 501 receives a start instruction, and opens a main interface of the native APP based on the start instruction; detecting a non-closing interactive instruction for WebAPP on a main interface through a loading unit 502, calling the Webview based on the non-closing interactive instruction to load an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface; if a closing instruction for the interactive interface is detected through the cache unit 503, calling the native APP to intercept the closing instruction, performing cache operation on at least one interactive interface and static resources in the WebAPP, and then jumping to a main interface of the native APP; if a non-closed interactive instruction for the WebAPP is detected on the main interface again, controlling the native APP to call the at least one interactive interface, and jumping from the at least one interactive interface to a target interactive interface corresponding to the detected interactive instruction again through a jumping unit 504.
According to the embodiment of the application, when a closing instruction of the Web application is executed, the native APP is called to intercept the closing instruction, cache operation is performed on at least one interactive interface and the static resources in the WebAPP, and when the interactive instruction based on the non-closing control on the main interface (namely the response instruction of the Web application is detected) is detected again, the previously cached interactive interface can be jumped to the target interactive interface, and because the cached interactive interface contains the static resources in the WebAPP, the loading time of the static resources in the WebAPP is reduced when the target interactive interface is loaded, so that the response time of the Web application is shortened.
The apparatus for optimizing hybrid APP in the embodiment of the present invention is described above from the perspective of modular functional entities, and the computer apparatus in the embodiment of the present invention is described below from the perspective of hardware processing:
the computer device is used for realizing the function of a device for optimizing hybrid APP, and one embodiment of the computer device in the embodiment of the invention comprises the following steps:
a processor and a memory;
the memory is used for storing the computer program, and the processor is used for realizing the following steps when executing the computer program stored in the memory:
receiving a starting instruction, and opening a main interface of the native APP based on the starting instruction;
if a non-closing interactive instruction for the WebAPP is detected on the main interface, calling the Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface;
if a closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP;
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
In some embodiments of the present invention, the processor may be further configured to:
judging whether the number of page stacks in the Webview is larger than 1;
if so, deleting the page stack to a last page stack, and executing cache operation on the last page stack and the static resources in the WebAPP;
if not, triggering a step of executing cache operation on the page stack in the Webview and the static resource in the WebAPP.
In some embodiments of the present invention, the processor may be further configured to:
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction of the WebAPP detected again.
In some embodiments of the present invention, the processor may be further configured to:
acquiring a user identification code and user authority;
judging whether the authority triggers the non-closing interactive instruction or not according to the user identification code and the user authority;
and if so, triggering the step of calling the Webview based on the non-closing interactive instruction and loading the interactive interface corresponding to the non-closing interactive instruction if the non-closing interactive instruction for the WebAPP is detected on the main interface.
In some embodiments of the present invention, the processor may be further configured to:
if the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and executing cache operation on the user identification code and the user authority, the page stack in the Webview and the static resource in the WebAPP.
In some embodiments of the present invention, the processor may be further configured to:
and if a closing instruction of the main interface is detected, calling the native APP to destroy the Webview, and completing resource recovery.
It is to be understood that, when the processor in the computer apparatus described above executes the computer program, the functions of each unit in the corresponding apparatus embodiments may also be implemented, and are not described herein again. Illustratively, the computer program may be partitioned into one or more modules/units that are stored in the memory and executed by the processor to implement the invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program in the apparatus for optimizing hybrid APP. For example, the computer program may be divided into units in the above-described apparatus for optimizing hybrid APP, which may implement specific functions as described above for the apparatus for optimizing hybrid APP.
The computer device can be a desktop computer, a notebook, a palm computer, a cloud server and other computing equipment. The computer device may include, but is not limited to, a processor, a memory. It will be appreciated by those skilled in the art that the processor, memory are merely examples of a computer apparatus and are not meant to be limiting, and that more or fewer components may be included, or certain components may be combined, or different components may be included, for example, the computer apparatus may also include input output devices, network access devices, buses, etc.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable gate array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like which is the control center for the computer device and which connects the various parts of the overall computer device using various interfaces and lines.
The memory may be used to store the computer programs and/or modules, and the processor may implement various functions of the computer device by running or executing the computer programs and/or modules stored in the memory and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the terminal, and the like. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
The invention also provides a computer readable storage medium for implementing the functionality of an apparatus for optimizing hybrid APPs, having stored thereon a computer program which, when executed by a processor, the processor is operable to perform the steps of:
receiving a starting instruction, and opening a main interface of the native APP based on the starting instruction;
if a non-closing interactive instruction for the WebAPP is detected on the main interface, calling the Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface;
if a closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP;
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
In some embodiments of the invention, the computer program stored on the computer-readable storage medium, when executed by the processor, may be specifically configured to perform the steps of:
judging whether the number of page stacks in the Webview is larger than 1;
if so, deleting the page stack to a last page stack, and executing cache operation on the last page stack and the static resources in the WebAPP;
if not, triggering a step of executing cache operation on the page stack in the Webview and the static resource in the WebAPP.
In some embodiments of the invention, the computer program stored on the computer-readable storage medium, when executed by the processor, may be specifically configured to perform the steps of:
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction of the WebAPP detected again.
In some embodiments of the invention, the computer program stored on the computer-readable storage medium, when executed by the processor, may be specifically configured to perform the steps of:
acquiring a user identification code and user authority;
judging whether the authority triggers the non-closing interactive instruction or not according to the user identification code and the user authority;
and if so, triggering the step of calling the Webview based on the non-closing interactive instruction and loading the interactive interface corresponding to the non-closing interactive instruction if the non-closing interactive instruction for the WebAPP is detected on the main interface.
In some embodiments of the invention, the computer program stored on the computer-readable storage medium, when executed by the processor, may be specifically configured to perform the steps of:
if the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and executing cache operation on the user identification code and the user authority, the page stack in the Webview and the static resource in the WebAPP.
In some embodiments of the invention, the computer program stored on the computer-readable storage medium, when executed by the processor, may be specifically configured to perform the steps of:
and if a closing instruction of the main interface is detected, calling the native APP to destroy the Webview, and completing resource recovery.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A method of optimizing a hybrid APP, wherein the hybrid APP comprises a native APP and a WebAPP, the WebAPP being embedded in Webview, the method comprising:
receiving a starting instruction, and opening a main interface of the native APP based on the starting instruction;
if a non-closing interactive instruction for the WebAPP is detected on the main interface, calling the Webview based on the non-closing interactive instruction, and loading an interactive interface corresponding to the non-closing interactive instruction, wherein the step of loading static resources in the WebAPP is at least included in the process of loading the interactive interface;
if a closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, executing cache operation on a page stack in the Webview and static resources in the WebAPP, and then jumping to a main interface of the native APP;
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the re-detected non-closing interactive instruction of the WebAPP.
2. The method of claim 1, wherein before performing caching operations on the page stack in Webview and the static resource in WebAPP, the method further comprises:
judging whether the number of page stacks in the Webview is larger than 1;
if so, deleting the page stack to a last page stack, and executing cache operation on the last page stack and the static resources in the WebAPP;
if not, triggering a step of executing cache operation on the page stack in the Webview and the static resource in the WebAPP.
3. The method of claim 2, wherein if a non-close interactive instruction for the WebAPP is detected again on the main interface, controlling the native APP to call an interactive interface in the page stack, and jumping from the interactive interface in the page stack to a target interactive interface corresponding to the again detected non-close interactive instruction for the WebAPP, includes:
and if the non-closing interactive instruction of the WebAPP is detected on the main interface again, controlling the native APP to call the last page stack, and jumping from the interactive interface corresponding to the last page stack to a target interactive interface corresponding to the non-closing interactive instruction of the WebAPP detected again.
4. The method according to claim 3, wherein before invoking the Webview based on the non-close interaction command and loading the interaction interface corresponding to the non-close interaction command, the method further comprises:
acquiring a user identification code and user authority;
judging whether the authority triggers the non-closing interactive instruction or not according to the user identification code and the user authority;
and if so, triggering the step of calling the Webview based on the non-closing interactive instruction and loading the interactive interface corresponding to the non-closing interactive instruction if the non-closing interactive instruction for the WebAPP is detected on the main interface.
5. The method of claim 4, wherein if a close instruction for the WebAPP is detected, calling the native APP to intercept the close instruction, and performing a caching operation on a page stack in the Webview and a static resource in the WebAPP, comprises:
if the closing instruction of the WebAPP is detected, calling the native APP to intercept the closing instruction, and executing cache operation on the user identification code and the user authority, the page stack in the Webview and the static resource in the WebAPP.
6. The method according to any one of claims 1 to 5, further comprising:
and if a closing instruction of the main interface is detected, calling the native APP to destroy the Webview, and completing resource recovery.
7. An apparatus to optimize a hybrid APP, wherein the hybrid APP comprises a native APP and a WebAPP, the WebAPP being embedded in Webview, the apparatus comprising:
the receiving unit is used for receiving a starting instruction and opening a main interface of the native APP based on the starting instruction;
a loading unit, configured to, when a non-close interaction instruction for the WebAPP is detected on the main interface, call the Webview based on the non-close interaction instruction, and load an interaction interface corresponding to the non-close interaction instruction, where, in a process of loading the interaction interface, at least a step of loading a static resource in the WebAPP is included;
the cache unit is used for calling the native APP to intercept the closing instruction when the closing instruction of the WebAPP is detected, executing cache operation on a page stack in the Webview and a static resource in the WebAPP, and then jumping to a main interface of the native APP;
and the skipping unit is used for controlling the native APP to call the interactive interface in the page stack and skipping from the interactive interface in the page stack to a target interactive interface corresponding to the again detected non-closing interactive instruction of the WebAPP if the non-closing interactive instruction of the WebAPP is detected on the main interface again.
8. The apparatus of claim 6, further comprising:
the first judging unit is used for judging whether the number of the page stacks in the Webview is greater than 1 or not before caching is performed on the page stacks in the Webview and the static resources in the WebAPP;
the first execution unit is used for deleting the page stack to the last page stack and executing cache operation on the last page stack and the static resource in the WebAPP when the number of the page stacks is larger than 1;
and the second execution unit is used for triggering the step of executing cache operation on the page stack in the Webview and the static resource in the WebAPP when the number of the page stacks is not more than 1.
9. A computer arrangement comprising a processor, characterized in that the processor, when executing a computer program stored on a memory, is adapted to carry out the method according to any of claims 1-6.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, is adapted to carry out the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110579235.0A CN113282363A (en) | 2021-05-26 | 2021-05-26 | Method and device for optimizing hybrid APP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110579235.0A CN113282363A (en) | 2021-05-26 | 2021-05-26 | Method and device for optimizing hybrid APP |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113282363A true CN113282363A (en) | 2021-08-20 |
Family
ID=77282084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110579235.0A Pending CN113282363A (en) | 2021-05-26 | 2021-05-26 | Method and device for optimizing hybrid APP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113282363A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11663285B2 (en) | 2021-09-06 | 2023-05-30 | Microsoft Technology Licensing, Llc | Webpage management in native application |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101237542A (en) * | 2008-02-29 | 2008-08-06 | 中兴通讯股份有限公司 | Realization method for access to electronic program bill |
| CN106371830A (en) * | 2016-08-25 | 2017-02-01 | 北京量科邦信息技术有限公司 | Interactive method for realizing close and back control of native APP and WEB pages |
| CN107506430A (en) * | 2017-08-22 | 2017-12-22 | 四川长虹电器股份有限公司 | A kind of route control method and system based on mixed developing |
| US20180203839A1 (en) * | 2017-01-13 | 2018-07-19 | Microsoft Technology Licensing, Llc | Fast page loading in hybrid applications |
| CN109165369A (en) * | 2018-07-12 | 2019-01-08 | 北京猫眼文化传媒有限公司 | Webpage display process and device |
| CN109429101A (en) * | 2017-08-31 | 2019-03-05 | 中国电信股份有限公司 | The desktop loading method and device of Interactive Internet TV |
| CN110020326A (en) * | 2018-09-07 | 2019-07-16 | 天翼电子商务有限公司 | A method of promoting Webview opening speed |
| CN110597612A (en) * | 2019-09-26 | 2019-12-20 | 三星电子（中国）研发中心 | Intelligent equipment task management method and device |
| CN111310084A (en) * | 2018-12-12 | 2020-06-19 | 北京嘀嘀无限科技发展有限公司 | Page loading method, device and system, user terminal and readable storage medium |
-
2021
- 2021-05-26 CN CN202110579235.0A patent/CN113282363A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101237542A (en) * | 2008-02-29 | 2008-08-06 | 中兴通讯股份有限公司 | Realization method for access to electronic program bill |
| CN106371830A (en) * | 2016-08-25 | 2017-02-01 | 北京量科邦信息技术有限公司 | Interactive method for realizing close and back control of native APP and WEB pages |
| US20180203839A1 (en) * | 2017-01-13 | 2018-07-19 | Microsoft Technology Licensing, Llc | Fast page loading in hybrid applications |
| CN107506430A (en) * | 2017-08-22 | 2017-12-22 | 四川长虹电器股份有限公司 | A kind of route control method and system based on mixed developing |
| CN109429101A (en) * | 2017-08-31 | 2019-03-05 | 中国电信股份有限公司 | The desktop loading method and device of Interactive Internet TV |
| CN109165369A (en) * | 2018-07-12 | 2019-01-08 | 北京猫眼文化传媒有限公司 | Webpage display process and device |
| CN110020326A (en) * | 2018-09-07 | 2019-07-16 | 天翼电子商务有限公司 | A method of promoting Webview opening speed |
| CN111310084A (en) * | 2018-12-12 | 2020-06-19 | 北京嘀嘀无限科技发展有限公司 | Page loading method, device and system, user terminal and readable storage medium |
| CN110597612A (en) * | 2019-09-26 | 2019-12-20 | 三星电子（中国）研发中心 | Intelligent equipment task management method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11663285B2 (en) | 2021-09-06 | 2023-05-30 | Microsoft Technology Licensing, Llc | Webpage management in native application |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6912583B2 (en) | Service processing method and equipment | |
| CN108121594B (en) | Process management method and device | |
| CN111427596B (en) | Software upgrading method and device and terminal equipment | |
| CN110020323B (en) | Page switching method and system for hybrid application, computer equipment and storage medium | |
| CN110874236B (en) | Cross-platform application device, terminal and storage medium | |
| CN108762956B (en) | Method for acquiring Native local data, server, mobile terminal and storage medium | |
| US20120227032A1 (en) | Method, apparatus, and system for invoking widget | |
| US10191751B2 (en) | Information processing device for generating application programming interface information | |
| JP2017146966A (en) | Method and system for extending function to package file | |
| CN109684573B (en) | Target picture display method and device, storage medium and electronic equipment | |
| CN111666497A (en) | Application program loading method and device, electronic equipment and readable storage medium | |
| CN107016282B (en) | information processing method and device | |
| CN109743359B (en) | Hybrid communication processing method and device, computer equipment and storage medium | |
| CN110765394A (en) | So file loading method and device, storage medium and terminal equipment | |
| CN111008132A (en) | Application debugging method and device for Android system, computer equipment and storage medium | |
| CN113434230A (en) | Jump control method and device for H5 page, storage medium and electronic device | |
| CN104598267A (en) | Application calling method and device | |
| CN110704131B (en) | Method and device for calling native application by HTML5 application | |
| CN108509228B (en) | Page loading method, terminal equipment and computer readable storage medium | |
| CN106293790B (en) | application program upgrading method and device based on Firefox operating system | |
| CN113282363A (en) | Method and device for optimizing hybrid APP | |
| CN115760391A (en) | Intelligent contract changing method and device in block chain, electronic equipment and storage medium | |
| US20240031166A1 (en) | Web-side data signature method and apparatus and computer device | |
| US20130332568A1 (en) | Method of data processing by a navigation module | |
| CN112035127B (en) | Method and device for installing application, vehicle, storage medium and electronic equipment |
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 |