Skip to content

Instantly share code, notes, and snippets.

@lawloretienne
Created November 8, 2016 03:40
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lawloretienne/c05536bd0158e02453e21c42561baf56 to your computer and use it in GitHub Desktop.
Save lawloretienne/c05536bd0158e02453e21c42561baf56 to your computer and use it in GitHub Desktop.
  • Test most important flows in the app (Request a table flow). By focusing the test you will get more actionable results.
  • Test popular phone manufacturers (Samsung, LG, HTC, Motorola)
  • Changing the look of an app can create intense dissatisfaction among your user base. Run user tests on major UI changes before you push them out to market.
  • Test for usability and emotional engagement
    • Usability means the ability of a typical user to easily figure out how to use your app. Mobile users are notoriously impatient; if an app confuses them, they will probably move on to something else.
      • Do users understand what they're supposed to do?
      • Have you made the most important features easy to find?
  • Emotional engagement measures the user's motivation to use your app.
    • Are you providing features that users actually want, and have you made it easy to get to them?
    • Do people feel rewarded enough by your app that they want to return?
    • Are you planting emotional hooks to keep users engaged with your app?
  • Testing apps with users from prototype to post-launch ensures a smooth and engaging app experience, leading to increased usage and higher ratings.
  • Apps have to delight users on the very first use or they will uninstall, forget they downloaded it, or worse, rate it negatively so that other users won’t even try it.
  • Test tasks that access the core functionality of your app.
  • Can your users accomplish simple tasks the first time they use your app?
  • Can required tasks be accomplished within a reasonable period of time?
  • When users move through your app, are they able to return to previous tasks? After an absence for a period of time, can a user quickly replicate tasks upon returning to the app?
  • While using your app, do users make errors? Are they encountering errors within the app?
  • Were users pleased with the app? What was their overall satisfaction with the experience?
  • Are there common failures from the users who tested your app?
  • Did users get hung up on the same tasks?
  • Are the failures critical?
  • Ask Good Questions. Make sure your questions are clear, open-ended, and focused on the topics you’re investigating.
  • Test with Five Users. Testing five users is typically enough to identify a design's most important usability problems.
  • Identify what needs to be tested and why (e.g. a new product, feature, etc.)
  • Identify the target audience (or your desired customers).
  • Create a list of tasks for the participants to work through.
  • Recruit the right participants for the test.
  • Ask questions in a neutral manner, listen well, make users feel comfortable, and know when and how to probe for more details.
  • Create a list of questions and follow up questions for user tests.
  • Identify your audience pain points and how exactly your app can help to solve them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment