A front-end H5 application management method loaded on a mobile APP

Abstract

The present invention provides a front-end H5 application management method loaded on a mobile terminal APP, which relates to the field of Internet technology; the method includes the following steps: S10, defining basic attribute parameters of the front-end H5 application; S20, configuring the basic attribute parameters; S30, the mobile terminal APP obtains the information object of the front-end H5 application that needs to be accessed by calling the interface of the back-end server; S40, obtaining the information object of the front-end H5 application through step S30, and parsing the information of the front-end H5 application; S50, when the user accesses the front-end application, it is necessary to perform logical judgment according to the parameters in step S10 to determine whether to load the front-end H5 application currently to be loaded; S60, the front-end H5 application that needs to be displayed meets the conditions for being loaded, and at this time the mobile terminal APP loads and renders the front-end H5 application through a web view loader webview; the beneficial effect of the present invention is: solving the problem of unified management of all front-end H5 applications loaded on the mobile terminal APP.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and more specifically, to a front-end H5 application management method loaded on a mobile APP. Background Art

[0002] With the continuous development of the information age, people use mobile devices in more and more places, and at the same time, more and more applications use H5 (HyperText Markup Language 5, HTML5) pages in mobile devices.

[0003] However, the following issues generally arise: First, when existing mobile apps load front-end H5 applications, they often only do so through a redirect URL, failing to manage other aspects of the entire front-end H5 application. Second, the release frequency of existing mobile apps and front-end H5 applications differs. Furthermore, even if the latest version of an app is released on the app store, a large portion of users are still using older versions. Once the front-end H5 application is deployed, it accesses the latest H5 application. In this case, if certain features implemented in the latest H5 application require the latest version of the app to function, problems such as display anomalies may occur when the older version of the app accesses the front-end H5 application. Third, existing mobile apps generally only load and display the front-end H5 application they need to access, failing to restrict the user groups that can access the front-end H5 application. Fourth, when existing mobile apps load multiple access points for the same front-end H5 application, their presentation cannot be consistent, and fixing issues may require multiple modifications. Fifth, the existing mobile APP loads a front-end H5 application. When problems occur with the front-end H5 application, effective management cannot be performed. Summary of the Invention

[0004] In order to overcome the shortcomings of the prior art, the present invention provides a front-end H5 application management method loaded on a mobile APP.

[0005] The technical solution adopted by the present invention to solve the technical problem is: a front-end H5 application management method loaded on a mobile terminal APP, the improvement of which is that the method includes the following steps:

[0006] S10. Define basic attribute parameters of the front-end H5 application, which defines the basic attribute parameters of the application information required when the mobile APP loads and displays the front-end H5 application;

[0007] S20: configuring basic attribute parameters, completing the configuration of basic attribute parameters through the operation management system and saving them to the backend server;

[0008] S30. The mobile app obtains the information object of the front-end H5 application that needs to be accessed by calling the interface of the back-end server;

[0009] S40. Obtain the information object of the front-end H5 application through step S30, parse the information of the front-end H5 application, and display the display attribute information of the front-end H5 application at the entrance of the mobile terminal APP displaying the front-end H5 application;

[0010] S50: When the user accesses the front-end application, a logical judgment is performed based on the parameters in step S10 to determine whether to load the front-end H5 application currently to be loaded;

[0011] S60: The front-end H5 application to be displayed meets the loading conditions. At this time, the mobile APP loads and renders the front-end H5 application through the web view loader webview.

[0012] Furthermore, in step S10, the attributes required when the mobile APP loads the front-end H5 application are defined, and common attribute parameters are extracted as the basic attribute parameters of all front-end H5 applications, which are used for unified management parameters of the front-end H5 application mathematics.

[0013] Furthermore, step S10 includes the following steps:

[0014] S101. Define the menuId parameter as the unique identifier of the front-end H5 application to ensure the uniqueness of the front-end H5 application and serve as the basis for determining the uniqueness of the front-end H5 application;

[0015] S102. Define the url parameter as the required access path for the front-end H5 application, which is used by the mobile app to load the network address of the front-end H5 application;

[0016] S103. Define the title parameter as the title of the front-end H5 application, and the title displayed when the mobile app loads the front-end H5 application and uses the navigation bar;

[0017] S104. Define the icon parameter as the remote resource address of the icon displayed by the front-end H5 application;

[0018] S105. Define the news parameter as a superscript description of the front-end H5 application, which is used to implement a recommended description of the front-end H5 application function;

[0019] S106. Define the versionSupport parameter as the minimum mobile APP version number that can normally display the front-end H5 application, which is used to intercept and prompt the jump of unsupported low-version mobile APP;

[0020] S107. Define the errorMsg parameter as a message to block the user's redirection and the corresponding description when a production problem occurs in the application.

[0021] S108. Define the userType parameter as an identifier of the user access type for accessing the front-end H5 application, to intercept users who do not meet the requirements and provide corresponding operations;

[0022] S109. Define the navigation parameter as an identifier to indicate whether the front-end H5 application uses the native navigation bar.

[0023] S110. Define the authType parameter as an identifier for whether to display the current front-end H5 application, and use the value of this parameter to determine whether to display the current entrance to the user who is currently using the mobile APP.

[0024] Furthermore, step S20 includes the following steps:

[0025] S201, the basic attribute parameters obtained in step S10 are used to meet the management of the general front-end H5 application by the mobile terminal APP;

[0026] The mobile app obtains basic attribute parameter information to complete the entry stack and access control of the front-end H5 application that the mobile app needs to access;

[0027] S202. Implement a front-end H5 application operation and management platform through front-end development of the Vue technology stack, which is used to configure the basic attribute parameters of the front-end H5 application, including setting the values ​​of the menuId, url, title, icon, news, versionSupport, errorMsg, userType, navigation, and authType fields;

[0028] S203: Save the data corresponding to the parameters configured in step S202 to the backend server for use by the mobile APP.

[0029] Furthermore, step S30 includes the following steps:

[0030] S301. The backend server provides different interfaces for the mobile APP to call and display according to the application display scenario of the mobile APP;

[0031] S302. The mobile APP calls the corresponding interface provided by the backend server according to the usage scenario to obtain the front-end H5 application information configured in the operation management system in S20. This information includes the front-end basic attribute parameter element object in S10 of the front-end H5 application that needs to be accessed.

[0032] Furthermore, step S40 includes the following steps:

[0033] S401. Parse the front-end H5 application information obtained in step S30 one by one according to the agreement in step S10.

[0034] S402. Get the current authType value according to the authTyp parameter;

[0035] If the value is a wildcard type, the front-end H5 application entrance will be displayed;

[0036] If the value is a blacklist type, if the current user is in the blacklist, the front-end H5 application entrance will not be displayed;

[0037] If the value is a whitelist type, the front-end H5 application entrance will be displayed if the current user is in the whitelist, otherwise it will not be displayed;

[0038] S403. Selectively display the front-end H5 application information based on the usage scenario;

[0039] S404. According to the title parameter, obtain the value of the current front-end H5 application title and use it as the title displayed at the front-end H5 application entrance;

[0040] S405. According to the image icon parameter, obtain the remote address of the application icon of the front-end H5 application, and display the icon when the front-end H5 application entrance needs to display the icon;

[0041] S406: Get the subscript value of the front-end H5 application according to the subscript news parameter. If there is a value, expand the value. Step S50 includes the following steps:

[0042] S501. According to the minimum version support versionSupport parameter in step S10, obtain the minimum access supported mobile APP version of the front-end H5 application, and compare the value with the current mobile APP version:

[0043] If the current mobile APP version is lower than the obtained versionSupport version, the user is prevented from accessing the current front-end H5 application and a pop-up window prompts the user that the version is not supported, and provides a quick entry to upgrade the mobile APP version;

[0044] If the current mobile APP version supports a version greater than or equal to the obtained versionSupport version, then proceed to the next logical judgment;

[0045] S502. According to the user access type parameter userType in step S10, obtain the user permission type that the front-end H5 application can access, and compare it with the user type currently using the mobile APP:

[0046] If the user permission type is not accessible, the current user will not be allowed to access the front-end H5 application and a corresponding prompt will be given;

[0047] If the user permission type is accessible, proceed to the next logical judgment;

[0048] S503. According to the errorMsg parameter of the application error information in step S10, a value is obtained as to whether the front-end H5 application has an exception. This is used when the front-end H5 application is undergoing an upgrade deployment or an exception occurs in the front-end H5 application.

[0049] When the errorMsg parameter has a value, the access to the front-end H5 application is intercepted and the error message is notified to the user to prevent the front-end application from being accessed during problems or maintenance.

[0050] Furthermore, step S60 includes the following steps:

[0051] S601. According to the navigation parameter of whether the native navigation bar is used in step S10, whether the front-end H5 application uses the native navigation bar is obtained, and the scanning bar properties corresponding to the controller are controlled;

[0052] S602, the mobile APP loads and renders the front-end H5 application through the web view control;

[0053] S603. According to the menu menuId parameter in step S10, obtain the unique identifier of the front-end H5 application, which is used to record the number of visits and visit time of the menu.

[0054] Furthermore, step S60 further includes step S70, and step S70 includes:

[0055] S701. Obtain the redirect address of the current front-end H5 application based on the URL parameter of the front-end H5 application, and determine whether there is an agreed protocol header for jumping to the native function page of the mobile app;

[0056] If so, it will jump to the native page according to the pre-agreed jump function module. In this way, the dynamic configuration and display of certain functions of the mobile APP can be completed.

[0057] The beneficial effects of the present invention are: solving the problem of unified management of all front-end H5 applications loaded on mobile APP; achieving a unified management effect of common elements such as unique identification, URL, minimum supported version, new version prompt, native navigation support, etc. for each application. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 This is a flow chart of a front-end H5 application management method loaded on a mobile APP of the present invention.

[0059] Figure 2 This is a diagram showing a specific embodiment of a front-end H5 application management method loaded on a mobile APP of the present invention. DETAILED DESCRIPTION

[0060] The present invention will be further described below with reference to the accompanying drawings and examples.

[0061] The following will clearly and completely describe the concept, specific structure and technical effects of the present invention in combination with the embodiments and drawings, so as to fully understand the purpose, characteristics and effects of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention. In addition, all the connection / connection relationships involved in the patent do not refer to the direct connection of components, but refer to the fact that a better connection structure can be formed by adding or reducing connection accessories according to the specific implementation situation. The various technical features in the invention can be combined interactively without conflicting with each other.

[0062] Reference Figure 1 、 Figure 2 As shown, the present invention discloses a front-end H5 application management method loaded on a mobile terminal APP. Specifically, the method includes the following steps:

[0063] S10. Define basic attribute parameters of the front-end H5 application, which defines the basic attribute parameters of the application information required when the mobile APP loads and displays the front-end H5 application;

[0064] In step S10, the attributes required when the mobile APP loads the front-end H5 application are defined, and common attribute parameters are extracted as the basic attribute parameters of all front-end H5 applications, which are used for unified management parameters of the front-end H5 application mathematics.

[0065] In this embodiment, step S10 includes the following steps:

[0066] S101. Define the menuId parameter as the unique identifier of the front-end H5 application to ensure the uniqueness of the front-end H5 application and serve as the basis for determining the uniqueness of the front-end H5 application; as well as for subsequent application usage statistics and other functions;

[0067] S102. Define the url parameter as the required access path for the front-end H5 application, which is used by the mobile app to load the network address of the front-end H5 application;

[0068] S103. Define the title parameter as the title of the front-end H5 application, and the title displayed when the mobile app loads the front-end H5 application and uses the navigation bar;

[0069] S104. Define the icon parameter as the remote resource address of the icon displayed by the front-end H5 application;

[0070] S105. Define the news parameter as a superscript description of the front-end H5 application, which is used to implement a recommended description of the front-end H5 application function;

[0071] S106. Define the versionSupport parameter as the minimum mobile APP version number that can normally display the front-end H5 application, which is used to intercept and prompt the jump of unsupported low-version mobile APP;

[0072] S107. Define the errorMsg parameter as a message to block the user's redirection and the corresponding description when a production problem occurs in the application.

[0073] S108. Define the userType parameter as an identifier of the user access type for accessing the front-end H5 application, to intercept users who do not meet the requirements and provide corresponding operations;

[0074] S109. Define the navigation parameter as an identifier to indicate whether the front-end H5 application uses the native navigation bar.

[0075] S110. Define the authType parameter as an identifier for whether to display the current front-end H5 application, and use the value of this parameter to determine whether to display the current entrance to the user who is currently using the mobile APP.

[0076] S20: configuring basic attribute parameters, completing the configuration of basic attribute parameters through the operation management system and saving them to the backend server;

[0077] Step S20 includes the following steps:

[0078] S201. The basic attribute parameters obtained in step S10 are used to meet the management of the general front-end H5 application by the mobile terminal APP; these basic attribute parameters need to be made dynamically configurable;

[0079] The mobile app obtains basic attribute parameter information to complete the entry stack and access control of the front-end H5 application that the mobile app needs to access;

[0080] S202. Implement a front-end H5 application operation and management platform through front-end development of the Vue technology stack, which is used to configure the basic attribute parameters of the front-end H5 application, including setting the values ​​of the menuId, url, title, icon, news, versionSupport, errorMsg, userType, navigation, and authType fields;

[0081] S203: Save the data corresponding to the parameters configured in step S202 to the backend server for use by the mobile APP.

[0082] S30. The mobile app obtains the information object of the front-end H5 application that needs to be accessed by calling the interface of the back-end server;

[0083] Step S30 includes the following steps:

[0084] S301. The backend server provides different interfaces for the mobile APP to call and display according to the application display scenario of the mobile APP;

[0085] S302. The mobile app calls the corresponding interface provided by the backend server according to the usage scenario to obtain the front-end H5 application information configured in the operation management system in S20. This information includes the front-end basic attribute parameter element object in S10 of the front-end H5 application that needs to be accessed; This information includes all the front-end basic attribute parameter element objects agreed in S10 of the front-end H5 front-end that needs to be accessed;

[0086] S40. Obtain the information object of the front-end H5 application through step S30, parse the information of the front-end H5 application, and display the display attribute information of the front-end H5 application at the entrance of the mobile terminal APP displaying the front-end H5 application;

[0087] Step S40 includes the following steps:

[0088] S401. Parse the front-end H5 application information obtained in step S30 one by one according to the agreement in step S10.

[0089] S402. Get the current authType value according to the authTyp parameter;

[0090] If the value is a wildcard type, the front-end H5 application entrance will be displayed;

[0091] If the value is a blacklist type, if the current user is in the blacklist, the front-end H5 application entrance will not be displayed;

[0092] If the value is a whitelist type, the front-end H5 application entrance will be displayed if the current user is in the whitelist, otherwise it will not be displayed;

[0093] S403. Selectively display the front-end H5 application information based on the usage scenario;

[0094] S404. According to the title parameter, obtain the value of the current front-end H5 application title and use it as the title displayed at the front-end H5 application entrance;

[0095] S405. According to the image icon parameter, obtain the remote address of the application icon of the front-end H5 application, and display the icon when the front-end H5 application entrance needs to display the icon;

[0096] S406. According to the subscript news parameter, obtain the subscript value of the front-end H5 application. If there is a value, display the value at the entrance of the current front-end H5 application to recommend the new application.

