|
|
by observing how the mouse cursor changes as they move it around the interface. This doesn't mean you have to create a wireframe for every page you're going to test. You just have to include a link, even if it doesn't lead to anywhere, in each of the navigation options that your website has. If a user clicks on any of them, you can tell them that it is not a fully functional prototype. You can suggest that he try again somewhere else. If you are conducting a remote test without moderation, remember to link to a standard landing page that contains a similar message.
This way, your users will not believe that the site is broken nor will they abandon the test. By the way, don't forget to put a button to go back on that page. This page will be useful to you if you work with a tool that allows you to view the Brazil Mobile Number List route each user has navigated. By counting how many times they viewed that page you can discover how many mistakes users have made. Check your browser compatibility When you test a website you can trust that it will look good in any browser. HTML prototypes, on the other hand, are not fully developed. They may not be optimized for all browsers. So, before testing a prototype, make sure it works correctly in the browser you are going to use during the session.
If the test is remote, make sure that the prototype works in the most common browsers. Or ask your users to use the browser that you know for sure is compatible with your prototype. This advice is especially important when it comes to user testing a prototype for a mobile device. Because what may look good on a PC may appear very differently on the devices used by your users. Be careful with A/B tests If you're testing different versions, make sure they both allow users to do the same tasks and access the same information . A/B tests with wireframes and prototypes at different levels of fidelity should be taken with caution as they give you partial and misleading results.
|
|
發表於 15:44:36