Final Project (50 pts)

The final project is a chance for you to synthesize the topics we have covered so far in class (and the topics we will soon cover). This project may be a group project of groups of up to three. If this is a group project, at least two ESP32s must be used and communicate directly with each other using wifi, bluetooth, or ESP-NOW.

Final Project Proposal (5 points)

A short plaintext description of your idea submitted to CourseWorks. Include in your proposal:

Final Project In-progress Presentation (15 points)

On the last day of class, we will have presentations of the progress you have made so far. Presentations should be 3 min per group member.

You will be evaluated on the following points:

Final Project Documentation (30 points)

As always, the standard deliverables. If working in a group, you may all submit the same code repository, but each need to submit your own blog post. The post should detail, in your own words, the creative vision of the device you have created. You should detail the technical challenges you specifically (as opposed to other group members) faced during the implementation of the device.

(10 points) Some aspects of this project are specific to the final. In particular, you must:

You must also meet the following “standard documentation deliverables”.

(10 pts) A blog post

Using a blog site of your choice (github pages, hackaday, medium, notion, etc) make a blog post describing your art. The post should give an overview of your artistic vision. In particular for this assignment, you should address how you have specialized your generative art to the space. What creative decisions did you work lead you to, and which decisions did you take? How were your decisions motivated by your larger creative vision for this project. In the same vein, also address any technical issues you encountered in your work. Particularly focus on issues that other artists may encounter when developing with your hardware setup.

(5 pts) A README

On your github repo add a readme that contains a short description and key information on reproducibility/installation/usage. This key information should be sufficient for a knowledge third party, outside the class, to replicate your design. This readme can be a subset of the material used in your blog post.

(5 pts) Visual documentation of your art (and in this case, the installation as a whole)

Both your blog post and the README should have some amount of visual documentation. Typically the blog post will have a video. The README can have some lighter weight visuals (e.g. a still image). The video can be a simple video shot on your phone - assuming you use basic best practices as discussed in class. You can host the video wherever you like as long as the hosting platform supports in-browser playback (e.g. YouTube, Vimeo). You may also choose to embed a gif in your README in place of a video link.