CN112433749A

CN112433749A - Application gray level publishing method and device, server and client

Info

Publication number: CN112433749A
Application number: CN202011326480.2A
Authority: CN
Inventors: 王栈; 冯晓峰; 向晖; 曹宝欣; 黄双雪; 徐摄摄; 潘春晓; 林树新; 黄坤; 陈勇
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2020-11-24
Filing date: 2020-11-24
Publication date: 2021-03-02

Abstract

The embodiment of the specification provides an application gray scale publishing method and device, a server and a client, wherein the method comprises the following steps: under the condition that the release gray scale version of the target application is determined, acquiring a characteristic user data set of the target application; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user; sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology; the client of each characteristic user responds to the gray level test notification to obtain a target configuration file of the gray level version of the target application; and switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file. In the embodiment of the specification, the gray versions can be switched under the condition that the user does not sense, so that the times of repeated downloading and installation of the user are effectively reduced, and the user experience is improved.

Description

Application gray level publishing method and device, server and client

Technical Field

The embodiment of the specification relates to the technical field of computers, in particular to a gray level issuing method and device for an application, a server and a client.

Background

With the high-speed development of the internet, the APP in the application market at present gradually gets rid of the traditional static content in combination with the mode of the C/S (customer service side and service side), and starts to move towards the operation, and the displayed content can be updated by the updating module at any time and any place, so that the dynamic layout of the APP is achieved, and the operability of the APP is realized.

The current application APP products are extremely fast in updating iteration speed, the new version is generally released through gray scale, market feedback conditions are obtained through a small part of user samples, and product teams can timely perfect relevant functions of the products according to feedback of users. The existing APP gray release technology needs to download a new gray release version for a user, so that the touch rate of the gray release version is low, if the gray release version has a problem, the user needs to download the previous version again, the user experience is poor, and the trial-and-error cost is high. Therefore, the technical solutions in the prior art cannot efficiently implement gray scale distribution.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The embodiment of the specification provides an application gray scale publishing method and device, a server and a client, so as to solve the problem that gray scale publishing cannot be efficiently realized in the prior art.

An embodiment of the present specification provides a grayscale issuing method for an application, including: under the condition that a target application release gray scale version is determined, acquiring a characteristic user data set of the target application; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user; sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology; the client of each characteristic user responds to the gray level test notification to obtain a target configuration file of the gray level version of the target application; and switching the target application in the client of the feature user from the currently used version to the grayscale version according to the target configuration file.

An embodiment of the present specification further provides a grayscale issuing device for application, including: the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a characteristic user data set of a target application under the condition of determining a release gray scale version of the target application; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user; the sending module is used for sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent pushing technology; a second obtaining module, configured to, in response to the grayscale test notification, obtain a target configuration file of the grayscale version of the target application by the client of each feature user; and the version switching module is used for switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file.

An embodiment of the present specification further provides an application gray scale publishing method, which is applied to a server, and includes: the method comprises the steps that a server of a target application obtains a characteristic user data set of the target application under the condition that a gray level version of the target application is determined; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user; and sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology.

An embodiment of the present specification further provides a server, including: the acquisition module is used for acquiring a characteristic user data set of the target application under the condition that the server of the target application determines the release gray scale version of the target application; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user; and the sending module is used for sending a gray test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent pushing technology.

An embodiment of the present specification further provides an application gray scale publishing method, which is applied to a client, and includes: responding to the gray level test notification by a client of a characteristic user of the target application, and acquiring a target configuration file of a gray level version of the target application; the gray level test notification is sent to a characteristic user of the target application by the server of the target application by utilizing a silent push technology under the condition that the server of the target application determines that the target application releases the gray level version; and switching the target application in the client of the feature user from the currently used version to the grayscale version according to the target configuration file.

An embodiment of the present specification further provides a client, including: the acquisition module is used for responding to the gray level test notification by a client of a characteristic user of the target application and acquiring a target configuration file of a gray level version of the target application; the gray level test notification is sent to a characteristic user of the target application by the server of the target application by utilizing a silent push technology under the condition that the server of the target application determines that the target application releases the gray level version; and the version switching module is used for switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file.

The embodiment of the present specification provides an application gray scale publishing method, which may obtain a feature user data set of a target application under a condition that a target application is determined to publish a gray scale version, where the feature user data set includes attribute data of at least one feature user, and the attribute data may be used to characterize the feature user. Furthermore, a silent pushing technology can be utilized to send a gray level test notification to the client of each feature user in the feature user data set, and the client receiving the gray level test notification can start a background downloading service to obtain a target configuration file of a gray level version of a target application. Because the silent notification content does not include any sound prompt and corner mark setting, background content updating can be performed under the condition that a user is not disturbed at all, and therefore, the target application in the client of the feature user can be switched from the currently used version to the gray version under the condition that the user does not perceive according to the acquired target configuration file, the times of repeated downloading and installation of the user are effectively reduced, and the user experience is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the embodiments of the disclosure, are incorporated in and constitute a part of this specification, and are not intended to limit the embodiments of the disclosure. In the drawings:

fig. 1 is a schematic structural diagram of a grayscale distribution system applied according to an embodiment of the present specification;

fig. 2 is a schematic step diagram of a gray scale publishing method for an application provided according to an embodiment of the present specification;

fig. 3 is a schematic structural diagram of a grayscale issuing device applied according to an embodiment of the present specification;

fig. 4 is a schematic step diagram of a gray scale publishing method of an application provided according to an embodiment of the present specification;

FIG. 5 is a schematic structural diagram of a server provided according to an embodiment of the present disclosure;

fig. 6 is a schematic step diagram of a gray scale publishing method of an application provided according to an embodiment of the present specification;

fig. 7 is a schematic structural diagram of a client provided according to an embodiment of the present specification;

fig. 8 is a schematic structural diagram of a grayscale issuing device of an application provided according to an embodiment of the present specification.

Detailed Description

The principles and spirit of the embodiments of the present specification will be described with reference to a number of exemplary embodiments. It should be understood that these embodiments are presented merely to enable those skilled in the art to better understand and to implement the embodiments of the present description, and are not intended to limit the scope of the embodiments of the present description in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As will be appreciated by one skilled in the art, implementations of the embodiments of the present description may be embodied as a system, an apparatus, a method, or a computer program product. Therefore, the disclosure of the embodiments of the present specification can be embodied in the following forms: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

Although the flow described below includes operations that occur in a particular order, it should be appreciated that the processes may include more or less operations that are performed sequentially or in parallel (e.g., using parallel processors or a multi-threaded environment).

In an example scenario of the present application, a gray scale distribution system applied is provided, as shown in fig. 1, which may include: client 101, server 102. The server 102 may send the grayscale test notification to the client 101 of each feature user in the feature user dataset using silent push technique, with the determination that the target application releases the grayscale version. The client 101 may obtain a target configuration file of the grayscale version of the target application in response to the grayscale test notification, and switch the target application in the client 101 from the currently used version to the grayscale version according to the target configuration file.

The client 101 may be a terminal device or software used by a user. Specifically, the terminal device may be a terminal device such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart watch, or other wearable devices, or may be a robot device. Of course, the client 101 may also be software that can run in the above-described terminal device. For example: system applications, payment applications, browsers, wechat applets, and the like.

The server 102 may be a single server or a server cluster, and certainly, the functions of the server may also be implemented by a cloud computing technology. The server 102 may be connected to a plurality of terminal devices, or may be a server having a strong information set library, and may send a grayscale test notification to the client of each feature user by using a silent push technique when determining that the target application issues a grayscale version, so that the client of each feature user switches the currently used version of the target application to the grayscale version when the user does not perceive the current version, thereby effectively improving the grayscale version touch rate.

Referring to fig. 2, the present embodiment can provide an applied gray scale publishing method. The gray level release method of the application can be used for sending the gray level test notification to the client of each characteristic user by utilizing the silent push technology under the condition that the target application release gray level version is determined, so that the client of each characteristic user can switch the currently used version of the target application to the gray level version under the condition that the user does not sense the gray level version, and the touch rate of the gray level version is effectively improved. The gray scale distribution method of the above application may include the following steps.

S201: under the condition that the release gray scale version of the target application is determined, acquiring a characteristic user data set of the target application; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user.

In this embodiment, in the case where the target application release grayscale version is determined, the feature user data set of the target application may be acquired. The feature user data set may include attribute data of at least one feature user, and the attribute data may be used to characterize the feature user, so that one feature user may be uniquely determined by one attribute data. The target application may be an application to be subjected to gray scale publishing, and a specific application name may be determined according to an actual situation, which is not limited in the embodiment of the present specification.

In some embodiments, the attribute data may be a user ID (Identity), and may include at least one of the following: a user name, a user account, an identification number, etc. Of course, the attribute data are not limited to the above examples, and other modifications are possible for those skilled in the art in light of the technical spirit of the embodiments of the present disclosure, and are intended to be included within the scope of the embodiments of the present disclosure as long as the functions and effects achieved by the present disclosure are the same as or similar to the embodiments of the present disclosure.

In this embodiment, since the number of users of the target application may be large, the users of the target application may be screened to determine the users suitable for performing the gray scale distribution of the target application, considering that some users use a lower version or use the target application less frequently. Further, the screened user suitable for performing the gray scale publishing of the target application can be used as the characteristic user of the target application.

