What is a vest bag
The vest bag is generally a clone or clone of the main app, or an app wearing a vest. When the vest is removed, the app will take on another style, which is often referred to as the AB face app.
1. The avatar or clone vest package of the main APP
Firstly, the first type is the avatar or clone of the main APP. Nowadays, many companies usually have their own main product, but they will also make some castrated versions of the APP similar to the main APP, and the project code is basically completely reused. The application name, subtitle, icon, application screenshot, package name, keywords and developer account are all different from the main app, and the others are basically the same, such as the picture below: Why do you want to do this
? What is the benefit of doing so?
a. Avoid market or policy risks
It is used for app brush volume, ranking, word brushing, hot search, circumventing account restrictions, emergency measures to prevent delisting, competition of competing products, etc., to resist the risk of the main package.
b. Seize the limited position in the application market
Keyword search results placeholders, list placeholders, covering more keywords, etc.
c. Derivative
The vest package itself can acquire new users, and it can guide users to download the main app through background information sharing with the main app, pop-up windows or push notifications to guide users to download the main app.
d. Test the effects of large-scale revisions to reduce risks
The advantage of the vest package is that after a large-scale revision, the effect can be verified online, and once adverse effects are caused, it will not cause great losses. If the test results are good, you can iterate the corresponding functions of the main App.
2. AB side APP type vest bag
This type of APP generally presents side A to Apple's reviewers during the review, and then presents side B to the user after the review is over; this is generally a kind of app that appears to avoid Apple's strict and strict review restrictions. Industry; this kind of application is very common, regardless of whether it is a small workshop APP or an APP of a large factory, basically they will do it; for example, in order to avoid Apple’s 30% commission payment, the virtual recharge entrance is hidden during the review, and the online recharge will be done after the successful launch Develop recharge portal, etc.;
Vest audit risk (Apple audit 4.3)
Apple review is roughly divided into three parts, pre-review, machine review and manual review. After the package is uploaded, the first thing to enter is the pre-examination, and the API will be scanned. If there is no problem, it will appear in iTC, and then it can be submitted to Waiting. In the early stage of the review, that is, the Waiting For Review (waiting for review) stage is generally a machine review. If the machine review fails, it will be directly rejected. After passing, it will enter the manual review, that is, the In Review (review) stage. This stage mainly looks at the metadata of the App, such as title, description, screenshots, etc., and detects the function usage of the App. , the commonly encountered ipv6 is also detected here.
4.3 Functions or applications appear repeatedly in the App Store, including products of the same type with consistent functions, and rejection responses caused by uploading vests or subpackages. The following solutions hope to help you deal with such problems!
发件人 Apple
4. 3 Design: Spam
Guideline 4.3 - Design - Spam
Your app duplicates the content and functionality of apps submitted to the App Store, which is considered a form of spam.
Apps that simply duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps.(机器审核)
发件人 Apple
4. 3 Design: Spam
Guideline 4.3 - Design - Spam
We found that your app provides the same feature set as other apps submitted to the App Store, which is not appropriate to theApp Store.(人工审核)
solution
As long as the difference between the projects is handled, the main points are generally as follows:
a. UI differentiation (material, UI tone, functional interface, etc.)
b. Differentiation of developer information (different accounts, application names, titles, icons, package names, keywords, project names, packaged computer IP addresses, project descriptions, product promotions, etc.)
c. Functional differentiation
d. Metadata differentiation (app price, release region, product classification, reply to Apple product design concept, etc.)
e. Code differentiation (project name, folder name, class name, function name, static resource name, keyword, prefix, suffix, resource Md5, etc.)
For details, see my other article "Summary of iOS Vest Packages on the Shelf"
What needs to be done for specific project differentiation can also see this "What should be done for iOS code obfuscation" , which introduces in detail which aspects of a project should be differentiated;
Summarize
In order to maintain a good Apple ecology, the vest package is definitely not in line with Apple's specifications, but in order for our APP to survive better and for our own dreams, we have to do everything we can!
Finally, I recommend an iOS code obfuscation tool to you, which can help you quickly confuse and differentiate your iOS code, and greatly save your development time. "iOS Code Obfuscation Software" is as follows:
"iOS Code Obfuscation Software"
gives a little star if you think it is easy to use!