Final Prototype {

Grade

• 25% of final grade

Deadline

• One week after last class (four weeks total)

If you ever need an extension, contact your instructor at least 3 days before the final deadline.

🔥 If you are running into trouble, get in touch with your instructor early to work out a plan, we want to help 🔥 Read the submission guidelines carefully. You will lose points for incorrect submission formats.

Objectives

• Demonstrating your mastery of the diverse technical concepts and skills learned over the course of the semester
• Exploring the different potentials and challenges of a larger scale project
• Reflecting on your path through programming both as a technical and artistic/design practice during this course

Deliverables

Prototype(s)

Create either a single substantial prototype or a cohesive collection of smaller prototypes that demonstrates both your mastery of the topics covered during this course as well as your engagement with the design/artistic potential of this medium. Consider:

• Looking at your past work to find ideas that you found exciting and wanted to extend on
• Finding ways to combine diverse prototypes and/or class examples in a way that produces a cohesive whole
• Choosing a broader theme/experience (the feeling of being lost, gambling, bears, exploration, …) and create multiple smaller prototypes to explore different facets of the theme

You do not have to include every single topic covered in the course, but demonstrating your abilities to use a diverse range of the topics will be important to your final grade.

As ever, feel free to borrow from any of the example code you’ve seen so far in the course, but make sure to attribute in you code in the top-level comment. Remember that is your work that will be graded in cases, not starting code you may use.

README

Your project must have a fully filled-in README following the template. It should include a description of the project, screenshots, instructions, inspirations, attributions, and anything else that would help someone understand and get excited about your work.

Weekly journal entries

Each week, write a journal entry in your process journal reflecting on the week’s work on your project. This can include planning documents, inspirations, sketches, explorations of your own confusion, technical problems and victories, insights into programming concepts, user experience goals and how you’re designing for them, reflections on your progress in the course, and more.

Include at least one screenshot per journal entry.

Each journal entry should be a minimum of 500 words (more is fine too), use this as an opportunity to reflect on your work, get unstuck, and generally lean in to what you’re learning through practice.

Advice

1. Start early. Don’t delay thinking about this. Start playing around immediately.
2. Start small. Think of the smallest possible version of what you want to make and make that first. Once it works, you can start making it bigger and bigger. Smaller ideas punch about their weight.
3. Seek help. Ask for help as soon as you need it either to discuss what you want to do or to figure out a problem.
4. Be stylish. Make sure you read the style guide.
5. Be committed. Remember your grade includes your use of version control and writing good, reflective commit messages.
6. Check your links. When you submit, make sure your links work.

What to submit

You should add the following to your class homepage (aka. cart253/README.md):

1. A heading naming the project
2. A screenshot and title, followed by links to the running prototype and its folder in your repository
3. A link to your reflective journal for the project

It might look like this (for Pippin, whose username is pippinbarr):

## Final Project

[Reflective Journal](./journal)

### Name of Prototype

![Screenshot of prototype](./screenshots/final/prototype-screenshot.png)

[View online](https://pippinbarr.github.io/cart253/final/prototype/)

[View code](https://github.com/pippinbarr/cart253/tree/main/final/prototype/)

You will then only need to submit a link to your README.md via Moodle (see below) beause the instructor will be able to easily find all your running prototypes and their code.

Submission

Submission will take place on Moodle. Go to the appropriately named assignment on the Moodle and then submit your work there.

Your submission should just be a plain text link to your website/README.md that contains the materials for this assignment, e.g. (for Pippin it would be)

Website version: https://pippinbarr.github.io/cart253/

or

Repository version: https://github.com/pippinbarr/cart253/

If you would like to be fancy you could make a new README.md for each topic and put it in a corresponding folder with all your prototypes and code linked there instead, e.g. you would submit something like:

Website version: https://pippinbarr.github.io/cart253/final/

Repository version: https://pippinbarr.github.io/cart253/tree/main/final/

🔥 Make sure all your links work before you submit 🔥
🔥 Make sure that you have commented your project before you submit 🔥

Evaluation

Read the assignment rubric on Moodle for precise details.

---

}