In this embodiment, the manner of acquiring the feature user data set of the target application may include: and reading the data from the preset position of the server of the target application. It is understood that, the sample data set may also be obtained in other possible manners, for example, a characteristic user of the target application is searched in a preset database according to a certain search condition, which may be determined according to actual situations, and this is not limited in this specification.

S202: and sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology.

In this embodiment, in the case that it is determined that the target application releases the grayscale version, the server of the target application may send a grayscale test notification to the client of each feature user in the feature user dataset by using the silent push technique. The grayscale test notification may be configured to notify each client that the target application has released a grayscale version that can be switched, and the grayscale test notification may include at least one of the following: the name of the target application, the IP address of the server of the target application, the version number of the grayscale version, and the like may be determined according to actual situations, and this is not limited in this embodiment of the present specification.

In the present embodiment, normally, after an APP (Application program) is started, the APP enters the foreground, for example, an Application icon or a point push notification is clicked to start the Application, and the silent push technology may be applied to start the Application to the background when the Application receives the silent push. The Silent Push technology (silence Push) is a background remote Push technology, and on the premise that remote notification is executed in the background, the Silent notification content does not include any sound reminding and corner mark setting, so that background content can be updated without disturbing a user. The target application in the client can directly run a section of code in a background state after receiving the notification, and the client can obtain content update from the server without clicking by a user.

In this embodiment, to ensure that the user can receive the silent push in time, a process keep-alive strategy can be adopted. Specifically, dual-process protection may be utilized, where two processes monitor each other, and when one process is terminated, the other process immediately recovers the process, so as to ensure that the user receives the silent push in time.

S203: and the client of each characteristic user responds to the gray level test notification to acquire a target configuration file of the gray level version of the target application.

In this embodiment, when the client of each feature user receives the grayscale test notification, the client may obtain the target configuration file of the grayscale version of the target application from the server of the target application. The target configuration file may contain specific settings for the grayscale version of the target application, configuration settings read by the common language runtime (e.g., assembly binding policies, remote processing objects, etc.), and settings that may be read by the target application.

In this embodiment, after writing the target configuration file of the grayscale version, the developer of the target application can manage and maintain the target configuration file through the code warehouse. Each application may have a corresponding code repository for storing all code and its submission history under the application service. Meanwhile, each code warehouse also supports developers to continuously push and pull codes to realize agile development and continuous delivery. The code repository of the target application can be stored in a preset position of a server of the target application, so that the client can pull the target configuration file from a remote end (server).

In the prior art, a configuration file needs to be loaded through a back-end API (Application Programming Interface) to implement dynamic layout, and a back-end visual operation configuration page needs to be additionally developed for operators to use, which increases development cost and learning cost of the operators. In the embodiment, dynamic layout can be realized by loading the remote configuration file, so that the development workload of the operation related functions of the management background can be effectively reduced, the configuration file can be maintained by a front-end developer, and the operation cost is effectively reduced.

In one embodiment, a target configuration file of a gray-scale version of a target application can be constructed based on the Flutter technology, so that a complete page can be combined by mutually wrapping, nesting and assembling custom components, styles can be set through interfaces of different components, and pages with various styles and styles can be assembled through a basic custom component library. The Flutter is a mobile UI (User Interface) framework of google, and can quickly construct a high-quality native User Interface on iOS (proprietary mobile operating system developed by apple for its mobile device) and Android (Android). The Flutter component is built using a modern responsive framework, with the central idea being to build your UI with a component (widget) that describes what they appear to be given their current configuration and state. When a component state changes, the component reconstructs its description, and Flutter compares the previous description to determine the minimum change needed to transition the underlying render tree from the current state to the next state.

In this embodiment, a custom component (Widget) library may be established based on the design concept of Flutter. The custom component library includes, but is not limited to, the following major types of components: 1) customizing the basic components: basic components with single functions and definite purposes, such as pictures (images), texts (texts), buttons (buttons) and the like; 2) custom layout style component: components such as containers (Container), rows (Row), columns (Column), lists (List), etc. may be used to lay out layouts, describe placeholders, positional relationships, arrangements; 3) self-defining the combined assembly: and assembling and combining the basic components and the layout style components according to the service requirements of the components.

In this embodiment, a custom attribute setting interface may be reserved for the custom component, for example, interfaces such as a width, a height, a fillet angle, an outer space, an inner space, an arrangement mode, an alignment mode, a background picture, text content, an icon style, a picture style, a button click effect, and click event monitoring may be reserved, and a display effect and a service processing logic of the custom component may be flexibly adjusted by changing an access parameter.

In an embodiment, the target configuration file may be an Extensible Markup Language (XML), and the XML may satisfy the description of the layout and the setting of the custom attribute, and has a natural advantage in describing a form of the Flutter that requires a large number of components to be wrapped and nested to realize a page, and is easy to read, simple to maintain, and efficient in parsing. The package, nesting and combination relation of the self-defined components can be described in the XML configuration file; setting the self-defined attribute of the component; adding relevant parameters of the component; business logic processing modes, and the like.

In this embodiment, the developer can directly update and maintain the target configuration file through the code warehouse, and upload the configuration file to the preset position of the server when the business is changed, the production is on line, and the gray scale is released.

S204: and switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file.

In this embodiment, the target application in the client of the feature user may be switched from the currently used version to the grayscale version according to the target profile. The currently used version of the target application may be a version of the target application currently used by a client of the feature user.

In this embodiment, the transition to the grayscale version of the target application can be made without the user's perception. Even if the user is using the application, the target profile of the grayscale version can be loaded when the user browses the switching page after the target profile download is completed, and the grayscale version is naturally and indispensably transited in the next new page.

Compared with a gray level publishing scheme in the prior art, the method and the device for releasing the gray level are lighter in weight, low in building cost and simpler in operation and maintenance, more workloads are placed in front-end engineering, a rear end only needs to determine a feature user data set of a target application and push gray level notification, other work is completed by the front end, a configuration file is written by a developer at the front end, and cost and complexity of building at the rear end are effectively reduced.

In one embodiment, before obtaining the feature user data set of the target application, the method may further include: the method comprises the steps of obtaining historical behavior data of a plurality of users of a target application, and determining at least one characteristic user according to preset screening conditions according to the historical behavior data of the plurality of users. Further, attribute data of at least one feature user is obtained, and a feature user data set of the target application is generated according to the attribute data of the at least one feature user.

In this embodiment, the target application may have a plurality of users, and the users of the target application may be screened to determine users suitable for performing gray-scale distribution of the target application, considering that some users use a lower version or use the target application less frequently. Accordingly, historical behavior data of multiple users of the target application may be obtained. The historical behavior data may be behavior data recorded by the target application for the historical use of the user, and the historical behavior data of the plurality of users may be stored in a preset database of a server of the target application so as to be obtained in time. Wherein, the historical behavior data at least comprises: the time when the user last updated the version, the version information used by the user, the frequency with which the user used the target application, the user's preference habits, the average daily duration of use of the target application by the user, etc. Of course, the historical behavior data is not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the embodiments of the present disclosure, and all such modifications are intended to be included within the scope of the embodiments of the present disclosure as long as they achieve the same or similar functions and effects as the embodiments of the present disclosure.

In this embodiment, since the historical behavior data of the user may represent the activity and the participation of the user in using the target application, at least one characteristic user may be determined according to the historical behavior data of the plurality of users and the preset screening condition. The preset screening condition may be preset according to a business requirement of the grayscale version of the target application, for example: (1) defining a version baseline, wherein users at or above the set application version baseline can be defined as characteristic users; (2) performing secondary delineation through the activity degree based on the users meeting the version baseline requirement, and preferentially ensuring that the users with higher activity degree are screened as characteristic users; (3) and based on the users meeting the activity requirement, carrying out third delineation through the user participation, and preferentially ensuring that the users with high participation are screened as the characteristic users.

In the embodiment, the screening conditions of the feature users can be increased according to the specific business requirements of the grayscale version of the target application, so that finer feature user groups can be further defined. For example, the function page of the grayscale version is an operation promotion activity page of an ancient drama, and the preset screening condition may be set as: users who prefer antique episodes. In some embodiments, a plurality of filtering conditions may be set, and different weights may be given to the filtering conditions, so that the feature users are filtered out through a weighting operation on the filtering conditions. Of course, the preset screening conditions are not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the embodiments of the present disclosure, and the functions and effects achieved by the present disclosure are all covered by the scope of the embodiments of the present disclosure.

In one embodiment, obtaining a target profile of a grayscale version of a target application may include: loading a target configuration file from a server of a target application, and analyzing the target configuration file under the condition of determining that the target configuration file is loaded successfully; in the event that it is determined that the target configuration file loading failed, the target configuration file may be reloaded from the server of the target application.

In this embodiment, dynamic layout can be realized by loading the remote configuration file, and after receiving the silence notification, the client of the feature user can directly start the background downloading service of the client, and download the target configuration file corresponding to the grayscale version from the server of the target application. Therefore, the client can analyze the configuration file, render a page and switch to the gray release version of the target application under the condition that a user does not sense the page.

In this embodiment, it may be determined whether the client successfully loads the target configuration file, and if successful, the loaded target configuration file may be directly analyzed, and if failed, the target configuration file may need to be reloaded until the loading is successful. It is understood that if the number of loading failures exceeds the preset number (for example, 8 times, 9 times, etc.), the number may be fed back to the corresponding maintenance personnel for processing. The specific situation can be determined according to actual situations, and the embodiment of the present specification does not limit the specific situation.

In one embodiment, after switching the target application in the client of the feature user from the currently used version to the grayscale version, the method may further include: feedback information of the grayscale version of the target application is obtained, and a quality level of the grayscale version of the target application is determined based on the feedback information of the grayscale version of the target application. In the event that it is determined that the quality level of the grayscale version of the target application is below a preset threshold, the target application in the client of the feature user may be switched from the grayscale version to the currently used version.

In this embodiment, after the target application in the client of the feature user is switched from the currently used version to the grayscale version, the feedback information of the grayscale version of the target application may be further acquired, so that the developer may refine and improve the grayscale version with respect to the feedback information. Wherein, the feedback information may include at least one of the following: the opinion and public opinion of satisfaction degree of the characteristic user using the gray version, online breakdown of the gray version collected by the probe, application performance compatibility and stability of technical layers such as white screen and stuck, and the like.

In this embodiment, the manner of collecting the feedback information may include: (1) an opinion feedback module is arranged in the gray scale version of the target application, and problem opinions generated in the using process of a user can be filled in and submitted in the opinion feedback module; (2) collecting question and public opinions through online customer service (including robots, artificial customer service and the like); (3) and acquiring error stacks, running logs and the like in the running process of the application by implanting a monitoring probe.

In this embodiment, the quality level of the grayscale version of the target application may be determined from feedback information based on the grayscale version of the target application. The quality level can be classified into three levels, namely high, medium and low levels, and can be set as one level, two levels, three levels, and the like, and it is understood that the quality level can be set in any other possible manner, and the quality level can be determined according to actual situations, and the embodiment of the present specification does not limit the quality level.

In the present embodiment, the quality level may be determined according to the number of collected bug (bug, failure) complaints of the user to the grayscale version and the number of problems in the technical level of the grayscale version collected by the probe. How to make the quality level lower than the preset threshold value, that is, the public opinion discussion of the grayscale version is negative, indicates that the user acceptance of the grayscale version is not high, the quality of the grayscale version is not in accordance with the expectation, the grayscale version cannot be released as a formal version at present, and developers still need to improve and perfect the grayscale version. Thus, in the event that it is determined that the quality level of the grayscale version of the target application is below a preset threshold, the target application in the client of the feature user may be switched from the grayscale version to the currently used version.

In this embodiment, the preset threshold may be determined according to the setting mode of the quality level, for example: the quality level is divided into three grades of high, medium and low, and then the preset threshold is high; the quality level is set to one level, two levels, three levels, and four levels, and then the preset threshold is "one level". Of course, the preset threshold is not limited to the above examples, and other modifications are possible for those skilled in the art in light of the technical spirit of the embodiments of the present disclosure, and the functions and effects achieved by the preset threshold are all within the scope of the embodiments of the present disclosure.

In this embodiment, in the case where it is determined that the quality level of the grayscale version of the target application is not lower than the preset threshold, it indicates that the user acceptance of the grayscale version is high, the grayscale version quality is satisfactory, and the version rollback operation does not need to be performed. At this time, the grayscale version may be published as a formal version, for example: the method can be formally put on shelves in the application mall, and the method can be determined according to actual conditions, and is not limited in the embodiment of the specification.

In one embodiment, in the case that it is determined that the quality level of the grayscale version of the target application is lower than the preset threshold, switching the target application in the client of the feature user from the grayscale version to the currently used version may include: in the event that it is determined that the quality level of the grayscale version of the target application is below a preset threshold, a silent push technique may be utilized to send a version rollback notification to the client of each feature user in the feature user dataset. Furthermore, the client of each feature user responds to the version rollback notification to acquire the configuration file of the currently used version, and switches the target application in the client of the feature user from the grayscale version to the currently used version according to the configuration file of the currently used version.

In this embodiment, when the server of the target application determines that the quality level of the grayscale version of the target application is lower than the preset threshold, it indicates that the user acceptance of the grayscale version is not high and the quality of the grayscale version is not in accordance with the expectation, and at this time, a silent push technology may be used to send a version rollback notification to the client of each feature user in the feature user data set. And the client of each characteristic user can start the background downloading service of the client under the condition of receiving the rollback notification of the version, and download the configuration file corresponding to the current version from the server of the target application. Therefore, the client can analyze the configuration file corresponding to the current version, further render the page, and switch from the gray-scale version to the current version used by each characteristic user under the condition that the user does not sense the page.

In the embodiment, the version rollback of the gray release can be triggered by silent pushing, the operation principle of the method is the same as that of the gray release, the same operation logic can be reused, the difficulty and the implementation cost of the version rollback are effectively reduced, the fault tolerance rate of the gray release is improved, the number of times of repeated downloading and installation of a user is reduced, and the user experience is improved.