[0097] S50: When the user accesses the front-end application, a logical judgment is performed based on the parameters in step S10 to determine whether to load the front-end H5 application currently to be loaded;

[0098] Step S50 includes the following steps:

[0099] S501. According to the minimum version support versionSupport parameter in step S10, obtain the minimum access supported mobile APP version of the front-end H5 application, and compare the value with the current mobile APP version:

[0100] If the current mobile APP version is lower than the obtained versionSupport version, the user is prevented from accessing the current front-end H5 application and a pop-up window prompts the user that the version is not supported, and provides a quick entry to upgrade the mobile APP version;

[0101] If the current mobile APP version supports a version greater than or equal to the obtained versionSupport version, then proceed to the next logical judgment;

[0102] S502. According to the user access type parameter userType in step S10, obtain the user permission type that the front-end H5 application can access, and compare it with the user type currently using the mobile APP:

[0103] If the user permission type is not accessible, the current user will not be allowed to access the front-end H5 application and a corresponding prompt will be given;

[0104] If the user permission type is accessible, proceed to the next logical judgment;

[0105] S503. According to the errorMsg parameter of the application error information in step S10, a value is obtained as to whether the front-end H5 application has an exception. This is used when the front-end H5 application is undergoing an upgrade deployment or an exception occurs in the front-end H5 application.

[0106] When the errorMsg parameter has a value, the access to the front-end H5 application is intercepted and the error message is notified to the user to prevent the front-end application from being accessed during problems or maintenance.

[0107] When the errorMsg parameter has no value, it indicates that the front-end H5 application is normal and can be accessed normally.

[0108] S60: The front-end H5 application to be displayed meets the loading conditions. At this time, the mobile APP loads and renders the front-end H5 application through the web view loader webview.

[0109] Step S60 includes the following steps:

[0110] S601. Based on the navigation parameter of whether the native navigation bar is used in step S10, obtain whether the front-end H5 application uses the native navigation bar, and control the corresponding shopping bar properties of the controller; to prevent the switching effect caused by controlling the display and hiding of the navigation bar through JavaScript script code when loading the front-end H5 application;

[0111] S602, the mobile APP loads and renders the front-end H5 application through the web view control;

[0112] S603. According to the menu menuId parameter in step S10, obtain the unique identifier of the front-end H5 application, which is used to record the number of visits and visit time of the menu.

[0113] In the above embodiment, step S60 is followed by step S70, and step S70 includes:

[0114] S701. Obtain the redirect address of the current front-end H5 application based on the URL parameter of the front-end H5 application, and determine whether there is an agreed protocol header for jumping to the native function page of the mobile app;

[0115] If so, it will jump to the native page according to the pre-agreed jump function module. In this way, the dynamic configuration and display of certain functions of the mobile APP can be completed.

[0116] Moreover, in this embodiment, when the same front-end H5 application has different scenarios such as banners, menus, recommendation functions, etc., which all have the same front-end H5 application entrance, the menuId of the front-end H5 application is set to be the same. In this way, the same application can be effectively counted, and the information displayed at the application entrance, the processing of the application jump logic, etc. can be uniformly configured to prevent different entrances from having different logical configurations, resulting in problems such as different display and logical judgment.

[0117] Based on the above-mentioned embodiments, the present invention provides a method for managing front-end H5 applications loaded on a mobile app. The method has the following features: First, it solves the problem of unified management of all front-end H5 applications loaded on a mobile app; achieving unified management of common elements such as a unique identifier, URL, minimum supported version, new version prompt, and native navigation support for each application. Second, it solves the problem of supporting front-end H5 applications across different versions of mobile apps. Third, it solves the problem of user access control for mobile apps accessing front-end H5 applications. Fourth, it ensures consistent access to the same front-end H5 application across all entry points on a mobile app. Fifth, it solves the problem of dynamically providing user prompts when a mobile app encounters temporary functional issues, improving the user experience. Sixth, it solves the problem of dynamically supporting native function pages by configuring the application's native support and redirecting to a specific functional module on the mobile app via a URL. Seventh, it solves the problem of displaying the mobile app's entry point to the front-end H5 application based on whether the user has permission to see the entry point.

