Sorting out issues with putting iOS vest bags on the shelves

1. What is a vest bag?

In fact, everyone knows this problem. In terminology, it usually refers to generating multiple application versions suitable for different situations based on the same code by modifying configurations, resource files, etc. This concept is similar to "channel package" or "multi-channel packaging" in Android applications.

Or, to put it simply, it is to put a shell on the existing app. The app with the new shell can have completely the same functions as the original app, or it can also have some functions.

2. Why make a vest bag?

The first thing we need to make clear is that Apple officially opposes this behavior, because the app store's own resources are limited, and the code consistency of the vest package is a problem. The review 4.3 is basically accurate one at a time. So why even so, many developers still develop vest packages?

Here’s why:

1. Marketing and distribution: Promoting your app in different app markets or channels may require fine-tuning for different audiences, regions, or markets. By developing vest packages, developers can adjust the icon, name, startup screen and other elements of the application according to the requirements of different channels to adapt to the promotion needs of different markets. Of course, on the other hand, it can cover more keywords and have more traffic entrances. Therefore, many vest bags actually serve the main package and guide traffic to the main package .
2. Brand customization: If a developer or company releases an application under multiple brands, each brand may need to have its own unique application version, including brand logo, color theme, etc. Using vest packages, you can easily customize different application versions for each brand while sharing the same code base.
3. Regional adaptation: Users in different regions may have different habits and needs. Developers can adjust application functions, built-in configurations, etc. according to the characteristics of different regions, thereby providing application versions that better meet the needs of local users.
4. Function differentiation: Sometimes, developers may want to provide different functions for different users within the same application. Through the vest package, different function sets can be customized based on the same code to meet the needs of different user groups.
5. Version testing: During the development and testing phases of your app, you may need to create different versions to test different features or improvements. The vest package can help developers quickly create these test versions without having to develop from scratch.
6. Gray area: Currently, some gray products, such as chess and card games and sports, have to make various vests to evade supervision due to increasingly strict platform regulations. The demand in this area is also very strong!

3. The problem of vest bag

As mentioned before, the functions of the vest package are likely to be consistent with the original app, which will cause a big problem: the risk of being removed from the shelves is extremely high . That is the iOS4.3 problem .

Apps put on the App Store will go through two steps: machine review (review of code duplication rate) and human review (review of UI issues). The vest is likely to be stuck in both places. Even after it is put on the shelf, it can easily be removed. This is one of the risks developers have to bear.

4. How to put it on the shelves

At present, there is no 100% way to completely guarantee that it will be put on the shelves. It can only be said that certain methods should be adopted to increase the probability of being put on the shelves. As far as the methods I have collected so far, there are mainly the following:

1. Submissions of the same vest package must be submitted at least one day apart to avoid being seen by the same reviewer.

2. You can generously inform Apple that the vest package is uploaded to test new functional modules of the product, or that the two apps were developed by different departments within the company and target different user groups. ( Vest bag for AB testing ).

3. Regarding the UI part: the new UI needs to be modified based on the original UI, and there must be differences! ! ! Even for reference competitions, distinctions need to be made; the startup image and logo are even more important and must not be the same!

4. For the code part: you can obfuscate and reinforce it, such as modifying the boundID (personal test, this is quite effective).

5. For developer accounts: If possible, try to choose a new developer account for packaging and listing. Because the vest package is definitely not compliant, there is a risk of being killed at any time. If you have other apps under this account, it may be affected, so try to use a new account, safety first.

that's all.