Release method, device, equipment, medium and product

Abstract

The invention discloses a publishing method and device, equipment, a medium and a product in the technical field of computers, and the method comprises the steps: for a created first application, if an operation triggered for a resource address of the first application is detected, displaying at least one candidate item, so that application processing flows indicated by different candidate items are different; therefore, a user can know which new application publishing mode is supported by the first application from the at least one candidate item, so that when the operation of selecting the first item from the at least one candidate item is detected, the application processing flow indicated by the first item is executed according to the resource file pointed by the resource address. The second application is automatically published according to the quick publishing path. Therefore, the application processing flow indicated by the first item is configured to automatically publish the second application based on the first application, so that user operation is not needed in the execution process of the application processing flow indicated by the first item, the user operation is simplified, the efficiency is improved, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly to a method, apparatus, device, medium, or product for publishing. Background Technology

[0002] An application is software developed for a specific task, such as office software, games, or mini-programs, to provide services to users.

[0003] In addition, for the already created application 1, some users may want to enjoy the services provided by application 1 by accessing application 1. However, other users may have the following needs: these users want to publish a new application based on application 1, so that the new application retains some features (such as some or all of the service features) compared to application 1, and the new application has undergone some changes compared to application 1 (such as changes in publisher, publishing permissions, and integration systems). Summary of the Invention

[0004] To meet the above requirements, this application provides a publishing method, apparatus, device, medium, and product.

[0005] To achieve the above objectives, the technical solution provided in this application is as follows:

[0006] This application provides a publishing method, the method comprising: in response to an operation triggered for a first application, displaying at least one candidate option, wherein different candidate options indicate different application processing flows; in response to detecting an operation of selecting a first item from the at least one candidate option, executing the application processing flow indicated by the first item according to the resource file of the first application, wherein the application processing flow indicated by the first item is configured to realize the automatic publishing of a second application based on the first application.

[0007] In one possible implementation, the method further includes: in response to detecting an operation that selects the first item from the at least one candidate, displaying the execution progress of the application processing flow indicated by the first item.

[0008] In one possible implementation, the method further includes: in response to the application processing flow including at least one stage, presenting a connection relationship between different stages in the at least one stage, the connection relationship being configured to indicate the execution order of the different stages in the at least one stage in the application processing flow.

[0009] In one possible implementation, the method further includes: in response to detecting an operation of selecting a second item from the at least one candidate item, executing an application processing flow indicated by the second item according to the resource file, wherein the application processing flow indicated by the second item is configured to implement the manual release of a third application based on the first application.

[0010] In one possible implementation, the at least one candidate further includes a second item; the application processing flow indicated by the first item lacks at least one stage compared to the application processing flow indicated by the second item, the at least one stage including a development error checking stage.

[0011] In one possible implementation, the method further includes: displaying configuration items corresponding to the first application in response to an operation triggered for the first application, the configuration items being determined based on at least one type of developable content corresponding to the first application; updating the configuration items in response to detecting an adjustment operation for the configuration items; the execution of the application processing flow indicated by the first item based on the resource files of the first application includes: executing the application processing flow indicated by the first item based on the configuration items and the resource files, the application processing flow indicated by the first item including an automatic development phase, the automatic development phase being configured to adjust the first application based on the configuration items to obtain the second application.

[0012] In one possible implementation, the application processing flow indicated by the first item includes a publishing association step, which is configured to be executed automatically based on information in the resource file corresponding to the publishing association step.

[0013] In one possible implementation, the at least one candidate further includes a second item; the method further includes: in response to detecting a problem during the execution of the application processing flow indicated by the first item, jumping to the stage in the application processing flow indicated by the second item that matches the problem.

[0014] In one possible implementation, the method satisfies at least one of the following constraints: the first application is an application template; the second application is the same application as the first application, the services provided by the second application are consistent with those provided by the first application, and the second application differs from the first application in at least one configuration, the at least one configuration including at least a portion of application publisher, application publishing permissions, application integration system, and application publishing scope; the different items in the at least one candidate are displayed using different components in the second interface, and the second interface also displays the configuration items corresponding to the first application; the application processing flow indicated by the first item includes an application installation stage and a publishing preparation stage, the application installation stage is configured to automatically execute the application installation process based on the resource file, and the publishing preparation stage is configured to automatically execute the application publishing preparation process for the second application.

[0015] This application provides a publishing apparatus, comprising: a data display unit, configured to display at least one candidate option in response to an operation triggered for a first application, wherein different candidate options indicate different application processing flows; and a first execution unit, configured to execute the application processing flow indicated by the first option based on the resource file of the first application in response to detecting an operation that selects a first option from the at least one candidate option, wherein the application processing flow indicated by the first option is configured to automatically publish a second application based on the first application.

[0016] This application provides an electronic device, the device comprising: a processor and a memory; the memory for storing instructions or computer programs; the processor for executing the instructions or computer programs in the memory to cause the electronic device to perform the publishing method provided in this application.

[0017] This application provides a computer-readable medium storing instructions or a computer program that, when executed on a device, causes the device to perform the publishing method provided in this application.

[0018] This application provides a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the publishing method provided in this application.

[0019] Compared with related technologies, this application has at least the following advantages:

[0020] In the technical solution provided in this application, for a pre-created first application (such as an application template), if an operation triggered by the first application is detected, it can be determined that the user wants to use the first application to meet a certain need (such as the need to publish a new application). Therefore, at least one candidate option (such as an "Install" option, an "Install and Publish" option, etc.) is displayed so that different candidate options indicate different application processing flows. This allows the user to know from the at least one candidate option which new application publishing method the first application supports. When an operation is detected where the first option (such as the "Install and Publish" option) is selected from the at least one candidate option, it can be determined that the user wants to automatically publish a new application based on the first application according to the quick publishing path. Therefore, the application processing flow indicated by the first option (such as a process that can realize the quick publishing path) is executed according to the resource files of the first application to automatically publish a second application (such as an application identical to the first application) according to the quick publishing path. It can be seen that because the application processing flow indicated by the first option is configured to automatically publish the second application based on the first application, no user operation is required during the execution of the application processing flow indicated by the first option, thereby simplifying user operation when publishing a new application, improving efficiency, and enhancing user experience. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 A flowchart illustrating a publishing method provided in an embodiment of this application;

[0023] Figure 2 A schematic diagram illustrating a different publishing process provided for an embodiment of this application;

[0024] Figure 3 This is a schematic diagram of the first part of a fast publishing process provided in an embodiment of this application;

[0025] Figure 4 A schematic diagram of the second part of a fast publishing process provided in an embodiment of this application;

[0026] Figure 5 A schematic diagram of the third part of a fast publishing process provided in an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of the structure of a publishing device provided in an embodiment of this application;

[0028] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] Research has revealed that in certain scenarios, users can leverage relevant platforms to streamline the new application release process. Specifically, this can include: after entering the platform, the user selects an application template from a large pool of options to access the template's details page. This page provides information about the selected template (such as resource addresses), allowing the platform to detect when the user initiates an installation process. Upon successful installation, the user is automatically redirected to the development platform to develop the application according to their needs. After development, if the platform detects that the user has triggered an application release action, the platform checks for errors in the developed application. If no errors are found, the platform initiates the application release process (such as submitting a release request or completing the release process). This allows the user to manually advance the release process until it is fully completed, resulting in the new application's release.

[0030] The research also found that the solution shown above, which uses the path of "creating an application template → installing the application → developing the application → publishing the application", has the following drawbacks: too many steps, cumbersome publishing process, easy user churn, and negative impact on application activity conversion rate.

[0031] Research also revealed that in some scenarios, users may have a need to "publish an app that is identical to an existing app." However, when using the solutions described in the two paragraphs above to achieve this need, at least the following drawbacks exist: the solution requires users to perform numerous operations, increasing the operational difficulty and usage threshold, thus impacting the user experience. Furthermore, the "identical app" is almost entirely different from the existing app.

[0032] Based on the above research, in order to better improve user experience, this application provides a publishing method, which includes: for a first application that has been created (such as an application template), if an operation triggered for the first application is detected, it can be determined that the user wants to use the first application to meet a certain need (such as the need to publish a new application). Therefore, at least one candidate option (such as "Install" option, "Install and Publish" option, etc.) is displayed so that the application processing flow indicated by different candidate options is different, so that the user can know from the at least one candidate option what kind of new application publishing method the first application supports. So that when an operation of selecting the first item (such as the "Install and Publish" option) from the at least one candidate option is detected, it can be determined that the user wants to automatically publish a new application based on the first application according to the quick publishing path. Therefore, the application processing flow indicated by the first item (such as the process that can realize the quick publishing path) is executed according to the resource file of the first application to realize the automatic publishing of a second application (such as the same application as the first application) according to the quick publishing path. As can be seen, the application processing flow of the first instruction is configured to automatically publish the second application based on the first application, so that no user operation is required during the execution of the application processing flow of the first instruction, thereby simplifying user operations when publishing a new application, improving efficiency, and enhancing user experience.

[0033] Furthermore, this application does not limit the subject of the published method; for example, the method can be applied to a terminal device. Alternatively, the method can be implemented through data interaction between the terminal device and a server. The terminal device can be a smartphone, computer, personal digital assistant (PDA), tablet computer, etc. The server can be a standalone server, a cluster server, or a cloud server.

[0034] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0035] To better understand the technical solution provided in this application, the publication method provided in this application will be explained below with reference to some accompanying drawings. For example... Figure 1 As shown, the publishing method provided in this application includes S1-S2 below.

[0036] S1: In response to an operation triggered by the first application, display at least one candidate option, with different candidate options indicating different application processing flows.

[0037] The first application refers to an application that has already been created and can be accessed and used by users (such as...). Figure 2 The application template shown or Figure 3 The application template shown is 1, so that new applications can be released based on this first application in the future.

[0038] Furthermore, this application does not limit the implementation method of the first application. For example, it can be implemented using any pre-created application capable of providing services to users. Also, in some scenarios, the first application may refer to an application template selected by the user from a large number of application templates that meets their needs.

[0039] Therefore, in one possible implementation, the first application mentioned above can be an application template, so that new applications can be subsequently released based on this application template. Since the application template refers to a pre-built application that can be directly used by users, it avoids any issues that might hinder release, thus allowing some steps (such as...) to be bypassed when releasing a new application based on the application template. Figure 2 The step shown, "Metadata check for errors," is used to improve efficiency.

[0040] At least one candidate option refers to an option presented to the user after the user selects the first application, which describes different ways of using the first application (such as by...). Figure 3 The pop-up window 305 shows options such as "Install" and "Install and Publish", so that different options in the at least one candidate indicate different processing methods for the first application.

[0041] Therefore, in one possible implementation, the above-mentioned at least one candidate option can describe the new application release path that can be selected when releasing a new application based on the first application (e.g., Figure 2 (e.g., quick release paths and regular release paths), so that different candidates in at least one candidate can indicate different application processing flows presented under different release paths, so that different release flows for the same application can be implemented separately using different candidates (e.g., ... Figure 2 The two publishing processes are shown.

[0042] Furthermore, this application does not limit the implementation of the above-mentioned at least one candidate option. For example, it can be implemented in any way that can present different options, such as a list or buttons.

[0043] Therefore, in one possible implementation, S1 can specifically be: in response to an operation triggered by the first application, displaying at least one component corresponding to each candidate option in the candidate options (such as...). Figure 3The pop-up window 305 shows the "Install" and "Install and Publish" buttons, so that the corresponding application processing flow can be triggered by operating the component later.

[0044] Furthermore, this application does not limit the implementation method of the "operation" in S1 above. For example, in some scenarios, the operation may refer to an operation triggered by a user for a first application they are accessing. As another example, in some scenarios, the operation may refer to an operation triggered by a user for content associated with the first application (such as a resource address, etc.). Figure 3 The component 303 shown on page 302 is triggered. The resource address describes the address where the resource files (such as the installation package) of the first application are located; moreover, this application does not limit the method of obtaining the resource address; for example, it can be implemented using any method capable of obtaining the application resource address.

[0045] Furthermore, this application does not limit the implementation method of S1 described above. For example, in some scenarios, S1 may specifically include the following steps: when a user enters a platform that provides new application publishing services (such as a platform provided by...), Figure 3 After the platform shown on page 301, some application templates (such as those provided by...) are displayed to the user. Figure 3 Application templates 1 to 4 shown on page 301 are used to detect when a user selects a first application from these application templates (as shown by...). Figure 3 After selecting application template 1 as shown on page 301, the content corresponding to the first application is displayed to the user (such as by...). Figure 3 Components 303, etc. shown on page 302, and when an action triggered by the user on the content is detected, at least one candidate option (such as those shown by [component name]) is displayed to the user. Figure 3 The options described in the pop-up window 305 (the "Install" button and the "Install and Publish" button) allow users to know what actions they can take for the first application.

[0046] S2: In response to detecting an operation that selects a first item from at least one candidate, execute the application processing flow indicated by the first item according to the resource file of the first application, the application processing flow indicated by the first item being configured to automatically publish a second application based on the first application.

[0047] The resource files (such as the installation package) of the first application refer to the resources required when installing the first application, so that the resource files can describe the characteristics of the first application.

[0048] Furthermore, this application does not limit the implementation method of the resource files of the first application described above. For example, it may include the installation package of the first application.

[0049] Furthermore, this application does not limit the relationship between the resource file of the first application and the resource address of the first application. For example, the resource address can indicate the location where the resource file is obtained.

[0050] The second application refers to following the quick publishing path (such as by...). Figure 2 The second application is a new application obtained by automating the processing of the first application (as shown in the shortcut deployment path). It is evident that the second application is automatically determined based on the first application.

[0051] Furthermore, this application does not limit the implementation of the second application. For example, in some scenarios, the second application can satisfy the following constraints: the second application is almost unchanged from the first application (e.g., there are no changes in content development), so that the functions implemented by the second application are consistent with the functions implemented by the first application (e.g., the same or highly similar), thereby making the resource files of the second application almost indistinguishable from the resource files of the first application.

[0052] As can be seen, in one possible implementation, the second application can be an identical application to the first application, providing services consistent with those of the first application (e.g., identical or with a similarity exceeding a certain threshold). The second application differs from the first application in at least one configuration aspect, including at least a portion of the application publisher, application publishing permissions, application integration system, and application publishing scope. Thus, the second application is virtually unchanged from the first application in terms of service, eliminating the need for a development process when automatically publishing the second application based on the first application. This ensures that the second application is functionally identical to the first application, better meeting the needs of some users who wish to "publish the same application." Here, "service" refers to the functionality provided by an application (e.g., image rendering, workflow generation). "Application publisher" refers to the application publishing account. "Application publishing permissions" refers to the permission information set when publishing an application. "Application publishing scope" refers to the range of users who can access the application when it is published.

[0053] It should be noted that this application does not limit the implementation method of the above-mentioned "at least one configuration". For example, the "at least one configuration" can be determined according to the application release requirements of the actual application scenario. Alternatively, the "at least one configuration" can also be automatically determined based on some configurations that each original application (such as the first application) has, such as pre-set adjustable attributes, pre-set adjustable functions, functional architecture, etc., so that these configurations can be presented to the user for selection after the user selects the original application.

[0054] The first item refers to an option that exists among at least one of the above candidates and can uniquely identify the quick release path (such as by...). Figure 3 The options described in the "Install and Publish" button shown in pop-up window 305) enable the application processing flow indicated by the first item to show which steps the quick publish path specifically includes, thereby enabling the application processing flow to show how to quickly and automatically publish new applications (such as the same application) based on the first application.

[0055] Furthermore, this application does not limit the implementation method of the application processing flow indicated in the first item above.

[0056] Furthermore, to better improve the user experience, the application processing flow indicated in the first point above may include at least the application installation phase (such as...). Figure 2 The installation phase (as shown) and the release preparation phase (as shown) Figure 2 The application installation phase (shown in the diagram) is configured to automatically execute the application installation process based on the resource files of the first application, and the application release preparation phase is configured to automatically execute the application release preparation process for the second application. This allows the application processing flow to demonstrate how to quickly and automatically release new applications (such as the same application) based on the first application, thereby improving application release efficiency.

[0057] For the above installation and application phase (such as) Figure 2 The installation phase shown or by Figure 4 Regarding the "Install Application" stage shown in pop-up window 307, this stage is configured to automatically execute the application installation process based on the resource files of the first application, so that the first application is installed after this stage, making the first application usable (e.g., modifiable, reusable, etc.), so that new applications (such as the same application) can be automatically released based on the first application. Furthermore, this application does not limit the implementation method of this stage; for example, it can adopt... Figure 2 The installation phase shown is carried out accordingly.

[0058] For the aforementioned preparation and release phase (such as) Figure 2 The preparation for release stage shown or by Figure 4 Regarding the "Preparing for Release" stage shown in pop-up window 309, this stage is configured to automatically execute an application release preparation process for the new application (such as a second application), such as a blocking configuration identification process, a warning-type configuration or metadata identification process, a release request process, and a release submission process, so that a new application (such as a second application) that meets the release requirements can be obtained after this stage, so that the new application can be automatically released subsequently. Furthermore, this application does not limit the implementation method of this stage; for example, it can adopt… Figure 2 The preparation and release phase shown will be implemented.

[0059] Based on the above three paragraphs, it can be seen that, in one possible implementation, the application processing flow indicated in the first item above (such as by...) Figure 2 The process shown in the left half of the middle section may include the following steps:

[0060] After detecting that the user has selected the quick release path for the first application, the application installation process is carried out based on the resource files of the first application.

[0061] Next, determine whether the installation was successful. If the installation fails, it can be determined that the resource file is defective, so you can simply exit the installation. However, if the installation is successful, it can be determined that the first application has been successfully installed in the platform environment based on the resource file, so that the first application is in a usable state in the platform (such as being modifiable or reusable). Therefore, the second application can be automatically determined based on the first application (such as directly reusing the first application as the second application to obtain an application identical to the first application).

[0062] Next, determine if there are any incomplete blocking configurations in the second application. If so, it can be determined that there are configurations in the second application that affect the release. Therefore, exit the quick release path and display the corresponding prompt to the user so that the user can go to the configuration page of the development backend (such as the development platform) to continue manually setting these blocking configurations. If not, it can be determined that there are no configurations in the second application that affect the release.

[0063] Next, determine if there are any warning-type configurations or metadata in the second application. If so, confirm whether these configurations or metadata need to be fixed by asking questions. If they need to be fixed, exit the quick release path and display the corresponding prompt to the user so that the user can manually adjust these configurations or metadata on the corresponding page in the development backend. If no fix is ​​needed or there are no warning-type configurations or metadata, continue with the subsequent processes (such as release application, release submission, etc.) to obtain a second application that meets the release requirements.

[0064] Next, determine whether the second application is exempt from review. If it is, automatically submit a release request for the second application so that subsequent release procedures can be carried out to obtain an accessible second application; if it is not exempt from review, then request the relevant reviewer (such as...) Figure 2 The user is shown the approval information. If the reviewer does not click the publish operation for the second application, the user will be directly exited from the quick publish path and a corresponding prompt will be displayed to the user so that the user can go to the corresponding page in the development backend to process it. If the reviewer clicks the publish operation for the second application, the publishing of the second application will be performed to obtain an accessible second application.

[0065] Based on the above S1 to S2, the quick release scheme provided by this application includes: for a first application that has already been created (such as an application template), if an operation triggered for the first application is detected, it can be determined that the user wants to use the first application to meet a certain need (such as the need to release a new application). Therefore, at least one candidate option (such as "Install" option, "Install and Release" option, etc.) is displayed so that the application processing flow indicated by different candidate options is different. This allows the user to know from the at least one candidate option what kind of new application release method the first application supports. When an operation of selecting the first item (such as the "Install and Release" option) from the at least one candidate option is detected, it can be determined that the user wants to automatically release a new application based on the first application according to the quick release path. Therefore, the application processing flow indicated by the first item (such as the process that can realize the quick release path) is executed according to the resource file of the first application to realize the automatic release of the second application (such as the same application as the first application) according to the quick release path. As can be seen, the application processing flow of the first instruction is configured to automatically publish the second application based on the first application, so that no user operation is required during the execution of the application processing flow of the first instruction, thereby simplifying user operations when publishing a new application, improving efficiency, and enhancing user experience.

[0066] Research has found that in some scenarios, users want to know the execution progress of the quick deployment path. Therefore, to better meet this need, the above deployment method may also include the following steps: in response to detecting an operation that selects a first item from at least one candidate (such as by...). Figure 4 The operation of clicking the "Install and Publish" option shown in interface 305 displays the execution progress of the application processing flow indicated by the first item, so that users can understand the execution progress of the quick release path in the automated state in real time. This achieves integrated display of all or most of the processes in the quick release path, ensuring that users only need to wait during the execution progress display period without performing any operations. Once the execution progress indicates that these processes have been automatically completed, the new application can be released. In this way, by combining and black-boxing processes such as installation and release, it is ensured that users do not need to perceive or participate in the internal processes of this black box (such as all processes in the quick release path), thereby simplifying user operations and improving efficiency.

[0067] Furthermore, this application does not limit the way the execution progress of the application processing flow indicated in the first item above is displayed. For example, it can specifically be: in response to detecting an operation that selects the first item from at least one candidate (such as by...). Figure 4 The operation of clicking the "Install and Publish" option shown in interface 305 displays the first interface (as shown by...). Figure 4As shown in pop-up window 307 on page 306, this first interface is configured to display the execution progress of the application processing flow indicated by the first item. It can be seen that because this first interface integrates and displays all or most of the processes in the quick release path, the user only needs to wait during the display of this first interface without performing any operation. Once the first interface indicates that these processes have automatically completed, the new application release is complete. This simplifies user operation and improves efficiency by combining and black-boxing processes such as installation and release, ensuring that the user does not need to perceive or participate in the internal processes (such as all processes in the quick release path). Here, the first interface refers to the visual interface used to display the execution progress; and this application does not limit the implementation method of the first interface. For example, it can be implemented using any interface capable of integrating and displaying multiple processes, such as a pop-up window.

[0068] As can be seen, in one possible implementation, the first interface can be a pop-up window, so that the user can understand the execution progress of the quick release path in real time. This allows the pop-up window to be used as a black box to implement the quick release path, thus ensuring that the user does not need to perceive or participate in the internal process of the black box, thereby simplifying user operation and improving efficiency.

[0069] Furthermore, to better improve the user experience, the above-mentioned publishing method may also include the following steps: The application processing flow in response to the first indication includes at least one stage (such as an application installation stage, a publishing preparation stage, etc.), presenting the connection relationships between different stages within that at least one stage (such as by...). Figure 4 The connection relationship shown in pop-up window 307 is configured to indicate the execution order of different stages in the application processing flow, so that users can better understand the execution status of the quick release path (such as which stages have been completed and which stages have not yet been executed) through the interface, thereby improving the user experience.

[0070] Furthermore, this application does not limit the timing of the display of the first interface. For example, the timing of the display of the first interface may be consistent with the timing of the execution of the application processing flow indicated in the first item above, so that the first interface can describe the execution progress of the application processing flow in real time, thereby providing a better user experience.

[0071] Therefore, in one possible implementation, the above-described publishing method may include at least the following steps: in response to detecting an operation that selects a first item from at least one candidate (such as by...). Figure 4 The operation of clicking the "Install and Publish" option shown in interface 305) executes the application processing flow indicated in the first item according to the resource files of the first application, and displays the first interface (as shown by...). Figure 4The pop-up window 307 shown on page 306 enables the first interface to display the execution progress of the application processing flow of the first instruction in real time, thereby overcoming the defect caused by the inability to display the execution progress in real time.

