App building methods, devices and storage media

Abstract

This invention belongs to the field of application development technology, specifically relating to an APP construction method, device, and storage medium, and is related to the field of communication technology. The method includes: acquiring the application functions implemented by the target APP; determining, based on a pre-stored historical construction library, whether there exists a target data packet in the historical construction library that can implement at least some of the application functions of the target APP; if so, constructing the basic data of the target APP based on the target data packet, wherein the historical construction library includes multiple data packets, each data packet including data of at least one functional component, and the functional component has a corresponding relationship with the application function; and uploading the basic data of the target APP to a preset application platform to complete the construction of the target APP. This method achieves unified management of third-party and internal components, improves APP construction efficiency, and reduces the probability of human error during the construction process.

Description

Technical Field

[0001] This invention belongs to the field of application development technology, specifically relating to an APP construction method, device, and storage medium. Background Technology

[0002] More and more programs need to support mobile devices. Building mobile apps requires integrating various ready-made third-party components as well as self-developed common internal components such as H5 (web page + JavaScript framework) and Flutter (open source mobile application framework). These components need to be managed in a unified manner during the app building process.

[0003] Currently, mobile operating systems are mainly divided into two major categories: iOS and Android. Different operating systems require different app versions, and in order to improve certain functions, iterative updates are needed to the versions from time to time.

[0004] Existing app building platforms focus more on a single app build and lack effective methods for handling continuous version iterations. Each build starts from scratch, making the process cumbersome. Human errors may also occur during the update process, resulting in unusable apps and severely impacting developer productivity. Summary of the Invention

[0005] To address the aforementioned problems in existing technologies, specifically the issue that building apps from scratch in existing technologies impacts developer efficiency, this invention provides an app building method, comprising:

[0006] Obtain the application functions implemented by the target APP;

[0007] Based on the pre-stored historical build library, determine whether there is a target data package in the historical build library that can achieve at least some of the application functions of the target APP;

[0008] If so, based on the target data packet, construct the basic data of the target APP. The historical construction library includes multiple data packets, each of which includes data of at least one functional component. The functional component has a corresponding relationship with the application function.

[0009] The basic data of the target APP is uploaded to the preset application platform to complete the construction of the target APP.

[0010] In one possible design, if the target data package in the historical build library fails to achieve all the application functions of the target APP, the step of building the basic data of the target APP based on the target data package includes:

[0011] Retrieve the target functional components corresponding to the remaining application functions;

[0012] Based on the target data packet and the data of the target functional components, construct the basic data of the target APP.

[0013] In one possible design, before constructing the basic data of the target APP based on the target data packet, the method further includes:

[0014] Obtain the version number of the target data packet stored in the historical build library;

[0015] Obtain a list of version numbers for the target data packet from the server;

[0016] Based on the version number of the target data packet and the list of version numbers, determine whether the target data packet is the latest version;

[0017] If not, the latest version of the target data package is obtained from the server, and the target data package in the historical build library is updated.

[0018] In one possible design, before constructing the basic data of the target APP based on the target data packet and the data of the target functional component, the method further includes:

[0019] Send the target data packet and the data of the target functional component to the component confirmation terminal;

[0020] Obtain the confirmation result uploaded by the terminal for the component confirmation;

[0021] Determine whether the confirmation result is "confirmation passed" to obtain the confirmation result.

[0022] In one possible design, before uploading the basic data of the target APP to the preset application platform, the method further includes:

[0023] Based on the target data packet and the data of the target functional components that have been confirmed, construct the basic data of the target APP;

[0024] The basic data of the target APP is stored in the historical build library in the form of data packets.

[0025] In one possible design, constructing the basic data of the target APP based on the target data packet includes:

[0026] Obtain the build type of the target APP, wherein the build type includes the mobile operating system of the target APP terminal, and the mobile operating system includes at least one of iOS system and Android system;

[0027] Based on the construction type and the target data package, construct the basic data of the target APP.

[0028] In one possible design, constructing the basic data of the target APP based on the construction type and the target data package includes:

[0029] Determine whether the mobile operating system of the preset target APP terminal is iOS;

[0030] If so, obtain the certificate of the iOS system, and construct the basic data of the target APP based on the certificate and the target data package.

[0031] Secondly, this application provides an APP building device, comprising:

[0032] The acquisition module is used to acquire the application functions implemented by the target APP.

