Disclosure of Invention
In view of the foregoing, it is desirable to provide a multi-type application distribution method, apparatus, computer device, and storage medium capable of improving distribution efficiency.
A method of multi-type application publishing, the method comprising:
acquiring corresponding application release data which are input by a target developer and are logged into a request release page aiming at each application to be released; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of the native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released;
generating an application auditing instruction based on the application release data, and sending the application auditing instruction to an auditing terminal to trigger a system administrator logged in the auditing terminal to audit the application release data;
receiving a first audit result fed back by the audit terminal based on the application release data, and determining that the first audit result in the application to be released is a plurality of first target applications passing audit;
and publishing a plurality of first target applications to an application publishing platform based on application publishing data corresponding to each first target application.
In one embodiment, before the target developer logs in to the request issuing page and issues data for each application to be issued and the corresponding application input, the method further includes:
Acquiring an application registration request instruction triggered by a developer logged in an application registration page, and analyzing the application registration request instruction to obtain corresponding application registration information; the application registration information comprises an application name and a package name of an application installation package;
acquiring a second verification result correspondingly generated after a system administrator logged in the verification terminal verifies the application registration information;
and aiming at the target developer with the second verification result passing the verification, granting the login permission for the target developer to login to the request release page.
In one embodiment, the first audit result is determined by:
when each item of data in the application release data is successfully matched with a preset auditing rule, a first auditing result which represents that auditing passes is generated;
and when any one of the application release data is unsuccessfully matched with the preset auditing rule, generating a first auditing result which represents that auditing is not passed.
In one embodiment, the preset audit rule includes an audit rule that applies a release scope, and the method further includes:
And determining the audit rule of the application release range according to at least one of a predetermined download request party, a functional department to which the download request party belongs, an identification tag corresponding to the download request party, an operation terminal used by the download request party and an identification tag corresponding to the operation terminal.
In one embodiment, the determining that the first verification result in the application to be deployed is a plurality of first target applications that pass verification includes:
screening out target auditing results which are characterized by auditing passing from a plurality of obtained first auditing results, and a plurality of first target applications corresponding to the target auditing results;
and before releasing the plurality of first target applications to an application release platform, storing the acquired application release data corresponding to each first target application.
In one embodiment, after said publishing the plurality of the first target applications to the application publishing platform, the method further comprises:
receiving application downloading request instructions sent by a plurality of first downloading requesters within the issuing range of the target application, and analyzing the application downloading request instructions to obtain target application types corresponding to the requested downloaded applications respectively;
When the target application type is a third party application or a light application, loading an access address corresponding to the third party application or the light application which is currently requested to be downloaded, and sending the target access address obtained by loading to a corresponding first downloading requester;
when the application type is a native application, loading an application installation package of the native application which is currently requested to be downloaded, and sending a target application installation package obtained by loading to a corresponding first downloading requester;
and pushing the prompt information of the downloading failure to a second downloading requester aiming at the second downloading requester which does not belong to the issuing range of the target application so as to prompt the downloading failure.
In one embodiment, the method further comprises:
acquiring an application deleting operation instruction triggered by a target developer logged in the request issuing page, and determining a second target application corresponding to the application deleting operation instruction;
and deleting the application release data corresponding to the second target application.
A multi-type application publishing device, the device comprising:
the first acquisition module acquires the request release page logged in by the target developer and inputs corresponding application release data aiming at each application to be released; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of the native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released;
The triggering module generates an application auditing instruction based on the application release data and sends the application auditing instruction to an auditing terminal so as to trigger a system administrator logged in the auditing terminal to audit the application release data;
the second acquisition module is used for receiving a first audit result fed back by the audit terminal based on the application release data and determining that the first audit result in the application to be released is a plurality of first target applications passing audit;
and the release module is used for releasing the plurality of first target applications to the application release platform based on the application release data corresponding to each first target application.
A computer device comprising a memory storing a computer program and a processor which when executing the computer program performs the steps of:
acquiring corresponding application release data which are input by a target developer and are logged into a request release page aiming at each application to be released; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of the native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released;
Generating an application auditing instruction based on the application release data, and sending the application auditing instruction to an auditing terminal to trigger a system administrator logged in the auditing terminal to audit the application release data;
receiving a first audit result fed back by the audit terminal based on the application release data, and determining that the first audit result in the application to be released is a plurality of first target applications passing audit;
and publishing a plurality of first target applications to an application publishing platform based on application publishing data corresponding to each first target application.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
acquiring corresponding application release data which are input by a target developer and are logged into a request release page aiming at each application to be released; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of the native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released;
Generating an application auditing instruction based on the application release data, and sending the application auditing instruction to an auditing terminal to trigger a system administrator logged in the auditing terminal to audit the application release data;
receiving a first audit result fed back by the audit terminal based on the application release data, and determining that the first audit result in the application to be released is a plurality of first target applications passing audit;
and publishing a plurality of first target applications to an application publishing platform based on application publishing data corresponding to each first target application.
According to the method, the device, the computer equipment and the storage medium for issuing the multi-type application, the application issuing data corresponding to the multi-type application input by the target developer can be acquired, the application auditing instruction is generated based on the currently acquired application issuing data, a system administrator logged in an auditing terminal is triggered to audit the currently acquired application issuing data through the currently generated application auditing instruction, and the application issuing is performed based on the application issuing data corresponding to the corresponding first target application under the condition that the application issuing data is audited. At present, a centralized application release platform is used for carrying out centralized release of multiple types of applications, and related information (namely application release data) required to be filled in by each type of application is simplified and unified, so that the application release application flow is simplified, and the application release efficiency is improved.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The method for publishing the multi-type applications can be applied to an application environment shown in figure 1. Wherein the requesting terminal 102 and the auditing terminal 104 communicate with the server 106 over a network, respectively. The server 106 obtains application release data which is logged in to a request release page by a target developer and input for each application to be released, wherein the request release page is provided by the request terminal 102, and in addition, the application release data input by the target developer is further transmitted to the server 106 through a connection network between the request terminal 102 and the server 106; generating an application auditing instruction by the server 106 based on the application release data transmitted by the request terminal 102, and sending the application auditing instruction to the auditing terminal 104 to trigger a system administrator logged on to the auditing terminal 104 to audit the application release data; the server 106 receives a first verification result fed back by the verification terminal 104 based on the application release data, and determines that the first verification result in the application to be released is a plurality of first target applications passing verification; the server 106 publishes the plurality of first target applications to the application publishing platform based on the application publishing data corresponding to each first target application.
The requesting terminal 102 and the auditing terminal 104 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the server 106 may be implemented as a stand-alone server or a server cluster composed of multiple servers.
In one embodiment, as shown in fig. 2, a multi-type application publishing method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:
step S202, acquiring corresponding application release data which are input by a target developer and are logged into a request release page aiming at each application to be released.
The application to be deployed comprises a native application, a light application and a third party application of different operating systems. It should be noted that, the native application refers to an application program that can directly run on a corresponding operating system (for example, android, ios—an operating system developed by apple corporation); the light application is a full-function application which is not required to be downloaded and used immediately after searching, and can be an H5 (Html 5, a language description mode for constructing webpage content) light application by way of example; the third party application may be an apple application mall or the like dedicated to providing iOS application downloads. The application release data comprises an application running version, an application installation package of a native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released. It should be noted that, the application installation package for the Android native application may be an apk package (Android application package ); an application installation package for iOS native applications, which may be an ipa package (iPhone Application, apple application); the access address corresponding to the third party application is an installation link address, and after a user clicks and enters an access page provided by the installation link address, the application to be downloaded can be selected according to the self requirement; the access address of the light application is an access entry, and after the user clicks and enters the access page provided by the access address, the user can enjoy the corresponding application service, for example, if the light application is a game application, the user clicks the corresponding access entry and can quickly enter the game interface when the data loading is successful.
It should be noted that, the server obtains the request issue page logged in by the target developer, and issues data for each application to be issued, the input application. The target developer requests the release page to be a front-end access page provided by the server to the target developer with release qualification. At present, the server provides a corresponding application release environment for the target developer, so as to assist the target developer in applying and releasing the application. The request issuing page may include an operation bar, an edit box, a navigation bar, and the like. When a target developer logs in to a request release page through a request terminal, application release data needing to be input are input into an edit box through corresponding input equipment, and when a 'submit' button in an operation column is clicked, the currently input application release data is transmitted to a server.
Specifically, before obtaining the data to be published by the corresponding application input by the target developer logging in to the request publishing page and aiming at each application to be published, the method further comprises: acquiring an application registration request instruction triggered by a developer logged in an application registration page, and analyzing the application registration request instruction to obtain corresponding application registration information; the application registration information comprises an application name and a package name of an application installation package; acquiring a second audit result correspondingly generated after a system administrator logged in an audit terminal audits application registration information; aiming at the target developer with the second verification result passing the verification, the login permission of the target developer to the request release page is granted.
In one embodiment, a server obtains an application registration request instruction, and after analyzing the application registration request instruction, obtains corresponding application registration information; in addition, the server also needs to generate a registration auditing instruction based on the application registration information, and the generated registration auditing instruction is sent to the auditing terminal to trigger a system administrator logged in the auditing terminal to audit the application registration information. After a system administrator logs in an auditing terminal and audits various data included in the application registration information, a corresponding second auditing result is generated; the second audit result generated by the audit terminal is further transmitted to the server, and the server grants login permission for logging in the request release page for the target developer passing the audit by aiming at the second audit result.
In one embodiment, the server may be deployed in an intranet, and the publishing of the target application is performed through the intranet. Enterprise members can also download published target applications from the application publication platform through intranet connection.
According to the embodiment, before the server obtains the application release data input by the target developer, based on the application registration information obtained by analyzing the application registration instruction, whether the login permission of the request release page is opened to the developer is judged, so that an illegal user which does not accord with the application qualification is prevented from logging in the request release page, and the application release quality is improved.
And step S204, an application auditing instruction is generated based on the application release data, and the application auditing instruction is sent to the auditing terminal so as to trigger a system administrator logged in the auditing terminal to audit the application release data.
The server generates an application auditing instruction based on the application issuing data, the application auditing instruction is used as an auditing prompt instruction, and after the application auditing instruction is transmitted to an auditing terminal through a connected network by the server, a system manager is prompted to currently have data to be audited, and the system manager is guided to audit the currently transmitted application issuing data.
Step S206, receiving a first audit result fed back by the audit terminal based on the application release data, and determining that the first audit result in the application to be released is a plurality of first target applications passing the audit.
Specifically, the first audit result is determined by: when each item of data in the application release data is successfully matched with a preset auditing rule, a first auditing result which represents that auditing passes is generated; when any one of the application release data is unsuccessfully matched with a preset auditing rule, a first auditing result which characterizes that auditing is not passed is generated.
In one embodiment, each item of data in the application release data is matched with a preset auditing rule by an auditing terminal; the preset auditing rules comprise a first auditing rule of an application running version, a second auditing rule of an application installation package, a third auditing rule of an access address and a fourth auditing rule of an application release range, wherein the auditing terminal performs auditing of application release data through the following steps:
(a1) And detecting whether the application running version meets the rule or not based on the first audit rule, and outputting an audit result of successful audit of the application running version under the condition that the current application running version is determined to meet the rule.
(a2) Detecting whether a missing file exists in the application installation package or not based on a second audit rule, and outputting an audit result of successful audit of the application installation package when determining that the missing file does not exist in the current application installation package;
(a3) And detecting whether the access address can be normally accessed or not based on the third audit rule, and outputting an audit result of successful audit of the access address under the condition that the current access address can be normally accessed.
(a4) And determining the audit rule of the application release range according to at least one of a predetermined download request party, a functional department to which the download request party belongs, an identification tag corresponding to the download request party, an operation terminal used by the download request party and an identification tag corresponding to the operation terminal. Based on the determined fourth audit rule, the audit terminal judges whether the application release range of the application required by the target developer meets the rule, and if the current application release range is determined to meet the rule, the audit result of successful audit of the application release range is output.
It should be noted that, referring to fig. 3, in the aspect of unified management of application distribution ranges, the server may perform unified distribution management for a single user, a user department, a user tag, a single device, and a device tag, where a download requester may be understood as a target user (i.e., a single user) within a target application distribution range and having a purpose of downloading requirements. The functional department to which the download requester belongs may understand the portion (i.e., user department) of the corresponding service of the target user in the company to which the download requester belongs, where the department may be understood as an administrative department, a technical department, a financial department, etc., which is not limited by the embodiment of the present application. According to the functional departments to which the downloading request party belongs, the audit sub rules of the application release range are determined, namely, the application rights for requesting the downloading of the users in different functional departments are different, for example, the users of the financial departments only have the downloading rights of the financial management application, but do not have the downloading rights of the administrative management application. And determining the audit rule of the application release range according to the identification tag (namely the user tag) corresponding to the download request party, wherein the audit rule is different for application download authorities of users with different job classes, for example, a first user with a manager class has the download authorities of the application A, and a second user with a lower manager class does not have the download authorities of the application A, but has the download authorities of the application B. The determination of the audit rule of the application release range according to the operation terminal (i.e. a single device) and the identification tag (i.e. a device tag) corresponding to the operation terminal may be further understood according to the above execution logic, which is not limited in the embodiment of the present application.
(5) And (3) integrating the auditing results corresponding to the data issued by each application in the steps (a 1) - (a 4) by an auditing terminal, and further generating a first auditing result representing that the auditing is passed or generating a first auditing result representing that the auditing is not passed.
According to the embodiment, the auditing sub-rule design of the application release range is carried out from different dimensions according to the predetermined download request party, the function department to which the download request party belongs, the identification tag corresponding to the download request party, the operation terminal used by the download request party and the identification tag corresponding to the operation terminal, so that unified management of the application release range is realized, and the application release efficiency and the accuracy and flexibility of application range distribution are improved.
Step S208, based on the application release data corresponding to each first target application, releasing the plurality of first target applications to the application release platform.
Specifically, the server publishes a plurality of first target applications corresponding to the application publishing requests to the application publishing platform based on the application publishing data corresponding to each first target application, so that a user logged in the application publishing platform can use the published applications.
In one embodiment, before the first target applications are published to the application publishing platform, the server stores the acquired application publishing data corresponding to each first target application. For example, the application release data may be stored based on a memory, or the application release data may be stored based on a database, and when the corresponding application release data needs to be fed back to the download requester, the server may call the stored data, and further pushing is performed.
In the embodiment, the unified management problem of multiple types of applications is solved, and the efficiency, quality, convenience and the like of application management are improved.
In the method for issuing the multi-type application, application issuing data corresponding to the multi-type application input by a target developer can be acquired, an application auditing instruction is generated based on the currently acquired application issuing data, a system administrator logged in an auditing terminal is triggered to audit the currently acquired application issuing data through the currently generated application auditing instruction, and application issuing is performed based on the application issuing data corresponding to the corresponding first target application under the condition that the application issuing data is audited. At present, a centralized application release platform is used for carrying out centralized release of multiple types of applications, and related information (namely application release data) required to be filled in by each type of application is simplified and unified, so that the application release application flow is simplified, and the application release efficiency is improved.
In one embodiment, as shown in fig. 4, the step of determining that the first audit result in the application to be published is a plurality of first target applications that pass the audit includes:
and step S402, screening out target audit results which are characterized by passing audit and a plurality of first target applications corresponding to the target audit results from the obtained plurality of first audit results.
The server screens out target auditing results which characterize auditing passing from the obtained multiple first auditing results based on preset identification rules, and multiple first target applications corresponding to the target auditing results. In the background management aspect of the application, the server follows the principle of three-rights separation to divide the fine authority into three roles of a security manager (i.e. a developer or a target developer), a system manager and an auditor, wherein the functional scope of the system manager comprises application registration audit, version release audit, version upgrading audit, application on-shelf audit, off-shelf audit and the like. The functional scope of the security manager comprises application registration application, application version release application, version upgrade application, application on-shelf application, application off-shelf application and the like. The auditor has clear authority to the functions of the system manager and the security manager, avoids the operation risk caused by overlarge authority of one party, improves the efficiency of personnel management and improves the security consciousness of operators.
Step S404, before publishing the plurality of first target applications to the application publishing platform, storing the obtained application publishing data corresponding to each first target application.
Specifically, the server stores the application release data based on the memory or the database, and when the corresponding application release data needs to be fed back to the download requesting party later, the server calls the stored data and pushes the stored data further.
In one embodiment, after publishing the plurality of first target applications to the application publishing platform, the method further includes: receiving application downloading request instructions sent by a plurality of first downloading requesters within the issuing range of the target application, and analyzing the application downloading request instructions to obtain target application types corresponding to the requested downloaded applications respectively; when the target application type is a third party application or a light application, loading an access address corresponding to the third party application or the light application which is currently requested to be downloaded, and sending the target access address obtained by loading to a corresponding first downloading requester; when the application type is a native application, loading an application installation package of the native application which is currently requested to be downloaded, and sending a target application installation package obtained by loading to a corresponding first downloading requester; and pushing the prompt information of the downloading failure to the second downloading requester aiming at the second downloading requester which does not belong to the issuing range of the target application so as to prompt the downloading failure.
In one embodiment, the method further comprises: acquiring an application deleting operation instruction triggered by a target developer logged in to a request issuing page, and determining a second target application corresponding to the application deleting operation instruction; and deleting the application release data corresponding to the second target application.
In connection with the above embodiment, please refer to fig. 5, which is a flowchart of publishing H5 light application, when publishing H5 light application, the method specifically includes the steps of:
(b1) When a developer logs in to an application registration request page provided by a request terminal with the identity of a security administrator, filling registration filling information to be filled in into an input box appointed in the application registration request page, and after clicking a 'submit' button in an operation column, acquiring application registration information by a server and carrying out security configuration storage of H5 light application.
(b2) And generating an application auditing instruction by the server according to the acquired application registration information, and sending the application auditing instruction to the auditing terminal so as to trigger a system administrator logged in the auditing terminal to audit the application registration information.
(b3) After logging in the auditing terminal, the system administrator audits the acquired application registration information, and feeds back the generated second auditing result to the server, and the server grants login permission for the target developer with the second auditing result passing the auditing to the request release page.
(b4) The target developer with application release qualification logs in the request release page through the identity of the security manager, fills the application release data required to be filled in an input box appointed in the request release page, and after clicking a 'submit' button in an operation column, the server acquires the application release data and stores an access address of the H5 light application. The application release data filled by the target developer further comprises application release ranges corresponding to the applications to be released.
(b5) And generating an application auditing instruction based on the application release data by the server, and sending the application auditing instruction to the auditing terminal so as to trigger a system administrator logged in the auditing terminal to audit the application release data.
(b6) And the server receives a first verification result fed back by the verification terminal based on the application release data, and determines that the first verification result in the application to be released is a plurality of first target applications passing verification.
(b7) And the server publishes the plurality of first target applications to the application publishing platform based on the application publishing data corresponding to each first target application.
It should be noted that, for the release process of the native application and the third party application, reference may be made to steps (b 1) - (b 7), and specific description is not given here in the embodiment of the present application.
It should be understood that, although the steps in the flowcharts of fig. 2, 4, and 5 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in fig. 2 and 4 may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the execution of the steps or stages is not necessarily sequential, but may be performed in turn or alternately with at least a portion of the steps or stages in other steps or other steps.
In one embodiment, as shown in fig. 6, there is provided a multi-type application publishing device 600 comprising: a first acquisition module 601, a triggering module 602, a second acquisition module 603, and a publishing module 604, wherein:
the first obtaining module 601 is configured to obtain, by a target developer, log in to a request issue page, and input corresponding application issue data for each application to be issued; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of a native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released.
The triggering module 602 is configured to generate an application auditing instruction based on the application release data, and send the application auditing instruction to the auditing terminal, so as to trigger a system administrator logged on the auditing terminal to audit the application release data.
The second obtaining module 603 is configured to receive a first audit result fed back by the audit terminal based on the application publishing data, and determine that the first audit result in the application to be published is a plurality of first target applications that pass the audit.
And the publishing module 604 is configured to publish the plurality of first target applications to the application publishing platform based on application publishing data corresponding to each first target application.
In one embodiment, the multi-type application publishing device 600 further includes a registration module, where the registration module includes a first acquisition sub-module, a second acquisition sub-module, and a rights granting sub-module, and the rights granting sub-module includes:
the first acquisition sub-module is used for acquiring an application registration request instruction triggered by a developer logged in an application registration page, and analyzing the application registration request instruction to obtain corresponding application registration information; the application registration information includes an application name and a package name of the application installation package.
And the second acquisition sub-module is used for acquiring a second verification result correspondingly generated after a system administrator logged in the verification terminal verifies the application registration information.
And the permission granting sub-module is used for granting login permission for the target developer to login to the request release page aiming at the target developer which passes the second verification result.
In one embodiment, the second obtaining module 603 is further configured to generate a first audit result that characterizes passing of the audit when each item of data in the application publishing data is successfully matched with a preset audit rule; when any one of the application release data is unsuccessfully matched with a preset auditing rule, a first auditing result which characterizes that auditing is not passed is generated.
In one embodiment, the second obtaining module 603 is further configured to determine an audit rule of the application publishing range according to at least one of a predetermined download requester, a functional department to which the download requester belongs, an identification tag corresponding to the download requester, an operation terminal used by the download requester, and an identification tag corresponding to the operation terminal.
In one embodiment, the second obtaining module 603 is further configured to screen out a target audit result that characterizes the passing of the audit from the obtained multiple first audit results, and multiple first target applications corresponding to the target audit result; before a plurality of first target applications are released to an application release platform, storing the obtained application release data corresponding to each first target application.
In one embodiment, the multi-type application publishing device 600 further includes a push module, where:
the pushing module is used for receiving application downloading request instructions sent by a plurality of first downloading requesters within the issuing range of the target application, and analyzing the application downloading request instructions to obtain target application types corresponding to the requested downloaded applications respectively; when the target application type is a third party application or a light application, loading an access address corresponding to the third party application or the light application which is currently requested to be downloaded, and sending the target access address obtained by loading to a corresponding first downloading requester; when the application type is a native application, loading an application installation package of the native application which is currently requested to be downloaded, and sending a target application installation package obtained by loading to a corresponding first downloading requester; and pushing the prompt information of the downloading failure to the second downloading requester aiming at the second downloading requester which does not belong to the issuing range of the target application so as to prompt the downloading failure.
In one embodiment, the multi-type application publishing device 600 further includes a delete module, wherein:
The deleting module is used for acquiring an application deleting operation instruction triggered by a target developer logged in a request release page and determining a second target application corresponding to the application deleting operation instruction; and deleting the application release data corresponding to the second target application.
The multi-type application release device can acquire application release data corresponding to multi-type applications input by a target developer, generate an application audit instruction based on the currently acquired application release data, trigger a system administrator logged in an audit terminal to audit the currently acquired application release data through the currently generated application audit instruction, and perform application release based on the application release data corresponding to the corresponding first target application under the condition that the application release data audit is passed. At present, a centralized application release platform is used for carrying out centralized release of multiple types of applications, and related information (namely application release data) required to be filled in by each type of application is simplified and unified, so that the application release application flow is simplified, and the application release efficiency is improved.
For specific limitations on the multi-type application publishing device, reference may be made to the above limitation on the multi-type application publishing method, and no further description is given here. The respective modules in the above-described multi-type application issuing apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing application publication data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a multi-type application publishing method.
It will be appreciated by those skilled in the art that the structure shown in FIG. 7 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of: acquiring corresponding application release data which are input by a target developer and are logged into a request release page aiming at each application to be released; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of a native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released; generating an application auditing instruction based on the application release data, and sending the application auditing instruction to an auditing terminal to trigger a system administrator logged in the auditing terminal to audit the application release data; receiving a first audit result fed back by an audit terminal based on application release data, and determining that the first audit result in the application to be released is a plurality of first target applications passing audit; and publishing the plurality of first target applications to an application publishing platform based on the application publishing data corresponding to each first target application.
In one embodiment, before obtaining the data to be published by the target developer logging into the request publishing page and inputting the corresponding application publishing data for each application to be published, the following steps are further implemented when the processor executes the computer program: acquiring an application registration request instruction triggered by a developer logged in an application registration page, and analyzing the application registration request instruction to obtain corresponding application registration information; the application registration information comprises an application name and a package name of an application installation package; acquiring a second audit result correspondingly generated after a system administrator logged in an audit terminal audits application registration information; aiming at the target developer with the second verification result passing the verification, the login permission of the target developer to the request release page is granted.
In one embodiment, the processor when executing the computer program further performs the steps of: when each item of data in the application release data is successfully matched with a preset auditing rule, a first auditing result which represents that auditing passes is generated; when any one of the application release data is unsuccessfully matched with a preset auditing rule, a first auditing result which characterizes that auditing is not passed is generated.
In one embodiment, the preset audit rules include audit sub-rules for applying the release scope, and the processor when executing the computer program further performs the steps of: and determining the audit rule of the application release range according to at least one of a predetermined download request party, a functional department to which the download request party belongs, an identification tag corresponding to the download request party, an operation terminal used by the download request party and an identification tag corresponding to the operation terminal.
In one embodiment, the processor when executing the computer program further performs the steps of: screening out target auditing results which are characterized by auditing passing and a plurality of first target applications corresponding to the target auditing results from the obtained plurality of first auditing results; before a plurality of first target applications are released to an application release platform, storing the obtained application release data corresponding to each first target application.
In one embodiment, after publishing the plurality of first target applications to the application publishing platform, the processor when executing the computer program further performs the steps of: receiving application downloading request instructions sent by a plurality of first downloading requesters within the issuing range of the target application, and analyzing the application downloading request instructions to obtain target application types corresponding to the requested downloaded applications respectively; when the target application type is a third party application or a light application, loading an access address corresponding to the third party application or the light application which is currently requested to be downloaded, and sending the target access address obtained by loading to a corresponding first downloading requester; when the application type is a native application, loading an application installation package of the native application which is currently requested to be downloaded, and sending a target application installation package obtained by loading to a corresponding first downloading requester; and pushing the prompt information of the downloading failure to the second downloading requester aiming at the second downloading requester which does not belong to the issuing range of the target application so as to prompt the downloading failure.
In one embodiment, the processor when executing the computer program further performs the steps of: acquiring an application deleting operation instruction triggered by a target developer logged in to a request issuing page, and determining a second target application corresponding to the application deleting operation instruction; and deleting the application release data corresponding to the second target application.
The computer equipment can acquire the application release data corresponding to the multiple types of applications input by the target developer, generate an application auditing instruction based on the application release data which is acquired currently, trigger a system administrator logged in an auditing terminal to audit the application release data which is acquired currently through the application auditing instruction which is generated currently, and perform application release based on the application release data corresponding to the corresponding first target application under the condition that the application release data is audited to pass. At present, a centralized application release platform is used for carrying out centralized release of multiple types of applications, and related information (namely application release data) required to be filled in by each type of application is simplified and unified, so that the application release application flow is simplified, and the application release efficiency is improved.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring corresponding application release data which are input by a target developer and are logged into a request release page aiming at each application to be released; the application to be distributed comprises a native application, a light application and a third party application of different operating systems; the application release data comprises an application running version, an application installation package of a native application, access addresses corresponding to the light application and the third party application, and application release ranges corresponding to the applications to be released; generating an application auditing instruction based on the application release data, and sending the application auditing instruction to an auditing terminal to trigger a system administrator logged in the auditing terminal to audit the application release data; receiving a first audit result fed back by an audit terminal based on application release data, and determining that the first audit result in the application to be released is a plurality of first target applications passing audit; and publishing the plurality of first target applications to an application publishing platform based on the application publishing data corresponding to each first target application.
In one embodiment, before obtaining the data published by the target developer to log on to the request publication page and for each application to be published, the computer program when executed by the processor further performs the steps of: acquiring an application registration request instruction triggered by a developer logged in an application registration page, and analyzing the application registration request instruction to obtain corresponding application registration information; the application registration information comprises an application name and a package name of an application installation package; acquiring a second audit result correspondingly generated after a system administrator logged in an audit terminal audits application registration information; aiming at the target developer with the second verification result passing the verification, the login permission of the target developer to the request release page is granted.
In one embodiment, the computer program when executed by the processor further performs the steps of: when each item of data in the application release data is successfully matched with a preset auditing rule, a first auditing result which represents that auditing passes is generated; when any one of the application release data is unsuccessfully matched with a preset auditing rule, a first auditing result which characterizes that auditing is not passed is generated.
In one embodiment, the pre-set audit rules include audit rules that apply a release scope, the computer program when executed by the processor further implementing the steps of: and determining the audit rule of the application release range according to at least one of a predetermined download request party, a functional department to which the download request party belongs, an identification tag corresponding to the download request party, an operation terminal used by the download request party and an identification tag corresponding to the operation terminal.
In one embodiment, the computer program when executed by the processor further performs the steps of: screening out target auditing results which are characterized by auditing passing and a plurality of first target applications corresponding to the target auditing results from the obtained plurality of first auditing results; before a plurality of first target applications are released to an application release platform, storing the obtained application release data corresponding to each first target application.
In one embodiment, after publishing the plurality of first target applications to the application publishing platform, the computer program when executed by the processor further performs the steps of: receiving application downloading request instructions sent by a plurality of first downloading requesters within the issuing range of the target application, and analyzing the application downloading request instructions to obtain target application types corresponding to the requested downloaded applications respectively; when the target application type is a third party application or a light application, loading an access address corresponding to the third party application or the light application which is currently requested to be downloaded, and sending the target access address obtained by loading to a corresponding first downloading requester; when the application type is a native application, loading an application installation package of the native application which is currently requested to be downloaded, and sending a target application installation package obtained by loading to a corresponding first downloading requester; and pushing the prompt information of the downloading failure to the second downloading requester aiming at the second downloading requester which does not belong to the issuing range of the target application so as to prompt the downloading failure.
In one embodiment, the computer program when executed by the processor further implements the steps of obtaining an application deletion operation instruction triggered by a target developer logged in to the request issue page, and determining a second target application corresponding to the application deletion operation instruction; and deleting the application release data corresponding to the second target application.
The storage medium can acquire application release data corresponding to multiple types of applications input by a target developer, generate an application auditing instruction based on the application release data which is acquired currently, trigger a system administrator logged in an auditing terminal to audit the application release data which is acquired currently through the application auditing instruction which is generated currently, and perform application release based on the application release data corresponding to the corresponding first target application under the condition that the application release data is audited and passed. At present, a centralized application release platform is used for carrying out centralized release of multiple types of applications, and related information (namely application release data) required to be filled in by each type of application is simplified and unified, so that the application release application flow is simplified, and the application release efficiency is improved.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.