On-demand upgrade method and system for hybrid mode application
In hybrid mode applications, the web end and the native end maintain function version information separately to determine whether the application needs to be upgraded, which solves the problem of inaccurate judgment of whether users need to upgrade in the existing technology, and achieves the effect of accurate upgrade and reducing maintenance costs.
Patent Information
- Application Number
- CN202411811390.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-10
- Publication Date
- 2025-04-01
AI Technical Summary
Existing mobile application upgrade technology cannot accurately determine whether users need to upgrade, resulting in users receiving unnecessary upgrade notifications, increasing maintenance costs.
In hybrid mode applications, the web and native sides maintain function version information separately to determine whether the application needs to be upgraded. The upgrade dialog box only pops up when the user behavior is triggered to achieve on-demand upgrade.
Accurate upgrades have been achieved, avoiding unnecessary disturbances and invalid upgrades to users, and reducing maintenance costs.
Smart Images

Figure CN119739405A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of user upgrade applications, and in particular to an on-demand upgrade method and system for hybrid mode applications. Background Art
[0002] Hybrid-mode apps are mobile apps that combine local native apps with Web technologies through the WebView component. In hybrid-mode apps, the main framework and some functions of the app are implemented by native code, while the page is implemented by loading a Web page through WebView. Mobile app upgrade refers to the process of updating and improving applications that have been released and installed on users' mobile devices. Upgrades can include the addition of new features, improvements to the user interface, performance optimization, security enhancements, and bug fixes. The purpose of the upgrade is to improve the overall performance of the app, enhance the user experience, and ensure that the app can adapt to new technical environments and user needs.
[0003] Existing mobile application upgrade technology solutions include hot update, gray release, forced upgrade, automatic upgrade or upgrade through application store and other different upgrade methods.
[0004] A mobile application contains many functions, and each upgrade usually involves only one or a few functions. When a mobile application is upgraded according to the existing technical solution, all users will receive an application upgrade notification, even if the user does not use the upgraded function of the application, which disturbs the user. Although gray release can specify a certain group of people, it still cannot accurately meet the user's upgrade needs, and requires the server to maintain the corresponding group information, increasing maintenance costs. Summary of the invention
[0005] In view of the above problems, the present invention is proposed to provide a method and system for on-demand upgrading of hybrid mode applications that overcome the above problems or at least partially solve the above problems.
[0006] According to one aspect of the present invention, a method for upgrading a hybrid mode application on demand is provided, and the method for upgrading on demand specifically comprises:
[0007] The web end calls native functions and obtains data provided by the native end;
[0008] Manage the pop-up and hiding of native upgrade dialog boxes;
[0009] The native end maintains the version information of each function;
[0010] The web terminal maintains the version information of each function;
[0011] Determine whether the application needs to be upgraded. If the web-side maintenance version is higher than the native-side maintenance version, it is determined that an upgrade is required.
[0012] Optionally, the native end maintains the function version information specifically including: each function version number and the description of the updated content of the function version, and the maintenance file uses json or plist.
[0013] Optionally, managing the pop-up and hiding of the native upgrade dialog box specifically includes: managing the pop-up and hiding of the native upgrade dialog box.
[0014] Optionally, the native end maintains the function version information specifically including: each function version number and the description of the updated content of the function version, and the maintenance file uses json or plist.
[0015] Optionally, the web end maintains version information of each function, specifically including: the web end maintains version information of each function, and this version information corresponds to the native end version information.
[0016] Optionally, the determining whether the application needs to be upgraded, if the web-side maintenance version is higher than the native-side maintenance version, specifically includes:
[0017] Determine whether the application needs to be upgraded based on the function name, native function version information, and web function version information;
[0018] If it is determined that the application needs to be upgraded, the web calls the native upgrade module through the JS bridge and pops up the upgrade dialog box. If it is determined that the application does not need to be upgraded, the application function is called up without affecting the user's normal usage process.
[0019] The present invention also provides an on-demand upgrade system for hybrid mode applications, the on-demand upgrade system specifically comprising: a web end calling a native function and obtaining data provided by a native end;
[0020] JS bridge module, used to manage the pop-up and hiding of native upgrade dialog boxes;
[0021] Native upgrade module, used for maintaining the version information of each function on the native side;
[0022] Native function version information module, the web terminal maintains the version information of each function;
[0023] The web function version information module determines whether the application needs to be upgraded. If the web maintenance version is higher than the native maintenance version, it is determined that an upgrade is required.
[0024] The present invention provides an on-demand upgrade method and system for hybrid mode applications, the on-demand upgrade method specifically comprising: the web end calls the native function and obtains the data provided by the native end; manages the pop-up and hiding of the native upgrade dialog box; the native end maintains the version information of each function; the web end maintains the version information of each function; determines whether the application needs to be upgraded, and if the web end maintenance version is higher than the native end maintenance version, it is determined that an upgrade is required. Determine whether it is necessary to remind the user to upgrade the application based on the user's behavior, so as to achieve accurate upgrade, avoid unnecessary disturbance to the user and invalid upgrade, and only require a small maintenance cost.
[0025] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.
[0027] Figure 1 A flowchart of an on-demand upgrade method for a hybrid mode application provided by an embodiment of the present invention;
[0028] Figure 2 A schematic diagram of an on-demand upgrade process of a hybrid mode application provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0029] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.
[0030] The terms "comprises" and "having" and any variations thereof in the description embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusions, for example, including a series of steps or units.
[0031] The technical solution of the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.
[0032] like Figure 1 and Figure 2As shown, a method for upgrading a hybrid mode application on demand specifically includes:
[0033] The web end calls native functions and obtains data provided by the native end;
[0034] Manage the pop-up and hiding of native upgrade dialog boxes;
[0035] The native end maintains the version information of each function;
[0036] The web terminal maintains the version information of each function;
[0037] Determine whether the application needs to be upgraded. If the web maintenance version is higher than the native maintenance version, it is determined that an upgrade is required. Based on the user's behavior, determine whether the user needs to be reminded to upgrade the application. This ensures accurate upgrades, avoids unnecessary disturbances to users and ineffective upgrades, and requires very low maintenance costs.
[0038] An on-demand upgrade system for a hybrid mode application, comprising:
[0039] JS bridge module: enables the web end to call native functions and obtain data provided by the native end;
[0040] Native upgrade module: manages the pop-up and hiding of the native upgrade dialog box. Users click the confirm upgrade button to download the latest application for installation;
[0041] Native function version information module: The native end maintains the version information of each function, including the version number of each function and the description of the updated content of the function version. The maintenance file uses json or plist;
[0042] Web function version information module: The web side maintains the version information of each function, which corresponds to the version information of the native side;
[0043] Web upgrade determination module: determines whether the application needs to be upgraded based on the function name, native function version information, and web function version information. If the web maintenance version is higher than the native maintenance version, it is determined that an upgrade is required.
[0044] A method for upgrading a hybrid mode application on demand comprises the following steps:
[0045] The application starts and loads the latest web resources through the Internet;
[0046] When the user clicks the entry button of a certain function, the web obtains the version information of each native function from the native function version information module through the JS bridge;
[0047] The web upgrade determination module determines whether the application needs to be upgraded based on the function name, native function version information, and web function version information;
[0048] If it is determined that the application needs to be upgraded, the web calls the native upgrade module through the JS bridge and pops up the upgrade dialog box. If it is determined that the application does not need to be upgraded, the application function is called up without affecting the user's normal usage process.
[0049] Beneficial effects: The present invention determines whether it is necessary to remind the user to upgrade the application based on the user's behavior, so as to achieve accurate upgrade, avoid unnecessary disturbance to the user and invalid upgrade, and reduce maintenance costs.
[0050] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
Claims
1. A method for upgrading hybrid mode applications on demand, characterized in that: The on-demand upgrade method specifically includes: The web end calls native functions and obtains data provided by the native end; Manage the pop-up and hiding of native upgrade dialog boxes; The native end maintains the version information of each function; The web terminal maintains the version information of each function; Determine whether the application needs to be upgraded. If the web-side maintenance version is higher than the native-side maintenance version, it is determined that an upgrade is required.
2. The on-demand upgrade method for hybrid mode applications according to claim 1, characterized in that: The native end maintains the function version information including: the function version number and the description of the updated content of the function version, and the maintenance file uses json or plist.
3. The on-demand upgrade method for hybrid mode applications according to claim 1, characterized in that: The managing pop-up and hiding of the native upgrade dialog box specifically includes: managing pop-up and hiding of the native upgrade dialog box.
4. The on-demand upgrade method for hybrid mode applications according to claim 1, characterized in that: The native end maintains the function version information including: each function version number and the description of the updated content of the function version, and the maintenance file uses json or plist.
5. The on-demand upgrade method for hybrid mode applications according to claim 1, characterized in that: The web end maintains the version information of each function specifically including: the web end maintains the version information of each function, and this version information corresponds to the native end version information.
6. The on-demand upgrade method for hybrid mode applications according to claim 1, characterized in that: The determining whether the application needs to be upgraded, if the web-side maintenance version is higher than the native-side maintenance version, determines that the application needs to be upgraded specifically includes: Determine whether the application needs to be upgraded based on the function name, native function version information, and web function version information; If it is determined that the application needs to be upgraded, the web calls the native upgrade module through the JS bridge and pops up the upgrade dialog box. If it is determined that the application does not need to be upgraded, the application function is called up without affecting the user's normal usage process.
7. An on-demand upgrade system for hybrid mode applications, characterized in that: The on-demand upgrade system specifically includes: the web end calls the native function and obtains the data provided by the native end; JS bridge module, used to manage the pop-up and hiding of native upgrade dialog boxes; Native upgrade module, used for maintaining the version information of each function on the native side; Native function version information module, the web terminal maintains the version information of each function; The web function version information module determines whether the application needs to be upgraded. If the web maintenance version is higher than the native maintenance version, it is determined that an upgrade is required.