Page opening method and device for hybrid mobile application, terminal and medium

Abstract

The embodiment of the invention discloses a page opening method and device for a hybrid mobile application, a terminal and a medium. The method comprises the steps that when it is determined that initial verification of the hybrid mobile application is passed, a secondary login native page is opened, meanwhile, preloading operation is conducted on a home page webpage of the hybrid mobile application, and a home page WebView object is obtained; when the secondary verification is passed, displaying a home page webpage according to a home page WebView object; according to a preset secondary page preloading prediction rule, obtaining at least one preloading secondary page entry; respectively carrying out preloading operation on the second-level web pages corresponding to the second-level page preloading entrances to obtain corresponding second-level page WebView objects; and when a page opening instruction of the target second-level page entry is received, displaying the target second-level webpage page according to a second-level page WebView object corresponding to the target second-level page entry. Through the embodiment of the invention, the opening speed of the webpage in the hybrid mobile application can be increased.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to methods, devices, terminals and media for opening pages in hybrid mobile applications. Background Technology

[0002] Hybrid mobile applications (Hybrid Apps) combine the advantages of native app and web app development technologies. Hybrid mobile applications use web technologies (such as HTML, CSS, and JavaScript) to build interfaces and functions, while also having access to the device's native functions (such as camera, GPS, and sensors).

[0003] Native mobile platforms all provide a common control / component called WebView. WebView is essentially a headless browser. Hybrid mobile applications can use WebView to load and display web page content, providing users with functionality and interaction. In this way, hybrid mobile applications can use the same code to build applications on multiple platforms (such as iOS and Android) while retaining the native application's access to device functionality.

[0004] In existing technologies, when a user needs to open a webpage in a hybrid mobile application, after triggering the command to open the webpage, the following three steps are required to open the corresponding webpage: 1. Initializing WebView; 2. Loading web resources; 3. WebView rendering the page. Each of these three steps takes a certain amount of time, resulting in a long waiting time for the user to open the corresponding webpage in the hybrid mobile application, which affects the user experience. Summary of the Invention

[0005] This application provides a method, apparatus, terminal, and medium for opening pages in hybrid mobile applications, which can improve the opening speed of web pages in hybrid mobile applications, reduce user waiting time, and improve user experience.

[0006] In a first aspect, embodiments of this application provide a method for opening a page of a hybrid mobile application, the method being applied to a user terminal on which a hybrid mobile application is installed, the method comprising:

[0007] In response to the received user launch command for the hybrid mobile application, the initial login native page of the hybrid mobile application is opened;

[0008] When the initial verification of the hybrid mobile application is determined to be successful based on the initial verification information entered by the user on the initial login native page, the secondary login native page of the hybrid mobile application is opened. At the same time, the home page of the hybrid mobile application is preloaded to obtain the home page WebView object, and the home page WebView object is stored in a preset WebView object pool.

[0009] When the secondary verification of the hybrid mobile application is determined to be successful based on the secondary verification information entered by the user on the secondary login native page, the homepage webpage is displayed according to the homepage WebView object in the WebView object pool. The homepage webpage includes secondary page entries for multiple secondary webpages.

[0010] Based on the preset second-level page preloading prediction rules, at least one preloaded second-level page entry is determined from the multiple second-level page entry points;

[0011] Perform a preloading operation on the secondary web pages corresponding to each of the preloaded secondary page entry points to obtain the secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and store the secondary page WebView objects in the WebView object pool;

[0012] When a user's instruction to open a target secondary page entry in the preloaded secondary page entry is received, the target secondary web page is displayed according to the secondary page WebView object corresponding to the target secondary page entry in the WebView object pool.

[0013] Secondly, embodiments of this application also provide a hybrid mobile application page opening device, wherein the hybrid mobile application page opening device is deployed on a user terminal, the user terminal having a hybrid mobile application installed, and the hybrid mobile application page opening device includes:

[0014] The acquisition unit is used to acquire the user's launch command for the hybrid mobile application;

[0015] The processing unit is configured to, in response to a received user launch command for the hybrid mobile application, open the initial login native page of the hybrid mobile application; when the initial verification of the hybrid mobile application is confirmed to be successful based on the initial verification information entered by the user on the initial login native page, open the secondary login native page of the hybrid mobile application, and simultaneously preload the homepage of the hybrid mobile application to obtain a homepage WebView object, and store the homepage WebView object in a preset WebView object pool; when the secondary verification of the hybrid mobile application is confirmed to be successful based on the secondary verification information entered by the user on the secondary login native page, display the homepage according to the homepage WebView object in the WebView object pool. A webpage, the homepage of which includes multiple secondary page entrances to secondary webpages; according to a preset secondary page preloading prediction rule, at least one secondary page entrance is determined from the multiple secondary page entrances for preloading; preloading operations are performed on the secondary webpages corresponding to each preloaded secondary page entrance to obtain secondary page WebView objects corresponding to each preloaded secondary page entrance, and the secondary page WebView objects are stored in the WebView object pool; when a user's page opening instruction for a target secondary page entrance among the preloaded secondary page entrances is received, the target secondary webpage is displayed according to the secondary page WebView object corresponding to the target secondary page entrance in the WebView object pool.

[0016] Thirdly, embodiments of this application also provide a user terminal, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0017] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, can implement the above-described method.

[0018] This application provides a method, apparatus, terminal, and medium for opening pages in hybrid mobile applications. In this application, after the initial verification of the hybrid mobile application is passed, the user terminal preloads the homepage during the secondary verification process. After the secondary verification is passed, the homepage can be directly displayed based on the preloaded homepage WebView object, thereby improving the opening speed of the homepage. Furthermore, after opening the homepage, before the user clicks on a secondary page entry, preloading of the preloaded secondary page entry begins. When the user needs to open the secondary page corresponding to the preloaded secondary page entry, the corresponding secondary page can be directly displayed based on the corresponding secondary page WebView object, thereby improving the opening speed of secondary pages. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 A schematic diagram illustrating an application scenario for the page opening method of a hybrid mobile application provided in this application embodiment;

[0021] Figure 2 A flowchart illustrating the page opening method for a hybrid mobile application provided in this application embodiment;

[0022] Figure 3 A schematic diagram of a sub-process of a page opening method for a hybrid mobile application provided in an embodiment of this application;

[0023] Figure 4 A schematic diagram of a sub-process of a page opening method for a hybrid mobile application provided in an embodiment of this application;

[0024] Figure 5 A schematic block diagram of a page opening device for a hybrid mobile application provided in an embodiment of this application;

[0025] Figure 6 This is a schematic block diagram of a user terminal provided in an embodiment of this application. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0027] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0028] It should also be understood that the terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit the present application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0029] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0030] This application provides a method, apparatus, terminal, and medium for opening pages in hybrid mobile applications.

[0031] The execution entity of the hybrid mobile application page opening method can be the hybrid mobile application page opening device provided in the embodiments of this application, or a user terminal that integrates the hybrid mobile application page opening device. The user terminal can be a smartphone, tablet computer, PDA, or laptop computer, etc.

[0032] Please also refer to Figure 1 and Figure 2 ,in Figure 1 This is a schematic diagram illustrating a scenario of a hybrid mobile application page opening method according to an embodiment of the present invention. Figure 2 This is a flowchart illustrating the page opening method for a hybrid mobile application provided in an embodiment of the present invention. Figure 1 As shown, the hybrid mobile application page opening method provided in this embodiment of the invention is applied to a user terminal 10, which is communicatively connected to an application server 20. The user terminal 10 has a hybrid mobile application installed, and the login page (login UI, including the initial login native page and the secondary login native page) in the hybrid mobile application is implemented based on Native, i.e., the page type is a native page. Except for the login page, all other pages of the hybrid mobile application (the homepage and all secondary webpages) are implemented based on Web development, i.e., the page type is a webpage.

[0033] In this embodiment, when a user opens a page in a hybrid mobile application through user terminal 10, user terminal 10 can preload the web page that needs to be preloaded in advance through interaction with application server 20, thereby improving the opening speed of web page in hybrid mobile application.

[0034] like Figure 2 As shown, the method includes the following steps S110-S160.

[0035] S110. In response to the received user's launch command for the hybrid mobile application, open the initial login native page of the hybrid mobile application.

[0036] In this embodiment, to improve login security and prevent brute-force attacks by hackers, the hybrid mobile application provided in this embodiment has dual authentication. After the hybrid mobile application is initially launched, the initial login native page of the hybrid mobile application needs to be opened first for initial verification. Since the page type of the initial login native page is a native page, its loading speed is faster than that of a web page. Therefore, in this embodiment, after the user opens the hybrid mobile application, the user terminal can quickly respond to the launch command and open the initial login native page. The initial login native page includes a username input box, a login password input box, and an initial login confirmation button. The user can enter a username in the username input box and a login password in the login password input box. After clicking the initial login confirmation button, the user terminal will confirm the currently entered username and login password as the initial verification information.

[0037] S120. When the initial verification of the hybrid mobile application is determined to be successful based on the initial verification information entered by the user on the initial login native page, the secondary login native page of the hybrid mobile application is opened. At the same time, the homepage webpage of the hybrid mobile application is preloaded to obtain the homepage WebView object, and the homepage WebView object is stored in a preset WebView object pool.

[0038] In this embodiment, after the user enters initial verification information on the native login page, the initial verification of the hybrid mobile application is verified based on this initial verification information. Specifically, the initial verification information can be sent to the corresponding application server. The application server performs initial login verification based on the received initial verification information. If the verification is successful, it returns initial verification success information to the user terminal; otherwise, it returns initial verification failure information to the user terminal. If the initial verification fails, the user must re-enter the initial verification information on the native login page until the initial verification is successful or the number of consecutive initial verification failures exceeds a preset number.

[0039] Specifically, when the initial verification is successful, the user terminal opens the secondary login native page of the hybrid mobile application. Since the page type of the secondary login native page is a native page, its loading speed is faster than that of a web page. Therefore, in this embodiment, the secondary login native page can be opened quickly when the initial verification is successful. Furthermore, during the process of opening the secondary login native page and the user performing secondary verification login, the homepage web page is preloaded in advance to obtain and save the homepage WebView object, so that the user terminal can quickly open the homepage web page after the secondary verification is successful.

[0040] In this embodiment, after obtaining the homepage WebView object, the homepage WebView object is stored in a preset WebView object pool, so that after the user terminal passes the secondary verification, the homepage WebView object is quickly retrieved from the WebView object pool to open the homepage webpage.

[0041] In this embodiment, the JS-Bridge in the hybrid mobile application provides the user terminal with the ability to preload web pages, and enables bidirectional communication between the hybrid mobile application and the native code in the WebView component.

[0042] Specifically, this embodiment performs the preloading operation of the homepage webpage in the following three steps: Step 1, initialize WebView; Step 2, load the web resources corresponding to the homepage webpage; Step 3, render the page using WebView to obtain the homepage WebView object.

[0043] in:

[0044] Step 1, Initializing the WebView includes:

[0045] 1. Create a WebView instance: Create a WebView control instance through code. This process includes configuring the container view for the WebView and setting relevant properties (such as size, layout, etc.).

[0046] 2. Configure WebView: Perform some initialization configurations on the WebView to ensure it can correctly display webpage content. Common configuration items include: error handling, progress bar display, title bar, writing cookies, and configuration callbacks.

[0047] Step 2: Load the web resources corresponding to this homepage, including:

[0048] 1. Load the page document (HTML);

[0049] 2. Parse the HTML and load other resources such as CSS, JavaScript, and images;

[0050] 3. Request backend data (front-end and back-end separation architecture);

[0051] Step 3: WebView renders the page, including:

[0052] 1. Rendering the DOM

[0053] 2. Apply CSS styles

[0054] 3. Execute JavaScript (component modularization), etc.

[0055] It should be noted that after obtaining the WebView object (including the homepage WebView object and the secondary page WebView object) in this embodiment, it is necessary to control the visibility property of the WebView to achieve the hiding effect of the corresponding page and only display the page currently selected by the user.

[0056] S130. When it is determined that the secondary verification of the hybrid mobile application has passed based on the secondary verification information entered by the user on the secondary login native page, the homepage webpage is displayed according to the homepage WebView object in the WebView object pool. The homepage webpage includes secondary page entries for multiple secondary webpages.

[0057] The secondary verification information includes OPT verification information, facial recognition verification information, gesture password verification information, or fingerprint verification information. By verifying twice, the security of the application can be improved.

[0058] In this embodiment, after the user terminal obtains the secondary verification information based on the secondary login native page, it sends the secondary verification information to the corresponding application server. After the application server performs the verification operation on the secondary verification information, it returns the secondary verification result to the user terminal. When the secondary verification result is successful, the homepage webpage is displayed according to the pre-loaded homepage WebView object, thereby realizing the "instant opening" of the homepage webpage.

[0059] Specifically, the display of the corresponding page is controlled by adjusting the visibility property of the WebView object.

[0060] If the secondary verification fails, the user should be prompted to perform the secondary verification operation again until the secondary verification is successful or the number of consecutive secondary verification failures exceeds the preset number of secondary verifications.

[0061] S140. Based on the preset second-level page preloading prediction rules, determine at least one preloaded second-level page entry from the multiple second-level page entries.

[0062] In this embodiment, after the homepage is displayed, the secondary page preloading prediction rule is executed immediately. At least one preloaded secondary page entry is determined from the multiple secondary page entries in the homepage. This preloaded secondary page entry is the page entry corresponding to the webpage that needs to be preloaded.

[0063] This embodiment provides several methods for determining the preloaded secondary page entry, as follows:

[0064] Option 1:

[0065] Please see Figure 3 In this embodiment, the preloaded secondary page entry can be determined by analyzing the guidance information in the homepage. In this case, step S140 includes:

[0066] S1401a. Determine whether a target guidance pop-up exists in the homepage webpage based on the homepage WebView object. The target guidance pop-up contains a secondary page entry. If the target guidance pop-up exists, add the secondary page entry in the target guidance pop-up to the candidate entry set.

[0067] S1402a. Determine whether there is a secondary page entry with a target guide mark in the homepage webpage based on the homepage WebView object; if there is a secondary page entry with a target guide mark, add the secondary page entry with the target guide mark to the candidate entry set;

[0068] S1403a. Determine whether a target push message exists on the homepage webpage based on the homepage WebView object, wherein the push message contains a secondary page entry; if the push message exists, add the secondary page entry in the push message to the candidate entry set;

