A cross-platform joint development method and system

Abstract

The present invention relates to a cross-platform joint development method and system, the method comprises the following steps of establishing a code cloud packaging mode and establishing a code offline packaging mode, wherein a joint developer develops a software project on a computer software, exports a resource file, puts the exported resource file into a local computer or a local server, and does not upload the resource file to a cloud platform, encrypts the exported resource file, adds a section of code to the encrypted resource file, and another joint developer obtains the resource file and needs to obtain authorization before opening the resource file; the joint developer selects a code cloud packaging mode or a code offline packaging mode according to the security level of the software project. Different from the prior art, it can effectively avoid uploading data to a cloud server, avoid the problem of easy loss of source code, effectively improve the security of the source code, and adopt the dual protection of encryption processing and authorized development.

Description

Technical Field

[0001] The present invention relates to the technical field of cross-platform joint development, and in particular to a cross-platform joint development method and system. Background Art

[0002] Traditional native development has the problems of high development cost, long version iteration cycle, slow response speed, and multiple staffing, which makes it difficult to keep up with the growing scale of enterprises at this stage and meet the business needs of enterprises that require fast iteration, fast launch, and multiple containers and multi-project access. For example, the cost of updating the whole package of traditional App is relatively high, and it also requires market review and a long cycle, which is not conducive to the rapid iteration and development of App. In addition, when developing applications for different platforms such as Android, IOS and Web, the same demand requires different developers for iOS and Android under native development.

[0003] More information related to the above technical solution can also be found in the following documents:

[0004] In the patent with publication number CN 111414158 A, a cross-platform development method, a cross-platform development system and its electronic device are disclosed. The cross-platform development method includes: converting the Vue source code into a JS package through a converter; deploying the JS package in a server; sending the JS package to the terminal according to the request of the terminal; receiving and executing the JS package by the JS framework in the terminal; sending rendering instructions to the local by the JS framework; rendering by the local rendering engine. It builds high-performance, high-reuse, and scalable native applications with the development experience of the web.

[0005] In the process of implementing the present invention, the inventors found that the prior art has the following problems:

[0006] In the existing cross-platform joint development method, the code ultimately needs to be uploaded to the cloud server, which will distribute it uniformly, making the source code easy to lose and the source code security weak. Summary of the invention

[0007] To this end, a cross-platform co-development method and system need to be provided to solve the technical problems that the existing cross-platform co-development methods ultimately need to upload the code to a cloud server and distribute it uniformly by the cloud server, which leads to the easy loss of source code and weak source code security.

[0008] To achieve the above object, the inventor provides a cross-platform co-development method, comprising the following steps:

[0009] Establish a code cloud packaging mode, in which one co-developer develops a software project on the computer software, exports resource files, and uploads the resource files to the cloud server, and another co-developer uses the same account to log in to the software, downloads resource files, imports them into the computer software to edit the software project, and after editing, exports resource files and uploads the resource files to the cloud server;

[0010] Establish a code offline packaging mode, where one of the co-developers develops a software project on the computer software, exports the resource file, and puts the exported resource file into the local computer or local server. The resource file is not uploaded to the cloud platform, and the exported resource file is encrypted. A piece of code is added to the encrypted resource file. Another co-developer obtains the resource file and needs to obtain authorization before opening the resource file. Otherwise, the opened resource file will be garbled.

[0011] The co-developers select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. After the co-developers select the code cloud packaging mode, they can switch the development software project to the code offline packaging mode. After the co-developers select the code offline packaging mode, they cannot switch back to the code cloud packaging mode.

[0012] Different from the prior art, the above technical solution establishes a code cloud packaging mode and a code offline packaging mode. In the code offline packaging mode, one of the co-developers develops a software project on the computer software, exports a resource file, and puts the exported resource file into a local computer or a local server. The resource file is not uploaded to the cloud platform, and the exported resource file is encrypted. A piece of code is added to the encrypted resource file. Another co-developer obtains the resource file and needs to obtain authorization before opening the resource file, otherwise the opened resource file is garbled. The co-developers choose the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. After the co-developers choose the code cloud packaging mode, they can switch the development software project to the code offline packaging mode. In this way, you can choose the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. When developing a software project with a low security level, you can choose the code cloud packaging mode. As long as you log in to the same account, you can edit the same software project; when developing a software project with a high security level, choose the code offline packaging mode. The software project is not uploaded to the cloud platform, and the data is encrypted. You must obtain authorization before you can open the data. This can effectively avoid uploading data to the cloud server and avoid the problem of easy loss of source code. It can effectively improve the security of the source code and adopt the dual protection of encryption and authorized development.

[0013] As an implementation mode of the present invention, the code cloud packaging mode is specifically as follows: one of the co-developers develops a software project on uni-app, exports resource files on uni-app, uploads the resource files on the cloud server of uni-app, uni-app returns an Android software or iOS software, another co-developer logs in to uni-app using the same account, downloads the resource files of the software project, modifies the source code on uni-app, and after editing, exports the resource files on uni-app, and uploads the resource files on the cloud server of uni-app.

[0014] In this way, co-developers can jointly edit a software project on uni-app to facilitate joint development. After uploading to uni-app, they can return an Android software or iOS software.

[0015] As an implementation mode of the present invention, the code offline packaging mode is specifically as follows: one of the co-developers develops a software project on uni-app, exports a resource file on uni-app, places the resource file in a local Android native project for editing, encrypts the exported resource file, adds a piece of code to the environment variable of the Android native project, and when opening the resource file again, authorization must be obtained before the resource file can be opened. After opening the resource file, the resource file needs to be decrypted before it can be edited again.

[0016] In this way, one of the co-developers can complete the development in the uni-app and export the data for local processing. After exporting locally, the data can be encrypted and pre-authorized in the local Android native project to facilitate data encryption.

[0017] As an implementation mode of the present invention, the added code is appid. When the application is started, it will automatically check whether the operator's id is the same as the added appid. If they are the same, authorization is obtained.

[0018] In this way, a physical address can be added to the source code. When the source code is opened again, the same physical address is required to open the source code, thereby improving the security of the source code.

[0019] As an implementation mode of the present invention, the added code is appkey, and the operator will be automatically verified when the application is started. If the verification is successful, authorization is obtained.

[0020] In this way, a software account can be added to the source code. When the source code is opened again, the same software account is required to open the source code, thereby improving the security of the source code.

[0021] As an implementation mode of the present invention, the added code is appsecret, and the operator will be automatically verified when the application is started. If the verification is successful, authorization is obtained.

[0022] In this way, a private key can be added to the source code. When the source code is opened again, a password is required to open the source code, thereby improving the security of the source code.

[0023] As an implementation of the present invention, another co-developer needs to use the development tool of uni-app to edit the source code of uni-app through a mobile storage device or on a local server, or the resource file.

[0024] In this way, when another co-developer edits the source code, he or she also needs to use uni-app's development tools to maintain the uniformity of the code and keep the code developed on the same platform, making it easier for the co-developer to read and edit the code.

[0025] As an implementation mode of the present invention, in the code offline packaging mode, it is necessary to first generate a signature based on the added code, and another co-developer obtains authorization based on the signature.

[0026] In this way, in the offline code packaging mode, another co-developer needs to generate a signature based on the added code, so that subsequent co-developers can obtain authorization based on the signature, without having to store the physical address, software account, and private key in the added code in advance.

[0027] As an implementation mode of the present invention, in the code offline packaging mode, the encryption process uses an asymmetric encryption algorithm to encrypt the code.

[0028] In this way, the code can be encrypted by scrambling, reversing, or changing the position of the source code, making it easier to decrypt the source code later.

[0029] To achieve the above objectives, the inventors also provide a cross-platform co-development system for executing any of the cross-platform co-development methods provided by the inventors above.

[0030] Different from the prior art, the system of the above technical solution can select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. When developing a software project with a low security level, the code cloud packaging mode can be selected. As long as the same account is logged in, the same software project can be edited; when developing a software project with a high security level, the code offline packaging mode is selected. The software project is not uploaded to the cloud platform, and the data is encrypted. The data can be opened only after obtaining authorization. This can effectively avoid uploading data to the cloud server and avoid the problem of easy loss of source code. It can effectively improve the security of the source code and adopt the dual protection of encryption and authorized development.

[0031] The above-mentioned records related to the invention content are only an overview of the technical solution of the present application. In order to enable ordinary technicians in the field to more clearly understand the technical solution of the present application, and then implement it according to the written contents of the specification, and to make the above-mentioned purpose and other purposes, features and advantages of the present application easier to understand, the specific implementation methods of the present application are explained below. DETAILED DESCRIPTION

[0032] In order to explain in detail the possible application scenarios, technical principles, specific schemes that can be implemented, and the purposes and effects that can be achieved, the following is a detailed description in conjunction with the specific embodiments listed. The embodiments described herein are only used to more clearly illustrate the technical solutions of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.

[0033] Reference to "embodiment" herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The term "embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment, nor does it particularly limit its independence or association with other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, the various technical features mentioned in the embodiments can be combined in any way to form a corresponding implementable technical solution.

[0034] Unless otherwise defined, the technical terms used in this document have the same meanings as those generally understood by those skilled in the art to which this application belongs; the use of relevant terms in this document is only for describing specific embodiments and is not intended to limit this application.

[0035] In the description of this application, the term "and / or" is an expression used to describe the logical relationship between objects, indicating that three relationships may exist, for example, A and / or B, which means: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in this article generally indicates that the objects before and after are in an "or" logical relationship.

[0036] In the present application, terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship of quantity, priority or sequence between these entities or operations.

[0037] Without further limitations, in this application, the words "include", "comprises", "has" or other similar expressions used in the sentences are intended to cover non-exclusive inclusion. These expressions do not exclude the presence of additional elements in the process, method or product including the elements, so that the process, method or product including a series of elements may include not only those limited elements, but also other elements not explicitly listed, or also include elements inherent to such process, method or product.

[0038] Similar to the understanding in the Examination Guidelines, in this application, expressions such as "greater than", "less than", "exceed" and the like are understood to exclude the number itself; expressions such as "above", "below", "within" and the like are understood to include the number itself. In addition, in the description of the embodiments of this application, "multiple" means more than two (including two), and similar expressions related to "multiple" are also understood in this way, such as "multiple groups", "multiple times", etc., unless otherwise clearly and specifically limited.

[0039] The concept of cross-platform is an important concept in software development, which means that it does not depend on the operating system or the hardware environment. An application developed under one operating system can still run under another operating system. Relatively speaking, if a certain computer language can be highly cross-platform without modifying the code, then the more abstract the language is, the lower the hardware control power is, and it is only suitable for developing highly abstract model systems. Cross-platform joint development requires developers to realize multiple people in multiple locations on the above basis to jointly develop the same software project without the need to gather people together.

[0040] In the existing cross-platform joint development method, the code must eventually be uploaded to the cloud server, which will distribute it uniformly. During the uploading or distributing process, the source code is easily lost or leaked, and the source code security is weak.

[0041] The applicant has found that the cloud-based code packaging mode or offline code packaging mode can be selected according to the security level of the software project. When developing a software project with a low security level, the cloud-based code packaging mode can be selected. As long as the same account is logged in, the same software project can be edited; when developing a software project with a high security level, the offline code packaging mode is selected. The software project is not uploaded to the cloud platform, and the data is encrypted. The data can be opened only after obtaining authorization. This can effectively avoid uploading data to the cloud server and avoid the problem of easy loss of source code. It can effectively improve the security of the source code and adopt the dual protection of encryption and authorized development.

[0042] The present embodiment relates to a cross-platform joint development method and system, which can be applied to technical fields related to cross-platform joint development.

[0043] According to some embodiments of the present application, this embodiment relates to a cross-platform co-development method, comprising the following steps:

[0044] Establish a code cloud packaging mode, in which one co-developer develops a software project on the computer software, exports resource files, and uploads the resource files to the cloud server, and another co-developer uses the same account to log in to the software, downloads resource files, imports them into the computer software to edit the software project, and after editing, exports resource files and uploads the resource files to the cloud server;

[0045] Establish a code offline packaging mode, where one of the co-developers develops a software project on the computer software, exports the resource file, and puts the exported resource file into the local computer or local server. The resource file is not uploaded to the cloud platform, and the exported resource file is encrypted. A piece of code is added to the encrypted resource file. Another co-developer obtains the resource file and needs to obtain authorization before opening the resource file. Otherwise, the opened resource file will be garbled.

[0046] The co-developers select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. After the co-developers select the code cloud packaging mode, they can switch the development software project to the code offline packaging mode. After the co-developers select the code offline packaging mode, they cannot switch back to the code cloud packaging mode.

[0047] In this embodiment, a code cloud packaging mode and a code offline packaging mode are established. The code offline packaging mode is that one of the co-developers develops a software project on the computer software, exports a resource file, and puts the exported resource file into a local computer or a local server. The resource file is not uploaded to the cloud platform, and the exported resource file is encrypted. A piece of code is added to the encrypted resource file. Another co-developer obtains the resource file and needs to obtain authorization before opening the resource file, otherwise the opened resource file is garbled. The co-developers select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. After the co-developers select the code cloud packaging mode, they can switch the development software project to the code offline packaging mode.

[0048] In this way, you can choose the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. When developing a software project with a low security level, you can choose the code cloud packaging mode. As long as you log in to the same account, you can edit the same software project; when developing a software project with a high security level, choose the code offline packaging mode. The software project is not uploaded to the cloud platform, and the data is encrypted. You must obtain authorization before you can open the data. This can effectively avoid uploading data to the cloud server and avoid the problem of easy loss of source code. It can effectively improve the security of the source code and adopt the dual protection of encryption and authorized development.

[0049] According to some embodiments of the present application, optionally, the code cloud packaging mode is specifically as follows: one of the co-developers develops a software project on uni-app, exports resource files on uni-app, uploads the resource files on the cloud server of uni-app, and uni-app returns an Android software or iOS software; another co-developer logs in to uni-app using the same account, downloads the resource files of the software project, modifies the source code on uni-app, and after editing, exports the resource files on uni-app, and uploads the resource files on the cloud server of uni-app.

[0050] uni-app is a framework that uses Vue.js(opens new window) to develop all front-end applications. Developers write a set of codes and can publish them to multiple platforms such as iOS, Android, Web (responsive), various mini-programs (WeChat / Alipay / Baidu / Toutiao / Feishu / QQ / Kuaishou / DingTalk / Taobao), and quick applications.

[0051] Specifically, in the code cloud packaging mode, the co-developer develops the software project on uni-app, exports the resource files on uni-app, and uploads the resource files to the cloud server of uni-app. After the packaging is successful, uni-app will return a link address for downloading apk, and the developer can download it by himself. Another co-developer uses the same account to log in to uni-app and log in to the third-party server (uni-app's cloud server) for editing.

[0052] In this way, co-developers can jointly edit a software project on uni-app to facilitate joint development. After uploading to uni-app, they can return an Android software or iOS software.

[0053] According to some embodiments of the present application, optionally, the code offline packaging mode is specifically as follows: one of the co-developers develops a software project on uni-app, exports a resource file on uni-app, places the resource file in a local Android native project for editing, encrypts the exported resource file, adds a piece of code to the environment variable of the Android native project, and when opening the resource file again, authorization is required before the resource file can be opened. After opening the resource file, the resource file needs to be decrypted before it can be edited again.

[0054] In this way, one of the co-developers can complete the development in the uni-app and export the data for local processing. After exporting locally, the data can be encrypted and pre-authorized in the local Android native project to facilitate data encryption.

[0055] According to some embodiments of the present application, optionally, the added code is an appid, and when the application is started, it will automatically check whether the operator's id is the same as the added appid. If they are the same, authorization is obtained.

[0056] Appid can be an app account, or it can refer to a physical id or physical address.

[0057] In this way, a physical address can be added to the source code. When the source code is opened again, the same physical address is required to open the source code, thereby improving the security of the source code.

[0058] According to some embodiments of the present application, optionally, the added code is appkey, and the operator is automatically verified when the application is started. If the verification is successful, authorization is obtained.

[0059] App key is short for API interface verification serial number, which is used to verify the legitimacy of API access. To access the API interface of a website, you need the permission of the website to access it. To put it simply, it can be understood as the username for logging into the website.

[0060] In this way, a software account can be added to the source code. When the source code is opened again, the same software account is required to open the source code, thereby improving the security of the source code.

[0061] According to some embodiments of the present application, optionally, the added code is appsecret, and the operator is automatically verified when the application is started. If the verification is successful, authorization is obtained.

[0062] appsecret is a private key (equivalent to a password). It is also called API interface key, and is used together with App Key. It can be simply understood as a password.

[0063] In this way, a private key can be added to the source code. When the source code is opened again, a password is required to open the source code, thereby improving the security of the source code.

[0064] According to some embodiments of the present application, optionally, another co-developer may use a mobile storage device or a local server, or the resource file, to edit the source code of the uni-app using a development tool of the uni-app.

[0065] In this way, when another co-developer edits the source code, he or she also needs to use uni-app's development tools to maintain the uniformity of the code and keep the code developed on the same platform, making it easier for the co-developer to read and edit the code.

[0066] According to some embodiments of the present application, optionally, in the code offline packaging mode, it is necessary to first generate a signature based on the added code, and another co-developer obtains authorization based on the signature.

[0067] In this way, in the offline code packaging mode, another co-developer needs to generate a signature based on the added code, which will facilitate subsequent co-developers to obtain authorization based on the signature, without the need to store the physical address, software account, and private key in the added code in advance.

[0068] According to some embodiments of the present application, optionally, in the code offline packaging mode, the encryption process uses an asymmetric encryption algorithm to encrypt the code.

[0069] In this way, the code can be encrypted by scrambling, reversing, or changing the position of the source code, making it easier to decrypt the source code later.

[0070] This embodiment also relates to a cross-platform joint development system, which is used to execute the cross-platform joint development method as described above. The system includes a computer, a local server, a cloud server, etc.

[0071] According to some embodiments of the present application, this embodiment relates to a cross-platform joint development method, comprising the following steps:

[0072] Establish a code cloud packaging mode, in which one co-developer develops a software project on the computer software, exports resource files, and uploads the resource files to the cloud server, and another co-developer uses the same account to log in to the software, downloads resource files, imports them into the computer software to edit the software project, and after editing, exports resource files and uploads the resource files to the cloud server;

[0073] Establish a code offline packaging mode, where one of the co-developers develops a software project on the computer software, exports the resource file, and puts the exported resource file into the local computer or local server. The resource file is not uploaded to the cloud platform, and the exported resource file is encrypted. A piece of code is added to the encrypted resource file. Another co-developer obtains the resource file and needs to obtain authorization before opening the resource file. Otherwise, the opened resource file will be garbled.

[0074] The co-developers select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. After the co-developers select the code cloud packaging mode, they can switch the development software project to the code offline packaging mode. After the co-developers select the code offline packaging mode, they cannot switch back to the code cloud packaging mode.

[0075] In this embodiment, the code cloud packaging mode and the code offline packaging mode are specifically developed based on uni-app.

[0076] Different from the prior art, the system of the above technical solution can select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. When developing a software project with a low security level, the code cloud packaging mode can be selected. As long as the same account is logged in, the same software project can be edited; when developing a software project with a high security level, the code offline packaging mode is selected. The software project is not uploaded to the cloud platform, and the data is encrypted. The data can be opened only after obtaining authorization. This can effectively avoid uploading data to the cloud server and avoid the problem of easy loss of source code. It can effectively improve the security of the source code and adopt the dual protection of encryption and authorized development.

[0077] Those skilled in the art should understand that the above embodiments can be provided as methods, devices, or computer program products. These embodiments can be in the form of complete hardware embodiments, complete software embodiments, or embodiments combining software and hardware. All or part of the steps in the methods involved in the above embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a storage medium readable by a computer device for executing all or part of the steps described in the above embodiments. The computer device includes, but is not limited to: personal computers, servers, general-purpose computers, special-purpose computers, network devices, embedded devices, programmable devices, smart mobile terminals, smart home devices, wearable smart devices, in-vehicle smart devices, etc.; the storage medium includes, but is not limited to: RAM, ROM, disk, tape, CD, flash memory, U disk, mobile hard disk, memory card, memory stick, network server storage, network cloud storage, etc.

[0078] The above-mentioned embodiments are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of the computer device to generate a machine, so that the instructions executed by the processor of the computer device generate a device for implementing the functions specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0079] These computer program instructions may also be stored in a computer device readable memory that can direct the computer device to work in a specific manner, so that the instructions stored in the computer device readable memory produce a product including an instruction device, which implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0080] These computer program instructions can also be loaded onto a computer device so that a series of operating steps are executed on the computer device to produce a computer-implemented process, whereby the instructions executed on the computer device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0081] It should be noted that, although the above embodiments have been described in this article, the patent protection scope of the present invention is not limited thereby. Therefore, based on the innovative concept of the present invention, changes and modifications made to the embodiments described herein, or equivalent structures or equivalent process changes made using the contents of the present invention specification, directly or indirectly applying the above technical solutions to other related technical fields are all included in the patent protection scope of the present invention.

