There happen to be many types of software in our lives. We use some of them as a necessity, some of them for fun, and even some of them we use unwillingly. If this software belongs to the mobile environment; we continue to use only the applications which aim productivity. If this application – even if it is Facebook – is pushing us and the waiting period exceeds our limits of tolerance, we leave it instantly. To put it simply, when the application is clicked to be used, the rate of abandonment is found to be 90% if the opening time exceeds 2 seconds. In fact, even the rate of deletion of the application from the phone is rising to 60%.

The user does not distinguish between a small or a large screen. The user is looking for speed and agility and doesn’t want to wait at all in the mobile environment. They say; “Splash screens should be no more than 3 seconds; you’ll lose if they are longer.” Software developers and product managers are looking for simple solutions to this problem such as adding an animation. However, if we are testing our application for usability and good service, in fact, the criteria we are looking for is not very hard to guess. Simplicity is the key since mobile environments do not like complex applications. Therefore, if you need to serve different functions, it will be much more beneficial if you choose to create two different applications rather than one.

Mobile Testing Success

In summary, I would like to emphasize that mobile testing success depends on the product manager, test engineer and application development team, all working smoothly. To make your applications available to your customers; there are things you need to do before you send your application to the market and after you send it. To fully increase the usability of your application; you need to be fully aware of the mobile behavior of your target group. If you can’t make this behavior pattern a part of your test; it will not be used by anyone even if you create the world’s best application regarding functionality.

Being Customer-Centric

User usage patterns are produced in specific test laboratories on a specific audience. In this case, deviations occur due to the distance from the natural environment and the wrong subject factors. These deviations can only be corrected through comments on the product after it has been used in the production environment. As a result, in a situation where 100% correctness is not correct; to provide a stable user experience, you need to do trial and error at certain points and set appropriate targets by going straight from safe harbors following the guidance of the correct reports.

While living in the 90’s, who could have predicted that Nokia would go bankrupt in 2010? Who would believe if someone told the American Ice company that one day Westinghouse’s invention would have them go bankrupt? From these experiences, we can say that you are obliged to follow your customers for a successful mobile test, listen to them to learn deeply about their behaviors and find the right solution for them. At least we have no other proven method to date. We will all see what kind of innovations we will face in the future.

Always focus on producing in the direction your users lead you, rather than a job-oriented production.