The 2016 WWDC Developer Conference is approaching, and the App Store under the control of Phil Schiller has been making frequent moves. On June 9, it announced adjustments to the developer tiering model and provided search ads to developers. In addition, the application review speed has been accelerated, the review requirements are high, and the approval rate is low, especially for vest products, which are more difficult to pass the review, bringing many difficulties to the CPs that promote the "vest group strategy". The common reasons for the rejection of vests are as follows: Question: There are similar apps in the app store , and you need to provide relevant information to prove the differentiation of the newly uploaded app. Apple's move is aimed at controlling the chaos of vests at the source. Although Apple's review is a manual operation, it is difficult to achieve absolute control due to different people and circumstances. In particular, there is basically no control over vests. Many individual developers use the vest group strategy to make considerable profits. Apple Policy Interpretation Apple uses binary codes to determine uniqueness and package names to distinguish products. Duplicate binary codes are not allowed online. The following four situations are interpreted: ① The package name is the same, but the binary code is different, which Apple considers as an update; ②The package names are different, but the binary codes are the same, so the review cannot pass; ③The package name is different, the binary code is different, which is usually called a vest, and the review may pass; ④The package name is the same, the binary code is the same, and it has no meaning. In addition to the requirements for binary codes, since May, the audit has been very strict on single-function products or similar products. It can basically be understood that products with a single function or similar products are not allowed to go online. The tightening of control has resulted in a low approval rate for vests in recent times. In the face of this industry phenomenon, Mr. Wen has the following suggestions for a breakthrough. When an app is submitted for review, Apple reviewers will be provided with a demonstration account with a username and password for a full access account so that they can experience the product. Binary codes must be different The binary code is used to determine uniqueness. A slight adjustment or partial change to the code will regenerate a new binary code, which is the prerequisite for operating the vest. If the main App has rich functions, you can use a fake App to separate some of the functions. This method has a high approval rate, but the cost of technical investment is also relatively expensive. It is suitable for large products and large companies. Product simplification (closing some functions or pages) If the operation of independent functions is complicated, you can choose to simplify the operation of the product. Specifically: ① Delete some interfaces/functions in the main App; ② Some interface/function setting switch buttons in the main App are closed during the review period and opened after the review is passed. This operation will not have any impact on the user experience. Common third-party payment interfaces generally work this way. Modify the first page after the App is launched to ensure that the vest is different from the first page of the main App, so as to confuse Apple reviewers from the initial visual perspective. Complete set of UI changes A complete set of UI/art changes, suitable for games . Vest A: First page (default page) Vest B: First page (default page) Interpretation and analysis: The first page (default page) is the page that auditors often pay attention to, and can be simply adjusted from the functional layout and UI of the page. Change the default column Vest A: The first column is used as the default column Vest B: The second column is used as the default column Interpretation and analysis: By adjusting the default columns of different vests and simply adjusting the binary code without making major changes to the main App, the duplication problem can be solved. Skin-changing type (suitable for games) Vest A: A female-themed elimination game Vest B: A level-breaking game Interpretation and analysis: For game products, it is not suitable to use the commonly used professional version/Plus version/paid version, etc. It is more about changing a set of art based on the original code logic, which is the commonly used skinning. Your APP |