hci assignment luh

Submit your assignments

Currently, it's not possible to submit any results.

You can currently submit your results to Assignment 12 . So far, we received 6 submissions.

You can currently submit your results to Woche 4 . So far, we received 10 submissions.

Please note our Privacy Policy .

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications You must be signed in to change notification settings

luh hci assignments 2021 2022

kaicb97/hci_group

Folders and files.

Repository files navigation

Contributors 4.

• JavaScript 48.2%

• Prerequisites
• Submit Work

Assignment 8, Example 3

In-person testing, user test 1, user test 2.

View a 3 minute video excerpt of the test.

User Test 3

Usability script.

• Before showing the test subject our app, we explained the goal of the app in order to set up their context; we told them that they’ll be testing a coupon consolidator. After prepping them, we asked what they are expecting of this app as far as brand and feel.
• Ask them to sign the consent form.
• Present the user with a smartphone displaying our app’s homepage and allow them to look at the home page for approximately 5 seconds before the assigning of tasks.
• Assign tasks:
• Add a coupon to the wallet.
• Sort a coupon list by expiration date.
• Add 3 more coupons.
• Remove a coupon.
• Ask the user to determine how many coupons are in the wallet without prior knowledge.
• Ask the user to take a picture of an imaginary coupon and upload it.
• Conduct post test survey.

Things to keep an eye out for:

• How is the user interacting with the navbar?
• Does the user use the how-to page at all?
• If so, how long do they spend on it?
• How often do they go back to the home page?
• What do they care about? What information helps them navigate?
• What do they not care about- what are some extraneous steps or information?

Consent forms were included here

List of changes.

• Disable the upload button until the user chooses a file to upload. Currently the user can upload an empty file which caused confusion in our second user test.
• Add informational text or diagrams to the “Snap” page to make it more intuitive to use. Currently there are no instructions or diagrams and relies on the user to divine how to use the page. Some users were not able to do so and were not able to use the page.
• Shorten/condense the text on the “How To” page. A user visited the page to find specific information, and although that information was present, they were not able to quickly find it and instead moved elsewhere on the site in pursuit of the information.
• Convert the drop down menu that handles coupon sort parameters to buttons. Users had to scroll or resize page when drop-down menu was used because it automatically zooms in slightly which cuts off information on the edges off the page. This creates more work for the user, and we might be able to fix this by creating buttons to represent the parameters.
• Change the Choose File button’s text from choose file to Take Picture/Choose FIle. When the user was presented with the task to take a picture and upload it, the user did not use the choose file button. To make this button’s purpose clearer, we might change the text to indicate that this button leads to taking a picture as well as choosing a file.
• Change the arrangement of grocery coupons available so that instead of displaying all of the information with the image of the food item, images of coupons would be displayed to look more like a gallery wall. (If time permits because this is actually a very large redesign change)

Implementation Plans

Last week's implementation plan.

This week's implementation plan.

View the redesign here. Note: The team submitted this as a functional, implemented redesign-- the video was made for archival purposes.

Description of Online Test

Experiment 1: dropdown or buttons (see user test 3).

While conducting in person testing, it became apparent that when the user interacted with the drop down bar that determined how coupons are sorted, the page zooms in after a sorting parameter is selected. This did not seem to bother the user, who immediately scrolled to find the information that was cut off when the page zoomed. While the user did not express frustration, we realize this is a single view point of a user who easily navigated the page. To a user who experiences difficulty navigating, this auto zoom byproduct might be a turnoff. To determine if this zoom effect is problematic, we need to increase the sample size in order to get more data, and we will do so by turning to online testing. This testing will be conducted in A/B fashion, with the A design being our original interface (the sort functionality being placed within a dropdown menu). The B design will incorporate changes to the interface by which users select coupons sorting parameters through a series of adjacent buttons. These buttons allow for the user to see all options simultaneously while still being able to see the list of coupons, it would negate the zoom factor caused by the drop down, and if we are able to find suitable imagery to represent the sort parameters, it will promote recognition over recall. We hope that this user testing will enable us to determine the superior, and more intuitive way to display sorting parameters by inquiring as to which design the user preferred, and asking about any frustrations or annoyances faced using either one. Additionally, if images or graphics are used in the buttons to represent the parameters, we will also be looking for confusion on the part of the user when interacting with the buttons.

Experiment 2: Snap page - Instructions or no instructions