[0118] The above is a specific description of the preferred implementation of the present invention, but the invention is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A front-end H5 application management method loaded on a mobile terminal APP, characterized in that: The method comprises the following steps: S10. Define basic attribute parameters of the front-end H5 application, which defines the basic attribute parameters of the application information required when the mobile APP loads and displays the front-end H5 application; S20: configuring basic attribute parameters, completing the configuration of basic attribute parameters through the operation management system and saving them to the backend server; S30. The mobile app obtains the information object of the front-end H5 application that needs to be accessed by calling the interface of the back-end server; Step S30 includes the following steps: S301. The backend server provides different interfaces for the mobile APP to call and display according to the application display scenario of the mobile APP; S302: The mobile app calls the corresponding interface provided by the backend server according to the usage scenario to obtain the front-end H5 application information configured in the operation management system in S20. This information includes the front-end basic attribute parameter element object in S10 of the front-end H5 application to be accessed; S40. Obtain the information object of the front-end H5 application through step S30, parse the information of the front-end H5 application, and display the display attribute information of the front-end H5 application at the entrance of the mobile terminal APP displaying the front-end H5 application; S50: When the user accesses the front-end application, a logical judgment is performed based on the parameters in step S10 to determine whether to load the front-end H5 application currently to be loaded; S60: The front-end H5 application to be displayed meets the loading conditions. At this time, the mobile APP loads and renders the front-end H5 application through the web view loader webview.

2. A front-end H5 application management method loaded on a mobile terminal APP according to claim 1, characterized in that: In step S10, the attributes required when the mobile APP loads the front-end H5 application are defined, and common attribute parameters are extracted as the basic attribute parameters of all front-end H5 applications, which are used for unified management parameters of the front-end H5 application mathematics.

3. A front-end H5 application management method loaded on a mobile terminal APP according to claim 2, characterized in that: Step S10 includes the following steps: S101. Define the menuId parameter as the unique identifier of the front-end H5 application to ensure the uniqueness of the front-end H5 application and serve as the basis for determining the uniqueness of the front-end H5 application; S102. Define the url parameter as the required access path for the front-end H5 application, which is used by the mobile app to load the network address of the front-end H5 application; S103. Define the title parameter as the title of the front-end H5 application, and the title displayed when the mobile app loads the front-end H5 application and uses the navigation bar; S104. Define the icon parameter as the remote resource address of the icon displayed by the front-end H5 application; S105. Define the news parameter as a superscript description of the front-end H5 application, which is used to implement a recommended description of the front-end H5 application function; S106. Define the versionSupport parameter as the minimum mobile APP version number that can normally display the front-end H5 application, which is used to intercept and prompt the jump of unsupported low-version mobile APP; S107. Define the errorMsg parameter as a message to block the user's redirection and the corresponding description when a production problem occurs in the application. S108. Define the userType parameter as an identifier of the user access type for accessing the front-end H5 application, to intercept users who do not meet the requirements and provide corresponding operations; S109. Define the navigation parameter as an identifier to indicate whether the front-end H5 application uses the native navigation bar. S110. Define the authType parameter as an identifier for whether to display the current front-end H5 application, and use the value of this parameter to determine whether to display the current entrance to the user who is currently using the mobile APP.

