An application updating method, device, equipment and storage medium

Abstract

This invention provides an application update method, apparatus, device, and storage medium. The method is applied to a user terminal, which communicates with a server. After subscribing to application update information from the server, the user terminal sends application-specific event tracking to the server. These event trackings include the application's current version information and user information. The user terminal then receives application update information from the server. The application update information is sent by the server when preset update conditions are met based on the user information and the current version information. Finally, the application is updated according to the application update information. This method of updating the application through event tracking and subscribing to application update information simplifies the update process and allows users who have reported issues to experience the updated version first.

Description

Technical Field

[0001] This invention relates to the field of application technology, and in particular to an application update method, apparatus, device, and storage medium. Background Technology

[0002] As the number of users of an application increases, the pace of updates and iterations accelerates, and the number of features added in each update, any major quality issues will inevitably lead to a surge in user complaints, negatively impacting the application. Therefore, to prevent major program problems during application updates and releases, and to allow developers to test the application's functionality, performance, and stability in a real-world environment and improve and optimize based on user feedback, creating a virtuous cycle, a public beta version of the application is typically provided to a select group of users before the official release. This allows users to act as "testers," and only after the public beta version has been tested and found to be stable is the official version of the application released to all users. This approach provides a better product experience for the vast majority of users and avoids major application quality issues.

[0003] Currently, most applications implement public beta testing either through user applications or by randomly selecting a group of people to experience the beta version. User applications typically involve filling out forms, a cumbersome process that may discourage users from actively participating in the beta. While randomly selecting a group is more convenient and faster, it doesn't prioritize users who provide feedback, prolonging their waiting time and resulting in a poor user experience. Summary of the Invention

[0004] In view of the above problems, embodiments of the present invention are proposed to provide an application update method, application update apparatus, device, and storage medium that overcome or at least partially solve the above problems.

[0005] To address the aforementioned problems, this invention discloses an application update method applied to a user terminal, wherein the user terminal communicates with a server, and the method includes:

[0006] After subscribing to application update information for the application from the server, the system sends event tracking information for the application to the server; the event tracking information includes the current version information of the application and user information.

[0007] The application receives program update information for the application sent by the server, wherein the program update information for the application is sent by the server when it determines that preset update conditions are met based on the user information and the current version information;

[0008] Update the application according to the program update information for the application.

[0009] Optionally, the method further includes:

[0010] The event tracking for the application is initialized to obtain the event tracking for the application.

[0011] Optionally, the application update information includes update version information and expiration time, and updating the application according to the application update information includes:

[0012] Determine whether the current version information is the same as the updated version information;

[0013] In addition, it determines whether the current time of the application is less than the deadline;

[0014] If the current version information is different from the updated version information;

[0015] Furthermore, the current time of the application is less than the deadline;

[0016] Then, based on the application update information, the application is updated.

[0017] Optionally, the method further includes:

[0018] The application prompts the user to update the application.

[0019] Accordingly, this invention discloses an application update method applied to a server, wherein the server communicates with a user terminal, and the method includes:

[0020] After the user terminal subscribes to the application update information for the application from the server, the server receives the event tracking for the application sent by the user terminal. The event tracking includes the current version information of the application and user information.

[0021] Based on the user information and the current version information, determine whether the preset update conditions are met; if the preset update conditions are met, send the program update information for the application to the user terminal so that the user terminal updates the application according to the program update information for the application.

[0022] Optionally, the application's update information includes update version information and a deadline. The step of determining whether the preset update conditions are met based on the user information and the current version information includes:

[0023] Determine whether the current version information is the same as the updated version information;

[0024] If the current version information is different from the updated version information, then the preset update conditions are met.

[0025] Optionally, the step of determining that a preset update condition is met if the current version information is different from the updated version information includes:

[0026] If the current version information is different from the updated version information, then determine whether there is any user feedback submitted regarding the application based on the user information;

[0027] If there is feedback submitted by the user regarding the application, then the preset update conditions are met.

[0028] Accordingly, this invention discloses an application update device applied to a user terminal, the user terminal communicating with a server, the device comprising:

[0029] The event tracking module is used to send event tracking information for the application to the server after subscribing to program update information for the application; the event tracking information includes the current version information of the application and user information.

[0030] The program update information receiving module is used to receive the program update information for the application sent by the server, wherein the program update information for the application is sent by the server when it determines that preset update conditions are met based on the user information and the current version information;

[0031] An update module is used to update the application based on the program update information for the application.

[0032] Optionally, the device further includes:

[0033] The event tracking initialization module is used to initialize the event tracking of the application and obtain the event tracking events for the application.

[0034] Optionally, the program update information for the application includes update version information and a deadline, and the update module further includes:

[0035] The first version information determination submodule is used to determine whether the current version information is the same as the updated version information;

[0036] In addition, a time determination submodule is used to determine whether the current time of the application is less than the deadline;

[0037] The update submodule is used if the current version information is different from the updated version information;

[0038] Furthermore, the current time of the application is less than the deadline;

[0039] Then, based on the program update information for the application, update the application.

[0040] Optionally, the device further includes:

[0041] A reminder module is used to remind the user to update the application.

[0042] Accordingly, embodiments of the present invention disclose an application update apparatus applied to a server, the server communicating with a user terminal, the apparatus comprising:

[0043] The event receiving module is used to receive event tracking information for the application sent by the user terminal after the user terminal subscribes to the application update information for the application from the server. The event tracking information includes the current version information of the application and user information.

[0044] The determination module is used to determine whether preset update conditions are met based on the user information and the current version information;

[0045] The program update information sending module is used to send the program update information for the application to the user terminal when the preset update conditions are met, so that the user terminal updates the application according to the program update information for the application.

[0046] Optionally, the application's update information includes update version information and a deadline, and the determining module further includes:

[0047] The second version information determination submodule is used to determine whether the current version information is the same as the updated version information;

[0048] The determination submodule is used to determine whether the preset update conditions are met if the current version information is different from the updated version information.

[0049] Optionally, the submodules to be determined include:

[0050] The user information determination subunit is used to determine whether there is any feedback submitted by the user regarding the application if the current version information is different from the updated version information.

[0051] A determination subunit is used to determine whether a preset update condition is met if there is feedback submitted by the user regarding the application.

[0052] Accordingly, embodiments of the present invention disclose an electronic device, including: a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the various steps of the above-described application update method embodiments.

[0053] Accordingly, embodiments of the present invention disclose a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the various steps of the above-described application update method embodiments.

[0054] The embodiments of the present invention have the following advantages:

[0055] This invention discloses an application update method applied to a user terminal. The user terminal communicates with a server. After subscribing to application update information from the server, the method sends application-specific event tracking data to the server. These event tracking data includes the application's current version information and user information. The user terminal then receives application update information from the server. This update information is sent by the server when preset update conditions are met, based on the user information and the current version information. Finally, the application is updated according to this update information. This invention updates the application by subscribing to application update information. For example, the application update information might correspond to a public beta version. This method eliminates the need for users to actively download and apply for the public beta version, simplifying the process. Furthermore, the server determines whether to push the update based on the application's current version information and user information in the event tracking data, allowing users who have reported issues to experience the public beta version first, thus improving the user experience. Attached Figure Description

[0056] Figure 1 This is a flowchart illustrating the steps of an application update method according to an embodiment of the present invention;

[0057] Figure 2 This is a flowchart illustrating the steps of another application update method according to an embodiment of the present invention;

[0058] Figure 3 This is a structural block diagram of an embodiment of an application update device according to an embodiment of the present invention;

[0059] Figure 4This is a structural block diagram of another embodiment of an application update device according to the present invention. Detailed Implementation

[0060] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0061] One of the core concepts of this invention is that the application update method is applied to a user terminal, which communicates with a server. After subscribing to application update information from the server, the method sends application-specific event tracking data to the server. These event tracking data includes the application's current version information and user information. The user terminal then receives application update information from the server, which is sent when preset update conditions are met based on the user information and the current version information. Finally, the application is updated according to this update information. This invention updates the application by subscribing to application update information, eliminating the need for users to actively apply for a public beta version download. The process is simple, and the server's decision to push updates based on the application's current version information and user information in the event tracking data allows users who have reported issues to experience the public beta version first, improving the user experience.

[0062] Current methods for allowing users to experience public beta versions include: first, users actively apply for public beta testing, which typically requires users to fill out forms, a cumbersome process that may discourage users from trying the public beta version; second, randomly selecting a group of people to experience it, which is convenient and quick, but doesn't prioritize users who provide feedback, prolonging their waiting time and creating a poor user experience, making it seem like user feedback is not valued; and third, it's impossible to continuously track user public beta status and allow development or product teams to make corresponding contingency plans in a timely manner. The method of this invention, based on event tracking and MQTT push for downloading the public beta version of the application, can solve these problems and provide a better user experience.

[0063] Reference Figure 1 This diagram illustrates a flowchart of an application update method according to an embodiment of the present invention, applied to a user terminal, wherein the user terminal communicates with a server, and specifically includes the following steps:

[0064] Step 101: After subscribing to program update information for the application from the server, send a tracking event for the application to the server; the tracking event includes the current version information of the application and user information.

[0065] Specifically, applications can subscribe to application update information via MQTT (Message Queuing Telemetry Transport). The application needs to deploy MQTT-related services and event tracking services first. For example, you can download the MQTT SDK (Software Development Kit) from the MQTT official website and then deploy it to the project according to the official documentation.

[0066] MQTT is a lightweight, client-server-based publish-subscribe messaging protocol suitable for resource-constrained devices and low-bandwidth, high-latency, or unstable network environments. MQTT uses the publish-subscribe messaging pattern, providing a one-to-many message distribution mechanism, thus decoupling it from applications. The publish-subscribe pattern is a messaging pattern where messages are not sent directly from sender to receiver (i.e., point-to-point). It decouples the client sending messages (message publisher) from the client receiving messages (message subscriber). Publishers and subscribers do not need to establish a direct connection; instead, the MQTT message server (MQTT Broker) handles message routing and distribution. Message publishers publish messages to a topic, and message subscribers subscribe to specific topics. When a message publisher publishes a message, all subscribers to that topic receive the message. Subscribers can be devices or applications.

[0067] "Event tracking" is a term in the field of data collection, especially user behavior data collection. It refers to the technologies and implementation processes involved in capturing, processing, and transmitting specific user behaviors or events. For example, the number of times a user clicks a button or the duration of watching a video can be considered specific user behaviors or events. The technical essence of event tracking is to first listen for events during application execution, and then judge and capture them when the events of interest occur. The formal name for event tracking is event tracking. Event tracking records user behavior processes and results to meet the needs of fast, efficient, and rich data applications. Data tracking is a commonly used data collection method. Event tracking is the source of data; the collected data can be used to analyze website and application usage, as well as user behavior habits, forming the foundation for building user profiles, user behavior paths, and other data products. For products, what users do within your product, how long they stay, and any anomalies can all be monitored through data tracking.

[0068] After deploying MQTT-related services and event tracking services in the application, the application is started, and MQTT public beta version information is subscribed to. This subscription allows the application to receive program update information from the server; exemplarily, the application update information can be the application's public beta version information. After subscribing to the application's public beta version information, event tracking for the application is sent to the server. These event tracking events include the application's current version information and user information; exemplarily, the application's current version information can include the application's current version number, and the user information can include the user's UID (User Identification). It should be noted that the timing of MQTT public beta version subscription can be set according to actual needs in practical applications, and this embodiment of the invention does not impose any limitations on it.

[0069] In this embodiment of the invention, the method further includes:

[0070] The event tracking for the application is initialized to obtain the event tracking for the application.

[0071] Specifically, the application sends event tracking data to the server. This can be done by initializing the event tracking data when the application starts. Of course, the timing of event tracking initialization can be set according to actual needs in practical applications. This embodiment of the invention does not impose any restrictions on this. When the event tracking is initialized, the application will report the event tracking data to the server. The reporting parameters of the event tracking data include the current version number of the application, the user UID, and the user terminal identifier. Of course, the reporting parameters of the event tracking data can also include other parameters. In practical applications, the reporting parameters of the event tracking data can be set according to actual needs. This embodiment of the invention does not impose any restrictions on this.

[0072] Step 102: Receive the application update information sent by the server, wherein the application update information is sent by the server when it determines that preset update conditions are met based on the user information and the current version information.

[0073] Specifically, after an application subscribes to the public beta version information via MQTT, it can receive the public beta version information pushed by the server. After the application subscribes to the public beta version information via MQTT, and the server pushes the public beta version information, the application receives program update information sent by the server, which is the public beta version information of the application. The server will judge based on the public beta version information of the application and user information in the event tracking reported by the application. When the preset update conditions are met, the server will send the public beta version information of the application.

[0074] Step 103: Update the application according to the application update information.

[0075] Specifically, the server determines the application's public beta version information and user information based on the event tracking data reported by the application. If the preset update conditions are met, the server sends the public beta version information for the application. After receiving the public beta version information, the application updates itself based on it. For example, the application's public beta version can be downloaded through the public beta version download pop-up and the public beta version download entry on the application, thus completing the application update.

[0076] In this embodiment of the invention, the application update information includes update version information and expiration time, and updating the application according to the application update information includes:

[0077] Determine whether the current version information is the same as the updated version information;

[0078] In addition, it determines whether the current time of the application is less than the deadline;

[0079] If the current version information is different from the updated version information;

[0080] Furthermore, the current time of the application is less than the deadline;

[0081] Then, based on the application update information, the application is updated.

[0082] Specifically, the public beta version information received by the application includes the public beta version number and the public beta end time. After receiving the public beta version information, the application can determine whether the application's current version number is the same as the public beta version number, and whether the application's current time is less than the public beta end time. If the application's current version number is different from the public beta version number, and the application's current time is less than the public beta end time, a public beta version download pop-up and a public beta version download entry will be displayed to the current user. The user can update the application by downloading and installing the public beta version.

[0083] In this embodiment of the invention, the method further includes:

[0084] The application prompts the user to update the application.

[0085] Specifically, because the application subscribes to the MQTT beta version information at startup, the application can receive MQTT messages when the server publishes the beta version information for the application to the MQTT Broker. The broker pushes public beta version information for the application. The application determines whether to display a download pop-up and download entry to the current user based on the public beta version number and end time in the public beta information. If the application's current version number is different from the public beta version number, and the application's current time is less than the public beta end time, then the download pop-up and download entry will be displayed to the current user. If the application's current version number is different from the public beta version number, and the application's current time is greater than the public beta end time, then the public beta has ended, and the download pop-up and download entry will not be displayed to the current user. If the application's current version number is the same as the public beta version number, then the user has already downloaded the public beta, and the download pop-up and download entry will not be displayed to the current user.

[0086] Users can click the "Download Public Beta Version" entry to download the public beta version. If the user downloads the public beta version, the download pop-up will close, and the download pop-up and entry will not be displayed to the current user again. If the user does not download the public beta version, the download pop-up and entry will be displayed to the current user at preset time intervals until the user downloads the public beta version or the public beta trial period ends. For example, the preset time interval can be 5 days or 10 days. Of course, the preset time interval can be set according to actual needs in practical applications, and this embodiment of the invention does not impose any limitations on it.

[0087] The application update method of this invention involves subscribing to application update information from a server, sending application-specific event tracking to the server, whereby the event tracking includes the application's current version information and user information. Then, the method receives application update information from the server, wherein the server sends the application update information when preset update conditions are met based on the user information and current version information. Finally, the application is updated according to the application update information. The public beta version download achieved through event tracking data reporting technology and MQTT push technology simplifies the public beta participation process, allows users who have reported issues to experience the public beta version first, and also allows the system to track whether qualified users have already downloaded the public beta version, making it more user-friendly and easier for developers to analyze issues.

[0088] Reference Figure 2 The diagram illustrates a flowchart of another application update method according to an embodiment of the present invention. This method is applied to a server that communicates with a user terminal, and specifically includes the following steps:

[0089] Step 201: After the user terminal subscribes to the application update information for the application from the server, the system receives the event tracking data for the application sent by the user terminal. The event tracking data includes the current version information of the application and user information.

[0090] Specifically, the application on the user terminal can subscribe to the public beta version information via MQTT when the application starts. After the application subscribes to the public beta version information via MQTT, the server receives the event tracking sent by the application on the user terminal. The event tracking includes the current version information of the application and user information. The current version information of the application may include the current version number of the application, and the user information may include the user UID (User Identification). The event tracking may also include the identifier of the user terminal. Of course, the specific content included in the event tracking can be set according to actual needs in practical applications, and this embodiment of the invention does not limit it.

[0091] Step 202: Determine whether the preset update conditions are met based on the user information and the current version information.

[0092] Specifically, the application initializes by tracking events and reports them to the server. The server then determines whether the preset update conditions are met based on the user information and current version information in the tracking events sent by the application.

[0093] In this embodiment of the invention, the application's update information includes update version information and a deadline. The step of determining whether preset update conditions are met based on the user information and the current version information includes:

[0094] Determine whether the current version information is the same as the updated version information;

[0095] If the current version information is different from the updated version information, then the preset update conditions are met.

[0096] Specifically, the server determines whether the preset update conditions are met based on user information and the current version information. The current version information can be the application's current version number. The server can determine whether the application's current version number is the same as the public beta version number. If the application's current version number is different from the public beta version number, then the preset update conditions are met.

[0097] In this embodiment of the invention, the step of determining that a preset update condition is met if the current version information is different from the updated version information includes:

[0098] If the current version information is different from the updated version information, then determine whether there is any feedback submitted by the user regarding the application based on the user information;

[0099] If there is feedback submitted by the user regarding the application, then the preset update conditions are met.

[0100] Specifically, if the application's current version number differs from the public beta version number, the system checks user information to determine if there is any user feedback on the application. If feedback exists, the system confirms that the preset update conditions are met. The existence of user feedback indicates that the user has previously reported issues with the application, meaning that user has public beta access and can be given priority access to the public beta version. This method prioritizes users who have previously reported issues, improving the efficiency of the public beta testing. Furthermore, users who have previously reported issues are also likely interested in experiencing the public beta version. If problems arise during the public beta testing process, it won't negatively impact their experience; instead, they will likely provide further feedback on any issues encountered during the testing phase, thus further improving the efficiency of the public beta testing.

[0101] This invention updates the application by subscribing to application update information. For example, the application update information can correspond to a public beta version. In this way, users do not need to actively apply for downloading the public beta version of the application, making the operation process simple. Furthermore, the server determines whether to push the update based on the application's current version information and user information in the event tracking. Specifically, the application is updated when the current version number of the application is different from the public beta version number, or when there is user feedback on the application. This allows users who have reported problems to experience the public beta version first, improving the user experience.

[0102] Step 203: When the preset update conditions are met, send the application update information to the user terminal so that the user terminal updates the application according to the application update information.

[0103] Specifically, when the preset update conditions are met, that is, when the server determines that the current version number of the user terminal's application is different from the version number of the public beta version and there is user feedback on the application, the server pushes the application update information to the MQTT Broker. Since the application has subscribed to the public beta version information via MQTT, the MQTT Broker then sends the application update information to the application. The user terminal's application updates the application according to the received application update information.

[0104] The application update information includes the public beta version number and the public beta end time. The user's application determines whether the current version number of the user's application is different from the public beta version number, and the current time of the user's application is less than the public beta end time. In this case, the user's application displays a public beta version download pop-up and a download entry for the public beta version to the current user. The user then downloads the public beta version and updates the application based on the displayed pop-up and download entry.

[0105] When determining whether to push application update information, the server needs to check if the current version number of the application on the user's terminal is the same as the public beta version number and if there is any user feedback on the application. If the current version number of the application on the user's terminal is different from the public beta version number, and there is user feedback on the application, the server confirms the push of application update information and pushes the application update information to the MQTT Broker. Since the application on the user's terminal has subscribed to the public beta version information via MQTT, the application on the user's terminal can receive the application update information sent by the MQTT Broker after the server pushes the application update information to the MQTT Broker. The application update information includes the public beta version number and the public beta end time.

[0106] After receiving an application update, the application on the user's terminal determines whether to display a pop-up window and download link for the public beta version based on the version number and end time of the public beta version in the update information. If the current application version number differs from the public beta version number, and the current application time is less than the end time of the public beta version, then the pop-up window and download link will be displayed. If the current application version number differs from the public beta version number, and the current application time is greater than the end time of the public beta version, it indicates that the public beta version has ended, and therefore the pop-up window and download link will not be displayed. If the current application version number matches the public beta version number, it indicates that the user has already downloaded the public beta version, and therefore the pop-up window and download link will not be displayed.

[0107] When the server determines that the current version number of the user's application is different from the public beta version number, it sends an application update message to the user's application. After receiving the update message, the user's application needs to check the public beta version number in the update message again to see if the current version number is the same. This is because there might be a situation where, after the server sends the update message, the user's application performs a normal update. Therefore, the user's application needs to check the public beta version number in the update message again to see if the current version number is the same.

