Assignment 12
Due
Submitting your homework
To submit the assignment, please visit Canvas
and submit the URL to your final commit that you want us to grade.
A commit URL looks like https://github.com/designftw/hw11-username/commit/b59f14ba05869b3067724aa6d2006667a54c8e7d.
You can submit as many times as you want.
This is important. Your homework is not submitted and is accruing slack hours until you do this!
To make sure your homework is graded correctly, please follow the following:
- Please make sure each of your exercise directories are self contained, i.e. that you don't reference any files outside of the directory (e.g. from your repo root or other exercises). While having a common assets directory for all your exercises might be a good idea in general, we extract each exercise directory separately (as it may be graded by different people), and that will result in your pages not working correctly.
- Do not use root-relative URLs (URLs that start with
/) or absolutelocalhostURLs, as these require the grader to run a local server at a specific directory within your repo. If for some reason you cannot avoid it, please document it in a README otherwise links may be broken for whomever is grading your homework.
If you submit after the deadline, it will count towards your slack hours.
Exercise 1: Chat app halfway checkpoint (100%)
This and the next (and last) assignment are to implement your designed chat app features. You will implement half this week and half next week. Since your designs are individually chosen, you will also need to determine a suitable halfway point that you submit this week. It should satisfy the following conditions:
- It involves roughly half the work and half the code
- It can be run and provides a functional chat app
- It demonstrates a significant part of your design.
What defines a significant part of your design? If your design involves several features/changes to the basic chat app, a good approach would be to fully implement half of them — in a way that provides some reasonable/coherent functionality not available in the basic app. If your design is all one large feature, aim to implement a simplifed (MVP) version of that still gets the basic idea across. We recommend discussing your plan with the course staff who can help you identify a suitable half. You will have an opportunity to do so in studio this week.
Now that you have had the chance to do development work with the chat app infrastructure, you may be reconsidering how ambitious you want to be in implementing your chosen feature. You may modify (simplify) your design, but should do so in a way that is informed by the user testing you have done — aim to keep the parts that were most important/valuable in your user tests.
Deliverable: Your customized prototype of the chat/messaging app in chat-client directory (if your directory is called chat-app, please simply rename it).
In addition, an HTML file with (i) a description of what design you ultimately plan to turn in for the second and final assignment (how it has changed from your figma mockup), and (ii) a description of what you are turning in this week, and why it represents an appropriate halfway point. Put this writeup also in chat-client directory in file hw12-writeup.html.
We will not release a new Github classroom assignment repo for this app. Continue working with the hw11 repository that you have already been using and simply submit a new commit URL for that repository when you wish to submit.
Exercise N: HW12 feedback
Since this is a new class, we need your constructive feedback about every aspect of it: lectures, homeworks, labs etc.
Please fill in your feedback about HW12 in this form. You can edit it as many times as you like until the survey closes (48 hours after the homework deadline). Since this is part of your participation grade, it does not affect your slack hours, but failing to submit the form on time, could result in a lower participation grade.