[0072] Research has found that in some scenarios, some users want to quickly publish existing applications, while others may still prefer to publish them in a more conventional manner.

[0073] Based on the above research, in order to meet the above requirements, at least one of the above candidates may also include a second item (such as by...). Figure 3 The options described in the "Install" button shown in pop-up window 305). The second option is used to uniquely identify the regular distribution path (e.g., ...). Figure 2 The second item indicates the standard release path, so that the application processing flow can show which steps the standard release path specifically includes, thereby enabling the application processing flow to show how to manually release a new application based on the first application.

[0074] Therefore, in one possible implementation, the above-described publishing method may include at least the following steps: in response to detecting an operation that selects a second item from at least one candidate, executing the application processing flow indicated by the second item based on the resource file of the first application (such as by...). Figure 2 (The process shown in the right half of the middle section) The application processing flow indicated by the second item is configured to enable the manual release of a third application based on the first application, in order to meet the manual application development needs of some users and to better improve the user experience.

[0075] The third application refers to applications published via a conventional path (such as by...). Figure 2 The third application is a new application obtained by manually developing the first application (as shown in the conventional release path). It is evident that the third application is obtained by the user through manual development based on the first application. It should be noted that this application does not limit the implementation method of the third application; for example, the third application may have significant or minor differences compared to the first application.

[0076] Furthermore, this application does not limit the implementation method of the application processing flow indicated in the second item above. For example, the application processing flow can be implemented by manually publishing a new application according to the path of "installing the application → developing the application → publishing the application".

[0077] It can be seen that, in one possible implementation, the application processing flow indicated in the second item above (such as by...) Figure 2 The process shown in the right half of the middle section may include the following steps:

[0078] After detecting that the user has selected the regular release path for the first application, the application installation process is first performed based on the resource files of the first application;

[0079] Next, determine whether the installation was successful. If the installation fails, it can be determined that the resource file is defective, so the installation can be exited directly. However, if the installation is successful, it can be determined that the first application has been successfully installed in the platform environment based on the resource file, so that the first application is in a usable state in the platform (such as being modifiable and reusable). Therefore, the system will automatically enter the development platform so that the user can manually adjust it according to their needs to obtain the third application. After the user confirms that the application development is complete, the user can click the "Publish" button presented in the development platform to end the development process.

[0080] Next, determine if there are any incomplete configurations in the third application. If so, it can be determined that the application development for the third application is still incomplete, so a prompt is displayed to the user so that the user can go to the corresponding page in the platform to make the configuration according to the prompt; if not, it can be determined that the application development for the third application is complete.

[0081] Next, metadata checks are performed to determine if there are any errors or warnings. If errors are found, it can be determined that the third-party application has a problem that affects its release. Therefore, a prompt is displayed to the user so that the user can go to the corresponding page on the platform to make adjustments. If there are no errors and no warnings (or only a few warnings), it can be determined that the third-party application does not have a problem that affects its release.

[0082] The user then performs the first step of the release request, with the aim of enabling the third-party application to check the changes through this first step;

[0083] The user then performs the second step of the release application, which aims to enable the third application to fill in version information, etc.

[0084] The user then performs the third step of the application process, which aims to enable the user to fill in permission information for the third application.

[0085] Users then manually submit application release requests for third-party applications, which, after review, are then released to make the third-party applications accessible.

[0086] Based on the aforementioned content of at least one candidate option, when the at least one candidate option includes the first item and the second item, since the quick release path identified by the first item does not involve a manual development process, the new application generated in the quick release path will not have development errors caused by manual development. Therefore, there is no need for a development error detection stage in the quick release path, and thus the at least one candidate option can at least satisfy the following constraint: the application processing flow indicated by the first item lacks at least one stage compared to the application processing flow indicated by the second item. This at least one stage includes a development error checking stage, which is configured to perform development error checking on the new application determined based on the first application (e.g., ...). Figure 2 The error check shown (e.g., "Metadata check for errors") makes the resource overhead of the quick release path identified by the first item much lower than that of the regular release path identified by the second item, thereby enabling better efficiency and resource saving with the help of the quick release path.

[0087] It is evident that, in one possible implementation, the execution speed of the application processing flow indicated by the first item in the at least one candidate option is faster than the execution speed of the application processing flow indicated by the second item in the at least one candidate option, so that the efficiency of releasing a new application based on the first item is higher than the efficiency of releasing a new application based on the second item, which is beneficial to improving the efficiency of some scenarios (such as releasing the same application scenario by means of a quick release path).

[0088] Research has found that in some scenarios, users may want to make minor changes to existing applications (such as changes to the integration system). To meet this need, some development content can be abstracted into configuration items that correspond to the existing application. This allows users to describe their development needs by setting these configuration items, so that new applications can be automatically developed based on these configuration items when they are automatically released on the basis of the existing application.

[0089] Based on the above research, in one possible implementation, the above-mentioned publishing method may include at least the following steps: In response to an operation triggered on a first application, displaying configuration items corresponding to the first application, wherein the configuration items are determined based on at least one type of developable content (such as interface systems, databases, operating environments, etc.) corresponding to the first application, so that the configuration items can indicate which content in the first application can be changed through automatic development, and also that the configuration items can indicate the state of the first application within the at least one type of developable content; In response to detecting an adjustment operation on the configuration items, updating the configuration items, so that the updated configuration items can indicate the state of the first application based on automatic development. The state of the developed second application within the at least one developable content; in response to detecting the operation of selecting a first item from at least one candidate, the application processing flow indicated by the first item is executed according to the configuration item and the resource file of the first application. The application processing flow indicated by the first item includes an automatic development stage, which is configured to adjust the first application according to the configuration item to obtain a second application, so as to realize the automatic minor development of the existing application to obtain a new application (such as the second application) under the quick release path, so that the new application presents some changes compared to the existing application under these developable contents, thereby improving efficiency while meeting the user's development needs.

[0090] It should be noted that the automated development phase shown above is implemented automatically using some method (such as a pre-built machine learning model or a pre-built execution script) to ensure that it follows pre-defined application development rules. This eliminates the errors that are easily encountered in manual development, thus eliminating the need for error checking after the automated development phase and improving efficiency.

