关于邀请分享

Last night, I invited Lao Qiu (Internet cancer) to experience the products of my company, and he was up all night.

The main thing to talk about is the design of the product's invitation to share.

Here's how existing invitations are shared:

• • Share QR code to social platforms = > Invitee identification QR code download app = > Scan the QR code in the app to add friends * *

There will be issues with the following experiences:

• Let the user identify the QR code to download. It is better to provide the download button directly.
• The QR code carries two functions: "Download the app" and "Scan the code to add friends". Many users recognize it and then download and install it, but the QR code is not saved.Then the cost for the user to return to the sharing page to scan the QR code is slightly higher.

So

I combine empirical analysis with previous design invitations:

• Start by separating the “Download App” from the “Add Friends” feature, rather than having the QR code carry the “Download” and “Scan to Add Friends” features.
• Secondly, by authorizing the user in the H5 page of the social platform and establishing an ID, any new user who opens this link will add friends according to the ID tag.
  • • This means that * * * * "After the user opens the H5 sharing page and obtains the authorization, an account has been established and the process of adding friends has been completed. After directly downloading the app and authorizing login, the friends have been added.Done. ”* *

The prototype process is as follows: