So why is the supervision of Apple's audit team getting stricter and stricter from 20 18?
I am deeply impressed that there are two important time periods, which make the supervision of ios shelves stricter. One is to call all legal persons with cash loans to Beijing for a meeting in February 65438+February 15. When it comes to loan interest rate and compliance, the main requirements are as follows: First, the comprehensive loan interest rate shall not exceed 36%; Second, related expenses cannot be deducted before lending; Third, all loan companies must comply with state approval.
Because of this clause, many wealth management apps were removed from the shelves that day. The problem reported at that time was 5.2. 1.
At the second time point, 65438+1October 1 1, a large-scale error report 3.2. 1 was started, requiring the app to submit a financial license and icp for filing. 95% companies in the market have no financial license. There were many ways of packaging in the market before, but the degree of supervision on the shelves in recent months has eliminated all the previous rough games.
Let's take a closer look at the problems encountered in recent months: the first thing exposed since June 5438+February 5.2. 1. The main clause of this question is that the product must have a qualified developer account, and the content of your product must be consistent with the business scope of your developer account.
Then there is the problem of 3.2. 1, which was widely exposed in June 1. 3.2. The problem of1is actually a qualification problem. Their operation method is actually similar to 5.2. 1, but it is really much more difficult than 5.2. 1.
Because he needs us to submit the financial license and icp of our developer's account, some companies with icp records can get it, but few companies in the market will have financial licenses. Because domestic developers have reacted too much, Apple has now given in, so it has relaxed a little. The author's bookshelves have a bank depository agreement and can also be put on shelves.
18 years, we met the Year of the Dog 2. 1 gift package. 2. The problem of1will encounter at most seven clauses, not that our products must encounter these problems, but because Apple's auditors think that our products may have problems, they will first give us a rejected gift package and let us check it ourselves. This clause will waste a lot of time and cost. Because you need to check the content of your product according to these terms, 2. 1 terms mainly include excessive concealment during product audit, third-party payment, financial product qualification, duplicate vest bag and so on.
These are the rejection clauses we will encounter recently. At this stage, clauses 3.2. 1 and 2. 1 are generally encountered. Usually I divide the shelf of 105 into two parts. The first part is the technical aspects you need to solve; The second part is qualification. At this stage, only you have to solve these two parts. Only in this way can you have a stable chance to get the parcel.
Let's talk about the technical level first. First of all, I want to share with you the review mechanism of ios. IOS is divided into manual audit and computer audit.
There will also be differences between China and the United States in people's evaluation. They mainly check whether the relevant qualification of your account matches the certificate uploaded by your attachment, and see if there is any third-party company information in the company information inside the product, and whether the app content belongs to your business scope. Computer censorship mainly looks at the code to see if there are any errors in the metadata. Whether the overall source code is the same as the App of the same account is more than 70%. Let me briefly mention the problem of 4.3 here, that is, the source code of vest package and main package is duplicated, which leads to errors. 4.3. This requires technology to modify the source code, and the corresponding UI and subtitles should also be adjusted.
Here, I want to focus on human trials, because there are many uncertainties in manual trials. If you are lucky, you may get nothing, but if it is really strict, many apps will get stuck in this human trial stage. Next, I will share some matters that should be paid attention to when the manual audit team examines and increases the product content of the probability base of the package.
We'd better hide all the company information of the first Lanfanghui in our app, at least not the word company.
Please pay special attention to reflect your company information in the registration agreement and your product name in the home page. This is to match your qualifications. We also need to add an "About Us" module. The name and copyright of the app that needs to be declared inside are similar to the picture below. At the same time, the App needs to add the contact information of customer service, which are relatively small details and easy to operate, but these are really the key points that auditors should look at when reviewing ios, because they think these contents can reflect the ownership of products. You can see the template that we ask customers to provide in the figure below.
Apple is very strict about payment. Many products will be rejected if there is a third-party payment channel inside. Therefore, there can be no information that there is a third-party payment channel inside the product. You can make a switch and turn it off after the audit. Let the technology work.
Gold touch products will definitely make vest bags to expand exposure. If you put on a vest bag, you need to do more surgery.
Simply operate the main subtitle, icon and application information of vest bag, which is different from the main bag to avoid the problem of 4.3. At the source code level, there must be at least 30% difference between the source code of vest package and main package. You can add some confusing codes to the source code, which can improve the probability of passing the computer review.
On the technical level, the methods to improve the shelf rate during the audit are roughly these. Next, let's take a look at several mainstream ways of putting on shelves in the market: appeal, PS, authorization, packing and finding a third party.
Here, I can tell you an unwritten rule. If it fails to be put on the shelves due to qualification problems, the ios auditor will give priority to your product when you put it on the shelves again. However, once you are rejected many times for one reason, Apple will think that this is an evil behavior, which is likely to lead to an indefinite extension of the review, usually 15 days to two months or will be blocked.
Regarding the appeal, I recommend companies with financial licenses to try it. We can write an email about the appeal first. The general content is that our products are in line with our business scope and we also have relevant qualifications. We serve consumers all over the country. I hope the ios team can understand and put you on the shelves. This method has a certain probability of being successfully put on the shelves in the early stage of 17, because at that stage, ios still has a great chance of being put on the shelves by luck, and your complaint email may directly solve this problem. What needs to be noted here is that the probability of getting lucky is getting smaller and smaller. You can try it, but you'd better pay attention to not more than three complaint mailboxes, because if there are too many, the ios audit team will think that you are intentional, probably.
Note: Many companies are actually doing qualifications, such as "ios development sub-team". If you have a financial developer account, but lack a financial license, you can try it. You can find a qualification of another company online, then go to Ps and change all the information in the qualification into your own company. There will be a certain chance. It should be noted that PS technology must be professional.
Because the manual audit team of ios is divided into China team and American team, it is done according to the random audit of the two teams. If it is assigned to the American team, it will be easier to get on the shelves. For example, a wealth management company uploaded a financial license because it did not have a financial license. The ios audit team will only look at whether the information on the financial license matches the company information of your developer account, and will not go to the CBRC to investigate whether your company has this financial license. If the audit team approves, your bag will pass. This method can now be successfully put on the shelves with a certain probability. What we need to pay attention to is that the content and logic of the product should match your qualification when the qualification is fully prepared. Because the success of the shelf is not only the qualification, but also the product itself. I mentioned the things that need to be paid attention to in terms of products.
The previous practice on the shell problem was relatively simple and rude. Simply put, it is to make a shell of information, a calculator, a notebook, or maybe just a submitted personal account. There is little chance that this method will be successfully put on the shelves now. Our main practice now is to be a bright eye in the same industry and then do it with qualifications. Give a typical example of borrowing supermarket products, because this kind of app involves many products of other companies, and it is difficult to pass if it is put on the shelves with local products. Now the mainstream practice in the market is to make a shell, of course, the content of the shell should match your developer account and qualification. Usually, the way to give loans to supermarkets is to pretend to be cash loans for trial use, which can avoid post-audit.
It should be noted here that the operation of the shell is complicated. One is to do ab surface, and the other is to do detection switch. If the app does not have a ready-made shell, the time period of this method is too long.
The authorized gameplay was actually released in June+10, 5438. At that time, the error was reported as 3.2. 1, and then the ios team sent an approval, which mentioned the specific method of authorization. Generally speaking, product companies are allowed to be affiliated with companies with complete qualification licenses in the same industry, or some large state-owned companies are authorized: here, everyone needs to pay attention to the way of authorization, which means that you are affiliated with qualified companies. It is stated in the approval that once you do it in an authorized way, your product needs to be authorized by the authorized company, and your developer account must be an authorized company. Many people use this method to go to 5.2. 1 before approval, but now it is clearly stated that your developer account must be an authorized company, which needs everyone's attention.
The last one is to find a third-party channel, which belongs to the original package qualification. There are many channels in the market now, and our approach will be more specific, that is, using the developer account of the bank, because at this stage, only two accounts are more reliable, namely the developer account of the bank and the qualification account of small commodities.
Their main approach is to use these qualified accounts to upload them for you, and then add their financial licenses and banks to the attachment! ICP filing. All company information in your product will be changed to their company. After the package is approved successfully, they will change all company information to your company while waiting for the developer to release it, and then send it back to you after the package is released online.
This practice is more reliable and time-saving at this stage without relevant qualifications. Everyone should pay attention to the choice of channels. At this stage, there may not be as many channels as before, but there are also a certain number. As far as I know, there are still many channels in the market that are relatively simple and rude. The following are the packages of different industries and different time periods when I recently helped the company to tighten supervision from 65438+February 15.