In 2010, Apple trademarked the popular phrase, “There’s an app for that” due to the climbing popularity of mobile apps. The mobile app industry continues to see tremendous growth, and now instead of there being an app for “that,” there are likely many apps for “that.” The average U.S. consumer spends around 5 hours a day on mobile devices, and over 90% of that time is spent in apps1. Companies are spending more time, money and resources on mobile apps than ever before.

As new apps strive for share of those 5 hours, first impressions are critical to continued utilization. Market research provides valuable insights and recommendations during various stages of the app development process to support a strong and successful app release.

Mobile App Development Process

Cue Insights provides critical feedback throughout several stages of the mobile app development process, including:

Based on Cue’s extensive experience, we have developed helpful tips to support successful testing of mobile apps.

1. Plan for iterative rounds of research and development. Iterative research during any stage of the process incorporates mini-rounds of user feedback in a short period of time.  App developers benefit greatly from this continuous improvement process.
   • One of the most critical pieces to iterative research is keeping all parties well informed. Developers need to be on track with the research timetable so they can plan their schedules to make the necessary updates to the stimuli prior to the next round of research.
   • If repeat respondents are being used, provide an overview of the entire process during the introduction of the study as better engagement leads to more thought between rounds and higher repeat show rates.
   • When testing multiple iterations of a digital prototype using repeat respondents, ensure respondents have access to previous iterations for comparison, as they don’t always remember what they saw in previous rounds of research.

2. Account for how technical requirements and willingness to download apps impact incidence and sample planning.
   • Consider the technical aspect. In typical market research, your incidence is based on finding the respondents who meet your general criteria. When testing mobile apps, the technical aspect is added to the list of requirements and takes on another level that needs to be accounted for in sample planning. Each mobile app will have its own technical requirements, such as necessary software versions, device compatibility and storage size needed. Some testing programs have requirements of their own such as specific phone models or operating systems. Be sure to clearly state these requirements in the screener. Even if respondents think they meet the technical requirements, they may have technical issues and not be able to download the app.
   • Recognize that not all respondents are open to downloading apps to their mobile devices. While some respondents are willing yet unable, others are simply unwilling to download apps onto their phone. In one study that Cue Insights conducted, 10% of qualified respondents who met the technical requirements terminated from the screener because they didn’t want to download an app.

3. Equip respondents with relevant and clear instructions.
   • Provide clear technical guidance. Once a respondent has passed the screener, provide them with detailed technical information for downloading the app and be prepared to help with any technical issues in order to aid project success. When possible,
     • Include links to download the app for a quick, easy and fool-proof download.
     • Include the app image that respondents should see when downloading the app in case they opt to download the app manually.
     • Consider if there are any similarly named apps worth mentioning. With the high number of apps available, there may be several apps with a name similar to the one being tested so it is sometimes helpful to include information on what NOT to download.
   • Communicate assumptions and limitations of the app in each stage and clearly state the objectives of the current stage of testing. For example, if respondents are evaluating an advanced wireframe, be sure to explain areas that will be updated in the future and what is a placeholder so that respondents do not get caught up in functionality or visual design at this stage.

Mobile app development and testing is a time-consuming process, but when done correctly, it aids in producing an amazing product that supports and grows your business. Instead of just being AN app, be THE app that your consumers want and need.

Case Study: New healthcare app testing

Cue Insights conducted qualitative interviews for a healthcare app that was in the wireframe stage of testing elements that affect the impact and understanding of the user interface. Three “sprints” (i.e., rounds) of interviews were conducted with 2 weeks in between each round. Each interview lasted 45 minutes. Due to the iterative methodology, significant improvements were made from round to round. Respondents were excited to see the improvements with each subsequent round and remained engaged throughout the entire process. By the end of the research, the app received much graphical improvement, but research suggested that more time needed to be spent on functionality improvements as these were frequently suggested. The client took the additional time necessary to refine the functionality of the app before moving forward with further development testing.

Healthcare App Testing Rounds

Is mobile app development or refinement in your future?
Contact denise.burns@cueinsights.com to schedule a consultation.

¹https://www.flurry.com/post/157921590345/us-consumers-time-spent-on-mobile-crosses-5

²https://en.wikipedia.org/wiki/Website_wireframe