Small programs work together and are published

In large and medium-scale companies, the division of personnel is very careful, generally there will be different roles of employees involved in the same small program project. To this end, the small program platform has designed different rights management so that project managers can more efficiently manage the team's work together.

In the past, after we developed the web page, we needed to put the code and resources of the web page on the server so that users could access it over the Internet. In a small program's platform, after the developer has completed development, he or she needs to submit the code package for the small program in the developer's tool, and then publish the small program in the background of the small program, which the user can access through search or other portals.

In this chapter we will introduce some of the concepts and processes involved before and after the release of the team's work together considerations and small programs.

Work together

If you're just developing a small program for one person, you can skip this section for the time being, and if it's a team you need to understand some concepts first.

In most cases, a team of multiple people is involved in the same small program project at the same time, each role has a different job or authority, and the division of labor between large and medium-scale companies is more careful. To better visually express the relationships between the different roles of the team and the management of permissions, we use a virtual project member organization structure to describe how we work together on a daily basis to complete the release of a small program, as shown in Figure 5-1.

Figure 5-1 Virtual Small Project Group

Project management members are responsible for overall the progress and risk of the entire project, put on the rhythm, product groups issued by the control, product group, design groups and product discussions, and design the visualization process and graphics, and output design.The development group is based on the design plan, after the program code is written, after the code is written, the product group and the design group experience the overall process of the small program, the test group writes test cases and performs various boundary tests for the applet.The composition of the project is constituted and the workflow is shown in Figure 5-2.

Figure 5-2 Squits to the process of publishing a small program

Small program member management

Small program member management includes management of small program project members and experience members.

• Project members: Represents members of participating in small procedures development, operation, can log in to the small program management background, including operators, developers, and data analysts.Administrators can add, delete project members, and set the role of project members.
• Experience members: Representing members of the participating in the small program, you can use the experience version of the applet, but do not belong to item members.Administrators and project members can add and delete the experience member.

Different project members have different permissions to ensure that the applet development is safe or orderly.

Authority	Operator	Developer	Data analyst
Developer permission		√
Experience	√	√	√
Log in	√	√	√
data analysis			√
WeChat payment	√
Promote	√
Development management	√
Development settings		√
Suspend the service	√
Disonect the public number	√
Tencent Cloud Management		√
The small program plug-in	√
Game operations management	√

Description of each permission function

• Developer rights: You can use small program developer tools and development version of small programs for development
• Experiencer permissions: Experienced gadgets are available
• Sign in: You can log in to the small program to manage the background without administrator confirmation
• Data analysis: Use the small program statistics module function to view the small program data
• WeChat Payment: Use the small program WeChat Payment (Virtual Payment) module
• Promotion: Use the small program traffic master, advertiser module
• Development management: small programs submit for review, release, fallback
• Development settings: set up small program server domain name, message push and scan ordinary link QR code open small program
• Pause service settings: Pause service on-line
• Unconnected Public Number: The untied public number that is already associated with the small program
• Small program plug-ins: You can manage and set up the small program plug-in development
• Game operations management: you can use small games to manage back-office footage management, game circle management and other functions

It is important to note that project managers control sensitive operations such as the release, fallback, and down-racking of entire small programs and should not assign permissions to sensitive operations to unrelevant personnel

The version of the gadget

In the general software development process, developers write code self-test development programs until the program reaches a stable and experienceable state, developers will give this version of the experience to product managers and testers for experience testing, and finally fix the bug of the program and release it for official use by external users. The version of the gadget is based on this process and the concept of the small program version is designed, as shown in Table 5-3.

Table 5-3 version of the gadget

Permissions	Description
The development version	Using developer tools, you can upload code to the development version. The development version retains only one copy of the uploaded code per person. Click Submit an audit to submit the code for review. The development version can be deleted without affecting the online version and the audited version of the code.
Experience version	You can select a development version as an experience version, and choose an experience version.
The version in the audit	Only one copy of the code is under review. After the audit results can be published online, can also be submitted directly to review, overwriting the original audit version.
Online version	The version of code used by all users online, which is overwritten and updated after the new version of the code is released.

Considering that the project is a collaborative development model, a small program may be developed by multiple developers at the same time, often developers in the small program developer tools after writing code to the mobile phone for a real experience, so each developer has their own corresponding development version. Because the version in development is unstable, the developer will modify the code coverage development version at any time, in order to allow the test and product manager to have a complete and stable version to experience testing, the small program platform allows one of the development versions to be set up as an experance version, so it is recommended that during the project development phase special allocation of a development role, for uploading stable code for experience testing, and his uploaded development version set up as an experience version.

Publish online

A small program from development to online generally go through the preview-upload code -

Preview

Developer tools allow you to preview small programs and help developers check how they really behave on mobile clients.

Clicking on the preview button in the action bar at the top of the developer tool, the developer tool automatically packages the current project and uploads the widget code to WeChat's server, which will display a QR code on the interface after success. Use the current small program developer's WeChat Broom to see how the small program is really performing on the mobile phone client.

Upload the code

Different from previews, upload code is used for submission experiences or audits.

Click on the upload button in the action bar at the top of the developer tool to fill in the version number and project notes, it is important to note that the version number and project notes here are for the convenience of the administrator to check the use of the version, developers can fill in these two fields according to their actual requirements.

After the upload is successful, log in to the small program management background - development management - development version you can find the version just submitted for upload.

You can set up this version for the Experience or submit for review

Submit an audit

In order to ensure the quality of the small program, as well as in line with the relevant specifications, the release of the small program needs to be reviewed.

After uploading the program code in the developer tool, log in to the small program management background - development management - development version to find the version that submitted the upload.

In the list of development versions, click Submit Review Follow the page prompts to fill in the relevant information, that is, you can submit the small program for review.

It is important to note that developers are required to rigorously test the version before submitting an audit, too many audits do not pass, may affect subsequent time.

Release

After the audit is approved, the administrator's WeChat will receive a notification that the program has passed the approval, at which point the approved version can be seen in the audited version by logging into the small program management background - development management - audit version.

Once you're posting, you can publish a small program. S mall programs provide two release modes: full and phased. F ull publishing means that when you click publish, all users access the gadget using the current latest release version. P hased releases are those that control some users' use of the latest releases at different times, and are also known as grayscaness releases. Generally speaking, ordinary small program release with full release can be, when the small program hosts more and more functions, the number of users used more and more, the use of phased release is a very good way to control risk.

Small program code

Many scenarios in which the user will quickly enter a small program by sweeping the code, in the early stages of the small program design, the small program platform provides the form of QR code. W e found that when the user sweeps a QR code, he does not know what kind of service will appear in the current scanning code, because behind the QR code there may be public numbers, small programs, web services, payment pages, add friends and other different services. In order for the user to have a clear expectation before sweeping the code, WeChat designed a small program code, as shown in Figure 5-3.

Figure 5-3 Small program code for the "Small Program Data Assistant"

Small program code in the style more recognizable and visual impact, compared to QR code, small program theme brand image is more clear and obvious, can help developers better promote small programs. After the release of the small program, the small program management platform will provide the corresponding small program code preview and download, developers can download their own for online and offline small program service promotion.

Operational data

There are two ways to easily see the operational data of a small program

Method one:

Sign in to the small program management background - data analysis

Click on the appropriate tab to see the relevant data.

Method two:

Use the small program data assistant to easily view operational data on WeChat