Listen to this blog
Mobile usability goes a long way in enhancing end-user app acceptance. But usability starts with the user, and users differ in terms of knowledge, interests, goals, and so on. This article discusses some core usability characteristics that matter to customers, and how test engineers can understand and achieve them.
Smartphone applications have been booming since the advent of iPhones and Android phones. There are more than 2,200,000 iOS and 2,600,000 android apps available as on Feb 2019. While a few apps go viral and get downloaded thousands of times, many do not generate even a few users. Apps can flop because the content is not interesting, but there’s another prevalent (and avoidable) reason for failure: because they are too difficult to be used on a mobile device.
Usability starts with the user, and users differ in terms of knowledge, interests, goals, and so on. As test engineers, we must ask questions about the app users, their mobile tasks, the environments they work in, the types of devices they use, and how tech-savvy they are. Clearly, usability is an important attribute to account for. This article discusses some core usability characteristics that matter to customers, and how test engineers can understand and achieve them.
The type of users and how they will interact with your product have to be taken into consideration for each app.
As Software test engineers, we must understand that mobile applications differ from traditional desktop and web-based apps in a number of ways. Correspondingly, the test focus areas also differ. Many areas require special attention, but let’s restrict our discussion to the below five elements:
- Range of devices
- Data entry methods
Context can be defined as the totality of a consumer’s mobile experience. This includes the situational, attitudinal, and preferential habits of the user. Mobile context is constrained by factors such as screen sizes, users’ fingers, location, posture, and network connectivity. Mobile context also includes various capabilities like automatic orientation detection, dynamic location detection, the compass, and accelerometers. Let us take the example of a mobile context with respect to location. Say you ask your application to display a list of Chinese restaurants. A good application will locate your geographical positioning and give you a list of nearby places, along with reviews of other users in the same geography, and specific eating options depending on the time of the day. Results should be targeted, contextual, and valuable.
Another focus area is the various supported device models for the application. An application may work fine on one device but then crash or fail on another. For example, Zomato is a restaurant guide app with great features and UI. However, the app crashes on Android 4.3. A Software tester has a prime responsibility in verifying these nuances, keeping an optimized test matrix in mind. Next up are data entry methods. We understand that mobile devices, especially smart devices, support a lot of data entry methods, including a stylus, touch, voice recognition, gestures, and so on. Test engineers must ensure that the application responds well to each potential entry point.
Multimodality combines voice and touch as input and displays visual screens and spoken responses as output—for example, a navigation application that provides spoken responses as audio aids for the driver and visual displays as directions. Testers need to examine input and output to be sure both audio and visual components function properly.
Taking into account the many variables that need to be considered from the mobile usability angle, Codoid recommends the following practices which come in handy when creating a testing strategy.
Start early. Testing should begin at the requirements analysis phase. Most usability issues are related to design, and if you can catch them upfront when you review the designs as wireframes or mockups, it will mean less trouble down the road.
Work iteratively. Testing regularly makes it a lot easier to support small incremental changes throughout the lifespan of the application. Usability should be considered in all stages throughout the development lifecycle because every change in design and every interaction with the product prototype has an impact.
Adopt usability in conjunction with other testing types. You need to think about combinatorial elements in usability testing. For example, functionality and usability can cause a conflict; a functional designer might want to make the product feature-rich, whereas the usability engineer’s focus is to keep the application simple and intuitive. Usability studies need to be performed collaboratively, keeping in mind the performance, security, localization, functionality, and accessibility aspects of the application.
Check in after launch. Usability studies should continue after the product launches. Checking the app store, studying the ratings and reviews by users, and analyzing competition are all valuable practices in enhancing the usability of the application.
Use productivity tools. Usability testing for mobile apps is still largely done manually, and there is room to use productivity tools to make the effort more effective. There are many handy productivity tools available for a variety of usability factors, including testing the application across multiple devices for optimum screen resolution. At the end you get a report with screenshots for each selected device, indicating the screen resolution effectiveness. Another tool creates heat maps to help find areas where users’ focus lingers the most. These visible indicators help realign UI if needed. And recording software shows where participants tapped and scrolled and how they navigated from page to page, helping gauge the level of workflow intuitiveness.
Go to the source to discover user expectations. Reading about usability is one thing, but interacting with people who have special accessibility needs is invaluable. It opens your eyes to their requirements and reveals some big coverage gaps you may have.
Talk like a human, not a programmer. Emotional intelligence factors are gaining attention. When you talk about end-users, don’t talk about them as entities, but as real people with emotions. If you want to account for an emotional angle in your testing strategy and you don’t know where to start, usability is a good place to consider.
Testing, testing, testing. While it is good to have a well-etched strategy, it’s better to set aside time for exploratory testing. Most often, usability issues surface when you try operating your product in an exploratory way. Invite groups to come to test your app and think of creative ways to maximize test coverage.
In essence, mobile usability goes a long way in enhancing end-user app acceptance. This industry is still evolving by the day, but the practices discussed above will give you a head start in building usable mobile applications.