Apple review is still tightening
Recently, I have a friend who is a developer. The product he developed is very formal, and there is only one account and two or three normal products. Make him forget about food and drink. But because he is indeed "upright", I suggested that he wait for 7 days to urge the progress. Sure enough, he received the review approval email from Apple very soon.
Although it was a small incident without any danger, it feels as heavy as Mount Tai when this kind of thing falls on every developer. As unscrupulous package developers who disrupt the ecology and Apple's battle of wits and courage escalate, under the strict prevention policy of Apple's review, there are quite a few innocent developers who have been "accidentally injured".
The joys and sorrows of developers are not connected
A few "new" friends who have just joined the ranks of Apple's individual developers, after reading some of my articles, dismissed me as "exaggerating", the reason is that he registered a developer account and submitted the first version It passed, and there were no problems in the next few updates. I felt that the wailing everywhere on the Internet was just eyeballs.
In fact, this is very normal, which means that one is that the account is clean, and the other is that the product is legitimate, and there are no major problems. In addition, I abide by the regulations, and I have not stepped on bad luck and accidentally injured. It is really easy to pass the package.
In fact, those who are really complaining are those friends who clearly stepped on the minefield but didn't know it was a minefield, including but not limited to:
- Buy a developer account from Taobao to publish products.
- I took a second-hand laptop from Xianyu as a development and release machine, but unfortunately that one is an associated machine.
- In a small company, I was instructed by my boss to register an account with my own identity, and I want to register another one with my own identity after leaving the company.
- Suffering from the lack of improvement in natural new additions, I saw a hot word on the Internet that many people searched for, and itched to put it together in the subtitle of the product
- Etc., etc
There are still many people who "take advantage of loopholes", but I sincerely do not recommend it
Recently, the goat has caught fire, so various vests are ready to follow suit. Among them, there are "sheep baa sheep", "sheep baa sheep", "sheep baa sheep" and so on. The pot was full, and after a while, it was blocked by Apple's relationship.
For a small number of followers, they are the real big winners. At least one to half a month before the account is removed from the shelves, they get more than 100,000 new additions every day, and the advertising revenue alone may make enough money.
But there are always a few winners. For most developers, the ending must be to lose time and send accounts.
The business of "taking advantage of loopholes" can only be done by "professional things for professional people". In fact, most developers didn't think about taking "exploiting loopholes" as a profession, they just wanted to make a temporary profit, and they paid a heavy price as a result.
Definitely be careful not to be hurt by "ex and teammates"
For example:
Developer A’s account has been blocked recently. All the products he developed are legitimate, and the account was registered by himself. How did he get blocked? Through understanding, it turned out that his previous company was a company specializing in gray products. He himself was responsible for development and subcontracting. Later, he resigned, and the company's notebooks were sold to him at a depreciated price.
Another example:
Developer B is a small boss of a start-up company. Recently, a personal account registered by the company is about to be blocked (14 days). After communicating with Apple many times, the feedback given by Apple is that they have found evidence to prove their account It was related to a group of blocked developer accounts. Xiao B was puzzled. Later, he finally found out the reason. Programmers from their company’s account company can log in, and each programmer is also assigned an Apple notebook. The programmers did personal development and outsourcing in private, and they made a lot of vest packages and were finally banned, so (presumably) the company's developer account was also linked.
Unforgiven payment problem
For payment issues, Apple's audit has always been treated as a high-voltage line. Once it is discovered that Apple Pay has been bypassed to avoid Apple taxes, the account will be banned directly.
Many "smart" developers have already learned how to deal with this, that is, they hide the payment function in the version that is put on the shelf for review, and then open it after it is put on the shelf. This trick is also the object of Apple's strict defense. Once it is found that the payment has been opened after the review, it is basically banned.
And if the developer’s code contains text similar to alipay, no matter whether it is intentional or unintentional, during the review process, they will encounter the special treatment of “trying to hide the payment function”, and the self-inspection will be rejected at least, and the account will be banned at worst.
Check the developer email every day
Whether it is in the field of apps or games, the issue of copyright infringement is always an unavoidable topic, and there are even many "copyright hooligans" who specialize in touching porcelain. Competitors also like to use this routine to do things.
When it comes to infringement disputes between developers, Apple generally adopts a "throwing the ball" attitude. For infringement complaint emails, they are first forwarded to the developers by email, allowing them to argue with each other. Apple will request the reply email to be forwarded. To Apple, he acts as a "spectator" before taking necessary measures to deal with it.
And if the developer on one side fails to reply to the email in time, Apple will default to the developer on the other side as "winning".
Many "Pengci" competitors have taken advantage of this, complaining everywhere with infringement statements that have not yet formed a factual basis, and even "followers forced the official to death". If the developer does not form the habit of reading emails, or if the emails are just thrown into the garbage category, then it is easy to stumble.
Learn to use the "audit information area" as a workplace
When developers submit new packages or versions, it is easy to directly leave the remarks area of "App Review Information" blank.
In my experience, this area has a surprising effect on improving the review efficiency and pass rate. If it is an update to modify bugs, you can just write "fix xxx bug" in the update list. However, you can communicate with the reviewers in the remarks area, specifying what problems are fixed and what the changes in the new version mean to users. Such sincere changes can easily win quick approval.
The other is the function update. Write clearly what functions are added and where they can be triggered. This approach improves the efficiency of the reviewers' work, and it is more professional rather than foolish. This can greatly avoid the possibility of being questioned.
read more
How Developers Correctly Handle Apple App Infringement Disputes
Apple Developer Anti-Association Checklist for Opening New Accounts
Talk about what developers can do in the face of Apple's 14-day ban