1. Avoid crash
If the application crashes, authentication fails. Therefore, before submitting the application, you must determine whether the interface and function crash.
2. the UI should be correctly displayed when the background of the topic is deep or light
The background of the system subject is deep by default. If it is light, the background and text color will change accordingly. Therefore, you must consider this issue when designing and developing apps, otherwise, authentication fails.
Solution: add style resources (global) to controls such as grid and textblock, such as the foreground color of text and the background color of grid. In this way, when the background of a topic is deep or light, text and background can be correctly and clearly displayed. It is best to use multiple skin schemes. Each skin scheme has its own configuration better.
3. The target language is consistent with the language on the interface.
"Neutral language" must be set in the project attribute and used as the main language. It must be the same for a single language, and the main language must be used in multiple languages; otherwise, the authentication will fail. Previously, this item was set to "Chinese", which always failed to be uploaded to the app. It was resolved as the store was opened to the Chinese region.
4. Progress and prompt
When an app request or an operation is executed, a progress bar should be added. If there is no response for a long time or the response fails, a corresponding prompt should be displayed, and the prompt content should not be the same. Otherwise, the authentication will fail.
V. flight mode requirements
Setting the mobile phone to the flight mode, that is, disabling WiFi, mobile phone and other networks, will be able to meet the above requirements, for example, will not crash, there will be a prompt when the network is disconnected, and so on.
Vi. Others
The entry to the application must be completed within 5 seconds;
Technical support and description in applications;
If you use GPS, you must prompt the user and have a corresponding interface to cancel