While conducting in person test, we found that one user found the snap page difficult to use. Specifically, when given the task “upload a coupon”, the user was not sure how to proceed once on the snap page. From there the user navigated to the “How To” page, skimmed the text, did not immediately find the information they needed, and then proceeded to navigate around aimlessly. We fear that this user’s experience is not unique and is indicative of the experience that many others will have. We plan on redesigning the “Snap” page to include information that instructs the user how to operate the page. This hopefully reduces the confusion that the “Snap” page causes. In the A/B testing, the A test will consist of the original design. The “Snap” page will not have any explanations on how to use the page. The B test will hold informational text, or diagrams to help the user understand the page’s functionality. Ideally, the results of the testing will be made apparent by the ratio of how many people successfully upload a coupon to the page quickly and efficiently between the two tests.

HCI for Product Managers

Schedule and readings, course introduction slides.

• Required What it takes to become a great product manager -- Julia Austin 2017
• Required How To Write a Good PRD -- Martin Cagan 2017
• Optional Lean Product Management -- Dan Olsen (Google Ventures Startup Lab)

Heuristic Evaluation Slides

• Due Assignment 1: Problem Statement
• Required Rapid Evaluation (Chapter 13) -- Rex Hartson and Pardha S. Pyla , The UX Book - Process and Guidelines for Ensuring a Quality User Experience
• Required 10 Usability Heuristics for User Interface Design -- Jakob Nielsen
• Required Severity Ratings for Usability Problems -- Jakob Nielsen

Contextual Inquiry Slides

• Required The Value of Rapid Ethnography (Chapter 5) -- Ellen Isaacs , Advancing Ethnography in Corporate Environments - Challenges and Emerging Opportunities
• Required 12 Tips for Early Customer Development Interviews (Revision 3) -- Giff Constable
• Required How to Choose a User Experience Technique -- Pooja Sawant

User Interviews Slides

• Due Assignment 2: Heuristic Evaluation
• Required Universal tools- Recruiting and Interviewing (Chapter 6) -- Elizabeth Goodman, Mike Kuniavsky and Andrea Moed , Observing the User Experience
• Required Example Interview Guide- Reading Ahead Interview Guide -- Portigal Consulting
• Required Example Interview Guide- Designer Information Search / Use Field Study Script -- Dan Russell

Stakeholders Slides

• Required Surveys (Chapter 12) -- Elizabeth Goodman, Mike Kuniavsky and Andrea Moed , Observing the User Experience
• Required Competitive Research Methods (Chapter 5) -- Elizabeth Goodman, Mike Kuniavsky and Andrea Moed , Observing the User Experience
• Required Stakeholder Mapping - The Complete Guide to Stakeholder Maps -- Rikke Friis Dam and Teo Yu Siang

Synthesis & Ideation I Slides

• Due Assignment 3: User Interview
• Required Personas and the Advantage of Designing for Yourself -- Joshua Porter
• Required Using Improvisation to Enhance the Effectiveness of Brainstorming -- Elizabeth Gerber , ACM CHI
• Required How Might We Questions -- Stanford d.school

Synthesis & Ideation II Slides

• Required Abductive Thinking and Sensemaking- The Drivers of Design Synthesis -- Jon Kolko , Design Issues
• Required Love, Hate, and Empathy- Why We Still Need Personas -- Kyra Edeker and Jan Moorman , UX Magazine

Low Fidelity Prototype & Storyboard Slides

• Due Assignment 4: Synthesis and Ideation
• Required Storyboarding- An Empirical Determination of Best Practices and Effective Guidelines -- Khai Truong, Gillian Hayes & Gregory Abowd , ACM DIS
• Required The Use of Stories in User Experience Design -- Dan Gruen, Thyra Rauch, Sarah Redpath, Stefan Ruettinger , International Journal of Human-Computer Interaction
• Required Rapidly Exploring Application Design Through Speed Dating -- Scott Davidoff, Min Kyung Lee, Anind K. Dey, and John Zimmerman , Ubicomp

Guest Lecture by Max Friedman (Google) Slides

No class slides, usability testing and think aloud slides.

