Back to
Schedule
P7: Prepare for Next Studio (Paper Prototyping)
Each team member should produce 1
revised and polished BASE screen sketch for one of the features using this
phone template (make sure you print at scale 100%). The base screen for a feature is usually the screen users see when they click on a tab on the mobile app. The sketch should simulate the intended layout (i.e., appropriately-sized interface elements, such as buttons, textboxes, labels) and actual content (i.e., real text, as opposed to placeholders for text). The sketch should still be low fidelity, i.e., they should look and feel like a sketch, has minimal or no color, no font, no styling, etc. Cut out this refined base screen sketch, and bring it to the next studio class. These screen sketches will serve as the static screens for your app, and during the studio class next week, we will make these static screens interactive. For P7 writeup, include photos of these refined sketches in the design notebook.
Important: for paper prototyping session, you will need pencils, pens, highlighters, erasers, rulers, glue, scissors, tape. Acquire these materials and bring them to the next studio class. We will provide paper and sticky notes; though if you have some at home, bring them as well.
R1: Research Proposal Draft (CS649 Only) - Due Friday Oct 25
Pick two different HCI methodologies to read from the reading list (link and instruction on Slack). You are expected to learn two different types of HCI methodologies, and individually produce a report that describes the design of two studies, one per methodology, to investigate research questions related to your CS449/649 design project, and provide a convincing argument on
how and
why these questions can be appropriately answered by the corresponding methodology/study design.
Your proposal draft should have the 5 sections - Introduction, Related Work, System Description, Research Questions, Study Design - as described in the
Deliverables page of the course website.
The proposal draft is 2 pages minimum, not counting references, using this
overleaf template (use sample-sigconf.tex). To submit, simply send the instructor a link to your overleaf project on Slack.
CH1: Challenge Report - Due Friday Oct 25
Complete the challenge report in your design notebook. In the challenge report, list
THREE assumptions that your team managed to break that were particularly surprising, and the methods/strategies you used to break these assumptions. Describe each assumption, including the rationale behind the assumption (i.e., the concrete evidence that caused you to have this assumption in the first place), how you challenged the assumption (i.e., the specific methods and strategies that you used to test the assumption), the insights you gained from testing the assumption (i.e., your findings), and new assumptions that followed from those insights. In discussing methods/strategies for testing assumptions, be specific and concrete. Don't just say "we did interviews" or "we did evaluations". Of course, we know that you have done interviews and evaluations! Tell us a story about how you managed to find the right strategies to test your assumptions, and the challenges or doubts you encountered along the way. The goal is to make the report interesting and something that other students can benefit learning from. Your challenge report will be graded based on this
rubric (see pg 1).
Sign up for Project Discussion (Optional)
On Oct 28, there will be a brief (30 minute) lecture explaining how the paper prototyping lab is going to work. Following the lecture, teams who are interested can schedule a 15-minute meeting (or two 15-minute blocks if you need more time) with the instructor to discuss the direction of their project, e.g., the scope and novelty of their features, etc. Meetings can be booked using this
Calendly link.