[0108] The application update method of this invention involves subscribing to application update information from a server on the user terminal, receiving application-specific event tracking data sent by the user terminal (the event tracking data includes the current version information of the application and user information), determining whether preset update conditions are met based on the user information and the current version information, and then sending application update information to the user terminal when the preset update conditions are met, so that the user terminal updates the application according to the application update information. This method simplifies the public beta testing process, allows users who have reported issues to experience the public beta version first, and also allows the system to track whether qualified users have already downloaded the public beta version, making it more user-friendly and easier for developers to analyze problems. By utilizing event tracking data reporting technology and MQTT subscription push technology, selecting public beta participants and optimizing the public beta experience, a better user experience is provided while facilitating developers to identify and fix bugs promptly.

[0109] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0110] Reference Figure 3 The diagram illustrates a structural block diagram of an application update device according to an embodiment of the present invention, applied to a user terminal, wherein the user terminal communicates with a server, and may specifically include the following modules:

[0111] The event tracking module 301 is used to send event tracking information for the application to the server after subscribing to program update information for the application from the server; the event tracking information includes the current version information of the application and user information.

[0112] The program update information receiving module 302 is used to receive the program update information for the application sent by the server, wherein the program update information for the application is sent by the server when it determines that preset update conditions are met based on the user information and the current version information.

[0113] The update module 303 is used to update the application according to the application update information.

[0114] In this embodiment of the invention, the device further includes:

[0115] The event tracking initialization module is used to initialize the event tracking of the application and obtain the event tracking events for the application.

[0116] In this embodiment of the invention, the application update information includes update version information and a deadline, and the update module further includes:

[0117] The first version information determination submodule is used to determine whether the current version information is the same as the updated version information;

[0118] In addition, a time determination submodule is used to determine whether the current time of the application is less than the deadline;

[0119] The update submodule is used if the current version information is different from the updated version information;

[0120] Furthermore, the current time of the application is less than the deadline;

[0121] Then, based on the application update information, the application is updated.

[0122] In this embodiment of the invention, the device further includes:

[0123] A reminder module is used to remind the user to update the application.

[0124] The application update device of this invention, after subscribing to application update information from a server, sends application-specific event tracking to the server. These event trackings include the application's current version information and user information. Then, it receives application update information from the server, which is sent when preset update conditions are met based on the user information and current version information. Finally, the application is updated according to this update information. The public beta version download, achieved through event tracking data reporting technology and MQTT push technology, simplifies the public beta process, allows users who have reported issues to experience the public beta version first, and also allows the system to track whether qualified users have already downloaded the public beta version, making it more user-friendly and easier for developers to analyze issues.

[0125] Reference Figure 4 This diagram illustrates a structural block diagram of another application update device according to an embodiment of the present invention, applied to a server, the server communicating with a user terminal, and specifically including the following modules:

[0126] The event receiving module 401 is used to receive event tracking information for the application sent by the user terminal after the user terminal subscribes to the application update information for the application from the server. The event tracking information includes the current version information of the application and user information.

[0127] The determining module 402 is used to determine whether the preset update conditions are met based on the user information and the current version information;

[0128] The program update information sending module 403 is used to send the program update information for the application to the user terminal when the preset update conditions are met, so that the user terminal updates the application according to the program update information for the application.

[0129] In this embodiment of the invention, the application update information includes update version information and a deadline, and the determining module further includes:

[0130] The second version information determination submodule is used to determine whether the current version information is the same as the updated version information;

[0131] The determination submodule is used to determine whether the preset update conditions are met if the current version information is different from the updated version information.

[0132] In this embodiment of the invention, the determined sub-module includes:

[0133] The user information determination subunit is used to determine whether there is any feedback submitted by the user regarding the application if the current version information is different from the updated version information.

[0134] A determination subunit is used to determine whether a preset update condition is met if there is feedback submitted by the user regarding the application.

[0135] Another application update apparatus according to an embodiment of the present invention receives application-specific event tracking data sent by the user terminal after the user terminal subscribes to application update information from the server. These event tracking data includes the current version information of the application and user information. Based on the user information and the current version information, it determines whether preset update conditions are met. If the preset update conditions are met, it sends application update information to the user terminal, enabling the user terminal to update the application accordingly. This method simplifies the public beta testing process, allows users who have reported issues to experience the public beta version first, and allows the system to track whether qualified users have already downloaded the public beta version, making it more user-friendly and easier for developers to analyze problems. By utilizing event tracking data reporting technology and MQTT subscription push technology, the system selects users participating in the public beta and optimizes the public beta experience, providing a better user experience while facilitating developers to identify and fix bugs promptly.