In one embodiment, before obtaining the target configuration file of the grayscale version of the target application, the method may further include: constructing a target configuration file of a gray-scale version of a target application based on the Flutter technology; and uploading the target configuration file to a preset position of a server of the target application.

In this embodiment, a developer of the target application may construct a target configuration file of a grayscale version of the target application based on Flutter technology, and may upload the target configuration file to a preset location of a server of the target application, so that a client may load a remote configuration file. Wherein, above-mentioned Flutter is a set of platform front end frame of striding, and a set of code can be applicable to Android and iOS bi-polar, has effectively reduced development cost, has also improved the application scope of platform.

From the above description, it can be seen that the embodiments of the present specification achieve the following technical effects: the method comprises the steps of obtaining a characteristic user data set of a target application under the condition that a gray-scale version issued by the target application is determined, wherein the characteristic user data set comprises attribute data of at least one characteristic user, and the attribute data can be used for representing the characteristic user. Furthermore, a silent pushing technology can be utilized to send a gray level test notification to the client of each feature user in the feature user data set, and the client receiving the gray level test notification can start a background downloading service to obtain a target configuration file of a gray level version of a target application. Therefore, the target application in the client of the feature user can be switched from the currently used version to the gray-scale version under the condition that the user does not sense according to the acquired target configuration file, the times of repeated downloading and installation of the user are effectively reduced, and the user experience is improved.

Based on the same inventive concept, the embodiment of the present specification further provides a grayscale issuing device applied thereto, as in the following embodiments. Because the principle of the applied gray scale issuing device for solving the problem is similar to that of the applied gray scale issuing method, the implementation of the applied gray scale issuing device can refer to the implementation of the applied gray scale issuing method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Fig. 3 is a block diagram of a structure of a gray scale distribution apparatus applied in the embodiment of the present specification, and as shown in fig. 3, the gray scale distribution apparatus may include: the first acquiring module 301, the sending module 302, the second acquiring module 303, and the version switching module 304 will be described below.

A first obtaining module 301, configured to obtain a feature user data set of a target application when it is determined that the target application issues a grayscale version; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user;

a sending module 302, configured to send a grayscale test notification to a client of each feature user in the feature user dataset by using a silent pushing technique;

a second obtaining module 303, configured to obtain, by the client of each feature user, a target configuration file of a grayscale version of the target application in response to the grayscale test notification;

the version switching module 304 may be configured to switch the target application in the client of the feature user from the currently used version to the grayscale version according to the target configuration file.

Referring to fig. 4, an embodiment of the present disclosure provides a gray level publishing method for an application. The applied gray scale distribution method can be applied to a server. The gray scale distribution method of the application may include the following steps.

Step S401: the method comprises the steps that a server of a target application obtains a characteristic user data set of the target application under the condition that a gray version of the target application is determined; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user.

Step S402: and sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology.

In one embodiment, after sending the grayscale test notification to the client of each feature user in the feature user data set by using the silent push technique, the method may further include: feedback information of the grayscale version of the target application is obtained, and a quality level of the grayscale version of the target application is determined based on the feedback information of the grayscale version of the target application. In the case that it is determined that the quality level of the grayscale version of the target application is less than the preset threshold, a silent push technique may be utilized to send a version rollback notification to the client of each feature user in the feature user dataset.

In the present embodiment, the quality level may be determined according to the number of collected bug (bug, failure) complaints of the user to the grayscale version and the number of problems in the technical level of the grayscale version collected by the probe. How to make the quality level lower than the preset threshold value, that is, the public opinion discussion of the grayscale version is negative, indicates that the user acceptance of the grayscale version is not high, the quality of the grayscale version is not in accordance with the expectation, the grayscale version cannot be fully released at present, and developers still need to improve and perfect the grayscale version. Thus, silent push techniques can be utilized to send a version rollback notification to the clients of individual feature users in the feature user dataset.

Referring to fig. 5, an embodiment of the present disclosure further provides a server, including: an acquisition module 501 and a sending module 502.

An obtaining module 501, configured to obtain a feature user data set of a target application by a server of the target application when determining that the target application releases a grayscale version; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user;

the sending module 502 may be configured to send the grayscale test notification to the client of each feature user in the feature user data set by using a silent push technique.

The server provided in this embodiment can realize functions and effects as explained with reference to other embodiments.

Referring to fig. 6, an embodiment of the present disclosure provides a gray level publishing method for an application. The applied gray scale release method can be applied to a client. The gray scale distribution method of the application may include the following steps.

Step S601: the client of the characteristic user of the target application responds to the gray level test notification to obtain a target configuration file of the gray level version of the target application; the gray level test notification is sent to the characteristic user of the target application by the server of the target application by utilizing a silent push technology under the condition that the server of the target application determines that the target application releases the gray level version.