[0091] Based on the above two paragraphs, it can be seen that in one possible implementation, the application processing flow indicated in the first item above may include an application installation stage, an automatic development stage, and a release preparation stage, so that the application processing flow may include at least the following steps: After detecting that the user has selected a quick release path for the first application, the application is first installed based on the resource files of the first application; then it is determined whether the installation is successful. If the installation fails, it can be determined that the resource file has defects, so the installation can be exited directly; however, if the installation is successful, it can be determined that the first application has been successfully installed in the platform environment based on the resource file, so that the first application is in a usable state (such as a modifiable or reusable state) in the platform. Therefore, it is determined whether the configuration items corresponding to the first application have been updated. If the configuration items have been updated, it can be determined that the user has adjusted the configuration items according to their needs. Therefore, the first application is automatically developed based on the configuration items to obtain a second application, and subsequent steps are performed based on the second application (such as... Figure 2 (The steps shown include the preparation and release phase). If the configuration item has not been updated, it can be determined that the user wants to directly use the configuration that the first application itself has. Therefore, the first application is directly used as the second application, and subsequent steps are performed based on the second application (such as...). Figure 2 The steps shown include the preparation and release phase.

[0092] Furthermore, this application does not limit the display method of the above configuration items. For example, the configuration item and at least one of the above candidate items can be displayed on the same interface to concentrate user operations on the same interface, so as to avoid the defects caused by dispersing user operations to different interfaces (such as poor user experience due to users having to constantly look at whether manual operation is required), so as to better improve the user experience.

[0093] Therefore, in one possible implementation, the above-described publishing method can at least satisfy the following constraints: the different items among the at least one candidate are respectively using a second interface (such as...) Figure 3 The second interface displays different components in the pop-up window 305 shown, and also displays the configuration items corresponding to the first application (such as...). Figure 3 The attributes 1 to 3 shown enable users to centrally set their needs (such as adjustments and changes to the first application, and the publishing method adopted by the first application) through the second interface. This ensures that no user operation is required after entering the quick publishing path based on the second interface, thus overcoming the defects caused by the relatively scattered user operations and improving the user experience.

[0094] Research has found that in some scenarios, when releasing a new application, it is necessary to first execute processes such as application submission and release request before proceeding with other application-related matters. Therefore, to better meet these release requirements, the information required for the application submission and release request processes (such as permissions and version information) can be pre-stored in the installation package of an existing application. This allows the application submission and release request processes to be automatically executed based on the pre-set information in the installation package under the quick release path, thus overcoming the shortcomings caused by manually entering this information.

[0095] Based on the above research, in one possible implementation, the application processing flow of the first instruction can at least satisfy the following constraints: the application processing flow of the first instruction includes a publishing-related step (such as publishing application, publishing submission, etc.), which is configured to be automatically executed based on the information corresponding to the publishing-related step in the resource file of the first application, so as to realize the automatic execution of the publishing-related process based on the preset information in the resource file, thereby overcoming the defects caused by manually inputting this information and better simplifying user operations.

[0096] It should be noted that the aforementioned release association steps refer to the steps that need to be performed after obtaining the second application to ensure its successful release; moreover, this application does not limit the implementation method of the release association steps. For example, the release association steps may include some or all of the steps in the aforementioned preparation for release stage. Alternatively, the release association steps may include steps such as release application and release submission. Furthermore, the information corresponding to the release association steps refers to the information required when performing these steps, such as version and permissions.

[0097] Research has revealed that in certain scenarios, users have the following needs: to remain on the current platform (e.g., by...). Figures 3 to 5 Understand the services provided by the application template, based on the platform shown.

[0098] Based on the above research, in order to better meet the above needs, the above publishing method may further include the following steps: after detecting the completion of the application processing flow indicated by the first item, displaying the access point of the second application (such as by...). Figure 5 The button 311 shown on page 310 allows users to access the second application through this entry point. Since the second application is based on the first application, it provides services that include some or all of the services provided by the first application (such as an application template). This allows users to learn about the services provided by the application template by accessing the second application, thereby improving the user experience.

[0099] Research has revealed that in some scenarios, users may have the following needs: when a user encounters problems in the quick release path, the user does not want to give up directly, but hopes to continue to advance the release process of the new application through other means.

[0100] Based on the above research, in order to meet the requirements shown in the previous paragraph, when at least one of the above candidate options includes the first and second items, the above publishing method may further include the following steps: in response to detecting a problem occurring during the execution of the application processing flow indicated by the first item (such as by... Figure 2 The prompt described in the left half indicates that the quick release path cannot continue. Therefore, it is possible to jump to the stage in the application processing flow that matches the problem, so that the new application can be released by executing this stage and its corresponding remaining stages in the regular release path. This allows for a flexible switch from the quick release path to the regular release path, ensuring that the new application can be released successfully and avoiding problems caused by the quick release path failing to execute smoothly (such as the inability to release the new application), thus improving the user experience.

[0101] Based on the aforementioned release methods, it is clear that the application release process based on a quick release path provided in this application (such as by...) Figures 3 to 5 The process shown may include the following steps: After a user enters a platform that provides application publishing services, the user is first shown some selectable application templates (such as those provided by...). Figure 3 Application templates 1 to 4 shown on page 301 are used to detect when a user selects a first application from these application templates (such as by...). Figure 3 When the user sees application template 1 shown on page 301, the details page corresponding to the first application (such as the one shown on page 301) will be displayed to the user. Figure 3 The application template details page shown on page 302 allows the details page to present relevant content of the first application (such as resource links, name, etc.) to the user; then, upon detecting an action triggered by the user through the details page for the first application (such as by... Figure 3 When clicking button 303 as shown on page 302, a second interface (such as one shown on page 302) is added to the details page. Figure 3 (as shown in pop-up 305 on page 304), so that the second interface not only displays the configuration items corresponding to the first application (such as those provided by...) Figure 3 The pop-up window 305 displays attributes 1 to 3, and also presents the processing methods allowed for this first application (such as by...). Figure 3The "Install" and "Install and Publish" buttons shown in pop-up window 305 describe the processing methods respectively. This allows users to not only set up minor developments for the first application through this second interface, but also to select a processing method that meets their needs (such as a new application publishing method). This is to detect when the user selects a quick publishing path through the second interface (such as by...). Figure 4 When clicking the "Install and Publish" button (as shown on page 304), the second interface is removed from the details page, and the first interface is added back to the details page (e.g., by...). Figure 4 The pop-up window 307 shown on page 306), and the automatic execution of the quick publishing path (as shown by...) Figure 2 The quick release path shown allows the first interface to not only indicate which stages the quick release path includes, but also to indicate the automatic execution progress of the quick release path in real time (e.g., by...). Figure 4 The 30% displayed in the pop-up window 307 shown on page 306 is due to... Figure 4 The pop-up window 309 shown on page 308 displays a 50% progress indicator. This is so that when the quick publish path presented by the first interface has been completed, it can be determined that the automatic publish of a new application (such as a second application) based on the first application has been successfully completed. Therefore, the first interface is removed, and the page redirects to a new page (such as the one shown on page 308). Figure 5 The release completion page shown on page 310 allows the new page to not only convey the message that the new application has been successfully released to the user, but also to reveal the access method of the new application (such as via...). Figure 5 (Button 311 shown on page 310) so that the user can subsequently access the new application using this access method.

[0102] It should be noted that, for Figure 2 As shown, a "blank application" refers to an initial application without preset functions, forms, or processes, so that the blank application cannot provide specific services to users. Therefore, the blank application does not support the quick release path and only supports the regular release path.

[0103] In addition, the quick release path provided in this application has the following advantages compared with the conventional release path: ① Because the quick release path is implemented automatically, it can automatically release new applications (such as this application) without user intervention, simplifying user operations and improving efficiency; ② Because there is no process of users manually modifying the application in the quick release path, it is impossible for the application to have errors caused by manual modifications, thus eliminating the need for the steps required to check for such errors (such as...). Figure 2The steps shown include "metadata check for errors," so these steps can be skipped to improve efficiency. ③ To better meet the minor development needs of some users (such as changes to the system integration), some development content can be pre-abstracted into configuration items (such as attributes) that correspond to the application template. This allows users to describe their development needs by adjusting these configuration items when using the application template. This enables automatic development of new applications based on these configuration items in the quick release path, eliminating the need for users to manually develop new applications using the development platform, thus improving development efficiency and effectiveness. ④ By pre-placing the information required for application template release (such as permissions and version information) into the application template's installation package, the quick release path can automatically implement the release application and submission processes based on the information recorded in the installation package, further simplifying user operations. As can be seen, this application black-boxes the complex and non-core processes involved in the application release process (such as abstracting them into pop-ups presented to users), so that users do not need to perceive or participate in the internal processes of this black box. This can reduce the waiting time for users when releasing a new application, greatly improve efficiency, simplify steps, and enable users to better achieve "one-click creation of the same application", significantly reducing user churn.

[0104] In addition, this application does not limit the application scenarios of the above-mentioned quick release path. For example, it is applicable to the following scenarios: (1) Users want to directly use the application template to create the same application without development; (2) The content that users need to develop has been abstracted into the configuration items corresponding to the application template, without the need for manual development through the development platform; (3) Users want to understand the effect presented by the application template by quickly releasing a new application, so that users can manually develop the application template based on the effect.

[0105] Based on the publishing method provided in the embodiments of this application, the embodiments of this application also provide a publishing device, which is described below in conjunction with... Figure 6 Explanation and clarification will be provided. Among them, Figure 6 This is a schematic diagram of a publishing device provided in an embodiment of this application. It should be noted that for technical details of the publishing device provided in this embodiment, please refer to the relevant content of the publishing method described above.

[0106] like Figure 6 As shown, the publishing device 600 provided in this application embodiment includes:

[0107] The data display unit 601 is used to display at least one candidate option in response to an operation triggered by the first application, wherein different candidate options indicate different application processing flows;

[0108] The first execution unit 602 is configured to, in response to detecting an operation of selecting a first item from the at least one candidate, execute the application processing flow indicated by the first item according to the resource file of the first application, wherein the application processing flow indicated by the first item is configured to automatically publish a second application based on the first application.

[0109] In one possible implementation, the first execution unit 602 is further configured to: in response to detecting an operation that selects the first item from the at least one candidate, display the execution progress of the application processing flow indicated by the first item.

[0110] In one possible implementation, the first execution unit 602 is further configured to: in response to the application processing flow including at least one stage, present a connection relationship between different stages in the at least one stage, the connection relationship being configured to indicate the execution order of the different stages in the at least one stage in the application processing flow.

[0111] In one possible implementation, the publishing device 600 further includes: a second execution unit, configured to, in response to detecting an operation of selecting a second item from the at least one candidate, execute an application processing flow indicated by the second item according to the resource file, wherein the application processing flow indicated by the second item is configured to implement manual publishing of a third application based on the first application.

[0112] In one possible implementation, the at least one candidate further includes a second item; the application processing flow indicated by the first item lacks at least one stage compared to the application processing flow indicated by the second item, the at least one stage including a development error checking stage.

[0113] In one possible implementation, the data display unit 601 is further configured to: display configuration items corresponding to the first application in response to an operation triggered for the first application, the configuration items being determined based on at least one type of developable content corresponding to the first application; and update the configuration items in response to detecting an adjustment operation for the configuration items.

[0114] The first execution unit 602 is specifically used to: execute the application processing flow indicated by the first item according to the configuration item and the resource file, wherein the application processing flow indicated by the first item includes an automatic development stage, and the automatic development stage is configured to adjust the first application according to the configuration item to obtain the second application.

[0115] In one possible implementation, the application processing flow indicated by the first item includes a publishing association step, which is configured to be executed automatically based on information in the resource file corresponding to the publishing association step.

[0116] In one possible implementation, the at least one candidate option further includes a second option;

[0117] The publishing device 600 further includes a jump unit, configured to, in response to detecting a problem occurring during the execution of the application processing flow indicated in the first item, jump to the stage in the application processing flow indicated in the second item that matches the problem.

[0118] In one possible implementation, the method satisfies at least one of the following constraints: the first application is an application template; the second application is the same application as the first application, the services provided by the second application are consistent with those provided by the first application, and the second application differs from the first application in at least one configuration, the at least one configuration including at least a portion of application publisher, application publishing permissions, application integration system, and application publishing scope; the different items in the at least one candidate are displayed using different components in the second interface, and the second interface also displays the configuration items corresponding to the first application; the application processing flow indicated by the first item includes an application installation stage and a publishing preparation stage, the application installation stage is configured to automatically execute the application installation process based on the resource file, and the publishing preparation stage is configured to automatically execute the application publishing preparation process for the second application.

[0119] Based on the aforementioned content regarding the publishing device 600, its working principle includes: for a pre-created first application (such as an application template), if an operation triggered by the first application is detected, it can be determined that the user wishes to use the first application to meet a certain need (such as the need to publish a new application). Therefore, at least one candidate option (such as an "Install" option, an "Install and Publish" option, etc.) is displayed so that different candidate options indicate different application processing flows. This allows the user to learn from the at least one candidate option what new application publishing method the first application supports. When an operation is detected in which the first item (such as the "Install and Publish" option) is selected from the at least one candidate option, it can be determined that the user wishes to automatically publish a new application based on the first application according to the quick publishing path. Therefore, the application processing flow indicated by the first item (such as the flow that can realize the quick publishing path) is executed according to the resource files of the first application to realize the automatic publishing of a second application (such as an application identical to the first application) according to the quick publishing path. As can be seen, the application processing flow of the first instruction is configured to automatically publish the second application based on the first application, so that no user operation is required during the execution of the application processing flow of the first instruction, thereby simplifying user operations when publishing a new application, improving efficiency, and enhancing user experience.

[0120] In addition, this application also provides an electronic device, the device including a processor and a memory: the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory so that the electronic device performs any implementation of the publishing method provided in this application.

[0121] See Figure 7 The diagram illustrates a structural schematic of an electronic device 700 suitable for implementing embodiments of the present disclosure. Terminal devices in embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0122] like Figure 7 As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0123] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0124] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 709, or installed from storage device 708, or installed from ROM 702. When the computer program is executed by processing device 701, it performs the functions defined in the methods of embodiments of this disclosure.