• Due Assignment 5: Storyboards and Sketches
• Required Turn User Goals into Task Scenarios for Usability Testing -- Marieke McCloskey , Nielsen Norman Group
• Required Thinking Aloud- The Number 1 Usability Tool -- Jakob Nielsen , Nielsen Norman Group
• Required Think−Aloud Usability Testing -- Bonnie John , User−Centered Design and Testing
• Required General Concepts of Usability Testing -- James Hom , The Usability Methods Toolbox
• Required Thinking Aloud Protocol -- James Hom , The Usability Methods Toolbox

UI Design Slides

• Due Assignment 6: Interactive Prototype & Visual Design
• Required The Psychology of Everyday Things (Chapter 2) -- Don Norman , The Design of Everyday Things
• Required Prototyping (Chapter 11) -- Rex Hartson and Pardha S. Pyla , The UX Book - Process and Guidelines for Ensuring a Quality User Experience
• Required Mental Models -- Jakob Nielsen , Nielsen Norman Group
• Required The Grid System- Building a Solid Design Layout -- Mads Soegaard , Interaction Design Foundation

Additional course information available on Canvas .

Product managers are ultimately responsible for developing products that meet customer needs. The field of Human-Computer Interaction (HCI) has developed techniques to understand user needs and design human-centered technology that directly addresses those needs. In this course, students will learn and practice these techniques through a course-long project.

In this course, students will develop skills drawn from the field of HCI to research, ideate, evaluate and define a new software application, culminating with the presentation of a document specifying use cases and functionality. This course provides an overview and introduction to the field of human-computer interaction, focusing on how it applies to product managers.  Particular emphasis will be placed on what HCI methods and HCI-trained specialists can bring to design and development teams. The course will provide a hands-on introduction to proven tools and techniques for creating and improving user interfaces, such as Contextual Interviewing, Rapid Prototyping, Heuristic Evaluation, and Think-Aloud Usability Testing. Students at the end of the course will have learned how to perform some useful techniques and will have an understanding of systematic procedures for creating usable and useful designs and systems.

Prerequisites

None. Assignments will involve conducting interviews and observations, doing synthesis and analysis, ideation, paper prototyping, and implementing a prototype of a working design, using some computational medium. We will use the interactive design tool Figma for some assignemnts. No background in HCI is expected.

Required Textbooks

There is no required textbook for this course. Readings are drawn from a variety of books, readings and online postings, and will be provided by the instructor.

Amount of Work

This is a “6 unit” mini. As per university policy, this means that this course is expected to take students 12 hours per week, including class time. Surveys of previous students show that this is accurate.

How to Submit Assignments

All assignments must be turned in using Canvas .

The tentative breakdown for grading is below. As a reminder, here is the university policy on academic integrity .

There will be 6 assignments, each worth 15% of your final grade.  All assignments in this course are individual: you are required to do them by yourself . Each person must do their own work independently. Participation will comprise the remaining 10%:

• Assignment 1: 15%
• Assignment 2: 15%
• Assignment 3: 15%
• Assignment 4: 15%
• Assignment 5: 15%
• Assignment 6: 15%
• Participation: 10%

Participation includes interaction during classroom activities, as well as sharing stories, questions and comments related to past and upcoming lectures.

Late Policy

Assignments are due before the beginning of class (12:30 PM ET) on the specified day. A penalty of 10 points out of 100 (one letter grade) will be immediately applied after the start time of class. An additional 5 points will be subtracted for each additional 24-hour period late.  You are responsible to confirm that your Canvas submittal was successfully uploaded.

Respect for Diversity

It is our intent that students from all diverse backgrounds and perspectives be well served by this course, that students’ learning needs be addressed both in and out of class, and that the diversity that students bring to this class be viewed as a resource, strength and benefit. It is our intent to present materials and activities that are respectful of diversity: gender, sexuality, disability, age, socioeconomic status, ethnicity, race, and culture. Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally or for other students or student groups. In addition, if any of our class meetings conflict with your religious events, please let us know so that we can make arrangements for you.

Accommodations for Students with Disabilities

If you have a disability and are registered with the Office of Disability Resources, we encourage you to use their online system to notify us of your accommodations and discuss your needs with us as early in the semester as possible. We will work with you to ensure that accommodations are provided as appropriate. If you suspect that you may have a disability and would benefit from accommodations but are not yet registered with the Office of Disability Resources, we encourage you to contact them at [email protected] .

Health and Well-being

If you are experiencing COVID-like symptoms or have a recent COVID exposure, do not attend class if we are meeting in-person. Please email the instructors for accomodations.

