Development experience
Not long ago, I developed a WeChat applet with a relatively simple page, so I tested it briefly. It was released within 2 hours after submitting the review.
So I am going to follow the gourd painting and develop a QQ applet. In fact, the principle is the same.
First of all, I slightly modified the source code of the WeChat applet and compiled it into a QQ applet.
The real-time preview can be used normally, and the user logic is the same.
1. The review is too long
Here comes the key review.
The first reminder, there is copywriting or QR code in the applet to guide you to jump out of the QQ external station. fail
Change to the second version, delete the guide to follow the official account copy, and submit again
The second reminder, your applet uses generalized induction, general, general, and non-identifying vocabulary/stacking as the name of the applet
So change the name of the applet again and submit again
The third reminder, hello, your mini program is too simple/imperfect, and does not meet the "integrity" and "usability" requirements of the mini program, please modify it before submitting
So add the content of the applet and submit it again on Friday
This time, I waited for two or three days before giving me a review reminder. The user privacy protection guidelines are not set perfectly. Please resubmit
I really rely on the defense a little bit, so I re-checked and waited for two days.
Finally got me online.
2. Problems and solutions
- Do not add any QR code or guide jump copy, and the network disk is not allowed
- There should be as many pages as possible, otherwise you will be prompted that the applet is not perfect
- You must think carefully about the name of the applet, don't use that kind of marketing vocabulary
- The user privacy agreement must also be filled out carefully, the QQ applet review is too slow, it is really a waste of time
3. Learning and Sharing
That's all, if you are interested, you can enter the experience:
