top of page

PROTOTYPES

​
Our goal is to test designs that are somewhere between 40 and 60% complete - given the time constraints of the class and the fact that we won't be able to conduct several rounds of testing, we feel that this provides a sufficient balance of product and feedback for our final iteration.  We may also consider soliciting feedback about the possibility of converting our web design into a mobile app to provide a paired desktop/mobile experience - since many of our users spend more time on their phone than on the computer (a trend that is on the rise among young people) it may benefit the longevity of our design to consider working towards a mobile-optimized interface in addition to the web interface.
​
Our goal is to test designs that are somewhere between 40 and 60% complete - given the time constraints of the class and the fact that we won't be able to conduct several rounds of testing, we feel that this provides a sufficient balance of product and feedback for our final iteration.  We may also consider soliciting feedback about the possibility of converting our web design into a mobile app to provide a paired desktop/mobile experience - since many of our users spend more time on their phone than on the computer (a trend that is on the rise among young people) it may benefit the longevity of our design to consider working towards a mobile-optimized interface in addition to the web interface.

Low&

Medium 

Fidelity

As far as user testing is concerned, our primary goal is to get feedback on the paper prototypes to determine a number of factors: how intuitive the interface and our data organization is, whether the design is usable and aesthetically pleasing, whether we are missing features/adding unnecessary features, and if the prototypes we put forth meet the needs we determined in our need-finding interviews. 

prototype 1

decision guide

Screen Shot 2017-06-10 at 12.38.54 PM
DASHBOARD
CONTENT DELIVERY
CONTENT DELIVERY
INTRO

prototype 2

ama style forum

bottom of page