[0125] The electronic device provided in this embodiment belongs to the same inventive concept as the method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0126] This application also provides a computer-readable medium storing instructions or a computer program that, when executed on a device, causes the device to perform any implementation of the publishing method provided in this application.

[0127] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0128] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0129] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0130] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, enable the electronic device to perform the aforementioned methods.

[0131] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0132] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0133] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units / modules do not necessarily limit the specific unit itself.

[0134] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0135] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0136] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems or apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.

[0137] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

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

[0139] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0140] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A publishing method, characterized in that, The method includes: In response to an operation triggered by a first application, at least one candidate option is displayed, and different candidate options indicate different application processing flows; In response to detecting an operation that selects a first item from the at least one candidate, the application processing flow indicated by the first item is executed according to the resource file of the first application, the application processing flow indicated by the first item being configured to automatically publish a second application based on the first application.

2. The method according to claim 1, characterized in that, The method further includes: In response to detecting an operation that selects the first item from the at least one candidate, the execution progress of the application processing flow indicated by the first item is displayed.

3. The method according to claim 2, characterized in that, The method further includes: The application processing flow in response to the first indication includes at least one stage, presenting a connection relationship between different stages in the at least one stage, the connection relationship being configured to indicate the execution order of the different stages in the at least one stage in the application processing flow.

4. The method according to claim 1, characterized in that, The method further includes: In response to detecting an operation that selects a second item from the at least one candidate, the application processing flow indicated by the second item is executed according to the resource file, the application processing flow indicated by the second item being configured to implement the manual release of a third application based on the first application.

5. The method according to claim 1, characterized in that, The at least one candidate also includes a second item; The application processing flow of the first instruction lacks at least one stage compared to the application processing flow of the second instruction, and the at least one stage includes a development error checking stage.

6. The method according to claim 1, characterized in that, The method further includes: In response to an operation triggered for the first application, the configuration items corresponding to the first application are displayed, the configuration items being determined based on at least one type of developable content corresponding to the first application; In response to detecting an adjustment operation for the configuration item, update the configuration item; The application processing flow that executes the first instruction based on the resource file of the first application includes: The application processing flow indicated by the first item is executed according to the configuration item and the resource file. The application processing flow indicated by the first item includes an automatic development stage, which is configured to adjust the first application according to the configuration item to obtain the second application.

7. The method according to claim 1, characterized in that, The application processing flow of the first indication includes a publishing association step, which is configured to be executed automatically based on the information corresponding to the publishing association step in the resource file.

8. The method according to claim 1, characterized in that, The at least one candidate also includes a second item; The method further includes: In response to the detection of a problem during the execution of the application processing flow indicated in the first item, the execution jumps to the stage in the application processing flow indicated in the second item that matches the problem.

9. The method according to any one of claims 1-8, characterized in that, The method satisfies at least one of the following constraints: The first application is an application template; The second application is the same application as the first application. The services provided by the second application are consistent with those provided by the first application. The second application and the first application differ in at least one configuration, which includes at least a portion of the application publisher, application publishing permissions, application integration system, and application publishing scope. The different items in the at least one candidate are displayed using different components in the second interface, and the second interface also displays the configuration items corresponding to the first application; The application processing flow indicated in the first item includes an application installation phase and a release preparation phase. The application installation phase is configured to automatically execute the application installation process based on the resource file, and the release preparation phase is configured to automatically execute the application release preparation process for the second application.

10. A dispensing device, characterized in that, include: The data display unit is used to display at least one candidate option in response to an operation triggered by the first application, wherein different candidate options indicate different application processing flows; A first execution unit is configured to, in response to detecting an operation that selects a first item from the at least one candidate, execute an application processing flow indicated by the first item based on the resource file of the first application, wherein the application processing flow indicated by the first item is configured to automatically publish a second application based on the first application.

11. An electronic device, characterized in that, The device includes: a processor and a memory; The memory is used to store instructions or computer programs; The processor is configured to execute the instructions or computer program in the memory to cause the electronic device to perform the method according to any one of claims 1-9.

12. A computer-readable medium, characterized in that, The computer-readable medium stores instructions or computer programs that, when executed on the device, cause the device to perform the method according to any one of claims 1-9.

13. A computer program product, characterized in that, It includes a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the method of any one of claims 1-9.

Images