Guide to listing on Android App Market!

The company's product line expanded and multiple applications needed to be put on the market, and I unfortunately took on this headache-inducing burden.

You should know that in recent years, the policies of the Android application market have changed frequently, especially with regard to user privacy protection. Many old practices have been excluded, and different markets are independent of each other. The road to listing is long and difficult, with pitfalls at every step.

Even if the market abuses me thousands of times, I have no regrets and love it every day.

I would like to use this article to record the pitfalls I have encountered, and I hope it will be helpful to my friends so that they can work less overtime and go home earlier.

Based on the current market share of mobile phone brands, the following content mainly revolves around the four major ones: Huawei, VIVO, OPPO, and Xiaomi. Other application markets are not within the scope of discussion for the time being. (Yes, Meizu has no human rights) The records are mainly divided into two parts: inside and outside the application.

1. Application of external materials

First, let's take a look at the following materials that need to be prepared in addition to the application:

1. Apply the logo

Based on the requirements of different application markets, three sizes of 200*200, 216*216, and 512*512 are required, and the size of the 512-size image must be within 50KB.

You can ask the UI girl for help with image compression, or just find a tool website.

2. Screenshot size

Based on the requirements of different application markets, the following three sizes need to be prepared, and the size of a single image must be within 1M.

3. ICP filing

It would be best if you have a screenshot of the product-related ICP filing. If you don’t have the company’s ICP filing, that’s fine too (the company’s filing was rejected once, and the rules are a little confusing).

4. Business license

5. Legal person ID card

A separate double-sided photo of the ID card is required; a double-sided photo of the person holding the ID card is required.

6. Mobile phone number and email address

Used to register an app market account and receive listing information.

Green Certification:

• Some markets require that templates can be downloaded on the application submission page;
• The main thing is to fill in the page location of the permission call, the SDK name used, etc. You can ask your development classmates to help complete it.

7. Letter of Commitment (Ownership of Application)

Some markets require that you can download a template on the application submission page. This is mainly to prove that the application does belong to your company and requires an official seal.

8. Application Classification

The application category selected on the market submission review page should be consistent with the actual function of the application as much as possible. If it cannot be completely matched, an optional intersection category can be selected. If a map appears in the application, you can select “Map Navigation” etc.

9. Application Introduction

It is recommended to keep it within the range of 50-100 words.

One sentence introduction: It is recommended to keep it within 10-15 words, without punctuation.

Version update notes:

• Some markets have mandatory requirements, and for the first time listing, you can directly write "App on the shelf", which will not affect the review.
• In addition, the application introduction and update instructions must not contain illegal content or other sensitive information, including but not limited to political, gambling, violence, pornography, sexual innuendo, and words not allowed in the Advertising Law, such as (best, first), etc.

10. Test Account

If the application requires login to be used normally, you need to provide a test account and password.

11. Package Name

It is better to ask the developer in advance why the package name is better. If you write the permissions but it is prompted that there are no permissions during the review, you can list the specific location of the permissions in the remarks.

If the app has been claimed by someone else or the market, you need to ask your fellow developers to help claim the signature package (the signature package is provided by each app market).

2. In-app correlation

What remains is that the relevant functions within the app must comply with the requirements of major markets, among which the Huawei market has the most stringent review and the most requirements. To deal with Huawei is almost the same as to deal with other application markets.

1. Clearly display the privacy policy and user agreement to users

• When the APP is launched for the first time, the privacy policy and user agreement must be displayed to the user, and the user must agree before entering the APP;
• The APP registration and login interface clearly states the privacy policy and user agreement to users, and users are required to manually tick the box to agree;
• The application must include a privacy policy and user agreement display entrance.

2. The app does not contain any empty content pages

If some pages need to load data before they can display content, please prepare at least one piece of corresponding data in advance, otherwise there is a chance that the page will be judged as abnormal.

3. All functions are available normally

All functions must be available and function without errors. Not all functions will be tested every time, but if an error is detected, the application will be rejected.

Hidden entrances to undeveloped functions will be rejected even if they are accompanied by text prompts such as "coming soon".

4. Use the official app

The word "test" or "BETA" cannot be used in the APP name or logo, as it will be considered as a beta version.

5. Privacy policy must meet requirements

• The application entity must be the same as the market account company;
• Indicate which permissions were called, where they were used, etc.
• The policy effective date;
• Statement on the use of user information;
• If the privacy policy is not written by a dedicated person such as a legal officer, the best way is to learn from competitors and modify it according to your own content.

6. Account cancellation function

The app must contain an entry for account cancellation and deletion (not account logout). It is sufficient for users to know how to cancel their accounts and there is no need to complete the entire process within the app.

Permission calls must meet the requirements:

• System permissions can only be called after the user agrees;
• It can be called only when the corresponding function is used, and all permissions cannot be called at startup;
• Once the user disables the permission, the pop-up should not appear again. If the business really needs some processes, you can use toast pop-up windows to inform users, and you cannot directly call the system permission application;
• When users register, they must be able to enter the application even if they deny some permissions such as photography and photo albums. If the business is not aware, the registration process needs to be adjusted.

The actual app icon must be consistent with the icon submitted to the app market for review.

Qualifications related to communication functions:

The chat module must supplement the "Safety Assessment Report" with the official seal, and the chat module must provide an open, transparent and accessible reporting function.

These are roughly the pitfalls I have encountered so far. I hope you all have fun.

Author: Cat No

Source: Dark Cuisine Restaurant