[0033] The judgment module is used to determine, based on the pre-stored historical build library, whether there is a target data package in the historical build library that can achieve at least some of the application functions of the target APP;

[0034] The processing module is used to construct the basic data of the target APP based on the target data packet. The historical construction library includes multiple data packets, and each data packet includes data of at least one functional component. The functional component has a corresponding relationship with the application function.

[0035] The sending module is used to upload the data components of the target APP to a preset application platform to complete the construction of the target APP.

[0036] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0037] The memory stores computer-executed instructions;

[0038] The processor executes computer execution instructions stored in the memory to implement the APP construction method.

[0039] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement an APP building method.

[0040] Those skilled in the art will understand that the APP building method, device, and storage medium provided by the present invention acquire the application functions implemented by the target APP; determine, based on a pre-stored historical building library, whether there exists a target data package in the historical building library that can implement at least some of the application functions of the target APP; if so, build the basic data of the target APP based on the target data package, wherein the historical building library includes multiple data packages, each of which includes data of at least one functional component, and the functional component has a corresponding relationship with the application function; and upload the basic data of the target APP to a preset application platform to complete the construction of the target APP. This method achieves unified management of third-party components and internal components, improves APP building efficiency, and reduces the probability of human error during the building process. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram illustrating the application scenario for building an APP provided in the embodiments of this application;

[0043] Figure 2 A flowchart illustrating the APP construction method provided in this application embodiment. Figure 1 ;

[0044] Figure 3 A flowchart illustrating the APP construction method provided in this application embodiment. Figure 2 ;

[0045] Figure 4 A flowchart illustrating the APP construction method provided in this application embodiment. Figure 3 ;

[0046] Figure 5 This is a schematic diagram of the framework structure of the APP building device provided in the embodiments of this application;

[0047] Figure 6 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0048] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without inventive effort are within the scope of protection of this invention.

[0049] Figure 1 This is a schematic diagram illustrating the application scenario of the APP construction method provided in this application. For example... Figure 1 As shown, developers view the pre-stored historical build library in the build server 102 through the developer client 101, and then match the application functions implemented by the target APP with the historical build library to determine whether there are target data packages in the historical build library that are similar to or similar to the application functions implemented by the target APP. If there are some similar or similar target data packages, functional components are added or removed based on these similar or similar target data packages. The confirmation terminal 103 confirms whether the changed functional components and similar or similar target data packages are usable. Then, the usable functional components and target data packages are combined to build the APP construction method provided in this application, which aims to solve the above-mentioned technical problems of the prior art.

[0050] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0051] Figure 2 Schematic diagram of the APP construction method provided in this application Figure 1 .like Figure 2 As shown, the method includes:

[0052] S201. Obtain the application functions implemented by the target APP;

[0053] Specifically, based on the target APP to be built, obtain the list of application functions to be implemented, and the list of application functions stores at least one application function.

[0054] S202. Based on the pre-stored historical build library, determine whether there is a target data package in the historical build library that can realize at least part of the application functions of the target APP. If so, build the basic data of the target APP based on the target data package. The historical build library includes multiple data packages, and each data package includes data of at least one functional component. The functional component has a corresponding relationship with the application function.

[0055] Specifically, the process begins by searching the pre-stored historical build repository for application functionalities. This determines if the repository contains target data packages that can implement at least some of the application functionalities of the target app. The historical build repository stores multiple data packages with specific application functionalities. Using these target data packages, the target app is built by adding or removing items based on the target data packages, thereby improving build efficiency and reducing the probability of errors during the build process. More specifically, each data package stored in the historical build repository contains data for one functional component that implements one application function, or multiple functional components that implement multiple application functions. Each functional component corresponds to an application function, allowing the search for a target data package to map the application function to a functional component, and then to a data package containing one or more of those functional components. Since the found data packages may be one or multiple, they need to be prioritized. Data packages that implement more of the target app's application functionalities have higher priority than those that implement fewer. The data package that implements the most of the target app's application functionalities is then output as the target data package.

[0056] Furthermore, the target data package is matched with the application function list to determine whether the target data package can implement all the application functions in the application function list. If all functions are implemented, the basic data of the target APP is constructed based on the target data package. If only some functions are implemented, the unimplemented application functions are matched with a pre-stored functional component library. The functional component library stores finished third-party components developed by third-party companies and internally developed common components. Each third-party component and each internal component corresponds to an application function stored in the functional component library. By searching, the functional component that matches the unimplemented application function can be obtained. Then, the functional component is combined with the target data package to construct the basic data of the target APP.

[0057] Furthermore, when the target data package can implement all application functions in the application function list, it is also necessary to determine whether the target data package is the latest version. The historical build library stores the version number of the data package along with the data package itself. The server records all data package update logs, forming a list of version numbers for each data package. By obtaining the version number list of the target data package, it can be determined whether the target data package being used is the latest version. If it is the latest version, it means that the target APP is the APP corresponding to the target data package already built in the historical build library, and the corresponding APP can be used directly without rebuilding. If it is not the latest version, the corresponding non-latest target function components in the target data package need to be updated to the latest version. In another embodiment, while updating the corresponding non-latest target function components in the target data package to the latest version, the original version needs to be retained. This allows for replacement with the original version when the latest version does not meet usage requirements or is incompatible with the application's hardware during subsequent APP building.

[0058] S203. Upload the basic data of the target APP to the preset application platform to complete the construction of the target APP.

[0059] Specifically, after the basic data of the target APP is built, it needs to be stored in the historical build library in the form of a data package to enrich the materials in the historical build library, so that the template can be directly applied when building a more complex target APP in the future. On the other hand, the basic data of the built target APP needs to be uploaded to a preset application platform, such as an online application publishing platform like an app market or app store, so that users can download and install the corresponding target APP through the preset application platform, thereby completing the complete build process of the target APP.

[0060] The method provided in this embodiment obtains the application functions implemented by the target APP; determines whether there is a target data package in the pre-stored historical build library that can implement at least part of the application functions of the target APP; if so, constructs the basic data of the target APP based on the target data package, wherein the historical build library includes multiple data packages, each of which includes data of at least one functional component, and the functional component has a corresponding relationship with the application function; and uploads the basic data of the target APP to a preset application platform to complete the construction of the target APP. This method achieves unified management of third-party components and internal components, improves APP construction efficiency, and reduces the probability of human error in the construction process.

[0061] The APP construction method of this application will be described in detail below with reference to a specific embodiment.

[0062] Figure 3 Schematic diagram of the APP construction method provided in this application Figure 2.like Figure 3 As shown, the method includes:

[0063] S301. Obtain the application functions implemented by the target APP;

[0064] The implementation of S301 is similar to that of S201 described above, and will not be repeated here in this embodiment.

[0065] S302. Based on the pre-stored historical construction library, determine whether there is a target data package in the historical construction library that can realize at least part of the application functions of the target APP. The historical construction library includes multiple data packages, each of which includes data of at least one functional component. The functional component has a corresponding relationship with the application function. If yes, then execute S303. If no, then construct the basic data of the target APP based on the data of the target functional component.

[0066] Specifically, as long as the historical build library stores data packages with some application functions that are the same as the target APP, it can be used as the target data package for building the target APP, thereby reducing the time cost of building the target data package.

[0067] S303. Determine whether the target data package in the historical construction library can realize all the application functions of the target APP. If not, execute S304-S305; if yes, execute S306-S310.

[0068] S304. Obtain the target functional components corresponding to the remaining application functions;

[0069] S305. Construct the basic data of the target APP based on the target data packet and the data of the target functional component;

[0070] Specifically, if the target data package in the historical build library cannot realize all the application functions of the target APP, it means that in addition to the target data package, some functional components need to be added to make up for the missing application functions of the target APP corresponding to the target data package. This first requires comparing the application functions of the target APP with the application functions of the target data package to find the missing application functions. Then, based on the missing application functions, the corresponding target functional components are found in the functional component library. After combining the found target functional components with the target data package, all the functions required by the target APP can be realized. Therefore, the basic data of the target APP is built based on the data of the target data package and the target functional components.

[0071] S306. Obtain the version number of the target data packet stored in the historical build library;

[0072] S307. Obtain a list of version numbers of the target data packet from the server;

[0073] S308. Based on the version number of the target data packet and the version number list, determine whether the target data packet is the latest version. If not, execute S309-S310; if yes, execute S310.

[0074] S309. Obtain the latest version of the target data packet from the server and update the target data packet in the historical build library;

[0075] S310. Based on the latest target data package, construct the basic data of the target APP;

[0076] Specifically, the build history library is a collection of data packages continuously added to it during the construction of different apps. Apps undergo version updates during use due to various factors such as feature improvements, bug fixes, device compatibility, and software compatibility, to better meet user needs. These updates are often for the better. However, the build history library is a collection of data packages recorded and uploaded during the initial build and does not participate in subsequent upgrades. Furthermore, recording each upgrade in the build history library would lead to excessive data storage and reduce search efficiency during the build process. In contrast, version upgrades of data packages are logged on the application maintenance server, generating a version number list based on the update time. Once the version number is known, it can be used to... The version number list is searched to confirm the current version number's position. Therefore, we can determine whether the target data package in the current historical build repository is the latest version by retrieving the server's version number list. If it is the latest version, it can be used directly. If not, the build server needs to obtain the latest version of the target data package or the latest version of the functional components from the server to replace the old version of the target data package or target functional components. Simultaneously, the latest version of the target data package is stored. Since the actual update frequency of the target data package may be very high, we only randomly select the latest version based on the build time. This avoids data redundancy caused by storing the target data package in the historical build repository every time it is updated, while ensuring the availability of the data package version. After updating the target data package, the basic data of the target app can be built based on the latest target data package.

[0077] S311. Upload the basic data of the target APP to the preset application platform to complete the construction of the target APP.

[0078] The implementation of S311 is similar to that of S203 described above, and will not be repeated here in this embodiment.

[0079] The method provided in this embodiment achieves unified management of functional components and the historical build library by: acquiring the application functions implemented by the target APP; determining, based on a pre-stored historical build library, whether there exists a target data package in the historical build library that can implement at least some of the application functions of the target APP; if the target data package in the historical build library fails to implement all the application functions of the target APP, acquiring the target functional components corresponding to the remaining application functions; constructing the basic data of the target APP based on the data of the target data package and the data of the target functional components; acquiring the version number of the target data package stored in the historical build library; obtaining a list of version numbers of the target data package from the server; determining, based on the version number of the target data package and the list of version numbers, whether the target data package is the latest version; if not, obtaining the latest version of the target data package from the server and updating the target data package in the historical build library. This achieves the goal of improving the efficiency of app building and ensuring the high availability of the built app.

[0080] Figure 4 Schematic diagram of the APP construction method provided in this application Figure 3 .like Figure 4 As shown, the method includes:

[0081] S401. Obtain the application functions implemented by the target APP;

[0082] The implementation of S401 is similar to that of S201 described above, and will not be repeated here in this embodiment.

[0083] S402. Based on the pre-stored historical build library, determine whether there is a target data package in the historical build library that can realize at least some of the application functions of the target APP. If the target data package in the historical build library fails to realize all the application functions of the target APP, obtain the target function components corresponding to the remaining application functions.

[0084] The implementation of S402 is similar to that of S202 described above, and will not be repeated here in this embodiment.

[0085] S403. Send the target data packet and the data of the target functional component to the component confirmation terminal;

[0086] S404. Obtain the confirmation result uploaded by the component confirmation terminal, determine whether the confirmation result is a confirmation pass, and obtain the confirmation pass result;

[0087] Specifically, the component confirmation terminal sets different approval and confirmation personnel for the target data package and functional components. For example, for the target data package, the developer who built or upgraded the target data package is invited to be the approval and confirmation personnel. The component confirmation terminal obtains the confirmation result uploaded by the approval and confirmation personnel, thereby ensuring the availability of the data package. At the same time, due to the professionalism of the approval and confirmation personnel, the confirmation process is faster and the confirmation result is more accurate.

[0088] S405. Based on the confirmation result, obtain the build type of the target APP. The build type includes the mobile operating system of the target APP terminal. The mobile operating system includes at least one of iOS system and Android system.

[0089] Specifically, functional components and target data packets can only be assembled after obtaining confirmation from the confirmation terminal, thus avoiding rework. During assembly, the build type must first be determined. Different build types require different assembly operations, the main difference being their corresponding mobile operating systems. Common mobile operating systems include iOS, Android, Windows Phone, Symbian, BlackBerry OS, WebOS, Windows Mobile, Harmony, and Zhuoyi OS. This application mainly uses iOS and Android as examples for discussion, but the protected content is not limited to iOS and Android. Those skilled in the art can make alternative choices according to actual needs.

[0090] S406. Determine whether the mobile operating system of the preset target APP terminal is iOS. If yes, execute S407; otherwise, execute S408.

[0091] S407. Obtain the certificate of the iOS system, and construct the basic data of the target APP based on the certificate and the target data packet;

[0092] S408. Construct the basic data of the target APP based on the target data packet;