If you or anyone you know experiences any academic stress, difficult life events, or feelings like anxiety or depression, we strongly encourage you to seek support. Counseling and Psychological Services (CaPS) is here to help; call 412-268-2922 and visit their website at www.cmu.edu/counseling/ . Consider reaching out to a friend, faculty or family member you trust for help getting connected to the support that can help. If you or someone you know is feeling suicidal or in danger of self-harm, call someone immediately, day or night:

• CaPS: 412-268-2922
• Re:solve Crisis Network: 888-796-8226

If the situation is life threatening, call the police. On campus call CMU Police: 412-268-2323 . Off campus: 911 .

If you have questions about this or your coursework, please let the instructors know. Thank you, and have a great semester.

Individual Assignment #1: UI Critique (due in 1 week)

  Administrative

• Create a personal course web page with your name and email address at the at the top and post it to a server somewhere. You will use this during the semester to post all of your individual homework assignments. You can organize this however you want, but make sure the instructor can quickly find each week’s work on the page. Send an email with your name, email, and the web address to [email protected] .
• Respond to the email you will receive with questions about your goals for the course.

Remdedial Programming

If you’re new to programming or not comfortable with it, you should begin working immediately on tutorials in your language of choice. If you are not sure what language to use, pick Java and start working your way through the Sun Java tutorial  Trails Covering the Basics . 

Find 2 examples of good user interface design, and 2 examples of bad user interface design.

Your examples should be  specific . It's very hard to find a large interface that's completely good or completely bad, so don't try. Instead, focus on a particular feature or aspect of a user interface that makes your case. Avoid fuzzy words like “intuitive” and “user-friendly”. B e as precise as possible about what makes it good or bad. For example, don’t just say that it “looks professional.” Explain what makes it look that way. Don't just say the interface "is confusing." Explain what specifically makes it so.

