关于Apple Review的Guideline 4.3 - Design的分析与建议

Posted 2022-01-26 Drunkard_001

Guideline 4.3 - Design 几乎是所有开发者或者运营团队的噩梦，一旦百被沾上就相当于被判了死刑，为什么这么说呢？我们先来看一下4.3邮件的原内容吧：

发件人 Apple

Guideline 4.3 - Design

We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam.

The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved.

Next Steps

- Review the Design section of the App Store Review Guidelines.
- Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program.
- Once your app is fully compliant, resubmit your app for review.

When creating multiple apps where content is the only varying element, you should offer a single app to deliver differing content to customers. If you would like to offer this content for purchase, it would be appropriate to use the in-app purchase API.

Alternatively, you may consider creating a web app, which looks and behaves similar to a native app when the customer adds it to their Home screen. Refer to the Configuring Web Applications section of the Safari Web Content Guide for more information.

Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the Terms & Conditions of the Apple Developer Program to learn more about our policies regarding termination.

译文我就不粘了，基本上有两点最为重要，也最为直接，首先是被拒了，其次是审核被延时了！ 

被拒或许并不可怕，但是延时审核这就有点瘆人了，虽说首次延时基本上没什么影响，二次延时也就三天、三次延时一个星期、四次审核是半个月......但是既然开始延时了就很难跳出这个魔咒，尤其是关于4.3协议。

下边首先我先列举一下可能遇到延时审核的情况：

• 苹果提出需要修改的问题，而开发者并未处理的情况会遇到延时审核，但是这种延时审核不会直接出现在开发者的被拒邮件中，而是在多次拒绝而屡次不改之后会上。这也是一种警告，我（Apple Review）多次提醒你改，而你不改，那我（Apple Review）就要对你实施惩罚了；
• 出现4.3，即被判定为马甲包等垃圾APP了，这种情况就最直接，第一次拒绝邮件就提示将被延时审核；

接下来就是分析4.3的原因了，首先是APP的源码与别的已上线的APP的重合率极高，或者是APP的名字、效果、甚至是开发者的信息与别的APP相对应的材料有极大的相似之处，满足这些条件中的任一点都可能会被判定为马甲包。 

解决办法：

首先是遇到4.3后，不要盲目修改并再次提审，这样不但没有任何作用，而且还会增加延时的时长，要做的是要认证、客观地分析出原因；

其次是要根据原因有针对性的提出合理解决方案，可以先尽可能多设计几条备用方案，然后选择最合理、最有效的方案；

再者，如果真的可能是被冤枉的，也是有可能误判的，本人这种情况就是属于误判的，这种情况最直接有效的办法就是上诉，直接向App Review Board上诉并简述理由。上诉的等待时间可能比较漫长，但也没有办法

如果你们有更好的建议，欢迎大家谈论