• Cat NooneCat Noone, almost 9 years ago

    High fidelity prototypes are not a waste of time if you're a designer who has zero experience with code and needs to communicate properly with a developer. It makes the entire process a lot easier - especially if the developer doesn't come in until that phase. Luckily, a lot of places do not run into that problem but it's a realistic issue and prototypes solve the problem. At the same time, it's really nice to see how you plan for your app to interact before you start getting into the nitty gritty.

    0 points
    • Aaron SagrayAaron Sagray, almost 9 years ago

      It's the "high fidelity" part that doesn't make sense. Prototyping should be used to test and communicate interactions. You don't need pretty prototypes to do that, just ones that work.

      Even, then there are diminishing returns to blowing out interactions in a prototype. I tend to model the more complex interactions, then annotate the rest.

      0 points
      • Oliver ChankOliver Chank, over 7 years ago

        Though I agree, sometimes clients or stakeholders don't quite understand if it's not hi-fi to a certain level...

        0 points