[0069] S1404a. Determine the preloaded secondary page entry based on the candidate entry set.

[0070] In this embodiment, the target guidance pop-up is a pop-up overlay on the homepage webpage. The pop-up overlay includes pop-up content and a button for a secondary page entry. The pop-up content covers the content area of ​​the homepage. In this embodiment, the secondary page entry in the target guidance pop-up is added to the candidate entry set as a candidate secondary page entry. Furthermore, it is determined whether each secondary page entry on the homepage webpage displays a target guidance mark. If a target guidance mark is displayed, the secondary page entry displaying the target guidance mark is added to the candidate entry set as a candidate secondary page entry. The target guidance mark includes at least one of a red dot, a small logo (such as HOT, NEW, etc.), and a number bubble. In addition, it is determined whether a target push message exists on the homepage webpage. If it exists, the secondary page entry in the target push message is added to the candidate entry set as a candidate secondary page entry.

[0071] In some embodiments, the target guidance pop-up can be any type of guidance pop-up, the target guidance marker can be any type of guidance marker, and the target push message can be any type of push message. In this case, it is necessary to filter the candidate secondary page entries in the candidate entry set.

[0072] At this point, determining the preloaded secondary page entry based on the candidate entry set includes: obtaining click behavior habit features corresponding to the currently logged-in user of the hybrid mobile application from the application server corresponding to the hybrid mobile application; and determining the preloaded secondary page entry based on the click behavior habit features and the candidate entry set.

[0073] Specifically, the click behavior habit feature is generated based on the current user's historical click behavior. The click behavior habit feature indicates the current user's interest-guided pop-up type, interest-guided tag type, and interest-push message type. At this time, the candidate secondary page entry corresponding to the interest-guided pop-up type, interest-guided tag type, and interest-push message type in the candidate entry set is determined as the preloaded secondary page entry.

[0074] In addition, if the number of preloaded secondary page entrances is greater than the preset number of preloaded entrances, then the number of preloaded secondary page entrances needs to be determined from the multiple preloaded secondary page entrances based on the historical click-through rates of each preloaded secondary page entrance from high to low.

[0075] Furthermore, in other embodiments, the aforementioned target guidance pop-up is a specific type of guidance pop-up, the target guidance marker is a specific type of guidance marker, and the target push message is a specific type of push message. In this case, the candidate secondary page entry included in the obtained candidate entry set is the secondary page entry corresponding to the specific type of guidance. In this case, determining the preloaded secondary page entry based on the candidate entry set includes: determining whether the number of preloaded secondary page entries in the candidate entry set is greater than the preset loading number. If it is greater than the preset loading number, then determining the number of preloaded secondary page entries from the multiple preloaded secondary page entries according to the historical click rate corresponding to each preloaded secondary page entry from high to low.

[0076] Option 2:

[0077] Please see Figure 4 In this embodiment, the preloaded secondary page entry can be determined by analyzing the guidance information in the homepage. In this case, step S140 includes:

[0078] S1401b: Obtain the historical click data of the currently logged-in user in the hybrid mobile application.

[0079] S1402b: Based on the historical click data and a preset statistical algorithm, determine the preloaded secondary page entry from multiple secondary page entries. The statistical algorithm includes a FIFO algorithm or an LRU algorithm.

[0080] In this embodiment, the historical click data of the currently logged-in user can be obtained from a local database or the application server corresponding to the hybrid mobile application. The historical click data includes the number of clicks and the click time of the user on each secondary page entry. Then, a preset number of preloaded items can be determined from multiple secondary page entries using a FIFO algorithm or an LRU algorithm. The number of preloaded items can be 5 or other values, such as 10. The specific value can be calculated based on the performance of the user terminal. The higher the performance, the more items can be preloaded.

[0081] S150. Perform a preloading operation on the secondary web pages corresponding to each of the preloaded secondary page entrances to obtain the secondary page WebView objects corresponding to each of the preloaded secondary page entrances, and store the secondary page WebView objects in the WebView object pool.

[0082] In this embodiment, after calculating one or more preloaded secondary page entry points, a preload operation is performed on each secondary webpage. The preload operation for the secondary webpage is similar to the preload operation for the homepage. The specific preload steps can be referred to the preload operation for the homepage described above, and will not be repeated here.

[0083] In this embodiment, after obtaining the second-level page WebView objects, each second-level page WebView object is stored in the WebView object pool.

[0084] S160. When a user's instruction to open a target secondary page entry in the preloaded secondary page entry is received, the target secondary webpage is displayed according to the secondary page WebView object corresponding to the target secondary page entry in the WebView object pool.

[0085] In this embodiment, when a user clicks on the entry point of a target secondary page that has already undergone webpage preloading from the homepage, the user terminal can display the target secondary webpage according to the corresponding secondary page WebView object in the WebView object pool, thus achieving "instant opening" of the secondary webpage.

[0086] Specifically, the visibility property of the WebView object corresponding to the target secondary webpage is set to show, while the visibility property of the homepage WebView object is set to hide.

[0087] In some embodiments, after opening the secondary login native page of the hybrid mobile application, the method further includes:

[0088] When a user's instruction to open a non-preloaded secondary page entry point on the homepage is received, the non-preloaded secondary page corresponding to the non-preloaded secondary page entry point is loaded to obtain a non-preloaded secondary page WebView object; the non-preloaded secondary page is displayed based on the non-preloaded secondary page WebView object; when a user's instruction to close the non-preloaded secondary page is received, the non-preloaded secondary page WebView object is stored in a preset WebView object pool, which stores the homepage WebView object and the secondary page WebView object.

[0089] Specifically, in this embodiment, when accessing a non-preloaded secondary page entry (the corresponding secondary page has not undergone preloading) through the homepage, the non-preloaded secondary page is loaded to obtain a corresponding non-preloaded secondary page WebView object. The corresponding non-preloaded secondary page is then displayed based on this WebView object. When a user's close command for the non-preloaded secondary page is received, for example, when switching back to the homepage, this embodiment does not directly destroy the corresponding WebView object. Instead, it controls the visibility property of the corresponding WebView object to achieve a hiding effect and stores the non-preloaded secondary page WebView object in a preset WebView object pool. This allows for "instant opening" of the page when the user accesses the secondary page again.

[0090] Furthermore, to prevent the WebView object pool from overloading and impacting terminal performance, this embodiment includes a WebView object destruction strategy. This strategy enables the updating and destruction of WebView objects. For example, if the number of WebView objects in the pool exceeds a preset threshold, the WebView objects need to be destroyed. Specifically, this can be done by destroying the WebView object with the lowest weight based on its preset weight, or by destroying the WebView object with the oldest usage time based on its most recent usage time.

[0091] In some embodiments, after performing preloading operations on the secondary web pages corresponding to each of the preloaded secondary page entry points to obtain secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and storing the secondary page WebView objects in the WebView object pool, the method further includes:

[0092] When a shutdown command is received for the hybrid mobile application, preload hit information corresponding to each of the preloaded secondary page entry points is sent to the application server corresponding to the hybrid mobile application, so that the application server updates the secondary page preload prediction rule according to the preload hit information and sends the updated secondary page preload prediction rule to the user terminal.

[0093] The updated second-level page preloading prediction rule can be issued when the user terminal reopens the hybrid mobile application. Corresponding to the above scheme one, the updated second-level page preloading prediction rule in this embodiment can update the type of interest-guided pop-up, the type of interest-guided marker, and the type of interest-push message. Corresponding to the above scheme two, the application server in this embodiment can calculate the user's hit rate based on the FIFO algorithm and the hit rate based on the LRU algorithm, and then update the statistical algorithm with the higher hit rate to the target statistical algorithm. The target statistical algorithm is the statistical algorithm used by the user terminal when determining the preloaded second-level page entry when the user terminal reopens the hybrid mobile application.

[0094] In summary, in this embodiment, after the initial verification of the hybrid mobile application is passed, the user terminal preloads the homepage during the secondary verification process. After the secondary verification is passed, the homepage can be directly displayed based on the preloaded homepage WebView object, thereby improving the opening speed of the homepage. Furthermore, after opening the homepage, the preload of the secondary page entry begins before the user clicks on it. When the user needs to open the secondary page corresponding to the preloaded secondary page entry, the corresponding secondary page can be directly displayed based on the corresponding secondary page WebView object, thereby improving the opening speed of the secondary page.

[0095] Figure 5 This is a schematic block diagram of a hybrid mobile application page opening device 500 provided in an embodiment of this application. Figure 5 As shown, corresponding to the above-described hybrid mobile application page opening method, this application also provides a hybrid mobile application page opening device 500. This hybrid mobile application page opening device 500 includes a unit for executing the above-described hybrid mobile application page opening method. This hybrid mobile application page opening device 500 can be configured in a user terminal, where a hybrid mobile application is installed. Specifically, please refer to... Figure 5 The page opening device 500 for the hybrid mobile application includes a transceiver unit 501 and a processing unit 502.

[0096] The acquisition unit is used to acquire the user's launch command for the hybrid mobile application;

[0097] Processing unit 502 is configured to, in response to a received user launch command for the hybrid mobile application, open the initial login native page of the hybrid mobile application; when the initial verification of the hybrid mobile application is confirmed to be successful based on the initial verification information entered by the user on the initial login native page, open the secondary login native page of the hybrid mobile application, and simultaneously preload the homepage of the hybrid mobile application to obtain a homepage WebView object, and store the homepage WebView object in a preset WebView object pool; when the secondary verification of the hybrid mobile application is confirmed to be successful based on the secondary verification information entered by the user on the secondary login native page, display the homepage WebView object in the WebView object pool. A homepage webpage includes multiple secondary page entry points for secondary webpages. Based on a preset secondary page preloading prediction rule, at least one secondary page entry point is determined from the multiple secondary page entry points for preloading. Preloading operations are performed on the secondary webpages corresponding to each preloaded secondary page entry point to obtain secondary page WebView objects corresponding to each preloaded secondary page entry point, and these secondary page WebView objects are stored in a WebView object pool. When a user's instruction to open a page for a target secondary page entry point among the preloaded secondary page entry points is received, the target secondary webpage is displayed according to the secondary page WebView object corresponding to the target secondary page entry point in the WebView object pool.

