Together with your team partners, implement your interface design in a medium-fidelity prototype in HTML, Powerpoint, Visual Basic, or any of the other methods discussed in class, and also listed on the course web page. In any case, how you actually implement your prototype is of minor importance.
The goal is to have a prototype that runs well enough that a user could sit down and try out the system. It doesn't have to perform most of the actual semantic functions, it should just go through the dialogues or screens that make up the syntactic and lexical levels of the user interface.
For example, the semantics can use "canned" data. The most important products of our whole design process are the designs and the test results. The real purpose of building the prototype is to make it possible to do the user testing.
Construct your prototype based on your target platform or medium. For example, a smartphone or smartwatch application prototype should maintain the same screen size and standard UI elements (such as buttons, keyboard, etc.) as a real phone or watch. You should not provide any functionality that would not be available on the target system. For a phone, there will probably be no external full sized keyboard, so your prototype should treat typing as a series of presses on a screen, mini-keyboard, or other hardware available on a mobile device.
Each team should hand in:
Engineering Question: How did you choose which implementation technology to use, and how close to the desired functionality were you able to get with it? If you were asked to iterate on this medium fidelity prototype to create a high fidelity product instead of starting from scratch, would you be able to develop it to production quality? What would be the biggest development challenge, and the greatest compromise?
Product Manager Question: What features did you prioritize in making this medium fidelity prototype? What questions could a medium fidelity prototype answer in product discovery that a low fidelity prototype couldn't? What are some of the pros and cons of a medium fidelity prototype and if you had to convince your stakeholders on why you need a medium fidelity prototype, what data and convincing arguments would you use to show that?
UX Researcher Question: What findings did you find during your last low fidelity study and how has that influenced your decision on what you should include for your medium fidelity prototype? Which UX research method did you use to test your medium fidelity study and how did you ensure that your test is free of bias? What were some of the usability questions you had before the study and what insights did the study give you?
Product Design Question: What key components should every mobile application screen have? What visual characteristics should you keep in mind when you're making mockups to ensure accessibility and effectiveness (e.g. legibility, information architecture, etc.)? If you're creating an application that will span across different channels (mobile, desktop, and smartwatch), what do you have to take into consideration?