What Is Prototype Testing?

Prototype testing consists of sharing prototypes or wireframes with contributors to view on their desktop or mobile device to assess the viability of a design during the development cycle.

 

This article applies to: ut logo tiny.pngUserTesting 

On this page:

 


 

Overview

Prototype testing allows you to evaluate designs early in development. A fully linked prototype isn’t necessary—start with a rough mock-up and test iteratively as you refine. Regular user feedback ensures a more successful site or app launch.

 

 

 

Prototype testing with UserTesting

 

 

 

Getting started

  • Sharing static images:

    • Share static images directly through the UserTesting Platform.
    • For mobile devices, use Dropbox to host static images, as it does not require login credentials.
  • Sharing higher-fidelity prototypes:

    • Use tools like InVision or other prototype-hosting platforms.
    • If hosting a prototype in your own environment, UserTesting can assist in sharing it with contributors (ensure your firewall allows access).
  • Placing prototype links:

    • Add the prototype link to the “Starting URL” field on the order form or within the first task of the test.
  • Testing static images:

    • Add images using an Image task in the test plan building page of the UserTesting Platform.
    • Supported file formats: PNG, JPG, GIF, TIFF, and PDF (max file size: 5MB).

 

 

 

Clickable prototypes and best practices

If you are using a clickable prototype, it is easy to get feedback from contributors. UserTesting supports a broad range of prototyping tools. Extract the URL to be shared from your prototyping tool of choice and include it as the starting URL for your test. Or insert it into a URL task within your test.

Best Practices for Conducting a Clickable Prototype Test

Some tips to consider when using a clickable prototype:

    • Turn off hotspot hinting, as you don’t want to bias contributors by showing them where to click. 
    • Share the public-facing sharing link. If contributors can’t reach your prototype, your test will likely go on hold.
    • Tell contributors they are working on a prototype and that everything might not be functional. You don’t want them to spend much time giving feedback about the prototype's functionality.
    • Give clear instructions when you want contributors to click on something and when you want them to respond where they expect to click. 
    • Test the experience by completing a dry run and pilot to affirm you're getting the feedback you need to answer your research objectives.
    • Consider the size of your prototypes. We recommend you produce a prototype specific for each device you want to test with (desktop, tablet, and mobile). Many design programs that you can test with us (e.g., Figma, XD, Sketch) can be set to "scale" the prototype to fit the browser width. This functionality can sometimes make elements appear bigger or smaller than intended, depending on the browser size. If you specify that a contributor uses their mobile device for example, show them a mobile version of your designs. A scaled-down desktop version on mobile isn’t great for feedback. 

 

 

 

Related content

information icon.png

knowledge icon.png

Want to learn more? Check out these Knowledge Base articles... 

Interested in growing your skills? Check out our University courses...

video icon 2.png

team icon.png

Need hands-on training?

Can't find your answer?

Was this article helpful?