[0098] In some embodiments, when the processing unit 502 performs the step of determining at least one preloaded secondary page entry from a plurality of secondary page entries according to a preset secondary page preloading prediction rule, it is specifically used for:

[0099] Based on the homepage WebView object, determine whether a target onboarding pop-up exists on the homepage webpage, and the target onboarding pop-up contains a secondary page entry; if the target onboarding pop-up exists, add the secondary page entry in the target onboarding pop-up to the candidate entry set; based on the homepage WebView object, determine whether a secondary page entry including a target onboarding marker exists on the homepage webpage; if the secondary page entry including the target onboarding marker exists, add the secondary page entry including the target onboarding marker to the candidate entry set; based on the homepage WebView object, determine whether a target push message exists on the homepage webpage, and the push message contains a secondary page entry; if the push message exists, add the secondary page entry in the push message to the candidate entry set; determine the preloaded secondary page entry based on the candidate entry set.

[0100] In some embodiments, when the processing unit 502 performs the step of determining the preloaded secondary page entry based on the candidate entry set, it is specifically used for:

[0101] Obtain click behavior habit features corresponding to the currently logged-in user of the hybrid mobile application from the application server corresponding to the hybrid mobile application; determine the preloaded secondary page entry based on the click behavior habit features and the candidate entry set.

[0102] In some embodiments, when the processing unit 502 performs the step of determining at least one preloaded secondary page entry from a plurality of secondary page entries according to a preset secondary page preloading prediction rule, it is specifically used for:

[0103] The transceiver unit 501 acquires the historical click data of the currently logged-in user in the hybrid mobile application; based on the historical click data and a preset statistical algorithm, the preloaded secondary page entry is determined from multiple secondary page entry points, and the statistical algorithm includes the FIFO algorithm or the LRU algorithm.

[0104] In some embodiments, after performing the steps of preloading the secondary web pages corresponding to each of the preloaded secondary page entry points, obtaining the secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and storing the secondary page WebView objects in the WebView object pool, the processing unit 502 is further configured to:

[0105] When a shutdown command is received for the hybrid mobile application, the transceiver unit 501 sends preload hit information corresponding to each preloaded secondary page entry to the application server corresponding to the hybrid mobile application, so that the application server updates the secondary page preload prediction rule according to the preload hit information and sends the updated secondary page preload prediction rule to the user terminal.

[0106] In some embodiments, after performing the step of opening the secondary login native page of the hybrid mobile application, the processing unit 502 is further configured to:

[0107] When a user's instruction to open a non-preloaded secondary page entry point on the homepage is received, the non-preloaded secondary page corresponding to the non-preloaded secondary page entry point is loaded to obtain a non-preloaded secondary page WebView object; the non-preloaded secondary page is displayed based on the non-preloaded secondary page WebView object; when a user's instruction to close the non-preloaded secondary page is received, the non-preloaded secondary page WebView object is stored in a preset WebView object pool, which stores the homepage WebView object and the secondary page WebView object.

[0108] In some embodiments, the initial verification information includes a username and a login password; the secondary verification information includes OPT verification information, facial recognition verification information, gesture password verification information, or fingerprint verification information.

[0109] In summary, the embodiments of this application, through the hybrid mobile application page opening device 500, preload the homepage webpage during the secondary verification process after the initial verification of the hybrid mobile application passes. After the secondary verification passes, the homepage webpage can be directly displayed based on the preloaded homepage WebView object, thereby improving the opening speed of the homepage webpage. Furthermore, after opening the homepage webpage, the preloading of the preloaded secondary page entry begins before the user clicks on the secondary page entry. When the user needs to open the secondary webpage corresponding to the preloaded secondary page entry, the corresponding secondary webpage can be directly displayed based on the corresponding secondary page WebView object, thereby improving the opening speed of the secondary page.

[0110] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the page opening device and each unit of the above-mentioned hybrid mobile application can be referred to the corresponding description in the foregoing method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0111] The page opening device for the aforementioned hybrid mobile application can be implemented as a computer program, which can, for example... Figure 6 It runs on the user terminal shown.

[0112] Please see Figure 6 , Figure 6 This is a schematic block diagram of a user terminal provided in an embodiment of this application. The user terminal 10 has a hybrid mobile application installed, see reference... Figure 6The user terminal 10 includes a processor 602, a memory, and a network interface 605 connected via a system bus 601. The memory may include a non-volatile storage medium 603 and internal memory 604.

[0113] The non-volatile storage medium 603 may store an operating system 6031 and a computer program 6032. The computer program 6032 includes program instructions that, when executed, cause the processor 602 to perform a hybrid mobile application page opening method.

[0114] The processor 602 provides computing and control capabilities to support the operation of the entire user terminal 10.

[0115] The internal memory 604 provides an environment for the execution of the computer program 6032 in the non-volatile storage medium 603. When the computer program 6032 is executed by the processor 602, the processor 602 can execute a page opening method for a hybrid mobile application.

[0116] This network interface 605 is used for network communication with other devices. Those skilled in the art will understand that... Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the user terminal 10 to which the present application is applied. The specific user terminal 10 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0117] The processor 602 is used to run a computer program 6032 stored in the memory to perform the following steps:

[0118] In response to the received user launch command for the hybrid mobile application, the initial login native page of the hybrid mobile application is opened;

[0119] When the initial verification of the hybrid mobile application is determined to be successful based on the initial verification information entered by the user on the initial login native page, the secondary login native page of the hybrid mobile application is opened. At the same time, the home page of the hybrid mobile application is preloaded to obtain the home page WebView object, and the home page WebView object is stored in a preset WebView object pool.

[0120] When the secondary verification of the hybrid mobile application is determined to be successful based on the secondary verification information entered by the user on the secondary login native page, the homepage webpage is displayed according to the homepage WebView object in the WebView object pool. The homepage webpage includes secondary page entries for multiple secondary webpages.

[0121] Based on the preset second-level page preloading prediction rules, at least one preloaded second-level page entry is determined from the multiple second-level page entry points;

[0122] Perform a preloading operation on the secondary web pages corresponding to each of the preloaded secondary page entry points to obtain the secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and store the secondary page WebView objects in the WebView object pool;

[0123] When a user's instruction to open a target secondary page entry in the preloaded secondary page entry is received, the target secondary web page is displayed according to the secondary page WebView object corresponding to the target secondary page entry in the WebView object pool.

[0124] It should be understood that in the embodiments of this application, the processor 602 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0125] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0126] Therefore, this application also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions. When executed by a processor, the program instructions cause the processor to perform the following steps:

[0127] In response to the received user launch command for the hybrid mobile application, the initial login native page of the hybrid mobile application is opened;

[0128] When the initial verification of the hybrid mobile application is determined to be successful based on the initial verification information entered by the user on the initial login native page, the secondary login native page of the hybrid mobile application is opened. At the same time, the home page of the hybrid mobile application is preloaded to obtain the home page WebView object, and the home page WebView object is stored in a preset WebView object pool.

[0129] When the secondary verification of the hybrid mobile application is determined to be successful based on the secondary verification information entered by the user on the secondary login native page, the homepage webpage is displayed according to the homepage WebView object in the WebView object pool. The homepage webpage includes secondary page entries for multiple secondary webpages.

[0130] Based on the preset second-level page preloading prediction rules, at least one preloaded second-level page entry is determined from the multiple second-level page entry points;

[0131] Perform a preloading operation on the secondary web pages corresponding to each of the preloaded secondary page entry points to obtain the secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and store the secondary page WebView objects in the WebView object pool;

[0132] When a user's instruction to open a target secondary page entry in the preloaded secondary page entry is received, the target secondary web page is displayed according to the secondary page WebView object corresponding to the target secondary page entry in the WebView object pool.

[0133] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0134] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0135] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0136] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0137] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a user terminal (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0138] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for opening a page in a hybrid mobile application, characterized in that, The method is applied to a user terminal, wherein a hybrid mobile application is installed on the user terminal, and the method includes: In response to the received user launch command for the hybrid mobile application, the initial login native page of the hybrid mobile application is opened; When the initial verification of the hybrid mobile application is determined to be successful based on the initial verification information entered by the user on the initial login native page, the secondary login native page of the hybrid mobile application is opened. At the same time, the home page of the hybrid mobile application is preloaded to obtain the home page WebView object, and the home page WebView object is stored in a preset WebView object pool. When the secondary verification of the hybrid mobile application is determined to be successful based on the secondary verification information entered by the user on the secondary login native page, the homepage webpage is displayed according to the homepage WebView object in the WebView object pool. The homepage webpage includes secondary page entries for multiple secondary webpages. Based on the preset second-level page preloading prediction rules, at least one preloaded second-level page entry is determined from the multiple second-level page entry points; Perform a preloading operation on the secondary web pages corresponding to each of the preloaded secondary page entry points to obtain the secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and store the secondary page WebView objects in the WebView object pool; When a user's instruction to open a target secondary page entry in the preloaded secondary page entry is received, the target secondary web page is displayed according to the secondary page WebView object corresponding to the target secondary page entry in the WebView object pool.

2. The method according to claim 1, characterized in that, The second-level page preloading prediction rule includes a first prediction sub-rule, a second prediction sub-rule, and a third prediction sub-rule; the step of determining at least one preloaded second-level page entry from the plurality of second-level page entry points according to the preset second-level page preloading prediction rule includes: Based on the first prediction sub-rule, determine whether there is a target guidance pop-up in the homepage webpage according to the homepage WebView object. The target guidance pop-up contains a secondary page entry. If the target guidance pop-up exists, add the secondary page entry in the target guidance pop-up to the candidate entry set. Based on the second prediction sub-rule, determine whether there is a secondary page entry with a target guide mark in the homepage webpage according to the homepage WebView object; if there is a secondary page entry with a target guide mark, add the secondary page entry with a target guide mark to the candidate entry set; Based on the third prediction sub-rule, it is determined whether a target push message exists on the homepage webpage according to the homepage WebView object, and the push message contains a secondary page entry; if the push message exists, the secondary page entry in the push message is added to the candidate entry set. The preloaded secondary page entry is determined based on the candidate entry set.

3. The method according to claim 2, characterized in that, The step of determining the preloaded secondary page entry based on the candidate entry set includes: Obtain click behavior habit characteristics corresponding to the currently logged-in user of the hybrid mobile application from the application server corresponding to the hybrid mobile application; The preloaded secondary page entry is determined based on the click behavior habits and the candidate entry set.

4. The method according to claim 1, characterized in that, The step of determining at least one preloaded secondary page entry from multiple secondary page entry points according to a preset secondary page preloading prediction rule includes: Obtain the historical click data of the currently logged-in user in the hybrid mobile application; Based on the historical click data and a preset statistical algorithm, the preloaded secondary page entry is determined from multiple secondary page entry points. The statistical algorithm includes a FIFO algorithm or an LRU algorithm.

5. The method according to claim 1, characterized in that, After performing preloading operations on the secondary web pages corresponding to each of the preloaded secondary page entry points to obtain the secondary page WebView objects corresponding to each of the preloaded secondary page entry points, and storing the secondary page WebView objects in the WebView object pool, the method further includes: When a shutdown command is received for the hybrid mobile application, preload hit information corresponding to each of the preloaded secondary page entry points is sent to the application server corresponding to the hybrid mobile application, so that the application server updates the secondary page preload prediction rule according to the preload hit information and sends the updated secondary page preload prediction rule to the user terminal.

6. The method according to claim 1, characterized in that, After opening the secondary login native page of the hybrid mobile application, the method further includes: When a user's instruction to open a non-preloaded secondary page entry in the homepage is received, the non-preloaded secondary page corresponding to the non-preloaded secondary page entry is loaded to obtain the non-preloaded secondary page WebView object corresponding to the non-preloaded secondary page entry. The non-preloaded second-level webpage is displayed based on the non-preloaded second-level webpage WebView object; When a user closes the non-preloaded secondary webpage, the WebView object of the non-preloaded secondary webpage is stored in the WebView object pool.

7. The method according to claim 1, characterized in that, The initial verification information includes the username and login password; the secondary verification information includes OPT verification information, facial recognition verification information, gesture password verification information, or fingerprint verification information.

8. A page opening device for a hybrid mobile application, characterized in that, The page opening device for the hybrid mobile application is deployed on a user terminal, which has the hybrid mobile application installed. The page opening device for the hybrid mobile application includes: The acquisition unit is used to acquire the user's launch command for the hybrid mobile application; The processing unit is configured to, in response to a received user launch command for the hybrid mobile application, open the initial login native page of the hybrid mobile application; when the initial verification of the hybrid mobile application is confirmed to be successful based on the initial verification information entered by the user on the initial login native page, open the secondary login native page of the hybrid mobile application, and simultaneously preload the homepage of the hybrid mobile application to obtain a homepage WebView object, and store the homepage WebView object in a preset WebView object pool; when the secondary verification of the hybrid mobile application is confirmed to be successful based on the secondary verification information entered by the user on the secondary login native page, display the homepage according to the homepage WebView object in the WebView object pool. A webpage, the homepage of which includes multiple secondary page entrances to secondary webpages; according to a preset secondary page preloading prediction rule, at least one secondary page entrance is determined from the multiple secondary page entrances for preloading; preloading operations are performed on the secondary webpages corresponding to each preloaded secondary page entrance to obtain secondary page WebView objects corresponding to each preloaded secondary page entrance, and the secondary page WebView objects are stored in the WebView object pool; when a user's page opening instruction for a target secondary page entrance among the preloaded secondary page entrances is received, the target secondary webpage is displayed according to the secondary page WebView object corresponding to the target secondary page entrance in the WebView object pool.

9. A user terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The user terminal has a hybrid mobile application installed, and when the processor executes the computer program, it implements the page opening method of the hybrid mobile application as described in any one of claims 1-7.

10. A storage medium, characterized in that, The storage medium stores a computer program, which includes program instructions that, when executed by a processor, cause the processor to perform the page opening method of the hybrid mobile application as described in any one of claims 1-7.

Images