4.3 the Design Guideline

There are two common responses:

The first:

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.
Copy the code

The second:

Guideline 4.3 - Design

This app duplicates the content and functionality of other apps submitted by you or another developer 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.

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.
Copy the code

Although both are 4.3 rejected, the above two responses have different meanings.

Combined with some online information, I think 4.3 generally falls into two situations

4.3 at the functional design level (e.g., response 1 above)

  1. Through some research on the company’s project audit, 4.3 of the general function design level can pass the machine audit, and the preliminary judgment has little relationship with the code
  2. Design can try some bold color matching, and try some different control layout (after the first version of the review, can slowly change back)
  3. In terms of functions, try to add some characteristic functions, and can explain the situation when replying to the review. The general idea is that our project has some core functions, which are different from other products
  4. UI new design, icon new design, background application screenshot replacement
  5. Use a new name

4.3 code repetition level (e.g., second response above)

  1. Code duplication problem, generally will be rejected in the machine review, you can check the time interval to determine whether the machine review. (Sending time of approved and rejected emails)
  2. 4.3 code duplication level, generally need to consider changing the development account submission.
  3. Folder name modification, class name modification, prefix modification, method name modification.
  4. Code obfuscation, adding junk code (usually with code obfuscation tools)
  5. New development computer packaging, new development account, new IP upload
  6. Change the image resources in the project as much as possible, or modify the hash value (there are tools online)

Other:

  1. Don’t put apps with similar functions in the same development account
  2. Try to avoid packing the same computer
  3. The IP for uploading should be fixed as much as possible, such as which App corresponds to which IP

Finally: Some of the above processing methods are practical, some are conjecture. Some friends also know other methods, welcome to communicate.