Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with prototype
Search options not deleted
user 96450
A simulation of a product created prior to development for the purpose of testing or gathering feedback.
6
votes
2
answers
493
views
When testing a prototype, do you inform your users that everything is not functional?
We use usertesting.com and when testing our prototypes we have opted to not notify the users that they are testing a high-fidelity (flexible, polished UI) prototype hence not every button or interaction … I can't disagree with this logic but I have seen other tests and an article stating that it is best to tell the users that they are testing a prototype. …
- 61