[0093] Specifically, the assembly steps performed when assembling target data packets and / or functional components differ for different mobile operating systems. The main difference lies in whether or not a certificate authentication process is required.

[0094] S409. Store the basic data of the target APP in the form of data packets in the historical construction library;

[0095] Specifically, after the basic data of the target APP is built, the basic data includes data of at least one functional component. This basic data containing specific application functions is stored as a data package in a historical build library containing multiple data package sets, so that the template can be directly applied when building a similar APP next time.

[0096] S410. Upload the basic data of the target APP to the preset application platform to complete the construction of the target APP.

[0097] The implementation of S410 is similar to that of S203 described above, and will not be repeated here in this embodiment.

[0098] The method provided in this embodiment involves sending the target data packet and the data of the target functional component to a component confirmation terminal; obtaining the confirmation result uploaded by the component confirmation terminal; determining whether the confirmation result is a successful confirmation; constructing the basic data of the target APP based on the target data packet and the data of the target functional component with the successful confirmation result; storing the basic data of the target APP in the form of a data packet in the historical build library; obtaining the build type of the target APP, the build type including the mobile operating system of the preset target APP terminal, the mobile operating system including at least one of iOS and Android systems; determining whether the mobile operating system of the preset target APP terminal is an iOS system; if so, obtaining the certificate of the iOS system, and constructing the basic data of the target APP based on the certificate and the target data packet. This method achieves a secondary confirmation process for functional components and target data packets during the target APP construction process, ensuring that the functional components and target data packets used meet the application functions while satisfying compatibility issues between different components when added. Professional personnel are consulted for judgment and confirmation from the time of addition to avoid the situation where the final built target APP is unusable, reduce the possibility of reconstructing, and assemble the corresponding hardware subsystems after the components are selected to avoid repeated selection and improve construction efficiency.

[0099] In this embodiment of the invention, electronic devices or main control devices can be divided into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment of the invention is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0100] Figure 5 A structural diagram of the APP building device provided in this application. (See diagram below.) Figure 5As shown, the device 50 includes:

[0101] The acquisition module 501 is used to acquire the application functions implemented by the target APP;

[0102] The judgment module 502 is used to determine, based on the pre-stored historical build library, whether there is a target data package in the historical build library that can realize at least some of the application functions of the target APP;

[0103] Processing module 503 is used to construct basic data of target APP based on target data packet. The historical construction library includes multiple data packets, each data packet includes data of at least one functional component, and the functional component has a corresponding relationship with the application function.

[0104] Specifically, the processing module is used to: obtain the version number of the target data packet stored in the historical build library; obtain a list of version numbers of the target data packet from the server; determine whether the target data packet is the latest version based on the version number of the target data packet and the list of version numbers; if not, obtain the latest version of the target data packet from the server and update the target data packet in the historical build library.

[0105] The processing module is further specifically used for: sending the target data packet and the data of the target functional component to the component confirmation terminal; obtaining the confirmation result uploaded by the component confirmation terminal; determining whether the confirmation result is a successful confirmation, and obtaining a successful confirmation result.

[0106] Furthermore, based on the target data packet and the data of the target functional component that have been confirmed, the basic data of the target APP is constructed; the basic data of the target APP is stored in the historical construction library in the form of data packets.

[0107] The processing module is further specifically used to: obtain the build type of the target APP, the build type including the mobile operating system of the target APP terminal, the mobile operating system including at least one of iOS system and Android system; and construct the basic data of the target APP according to the build type and the target data packet.

[0108] Furthermore, it is determined whether the mobile operating system of the preset target APP terminal is an iOS system; if so, the certificate of the iOS system is obtained, and the basic data of the target APP is constructed based on the certificate and the target data packet.

[0109] The sending module 504 is used to upload the data components of the target APP to a preset application platform to complete the construction of the target APP.

[0110] Furthermore, the device also includes:

[0111] The second processing module is used to construct the basic data of the target APP based on the target data package when the target data package in the historical construction library fails to achieve all the application functions of the target APP.

[0112] Specifically, the second processing module is used to: obtain the target functional components corresponding to the remaining application functions; and construct the basic data of the target APP based on the target data packet and the data of the target functional components.

[0113] The APP building device provided in this embodiment can execute the APP building method of the above embodiment. Its implementation principle and technical effect are similar, and will not be described again in this embodiment.

[0114] In the specific implementation of the aforementioned APP building device, each module can be implemented as a processor. The processor can execute computer execution instructions stored in the memory, thereby enabling the processor to execute the aforementioned APP building method.

[0115] Figure 6 A schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 60 includes at least one processor 601 and a memory 602. The electronic device 60 also includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus 604.

[0116] In the specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, causing at least one processor 601 to execute the APP construction method executed on the electronic device side as described above.

[0117] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0118] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0119] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage.

[0120] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0121] The above description of the functions implemented by electronic devices and main control devices has introduced the solutions provided by the embodiments of the present invention. It is understood that, in order to implement the above functions, the electronic device or main control device includes hardware structures and / or software modules corresponding to the execution of each function. By combining the units and algorithm steps of the various examples described in the embodiments of the present invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.

[0122] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described APP construction method.

[0123] The aforementioned computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0124] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in application-specific integrated circuits (ASICs). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.

[0125] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0126] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for constructing an APP, characterized by, include: Obtain the application functions implemented by the target APP; Based on the pre-stored historical build library, determine whether there is a target data package in the historical build library that can achieve at least some of the application functions of the target APP; If so, and there are multiple target data packets, then prioritize them according to the number of application functions of the target APP that each target data packet can implement, and output the data packet that implements the most application functions of the target APP as the target data packet. Based on the target data packet, the basic data of the target APP is constructed, and the basic data of the target APP is stored in the historical construction library in the form of data packets. The historical construction library includes multiple data packets, each of which includes data of at least one functional component, and the functional component has a corresponding relationship with the application function. If the mobile operating system adapted by the target APP is iOS, the certificate of the iOS system is obtained, and the basic data is constructed based on the certificate and the target data packet. The basic data of the target APP is uploaded to the preset application platform to complete the construction of the target APP; It also includes: matching the target data packet with the application function list, and determining whether the target data packet can implement all application functions in the application function list; If all are achieved, then the basic data of the target APP is constructed based on the target data package; If partially implemented, the unimplemented application functions will be matched with the pre-stored functional component library. The functional component library stores finished third-party components developed by third-party companies and internally common components pre-developed by the company. Each third-party component and each internal component corresponds to an application function stored in the functional component library. Retrieve functional components that match the unimplemented application functionalities; The functional components are combined with the target data package to construct the basic data of the target APP.

2. The method of claim 1, wherein, If the target data package in the historical build library fails to achieve all the application functions of the target APP, the step of building the basic data of the target APP based on the target data package includes: Retrieve the target functional components corresponding to the remaining application functions; Based on the target data packet and the data of the target functional components, construct the basic data of the target APP.

3. The method according to claim 1 or 2, characterized in that, Before constructing the basic data of the target APP based on the target data packet, the method further includes: Obtain the version number of the target data packet stored in the historical build library; Obtain a list of version numbers for the target data packet from the server; Based on the version number of the target data packet and the list of version numbers, determine whether the target data packet is the latest version; If not, the latest version of the target data package is obtained from the server, and the target data package in the historical build library is updated.

4. The method of claim 2, wherein, Before constructing the basic data of the target APP based on the target data packet and the data of the target functional component, the method further includes: Send the target data packet and the data of the target functional component to the component confirmation terminal; Obtain the confirmation result uploaded by the terminal for the component confirmation; Determine whether the confirmation result is "confirmation passed" to obtain the confirmation result.

5. The method of claim 4, wherein, Before uploading the basic data of the target APP to the preset application platform, the method further includes: Based on the target data packet and the data of the target functional components that have been confirmed as passed, the basic data of the target APP is constructed.

6. The method according to claim 1 or 2, characterized in that, The step of constructing the basic data of the target APP based on the target data packet includes: Obtain the build type of the target APP, wherein the build type includes the mobile operating system of the target APP terminal, and the mobile operating system includes at least one of iOS system and Android system; Based on the construction type and the target data package, construct the basic data of the target APP.

7. An APP building device, characterized in that, The APP building device is used to implement the APP building method according to any one of claims 1-6, including: The acquisition module is used to acquire the application functions implemented by the target APP. The judgment module is used to determine, based on the pre-stored historical build library, whether there is a target data package in the historical build library that can achieve at least some of the application functions of the target APP; The processing module is used to construct the basic data of the target APP based on the target data packet. The historical construction library includes multiple data packets, and each data packet includes data of at least one functional component. The functional component has a corresponding relationship with the application function. The sending module is used to upload the data components of the target APP to a preset application platform to complete the construction of the target APP.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

Images