Dingdingapplets development guide – research

Project background

The frameworks we use, such as VUE and React, have their own life cycle, and each company we work for also has its own development life cycle. Different from VUE and React, the company’s life cycle can be roughly divided into four stages: start-up stage, growth stage, maturity stage and decline stage.

If a company does not want to go out of business during a recession, it needs to start a new cycle during the growth or maturity period to find new business growth points and achieve the second curve of enterprise development.

What I talked about at the beginning of the article was to introduce the background of the project and the strategic intention of the company. The company gave me this task to create a new product, create a new business line, and build the second curve of enterprise development.

Classification of nail applications

Well, without further ado, how to quickly develop a nail application, there are related tutorials in the Nail open platform, follow a run to make a simple demo. This article is not a tutorial, but a nail in the ecology research article, what can and can’t be done, etc.

Nailing applications can be divided into the following categories:

• Third-party enterprise Applications
• Internal enterprise applications
• Third party personal applications
• Mobile access application

The application type	developers	Using personnel	Ability to support	Can you upload to dingding application market
Third-party enterprise Applications	Developers of application services	Purchase the internal personnel who have opened the tripartite application	Small program H5 micro application	is
Internal enterprise applications	Enterprise internal developers or entrusted developers of custom service providers	The person inside the enterprise who installed the application	Small program H5 micro application The robot	no
Third party personal applications	Developers of application services	Nail individual users	Small program	is
Mobile access application	In-house developer Developers of application services	User of the application to be accessed	Login (Nail scan code and login with Nail account) Share (Share apps to Dingding)	–

Third-party enterprise apps and internal apps are the most frequently used nail apps. A mobile access application only supports login and sharing. It is a low-level application with basic functions and has little relationship with the company’s business. Third party personal applications only support small application development and have more restrictions and fewer capabilities than enterprise applications.

Internal enterprise applications

The first tutorial of Dingding open platform is the development and deployment of enterprise internal applications, development of internal dingding applications need to log in Dingding developer background, before this you need to apply to the company as an administrator or sub-administrator, and then you can follow the official tutorial step by step. When the login interface is activated to obtain user information after all steps are completed, the interface returns error:

It turned out to be an interfaceNo corresponding permissions are addedAfter adding the corresponding permissions in the background, the interface returns the correct data:

Internal enterprise applications are used by internal enterprise personnel who have installed the application, although they can be used by third party enterprises through actions such as:

First, let a third-party company manually create an internal application (micro-application) in the background of the nail, and then send the AppID, corpId, agentId and other application information in the micro-application to the enterprise, and the enterprise adds it to the program. However, the IP in the whitelist of an internal application (micro-application) can only be set once. If the server IP is set on the enterprise side, third-party companies cannot set that IP in their micro application. One solution is to: first to the third party company to buy a server, and then put the IP limitation method in the application of nailing (that is, call interface) copy out the deployment to the third party company to buy the server, and then the third party company micro white list is set at the application of them to buy the server IP

But when using the internal application of third-party companies more and more, the problem will be exposed, obviously, because the project deployment in the third party company’s own server, in the subsequent iterations once invoked nailing interface to the changes, in all third-party company server project to deploy again, very trouble, So intra-enterprise applications should be used by intra-enterprise people. If you want to use third-party companies, you should use third-party enterprise applications.

Third-party enterprise Applications

What are third-party enterprise applications

Third-party enterprise applications are third-party enterprise applications developed by application service providers, which can be sold to Enterprise organizations of Dingding by putting them on the shelves of Dingding Application Square, or offline applications can be distributed to enterprise organizations by creating application distribution projects in developer background through service providers. A type of application that can be developed and licensed for use by different organizations.

Applets and H5 microapplications are supported by third-party enterprise applications as well as intra-enterprise applications, but there are two important points to note:

1. Application Distribution Mode
2. Application licensing development

Application Distribution Mode

There are two main application distribution methods, both of which need to be settled into Dingding [application service provider]

• Nails app square distribution

  After the application is approved, it can be put on the app square for promotion. After the application is put on the shelf, the enterprise administrator can search in the application square of Dingding to find the third-party enterprise application needed, and let the employees in the enterprise use it after opening

• Own channel distribution

  The offline promotion TWO-DIMENSIONAL code can be generated through the interface provided by Dingding, and the application can be actively pushed to the administrator through the service provider’s own channels or external channels of Dingding (such as external advertising, third-party official websites, etc.), which can be installed and used after the administrator is authorized.

Before developing an application, determine the application distribution mode. The distribution mode determines the application interface permissions, deployment requirements, and delivery experience.

Application of authorization

The authorization here is similar to the authorization of users in the micro channel small program, but the micro channel small program is a single user, and the nail nail is the whole enterprise.

The application authorization process is as follows:

1. Customized service provider applications and service providers need to obtain an Access_token from an authorized enterprise through an interface. When the server API is invoked to obtain application resources, the access_Token is used to authenticate the identity of the caller for authorization.

2. Register a callback.

   A third-party enterprise application must register a callback event to receive an application authorization event. The event is used to notify the application which organization has enabled the application. After receiving the event, the third-party application background needs to initialize the enterprise information to enable the application.

3. Authorize the application.

   Nail nail application square in the third party enterprise applications, enterprise administrators can be authorized to open. During the authorization process, you need to receive the callback events enabled by the enterprise. The nail supports different callback push modes. The application initiation process varies with the callback method.

   RDS and HTTPSync are recommended to facilitate application authorization. There are three ways to push, and one is HTTP data push (not recommended).

4. Ability to access the server.

   Third-party enterprise applications must have access to nailing free, contacts, and job notification capabilities.

   • Free’s development

     When employees use a third-party enterprise application in Dingding, they can directly log in to the application without entering their account and password. The user information can be stored in the front-end cache (DD.setStorage) or cookie to avoid the need to call the pin interface for no-login every time you enter the application.

     The registration free access process is as follows:

     1. Obtain the unregistered authorization Code.
     2. Obtain the enterprise authorization certificate (access_token) by calling the service/get_corp_token interface.
     3. Call the user/ getUserInfo interface to get the userID of the user.
     4. Obtain user details through topAPI /v2/user/ GET.

   • The address book

     Obtain basic user information (excluding mobile phone numbers) of the application installation organization for user addition and authorization management.

   • Work order

     Send pin job notifications to users through the job notification interface.

5. The front-end development

   If you are developing H5 microapplications, JSAPI authentication is required.

conclusion

This paper mainly introduces the types of nail applications, focusing on internal applications and third-party enterprise applications, as well as the distribution and application authorization of nail applications. We hope readers can have a general understanding of the nail application. For a specific and detailed understanding, you can go to the nail open platform to read the relevant tutorials.