What do I need to check before launching a mobile application?
Let’s say you worked side by side with programmers for a long time, developing your application. Finally, everything is ready and the stage of putting the application comes. Of course, the developing company on its side is testing the application, however you should also do some testing because they could overlook some errors.
Therefore, we have compiled a list of the main errors that may occur so that you know what to look for before the release of the application.
1. Problems with geolocation
If your application uses the geolocation function, you need to check how it behaves in several situations:
A) The user is in a room where there is unstable connection to the Internet or he disconnected the mobile Internet or Wi-Fi, therefore the application will not be able to determine the user’s coordinates.
The application should: show the user’s last specified location or some default point.
How to check it: run the application when the airplane is on or turn off the Internet.
B) The user has denied the application access to the geolocation
The application should: show a message that location has been disabled and propose to allow access by going to the settings.
How to check it: open the settings and prevent the application from accessing the geodata, after running the application.
2. Internet Connection problems
A) While the screen was loading, the Internet has gone.
The application should: show the user a message which will be show that there is no connection to the Internet. If some of the data has already been downloaded, then the application should leave it on the screen and display information that there are problems with the Internet.
How to check it: run the application, go to the section to open which you want to download data from the server, and disconnect the Internet during the download process.
B) The Internet is connected after opening a new screen in the application
The application should: periodically check the presence of the Internet, in case it has appeared – continue to download the remaining data.
How to check it: run the application, start downloading data, enable airplane mode, and then turn off.
3. Issues with the server
The server can return various types of errors, in this case the user sees incomprehensible messages to them, for example, “500 Internal server error” or “401 Token is invalid” and does not understand what to do next.
The application should: show the user a message that will tell them what actions he should take next, for example, contact technical support or update the page. A blank screen may also appear.
How to check it: ask your back-end developer to emulate those, or other situations in which the application will lead to an error.
4. Content development
The text on the application screen is very important for the user. If the user encounters uninformative prompts working with the application or incomprehensible names of buttons, he may stop using the software.
How to check it: go to each screen of the application and check the texts for grammatical, spelling errors, and also on the clarity of the texts.
5. Confirmations for important actions
The user commits an action that can not be reversed, for example, deleting a message, logging out of an account, etc.
The application should: show the user a message, asking them to confirm their actions.