Claims

1. A cross-platform joint development method, characterized in that: The following steps are involved: Establish a code cloud packaging mode, where A co-developer develops a software project on the computer software, exports resource files, and uploads the resource files to the cloud server. Another co-developer uses the same account to log in to the software, downloads resource files, imports them into the computer software to edit the software project, and after editing, exports resource files and uploads the resource files to the cloud server. Establish code offline packaging mode, where A co-developer develops a software project on a computer software, exports a resource file, and puts the exported resource file into a local computer or local server. The resource file is not uploaded to the cloud platform, and the exported resource file is encrypted. A piece of code is added to the encrypted resource file. Another co-developer obtains the resource file and needs to obtain authorization before opening the resource file. Otherwise, the opened resource file will be garbled. The co-developers select the code cloud packaging mode or the code offline packaging mode according to the security level of the software project. After the co-developers select the code cloud packaging mode, they can switch the development software project to the code offline packaging mode. After the co-developers select the code offline packaging mode, they cannot switch back to the code cloud packaging mode.

2. The cross-platform joint development method according to claim 1, characterized in that: The code cloud packaging mode is specifically: One of the co-developers develops a software project on uni-app, exports resource files on uni-app, and uploads the resource files to uni-app's cloud server. Uni-app returns an Android software or iOS software. Another co-developer logs in to uni-app using the same account, downloads the resource files of the software project, modifies the source code on uni-app, and after editing, exports the resource files on uni-app and uploads the resource files to uni-app's cloud server.

3. The cross-platform joint development method according to claim 1, characterized in that: The code offline packaging mode is specifically: One of the co-developers develops a software project on uni-app, exports resource files on uni-app, places the resource files in a local Android native project for editing, encrypts the exported resource files, adds a piece of code to the environment variables of the Android native project, and when opening the resource file again, authorization is required before the resource file can be opened. After opening the resource file, the resource file needs to be decrypted before it can be edited again.

4. The cross-platform joint development method according to claim 3, characterized in that: The code for joining is appid. When the application is started, it will automatically check whether the operator's id is the same as the joined appid. If they are the same, authorization is obtained.

5. The cross-platform joint development method according to claim 3, characterized in that: The added code is appkey. When the application is started, the operator will be automatically verified. If the verification is successful, authorization will be obtained.

6. The cross-platform joint development method according to claim 3, characterized in that: The added code is appsecret. When the application is started, the operator will be automatically verified. If the verification is successful, authorization will be obtained.

7. The cross-platform joint development method according to claim 3, characterized in that: Another co-developer needs to use the uni-app development tool to edit the uni-app source code through a mobile storage device or on a local server, or the resource file.

8. The cross-platform joint development method according to claim 3, characterized in that: In the offline code packaging mode, you need to generate a signature based on the added code first, and another co-developer obtains authorization based on the signature.

9. The cross-platform joint development method according to any one of claims 1 to 8, characterized in that: In the offline code packaging mode, encryption processing uses an asymmetric encryption algorithm to encrypt the code.

10. A cross-platform joint development system, characterized in that: Used to execute the cross-platform co-development method according to any one of claims 1 to 9.