While running their own small program, many developers want to further understand, how to achieve my own small program, and other apps (especially wechat App) jump?

When it comes to small programs, the first thing that comes to mind is wechat small programs. Now, FinClip “opens up” this capability, so that any App can run its own small programs.

While running their own small program, many developers want to further understand, how to achieve my own small program, and other apps (especially wechat App) jump?

Today, we will focus on the logic of this jump and how it is implemented.

I. FinClip applet and wechat applet

The beginning is clear and concept first. Before sorting through jumps, it’s worth taking a second look at what each of these small programs is.

Wechat applets: Almost without explanation, is a small program specification running in wechat App

FinClip applet:

FinClip applet = wechat applet: From the technical stack, a wechat applet can be directly compiled into FinClip applet, a code package on both sides (wechat App and App integrating FinClip SDK), the performance is exactly the same

FinClip ≠ wechat: In terms of the launching process, FinClip is an independent platform with its own management background. Customers can run small programs on their own APP through FinClip SaaS SDK. At the same time, wechat is an absolutely independent APP. Small programs must apply for an account on wechat and wait for approval. The whole process is handled by wechat (also known as Tencent), and no third party can interfere

FinClip > wechat: The FinClip SDK enables any App to have the ability to run small programs, and also supports the ability to put small programs on other mainstream App platforms (such as Baidu, Alipay).

2. Arrangement and combination of applets and App jumps

Based on FinClip capability, the jump between apet and App is not just one way or path. We have sorted out 6 paths as shown in the figure below.

Next, take a look at how to implement it.

Three, how to realize the specific jump

Scenario 1: wechat applet — wechat App

Scenario Description:

This is the jump of the most basic applet to App. In fact, both FinClip applet to FinClipApp and wechat applet to wechat App realize content switching within their own ecology

Implementation method:

The applet can return to the App by returning and exiting, and the App can also enter the page of the specified applet by defining the entry parameters of the applet

FinClip: Setting method for entering the specified page of the App

  • Finclip: Setting method for entering the specified page of the App
  • Finclip: Closes applets at the interface level

Scenario 2: FinClip – wechat App

Scenario Description:

What is wechat? It is the largest public domain traffic in the network world. By sharing to wechat, we can:

  • For example, when App shares H5 to wechat, users can only see one page and one function point in the current H5. Users cannot view the overall description or other contents from this function point. However, small programs are different. Small programs can realize multi-level business functions. Users can also log in, operate and complete more complex operations associated with App directly in small programs
  • Fission sharing in wechat is realized through small programs, which provides another solution to the problem of attracting new and activating App

How to do it: With just a few lines of code, FinClip App can share small programs to wechat

  • Share to wechat in APP integrated with finclipSDK
  • When sharing, the screenshot of the current page is synchronized to draw the sharing poster

Scenario 3: wechat Applets – Own App (App integrated with FinClip SDK)

Scenario Description: Traffic diversion Traffic diversion is the traffic that leads to your home. In wechat small program through content, activities to attract the flow, naturally to flow back to its own App

Implementation method: It should be emphasized that the jump from wechat to its own App is mainly limited by the provisions of wechat itself, and the capabilities that wechat does not provide are basically difficult to solve. In the recent version of wechat mini program, the entry of direct “return to App” has been removed. At present, the drainage that can be realized through the mini program is mainly as follows:

  • In the small program, guide the user to open the customer service message, and reply the App download link in the customer service message

Set the entrance in wechat mini program → guide to customer service information → customer service reply download link → guide to App (or guide users to download) → open corresponding content in its own App

  • In the applet, add an H5 page, implemented through the launchApp in H5

Scenario 4: FinClip – wechat – Own App

Scenario Description:

A closed loop, a closed loop, is a closed loop. Only by realizing the closed loop of FinClip to wechat and back to App can the activity operation be complete.

Implementation method: This scenario is actually a combination of scenario 3 and scenario 4, which can be achieved by superimposing the two methods.

Scenario 5: Others (SMS, email, web page, etc.) – FinClip (own App)

Scenario Description: In addition to the mutual hop between wechat and App, any other location can also be realized to the small program and App. Here’s an example:

  • When 618 comes, target these customers with a “10% off benefit” via SMS, email, web page, etc., and then steer them back to the mini program or App from the benefit
  • In EDM marketing, we always face the problem of low user touch rate and lower conversion rate. If we provide users with a shorter landing method, can we effectively improve the conversion rate?

How to do it: The FinClip applet supports production of short chains that can be woken up from the outside