Step S602: and switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file.

In one embodiment, after switching the target application in the client of the feature user from the currently used version to the grayscale version, the method may further include: and the client of the characteristic user acquires the configuration file of the currently used version under the condition of receiving the version rollback notification sent by the server of the target application. Further, the target application in the client of the feature user may be switched from the grayscale version to the currently used version according to the configuration file of the currently used version.

In the embodiment, the version rollback of the gray release can be triggered by silent pushing, the operation principle of the method is the same as that of the gray release, the same operation logic can be reused, the difficulty and the implementation cost of the version rollback are effectively reduced, the fault tolerance rate of the gray release is improved, the repeated downloading and installation times of a user are reduced, and the user experience is improved.

Referring to fig. 7, an embodiment of the present disclosure further provides a client, including: an obtaining module 701 and a version switching module 702.

An obtaining module 701, configured to obtain, by a client of a feature user of a target application, a target configuration file of a grayscale version of the target application in response to the grayscale test notification; the gray level test notification is sent to a characteristic user of the target application by using a silent push technology under the condition that the server of the target application determines that the target application releases the gray level version;

the version switching module 702 may be configured to switch the target application in the client of the feature user from the currently used version to the grayscale version according to the target configuration file.

The functions and effects of the client provided in this embodiment can be explained with reference to other embodiments.

The embodiment of the present specification further provides an electronic device, which may specifically refer to a schematic structural diagram of the electronic device based on the gray scale publishing method of the application provided by the embodiment of the present specification, and the electronic device may specifically include an input device 81, a processor 82, and a memory 83. The input device 81 may specifically be used for inputting a characteristic user data set of the target application, among others. The processor 82 may be specifically configured to, in a case where it is determined that the target application issues the grayscale version, obtain a feature user data set of the target application; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user; sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology; the client of each characteristic user responds to the gray level test notification to obtain a target configuration file of a gray level version of the target application; and switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file. The memory 83 may be used to store parameters such as target configuration files.

In this embodiment, the input device may be one of the main apparatuses for information exchange between a user and a computer system. The input devices may include a keyboard, mouse, camera, scanner, light pen, handwriting input panel, voice input device, etc.; the input device is used to input raw data and a program for processing the data into the computer. The input device can also acquire and receive data transmitted by other modules, units and devices. The processor may be implemented in any suitable way. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth. The memory may in particular be a memory device used in modern information technology for storing information. The memory may include multiple levels, and in a digital system, memory may be used as long as binary data can be stored; in an integrated circuit, a circuit without a physical form and with a storage function is also called a memory, such as a RAM, a FIFO and the like; in the system, the storage device in physical form is also called a memory, such as a memory bank, a TF card and the like.

In this embodiment, the functions and effects specifically realized by the electronic device can be explained by comparing with other embodiments, and are not described herein again.

Embodiments of the present specification further provide a computer storage medium for an application-based gray scale distribution method, where the computer storage medium stores computer program instructions, and when the computer program instructions are executed, the computer storage medium may implement: under the condition that the release gray scale version of the target application is determined, acquiring a characteristic user data set of the target application; the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for representing the feature user; sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology; the client of each characteristic user responds to the gray level test notification to obtain a target configuration file of a gray level version of the target application; and switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file.

In this embodiment, the storage medium includes, but is not limited to, a Random Access Memory (RAM), a Read-Only Memory (ROM), a Cache (Cache), a Hard Disk Drive (HDD), or a Memory Card (Memory Card). The memory may be used to store computer program instructions. The network communication unit may be an interface for performing network connection communication, which is set in accordance with a standard prescribed by a communication protocol.

In this embodiment, the functions and effects specifically realized by the program instructions stored in the computer storage medium can be explained by comparing with other embodiments, and are not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the embodiments of the present specification described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed over a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different from that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the present description are not limited to any specific combination of hardware and software.

Although the embodiments herein provide the method steps as described in the above embodiments or flowcharts, more or fewer steps may be included in the method based on conventional or non-inventive efforts. In the case of steps where no causal relationship is logically necessary, the order of execution of the steps is not limited to that provided by the embodiments of the present description. When the method is executed in an actual device or end product, the method can be executed sequentially or in parallel according to the embodiment or the method shown in the figure (for example, in the environment of a parallel processor or a multi-thread processing).

It is to be understood that the above description is intended to be illustrative, and not restrictive. Many embodiments and many applications other than the examples provided will be apparent to those of skill in the art upon reading the above description. The scope of embodiments of the present specification should, therefore, be determined not with reference to the above description, but should instead be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

The above description is only a preferred embodiment of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure, and it will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present disclosure. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the embodiments of the present disclosure should be included in the protection scope of the embodiments of the present disclosure.

Claims

1. A method for gray scale distribution of an application, comprising:

under the condition that a target application release gray scale version is determined, acquiring a characteristic user data set of the target application; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user;

sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology;

the client of each characteristic user responds to the gray level test notification to obtain a target configuration file of the gray level version of the target application;

and switching the target application in the client of the feature user from the currently used version to the grayscale version according to the target configuration file.

2. The method of claim 1, further comprising, prior to obtaining the feature user data set for the target application:

acquiring historical behavior data of a plurality of users of the target application;

determining at least one characteristic user according to the historical behavior data of the users and preset screening conditions;

acquiring attribute data of the at least one characteristic user;

and generating a characteristic user data set of the target application according to the attribute data of the at least one characteristic user.

3. The method of claim 1, wherein obtaining a target profile for a grayscale version of the target application comprises:

loading the target configuration file from a server of the target application;

under the condition that the target configuration file is successfully loaded, analyzing the target configuration file;

and in the case of determining that the target configuration file loading fails, reloading the target configuration file from the server of the target application.

4. The method of claim 1, further comprising, after switching a target application in a client of the feature user from a currently used version to the grayscale version:

acquiring feedback information of the gray scale version of the target application;

determining a quality level of the grayscale version of the target application based on the feedback information of the grayscale version of the target application;

and under the condition that the quality low level of the gray scale version of the target application is determined to be less than a preset threshold value, switching the target application in the client of the feature user from the gray scale version to the currently used version.

5. The method of claim 4, wherein switching the target application in the client of the feature user from the grayscale version to the currently used version if it is determined that the quality level of the grayscale version of the target application is below a preset threshold comprises:

under the condition that the quality level of the gray-scale version of the target application is lower than a preset threshold value, sending a version rollback notification to the client of each characteristic user in the characteristic user data set by utilizing a silent pushing technology;

the client of each characteristic user responds to the version rollback notification to acquire the configuration file of the currently used version;

and switching the target application in the client of the feature user from the grayscale version to the currently used version according to the configuration file of the currently used version.

6. The method of claim 1, further comprising, prior to obtaining a target profile for the grayscale version of the target application:

constructing a target configuration file of the gray-scale version of the target application based on the Flutter technology;

and uploading the target configuration file to a preset position of a server of the target application.

7. The method of claim 1, wherein the target configuration file is a file written using an extensible markup language.

8. The method of claim 1, wherein the attribute data comprises: the ID of the feature user.

9. A gradation issuing apparatus for an application, characterized by comprising:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a characteristic user data set of a target application under the condition of determining a release gray scale version of the target application; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user;

the sending module is used for sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent pushing technology;

a second obtaining module, configured to, in response to the grayscale test notification, obtain a target configuration file of the grayscale version of the target application by the client of each feature user;

and the version switching module is used for switching the target application in the client of the feature user from the currently used version to the gray-scale version according to the target configuration file.

10. The gray scale release method applied to the server is characterized by comprising the following steps:

the method comprises the steps that a server of a target application obtains a characteristic user data set of the target application under the condition that a gray level version of the target application is determined; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user;

and sending a gray level test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology.

11. The method of claim 10, after sending a grayscale test notification to the client of each feature user in the feature user data set using a silent push technique, further comprising:

and under the condition that the quality level of the gray-scale version of the target application is determined to be less than a preset threshold value, sending a version rollback notification to the client of each characteristic user in the characteristic user data set by utilizing a silent push technology.

12. A server, comprising:

the acquisition module is used for acquiring a characteristic user data set of the target application under the condition that the server of the target application determines the release gray scale version of the target application; wherein the feature user data set comprises attribute data of at least one feature user, and the attribute data is used for characterizing the feature user;

and the sending module is used for sending a gray test notification to the client of each characteristic user in the characteristic user data set by utilizing a silent pushing technology.

13. The gray scale release method applied to the client side comprises the following steps:

responding to the gray level test notification by a client of a characteristic user of the target application, and acquiring a target configuration file of a gray level version of the target application; the gray level test notification is sent to a characteristic user of the target application by the server of the target application by utilizing a silent push technology under the condition that the server of the target application determines that the target application releases the gray level version;

14. The method of claim 13, further comprising, after switching a target application in a client of the feature user from a currently used version to the grayscale version:

the client of the characteristic user acquires the configuration file of the currently used version under the condition of receiving a version rollback notification sent by the server of the target application;

15. A client, comprising:

the acquisition module is used for responding to the gray level test notification by a client of a characteristic user of the target application and acquiring a target configuration file of a gray level version of the target application; the gray level test notification is sent to a characteristic user of the target application by the server of the target application by utilizing a silent push technology under the condition that the server of the target application determines that the target application releases the gray level version;