[0136] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0137] This invention also provides an electronic device, comprising:

[0138] It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, it implements the various processes of the above-described application update method embodiment and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0139] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described application update method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0140] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0141] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, embodiments of the present invention can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present invention can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0142] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0143] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0144] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0145] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0146] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0147] The above provides a detailed description of the application update method, application update apparatus, device, and storage medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for updating an application, characterized in that, Applied to a user terminal, wherein the user terminal communicates with a server, the method includes: After subscribing to program update information for the application from the server, the system sends event tracking information for the application to the server; the event tracking information includes the current version information of the application and user information; the event tracking information is obtained by initializing the event tracking information for the application. The system receives program update information for the application sent by the server, wherein the program update information for the application is sent by the server when a preset update condition is met based on the user information and the current version information; the user information includes whether there is any feedback submitted by the user regarding the application; the preset update condition is that the current version information and the updated version information are different, and there is feedback submitted by the user regarding the application; the program update information for the application includes the updated version information and a deadline. Determine whether the current version information is the same as the updated version information; In addition, it determines whether the current time of the application is less than the deadline; If the current version information is different from the updated version information; Furthermore, the current time of the application is less than the deadline; Then, based on the program update information for the application, update the application.

2. The method according to claim 1, characterized in that, The method further includes: The application prompts the user to update the application.

3. A method for updating an application, characterized in that, Applied to a server, wherein the server communicates with a user terminal, the method includes: After the user terminal subscribes to the application update information for the application from the server, the server receives the event tracking for the application sent by the user terminal. The event tracking includes the current version information of the application and user information. The event tracking is obtained by initializing the event tracking for the application. Determine the updated version information of the application; Determine whether the current version information is the same as the updated version information, and determine whether there is any user feedback submitted regarding the application based on the user information; If the current version information is different from the updated version information, and there is feedback from the user regarding the application, then the preset update conditions are met. When the preset update conditions are met, the application update information for the application is sent to the user terminal. The application update information for the application includes the update version information and the expiration time, so that the user terminal can update the application according to the application update information when the current version information is different from the update version information and the current time of the application is less than the expiration time.

4. An application update device, characterized in that, Applied to a user terminal that communicates with a server, the device includes: The event tracking module is used to send event tracking information for the application to the server after subscribing to program update information for the application; the event tracking information includes the current version information of the application and user information; the event tracking information is obtained by initializing the event tracking information of the application. The application update information receiving module is used to receive the application update information sent by the server, wherein the application update information is sent by the server when a preset update condition is met based on the user information and the current version information; the user information includes whether there is any feedback submitted by the user regarding the application; the preset update condition is that the current version information and the updated version information are different, and there is feedback submitted by the user regarding the application; the application update information includes the updated version information and a deadline. The update module determines whether the current version information is the same as the updated version information; and determines whether the current time of the application is less than the deadline; if the current version information is different from the updated version information; and the current time of the application is less than the deadline; then the application is updated according to the program update information for the application.

5. An application update apparatus, characterized in that, The device is used in a server that communicates with a user terminal, and includes: The event receiving module is used to receive event tracking information for the application sent by the user terminal after the user terminal subscribes to the application update information for the application from the server. The event tracking information includes the current version information of the application and user information. The event tracking information is obtained by initializing the event tracking of the application. The judgment module is used to determine whether the current version information is the same as the updated version information, and to determine whether there is any user feedback submitted regarding the application based on the user information. The first determining module is used to determine the updated version information of the application. The second determining module is used to determine that the preset update conditions are met if the current version information is different from the updated version information and there is feedback from the user regarding the application. The program update information sending module is used to send program update information for the application to the user terminal when the preset update conditions are met. The program update information for the application includes the update version information and the expiration time, so that the user terminal can update the application according to the program update information for the application when the current version information is different from the update version information and the current time of the application is less than the expiration time.

6. An electronic device, characterized in that, include: A processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the update method for the application as described in any one of claims 1-2 or 3.

7. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, which, when executed by a processor, implements the steps of the update method for the application program as described in any one of claims 1-2 or 3.

Images