You aren't limited to desktop software. Web sites offer many great candidates for fame and shame. You aren't even limited to traditional computer interfaces. Feel free to go out into the real world, and consider consumer appliances, car dashboards, building entrances, traffic intersections, shower controls, etc. (Norman's book  Design of Everyday Things  includes a lot of examples of this kind, which you may find inspirational.)

What to Post   

Your report should include 2 good examples and 2 bad examples. For each example:

• describe the purpose of the overall interface
• describe the particular aspect you find good or bad
• in a bullet list, explain why it's good or bad (please make explicit reference to the "design heuristics" described in class, e.g., consistency, feedback, etc)
• if bad, in a bullet list, speculate why it might have been designed that way, and suggest a better design if possible
• illustrate with screenshots or photographs if possible 

Your document needs to be well organized, easy to read, and free of typos.

Individual Assignment #2 – Project Brainstorming (part 1 due on 1/24; part 2 due 1 hour before class 1/26)

Skim Tim Bickmore's bibliography of HCI for older adults , and the research papers on interfaces for older adults and health interfaces, and think about project ideas for the course (see Team Assignment #1 for more details). Pick three different project ideas that you would be interested in working on for a team project, make a rough sketch of a user interface (a scanned or photographed sketch on paper is best) and write a 1 paragraph proposal for each, further fleshing out the idea.

Part 1: Post your 1 paragraph proposal for each idea on the Piazza newsgroup under #projectbrainstormingideas (Do this by 1/24 6PM). Monitor the website and see how other students and Stephen respond to your ideas. Comment on ideas from your peers.

Part 2: Revise your ideas (or come up with new ones) based on the newsgroup feedback and post your three best ideas and write-ups and sketches on a web page in your order of preference (these will be used to help form project teams).

Individual Homework #3 – Ethnography (due in 1 week)

Please do not attempt this until we have discussed it in class on 1/26.

In this assignment you will spend some time observing an an environment where older adults spend time. You will hone your observation skills and generate ideas about how technology could either help older adults with their help or help researchers advance health with the help of older adults.

Tasks (detailed in the class slides ... please review them for the full information!):

• Select a place where you will spend 2.5 hours observing and interviewing older adults. You need to select a location where older adults are spending time.
• Arrive at the location and check in with someone and let them know that you are working on a class project and are hoping that you will be able to sit and observe for a while and perhaps talk with some people in the location. If anyone tells you that you cannot do so, you need to thank them and leave immediately. It is critical that you be respectful at all times.
• Find a good place to observe older adults working on a task or interacting. Observe for at least an hour, making notes about what you see. Pull ideas about how to do that from the readings. What is important that might impact UI design: people, objects, timing, relationships, exchange of information, documents, etc. Your goal is to observe carefully and thoughtfully and try to understand the behavior and activity that you see.
• Spend at least 30 minutes trying to interview at least one and optimally 2-3 older adults about what they are doing in the location that you chose. Again, your goal is to observe and listen, and to learn what some of the activities or challenges are for the people. This should help you come up with (or refine) project ideas.
• If you already have a project idea in mind, you can approach this exercise from that perspective. However, you need to keep an open mind. Your primarily goal is to learn what the really important issues are ... not those that you think might be important.
• In total, spend 2.5 hours in a single block of time observing, listening, and thinking. For some of this time you may feel like you are not seeing much. But look around! Use your keen senses. You will see things you did not expect if you do this exercise properly.
• Please do not bring your phone or computer or any other device that could distract you. You need to be completely focussed on the environment for the 2.5 hours.
• Afterwards, spend some time reviewing your notes and organizing them. Make some bullet lists of your most important observations that might impact user interface design (and project selection) for older adults. In particular, I'd like you to focus on what you saw the older adults actually doing and how that provides information about the tasks they may most care about or need help with.

What to Post

Your report should include a copy of the notes you made while doin the observation (if they are messy that is ok), a one-paragraph summary of why you picked your particular activity to focus on, followed by an overview of the activity, the kinds of people you observed engaging in it, a description of any artifacts they used. Following this, provide a detailed description of the activity and any variations you observed, and what you found out in your interviews (do not identify people by full name in your writeup - first name is OK). You should try to include a few quotes from people that support your conclusions. (See the ethnography research readings for examples of how to write your report.) You can include sketches in your report but no photographs, and you cannot mention any person's name. Total report length (not including the raw notes) should be 2-3 pages.

Individual Homework #4 –Task Analysis (due in 1 week)

In this individual assignment, you will start the design of your term project by doing the following:

• User analysis . Identify the characteristics of your user population, as we discussed in lecture. If you have multiple user classes, identify each one. Identify all stakeholders in your application.
• Task analysis . Determine the tasks of the problem you've chosen, analyze their characteristics, and answer the general questions about tasks we asked in lecture. Think about other questions you should ask that might be relevant to your particular domain. You should find and analyze at least 6 tasks. If you can't find that many tasks in your problem, try drilling down to more specific tasks, and consider exceptional and emergency tasks.

Each person on the team should do this assignment independently. You are not to consult with one another!

What to Post. Your user analysis and task analysis report should be around 4 pages long. Include the following parts:

• Title . Give your project a title, if you haven't already.
• Problem . Briefly restate your problem.
• Users . Describe each of your user classes and other stakeholders.
• Tasks . Describe 6 (or more) tasks you have identified. Every task should have a goal, preconditions, subtasks (if any), and exceptions (what can go wrong). Also include a paragraph describing other relevant features of the task, such as time constraints or frequency of use.
• Problem Scenarios . For the 3 most important tasks in your task analysis, write a paragraph-length problem scenario: a concrete, realistic example of the task.

Individual Homework #5 – Idea to Low-fidelity storyboarding (due in 1 week)

At this point in the course you should be gaining an appreciation for not committing to an idea too early in the design process. You should also have gained an appreciation for how you should go about understanding the user and problem domain in order to come up with useful and innovative solutions to problem that are likely to work in the real world (as opposed to only in your head!). In this assignment your goal is to put these skills to use on a new problem you haven't thought about so far.

This is an individual assignment that you should perform on your own. Please do not talk with your classmates.

Your mission in this exercise is to design and storyboard the best interface you can to address this problem:

There is increasing evidence that extended sitting is bad for your help. Scientists have known for a long time that lack of physical activity causes health problems. More recently, however, they have uncovered evidence that extended sitting (even for just two hours) causes physiological changes in the body that may be harmful. We are trained throughout our lives to sit, but this may not be good for us. Increasingly, there are people (such as your instructor) who are vowing to (1) spend more time walking or standing throughout the day, especially the workday, and (2) break of long bouts of sitting with short or long bouts of standing or walking. To facilitate this, these people (such as your instructor) are buying desks that can be manually (and easily) raised or lowered so that some of the workday can be spent standing. Other innovations such as cordless phones, mobile phones, instant messaging, location-based systems, and others may also facilitate this change. The problem is that even with these innovations, many people (such as your instructor) may still spend the vast majority of their time sitting. A big-time silicon valley investor has decided that creating software that will help people spend less time sitting is a big-time business opportunity. The investor is ready to fund you to build the system, but has told you to come up with a good idea of what to build. The investor has given you one week to make a case that you should be the one to create this software. The investor has made a few rules. You can assume that people will have manual sit-to-stand desks. You can assume that people have advanced smartphones. Your target users are office workers in the U.S. (such as most of us at Northeastern). You cannot assume that people will invest in fancier desks (such as sit-to-stand desks with treadmills built in). Although some people are interested in sitting less already, most of people the investor would like to sell the software to are not even aware that sitting is a problem. Finally, the investor does want to make money somehow. Your challenge, therefore, is to develop an idea for computer software that will address this problem and help people who want to spend less time sitting actually do it. You must hand in a storyboard that will convey the idea effectively to this investor.

What to Post. Please turn in the following:

• A bullet list of what you did as you developed your idea.
• A bullet list of important concepts, tasks, and/or constraints that you learned from #1 that your design takes into account.
• Your storyboard, that clearly shows how the interface works and demonstrates that you have used strategies that we have talked about so far in the course. One suggestion is to do this in a powerpoint presentation, but you can use another format if you'd like. It must be clear what you propose and professionally presented, with some justification of your major design decisions. It needs to be understandable on its own (i.e., you will not be there to present it, the investor will just read what you hand in).

Our "investor" will pick the five ideas that seem to have the most promise based on the information posted and only those assignments will receive an A on this assignment. You are therefore competing against your classmates and want to employ your new skills!

Individual Homework #6 – Heuristic evaluation guidelines (due in 1week)

Your mission in this exercise is to create a comprehensive list of heuristic guidelines, user interface rules, and tips and tricks . Your goal is to record the "nuggets" of ideas you that have been mentioned in all the reading materials up to this point, and to organize those ideas in a way you believe to be helpful for you. Your work will be shared with the rest of the class.

• A well-organized list of heurstic guidelines. The guidelines should be clustered by topic area. Please make sure the list is proofread and suitable for distribution to the rest of the class. You need to do more than list ideas, you need to cluster them in some useful way.

We will send around a document with links to all the checklists for the entire class, so make sure your checklist will be accessble by everyone else.

Individual Homework #7 – Graphic design (due in 1 week (after the break) )

In this assignment, you will design a mockup of the user interface for a hypothetical home-automation application that may run on a phone, desktop, or tablet computer (a well-designed UI will scale to each).  This will be designed for users with a minimum amount of technological experience, and may include older adults (avoid fiddly little controls).  What you submit will be one or more "screen shots" that demonstrate understanding of the graphic design principles outlined in Krause and the other readings.

The tools you use are up to your discretion, but may include colored pencils, graph paper, OmniGraffle, PowerPoint, HTML, etc.  What you will produce should be adequate to show to a developer with some reasonable expectation that they would be able to implement it.

The application, though Wizard-of-Oz magic, has the following capabilities:

• Make a cup of coffee
• Start your car remotely
• Adjust the home thermostat to a desired temperature

At minimum, you must create iconic buttons (a button with text that says "make coffee" is not iconic!) for each of these functions. Refer to Krause p164-169 for tips on creating a good icon.  Artistic talent is helpful but not required as long as you can convey your concept.  Ultimately, this button will be pressed by the user in order to "do this thing now"

For each of these functions, your interface should provide additional widgets for the following:

[Make a cup of coffee] - Select light, medium, dark roast - Add cream and/or sugar

[Start your car remotely] - Display status whether car is currently on or off

[Adjust home thermostat] - Show current temperature - Select a new temperature in the range of 55-85 deg

Think carefully how these functions are organized, arranged, and when/where they are presented to the user.  And that's all the instruction you will get.  Design is an open-ended iterative process.  You probably have questions about other details related to this broadly specified application.  Make some educated guesses, and show your ideas to other people to elicit feedback.  When you come up with a final solution, render it as convincingly as possible.  A well-designed interface will include some consideration of the following principles (among others):

• Color (we want this to be eye-catching but not overwhelming)
• Typography (Serif, Sans Serif, or both?)