What is a vest bag

Vest bag is generally a duplicate or clone of the main APP, or an APP wearing the vest. If the vest is removed, the APP will show another style, which is often said to be the AB APP.

1. Vest bag of the clone or doppelganger of the main APP

Say the first kind is the first main APP erection or cloning, now a company usually has a main products of its own, but also to do something similar to the APP castration version of the APP, project code was fully reuse basically, the APP application name, subtitle, icon, screenshots, package name, keyword and developer account is different from the main APP, Everything else is pretty much the same, like the following:Why do you do that? What good would that do?

A. Avoid market or policy risks

It is used to brush app volume, rush list, brush words, brush hot search, evade account restrictions, prevent takedown emergency measures, competitive products competition, etc., to resist the main package risk.

B. Grab a limited position in the app market

Keyword search results placeholder, list placeholder, cover more keywords, etc.

C, guide

The vest package itself can obtain new users, and it can guide users to download the main App by sharing background information with the main App, popup or push.

D. Test the effect of large-scale revision and reduce risks

The advantage of vest bag is a large range of revision can be online verification effect, once caused adverse effects will not cause a great loss. If the test results are good, corresponding functional iterations can be carried out on the main App.

2, AB side APP type vest bag

In this type of APP, side A is presented to Apple’s reviewers during the review process, and side B is presented to users after the review. This is an industry that has generally emerged to circumvent Apple’s strict censorship restrictions; This kind of application is very common, whether small workshop APP or big factory APP, basically do; For example, in order to avoid Apple’s 30% royalty payment, the virtual recharge entrance is hidden during the audit, and the recharge entrance is developed after the online success, etc.;

Audit risk of vest bag (Apple audit 4.3)

Apple audit is generally divided into three parts, pre-audit, machine audit and manual audit. After the package is uploaded, it will enter the pre-review first, and it will be scanned API, etc. If there is no problem, it will appear in iTC, and then it can be submitted to Waiting. In the early stage of an audit, Waiting For Review, there is usually a machine audit. If the machine does not pass the examination, it will be directly rejected. After passing the examination, it will enter the manual Review stage, that is, In Review stage, this stage mainly looks at the metadata of App, such as title, description, screenshots, etc., and detect the use of App functions. Ipv6 is also detected here.

4.3 Functions or applications repeatedly appear in the App Store, including consistent functions of products of the same type, and rejected responses caused by uploading vests or subcontractors. The following solutions hope to help you deal with such problems!

The sender Apple4. 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 forThe end user, and reduce the ability of developers to market their apps4. 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.Copy the code

The solution

As long as the difference of the project is handled, the following points are generally the main ones:

A. UI differentiation (materials, UI colors, functional interfaces, etc.)

B. Differentiation of developer information (different accounts, application name, title, icon, package name, keywords, project name, IP address of packaging computer, project description, product promotion, etc.)

C. Functional differentiation

D. Differentiation of metadata (app price, release region, product category, 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.)

The details can be seen in my other article “summary of iOS Vest package launch”.

What needs to be done for specific project differentiation can also be seen in the iOS Code confusion should be done, which details a project should be differentiated from what aspects;

conclusion

In order to maintain a good Apple ecology, waistcoat bag is certainly not in line with the Apple standard, but in order to make our APP can better survive, but also for their dreams, we have to do it! Finally, I recommend an iOS code obfuscation tool, which can help you quickly obfuscate and differentiate your iOS code, greatly saving your development time.IOS Code Obfuscation SoftwareAs follows:

IOS Code obfuscation software feels good to give a little star!