4. A front-end H5 application management method loaded on a mobile terminal APP according to claim 3, characterized in that: Step S20 includes the following steps: S201, the basic attribute parameters obtained in step S10 are used to meet the management of the general front-end H5 application by the mobile terminal APP; The mobile app obtains basic attribute parameter information to complete the entry stack and access control of the front-end H5 application that the mobile app needs to access; S202. Implement a front-end H5 application operation and management platform through front-end development of the Vue technology stack, which is used to configure the basic attribute parameters of the front-end H5 application, including setting the values ​​of the menuId, url, title, icon, news, versionSupport, errorMsg, userType, navigation, and authType fields; S203: Save the data corresponding to the parameters configured in step S202 to the backend server for use by the mobile APP.

5. A front-end H5 application management method loaded on a mobile terminal APP according to claim 3, characterized in that: Step S40 includes the following steps: S401. Parse the front-end H5 application information obtained in step S30 one by one according to the agreement in step S10. S402. Get the current authType value according to the authTyp parameter; If the value is a wildcard type, the front-end H5 application entrance will be displayed; If the value is a blacklist type, if the current user is in the blacklist, the front-end H5 application entrance will not be displayed; If the value is a whitelist type, the front-end H5 application entrance will be displayed if the current user is in the whitelist, otherwise it will not be displayed; S403. Selectively display the front-end H5 application information based on the usage scenario; S404. According to the title parameter, obtain the value of the current front-end H5 application title and use it as the title displayed at the front-end H5 application entrance; S405. According to the image icon parameter, obtain the remote address of the application icon of the front-end H5 application, and display the icon when the front-end H5 application entrance needs to display the icon; S406. According to the subscript news parameter, obtain the subscript value of the front-end H5 application. If there is a value, display the value at the entrance of the current front-end H5 application to recommend the new application.

6. A front-end H5 application management method loaded on a mobile terminal APP according to claim 3, characterized in that: Step S50 includes the following steps: S501. According to the minimum version support versionSupport parameter in step S10, obtain the minimum access supported mobile APP version of the front-end H5 application, and compare the value with the current mobile APP version: If the current mobile APP version is lower than the obtained versionSupport version, the user is prevented from accessing the current front-end H5 application and a pop-up window prompts the user that the version is not supported, and provides a quick entry to upgrade the mobile APP version; If the current mobile APP version supports a version greater than or equal to the obtained versionSupport version, then proceed to the next logical judgment; S502. According to the user access type parameter userType in step S10, obtain the user permission type that the front-end H5 application can access, and compare it with the user type currently using the mobile APP: If the user permission type is not accessible, the current user will not be allowed to access the front-end H5 application and a corresponding prompt will be given; If the user permission type is accessible, proceed to the next logical judgment; S503. According to the errorMsg parameter of the application error information in step S10, a value is obtained as to whether the front-end H5 application has an exception. This is used when the front-end H5 application is undergoing an upgrade deployment or an exception occurs in the front-end H5 application. When the errorMsg parameter has a value, the access to the front-end H5 application is intercepted and the error message is notified to the user to prevent the front-end application from being accessed during problems or maintenance. When the errorMsg parameter has no value, it indicates that the front-end H5 application is normal and can be accessed normally.

7. A front-end H5 application management method loaded on a mobile terminal APP according to claim 3, characterized in that: Step S60 includes the following steps: S601. According to the navigation parameter of whether the native navigation bar is used in step S10, whether the front-end H5 application uses the native navigation bar is obtained, and the scanning bar properties corresponding to the controller are controlled; S602, the mobile APP loads and renders the front-end H5 application through the web view control; S603. According to the menu menuId parameter in step S10, obtain the unique identifier of the front-end H5 application, which is used to record the number of visits and visit time of the menu.

8. A front-end H5 application management method loaded on a mobile terminal APP according to claim 3, characterized in that: Step S60 is followed by step S70, and step S70 includes: S701. Obtain the redirect address of the current front-end H5 application based on the URL parameter of the front-end H5 application, and determine whether there is an agreed protocol header for jumping to the native function page of the mobile app; If so, it will jump to the native page according to the pre-agreed jump function module. In this way, the dynamic configuration and display of certain functions of the mobile APP can be completed.

Images