interaction lab

Cosmic Clash: A Laser Shooting Game – Yancy Jairo Tavares – Andy Garcia

VIDEO DOCUMENTATION:

https://drive.google.com/file/d/1hdaXuMpcq6xzkq17s7jbGnHaVP62Jkvf/view?usp=sharing

CONCEPTION AND DESIGN:
The project centered on designing and integrating various elements to create an engaging alien-shooting game that combined physical and digital interactions. The concept emerged from preparatory research and essay work, merging the fast-paced elements of reaction games with the thematic shooting mechanics of games like Galactica.

Space Invaders: Galactica

The design process began with creating a physical backdrop to house the light sensors, ensuring consistent lighting through the addition of a covered roof to eliminate external interference. The gun, consisting of an Arduino-powered laser and a button trigger, was designed to be intuitive and self-explanatory, enabling users to interact naturally without extensive instructions. Features such as a tutorial, hit-and-miss visual effects, and background music were added to guide players and immerse them in the dystopian gameplay. The Processing code dynamically handled visual feedback, including a scoreboard, timers, and a gameover screen, providing a cohesive and polished experience. These elements were chosen for their ability to create a simple yet engaging gameplay loop while remaining practical for transport and showcasing.

Understanding how users would interact with the game heavily informed key design decisions, and user testing played a critical role in refining these choices. For instance, the tutorial was highly effective in addressing potential learning curves, guiding players on how to aim and shoot accurately, which enhanced their overall experience. Feedback from testing revealed challenges like spamming the gun, disrupting gameplay, and difficulty in hitting the sensors accurately. This led to the introduction of a clearer explanation that after each shot, a new alien would appear, encouraging players to be more deliberate with their actions. Visual indicators were also added to guide players on where to aim, significantly improving accessibility and making the game more intuitive. The gameover screen, with its own music and countdown timer, provided a smooth transition back to the start, maintaining the game’s flow and replayability. Background music and sound effects for hits and misses enriched immersion, making the game feel more dynamic and responsive. The covered roof ensured reliable sensor performance in various lighting conditions, while the anti-spam features preserved gameplay integrity. Together, these adaptations not only addressed user feedback but also elevated the game to a polished, interactive, and enjoyable experience, aligning perfectly with the project’s goals.

FABRICATION AND PRODUCTION:
The production process for my project involved merging two initial concepts: a shooting alien game and a reaction-based hitting game. The design combined reaction game elements, such as timers, scores, and structured gameplay loops, with a thematic shooting experience inspired by games like Galactica and Bop It. I selected light sensors as the primary input devices to detect laser hits on specific targets, paired with an Arduino-powered laser and a button trigger to simulate an interactive gun. These components were chosen for their reliability, precision, and ease of integration, aligning perfectly with the project’s goal of creating a simple yet engaging gameplay experience. An alternative idea was to use motion sensors to track player movements for targeting aliens, but this was rejected due to concerns about portability, efficiency, and the complexity of implementation for showcasing. The light sensor-based approach proved optimal for its balance of simplicity and functionality, ensuring smooth interaction and effective user feedback.

  

initial sketch of game

 

Initial Core Circuit

 

Completed Core Circuit

Key features, such as a tutorial, gameover screen, scoreboard, and real-time hit and miss effects, were integral to enhancing the player’s experience. The tutorial guided users through the mechanics of aiming and shooting, making the game accessible to players of varying skill levels. The scoreboard and timer, rendered dynamically through Processing, provided a competitive and engaging element to the gameplay loop.

 

IMG_6422

Initial Gameplay Loop

IMG_6428

 

User Testing Gameplay Loop

 

IMG_6592

Gameplay with background score and effects

 

Background music, combined with sound effects for hits and misses, further immersed players in the dystopian setting. The Game Over screen included its own distinct music track and a countdown to reset the game, ensuring a smooth transition back to the starting screen. User testing revealed areas for improvement, such as spamming the gun and difficulty in targeting the sensors, leading to important adaptations like anti-spam functionality, visual indicators for targets, and a covered roof for consistent lighting. These adjustments, paired with polished code and hardware integration, created a cohesive, immersive, and stable final product.

 

IMG_6593

Gameplay with proper sounds and tutorial

CONCLUSIONS:
The goal of my project was to create an engaging and interactive alien-shooting game that combined physical and digital elements to provide an immersive experience for the audience. The project successfully achieved its stated goals by delivering an intuitive gameplay loop with features such as a tutorial, hit-and-miss effects, a scoreboard, and dynamic feedback through Processing. Based on my expectations, the audience interacted with the project with interest, showing appropriate reactions of excitement when they hit targets and mild frustration when they missed, which enhanced the competitive and immersive aspects of the game. Initially, many players spammed the button, misunderstanding the mechanics, but once I explained that a new alien appeared only after each shot, they adjusted their approach, becoming more strategic. This interaction aligns well with my definition of interaction, as the audience’s input directly influenced the game’s responses, creating a dynamic and engaging exchange.
What sets this project apart is the deliberate attention to how players would engage with the system and the seamless integration of feedback-driven design elements. The tutorial, for example, not only enhanced accessibility but demonstrated the value of guiding users toward intended interactions without compromising their sense of discovery. The audience’s shift from spamming to strategic play underscored the importance of clear communication and visual cues, which became a critical design takeaway. The score, little visual feedback, and immersive sound design were particularly valuable, as they showed how subtle but intentional details could dramatically improve user experience. If I had more time, I would have refined several aspects, such as improving the aesthetic appeal of the door and aligning the gun design with the game’s theme by creating a space gun rather than a cardboard pistol. I would also add more levels to the game to create a more progressive experience. I would also have added more targets, adjusted the randomization to prevent aliens from reappearing in the same location, and ensured the game reset itself properly. From setbacks, I learned the importance of iterative testing to uncover unexpected user behaviors, which is essential for refining any interactive system. Ultimately, this project has distinct value in illustrating how thoughtful design choices, informed by user feedback and iterative improvement, can transform technical execution into an experience that captivates and delights its audience, while also deepening my understanding of interaction design.

E. DISASSEMBLY:

F. APPENDIX

Creation of Backdrop and Gun

Arduino Code:

Processing Code:

import processing.serial.*;
import ddf.minim.*;

PImage backgroundImg; 
PImage aliveSprite, deadSprite; 
Serial myPort; 
Minim minim; 
AudioPlayer gameOverMusic, backgroundMusic, bloodSound, shootSound, hitSound, missSound; // Sound players

Alien[] aliens; // Array of aliens
int activeAlienIndex; // Index of the active alien
String feedback = ""; // Current feedback to display ("HIT" or "MISS")
int displayTime = 1000; // Time to display the message in milliseconds
long messageStartTime; // Timestamp of the last message

// Feedback delay
boolean feedbackPending = false; // Whether feedback is waiting to be shown

// Score and timer
int score = 0; // Initial score
int gameDuration = 30000; // Game duration in milliseconds (e.g., 30 seconds)
long gameStartTime; // Time when the game starts
boolean gameOver = false; // Game over state
boolean gameStarted = false; // Game start state

// Start Screen
boolean showStartScreen = true; // Tracks whether the "Shoot anywhere to start" screen is active

// Tutorial
boolean tutorialActive = false;
Alien tutorialAlien; 
boolean tutorialComplete = false; 
long tutorialStartTime; // Timestamp when the tutorial starts
boolean showTutorialAlien = false; // Controls when the tutorial alien appears
String tutorialFeedback = ""; // Feedback during the tutorial ("HIT" or "MISS")
long tutorialFeedbackStartTime; // Start time for showing feedback. Online resources for learning "long"
int tutorialFeedbackDisplayTime = 1000; // How long to display the feedback (in milliseconds)

//Gameover reset
long gameOverStartTime = 0; // Time when the game over screen starts

void setup() {
size(1920, 1080);
backgroundImg = loadImage("background.png");
aliveSprite = loadImage("alive.png");
deadSprite = loadImage("dead.png");
println(Serial.list());
myPort = new Serial(this, "/dev/cu.usbmodem14401", 9600); 
myPort.bufferUntil('\n');

// Initialize Minim and load sounds
minim = new Minim(this);
shootSound = minim.loadFile("shoot.wav"); 
hitSound = minim.loadFile("ding.wav"); 
missSound = minim.loadFile("miss.wav"); 
bloodSound = minim.loadFile("blood.mp3"); 
backgroundMusic = minim.loadFile("background_music.mp3"); 
gameOverMusic = minim.loadFile("gameover_music.mp3"); 

backgroundMusic.loop(); // Play background music in a loop
backgroundMusic.setGain(-10); // Set initial volume

// Initialize aliens for main game
aliens = new Alien[5];
aliens[0] = new Alien(300, 300, aliveSprite, deadSprite);
aliens[1] = new Alien(1620, 300, aliveSprite, deadSprite);
aliens[2] = new Alien(960, 540, aliveSprite, deadSprite);
aliens[3] = new Alien(300, 780, aliveSprite, deadSprite);
aliens[4] = new Alien(1620, 780, aliveSprite, deadSprite);

// Make tutorial alien at the center
tutorialAlien = new Alien(width / 2, height / 2, aliveSprite, deadSprite);

// Set the first active alien randomly
activeAlienIndex = int(random(5));
}

void draw() {
image(backgroundImg, 0, 0, width, height); // Draw the background image
filter(BLUR, 5); 

if (showStartScreen) {
// Starting screen
fill(255);
textAlign(CENTER, CENTER);
textSize(72);
text("SHOOT ANYWHERE TO START", width / 2, height / 2);
textSize(36);
text("Press the button and aim anywhere on the screen", width / 2, height / 2 + 80);
} else if (tutorialActive && !tutorialComplete) {
// Tutorial screen
long timeElapsed = millis() - tutorialStartTime;

if (timeElapsed < 5000) { // During the first 5 seconds
fill(255);
textAlign(CENTER, CENTER);
textSize(72);
text("TUTORIAL", width / 2, height / 4);
textSize(36);
text("Hold the button and align the laser with the front sight", width / 2, height / 2);

// Countdown
int countdown = 5 - (int)(timeElapsed / 1000);
textSize(48);
text("Alien will appear in: " + countdown, width / 2, height / 2 + 100);

fill(255, 0, 0); // Red tooltip text
textSize(24);
text("TIP: Aim carefully to hit the alien!", width / 2, height - 100);
} else {
showTutorialAlien = true; // Enable the alien display after 5 seconds
}

if (showTutorialAlien) {
tutorialAlien.display(); // Show tutorial alien at the center

// Display feedback (HIT or MISS) if available
if (!tutorialFeedback.isEmpty() && millis() - tutorialFeedbackStartTime < tutorialFeedbackDisplayTime) {
fill(tutorialFeedback.equals("HIT") ? color(0, 255, 0) : color(255, 255, 0)); // Green for HIT, Yellow for MISS
textSize(48);
text(tutorialFeedback, width / 2, height / 2 - 150);
}
}
} else if (!gameOver) {
// Main game logic
aliens[activeAlienIndex].display();

if (!feedback.isEmpty()) {
fill(feedback.equals("HIT") ? color(255, 0, 0) : color(255, 255, 0)); // Red for HIT, Yellow for MISS
textAlign(LEFT, CENTER);
textSize(48);
text(feedback, aliens[activeAlienIndex].x + 50 + 20, aliens[activeAlienIndex].y);

if (millis() - messageStartTime > displayTime) {
feedback = "";
feedbackPending = false;
aliens[activeAlienIndex].reset(); // Reset alien state
activeAlienIndex = int(random(5));
}
}

fill(255);
textAlign(LEFT, TOP);
textSize(36);
text("Score: " + score, 50, 50);
int timeLeft = max(0, (int)((gameDuration - (millis() - gameStartTime)) / 1000.0));
textAlign(RIGHT, TOP);
text("Time: " + timeLeft + "s", width - 50, 50);

if (millis() - gameStartTime >= gameDuration) {
gameOver = true;
gameOverStartTime = millis(); // Record when the game over screen starts
}
} else {
// Game over screen
fill(255, 0, 0);
textAlign(CENTER, CENTER);
textSize(96);
text("GAME OVER", width / 2, height / 2 - 100);
textSize(48);
text("Final Score: " + score, width / 2, height / 2 + 50);

// Countdown to return to the start screen
int countdown = 5 - (int)((millis() - gameOverStartTime) / 1000);
if (countdown > 0) {
textSize(36);
text("Returning to Start in: " + countdown, width / 2, height / 2 + 150);
} else {
resetGame(); // Reset the game state and return to the start screen //Did not work completely
}

// Switch to Game Over music
if (backgroundMusic.isPlaying()) {
backgroundMusic.pause(); // Stop background music
}
if (!gameOverMusic.isPlaying()) {
gameOverMusic.loop(); // Play Game Over music in a loop
}
}
}

void resetGame() {
score = 0;
gameOver = false;
gameStarted = false;
showStartScreen = true;
tutorialActive = false;
tutorialComplete = false;
feedback = "";
feedbackPending = false;
activeAlienIndex = int(random(5)); // Randomize the first alien

// Stop Game Over music
if (gameOverMusic.isPlaying()) {
gameOverMusic.pause();
}

// Resume background music
if (!backgroundMusic.isPlaying()) {
backgroundMusic.loop();
}

// Reset tutorial alien to its initial state
tutorialAlien.reset();
}

void serialEvent(Serial myPort) {

shootSound.rewind();
shootSound.play();

// Transition from the "Shoot anywhere to start" screen to the tutorial
if (showStartScreen && input.matches("(HIT|MISS) [1-5]")) {
showStartScreen = false;
tutorialActive = true;
tutorialStartTime = millis(); // Start the tutorial timer
println("Transitioning to Tutorial...");
return;
}

// Tutorial logic
if (tutorialActive && !tutorialComplete && showTutorialAlien) {
if (input.equals("HIT 3")) {
tutorialFeedback = "HIT"; // Display HIT feedback
tutorialFeedbackStartTime = millis();
tutorialAlien.setDead(); // Set tutorial alien to dead state
tutorialComplete = true; // tutorial as complete
tutorialActive = false;
hitSound.rewind();
hitSound.play();
bloodSound.rewind();
bloodSound.play(); // Play blood.mp3
println("Tutorial Completed! Game Starting..."); // Did not work
gameStarted = true;
gameStartTime = millis();
return;
} else if (input.equals("MISS 3")) {
tutorialFeedback = "MISS"; // Display MISS feedback
tutorialFeedbackStartTime = millis();
missSound.rewind();
missSound.play();
println("Tutorial: MISS Detected");
return;
}
}

// Main game logic
if (!gameStarted && input.matches("(HIT|MISS) [1-5]")) {
gameStarted = true;
gameStartTime = millis();
return;
}

if (!feedbackPending) {
if (input.equals("HIT " + (activeAlienIndex + 1))) {
feedback = "HIT";
feedbackPending = true;
messageStartTime = millis();
aliens[activeAlienIndex].setDead(); // Set alien to dead state
hitSound.rewind();
hitSound.play();
bloodSound.rewind();
bloodSound.play(); // Play blood.mp3
score += 7;
} else if (input.equals("MISS " + (activeAlienIndex + 1))) {
feedback = "MISS";
feedbackPending = true;
messageStartTime = millis();
missSound.rewind();
missSound.play();
score -= 1;
}
}
}

class Alien {
float x, y;
PImage aliveSprite, deadSprite;
boolean isDead;

Alien(float x, float y, PImage aliveSprite, PImage deadSprite) {
this.x = x;
this.y = y;
this.aliveSprite = aliveSprite;
this.deadSprite = deadSprite;
this.isDead = false;
}

void display() {
float spriteWidth = 200; // Adjust width here
float spriteHeight = 250; // Adjust height here

if (isDead) {
image(deadSprite, x - spriteWidth / 2, y - spriteHeight / 2, spriteWidth, spriteHeight);
} else {
image(aliveSprite, x - spriteWidth / 2, y - spriteHeight / 2, spriteWidth, spriteHeight);
}
}

void setDead() {
isDead = true;
}

void reset() {
isDead = false;
}
}

 

SPRITES:

 

BACKGROUND:

SOUND EFFECTS:

BACKGROUND MUSIC:

 

 

 

PERFORMANCE: TIDE – AI

Members: Alice, Constance, Tim, Yancy

---

The intention of our artifact was to create a device that limits other device usage by tying its usability to how often the user interacts with other people. Once time runs out on the device, it will shut down all of the user’s other devices. The devices would then turn back on and recharge once enough socialization has occurred.

The strengths and limitations of the artifact were presented through our demonstration.

---

SUCCESSES OF ARTIFACT:

The device successfully addresses one of the primary issues presented in the “Connection Paradox” prompt by solving the feeling of disconnection that can result from being constantly online. Our artifact remedies this by requiring people to socialize with other individuals for a specified duration to extend use of their devices. This ensures that connections between real-life human beings still occur and remain important.

While able to solve the problem of being chronically online, digitally addicted, and encouraging in-person socialization, the artifact has numerous limitations.

FAILURES OF THE ARTIFACT:

Main Problem:
I feel that the type of connection made by this artifact is not necessarily authentic. People are primarily motivated to socialize with others because they want to use their devices, which could take away from forming meaningful social interactions. However, despite this potential issue, the main purpose of the device is to create opportunities for developing meaningful connections with people. Although there may be some initial resistance from those just wanting to use their devices, with time, people may adjust to the new government mandate requiring installation of TIDE AI and gradually develop habits of forming meaningful connections as they go outside to recharge their devices through socialization.

Others:

As noted in our script, the economy could also be initially impacted. As individuals adjust to disconnecting from devices to socialize outdoors, significant modifications would need to be made to lifestyle routines in order to adapt to the constraints introduced by this technology’s implementation. This appears to be a temporary limitation arising from the product, but one that could be addressed over the longer term as habits adjust. People would need to restructure how they structure their daily lives and schedules to accommodate the need to interact face-to-face when seeking to use digital devices. While challenging at first, over time as social norms and expectations change, the flow of everyday living could smooth out to align with the new parameters in place around technology utilization.

---

RELATION TO “INTERACTION”

In my research, interaction was defined as “as a dialogue between an audience and an artistic work through direct engagement and action…The role of the artist is to “set the stage” by carefully considering how to facilitate interaction without dictating interpretation”.

Our team selected the “Connection Paradox” design prompt to develop our artifact in response to. Given that, I believe our artifact relates well to existing forms of social interaction identified in the definition. For example, during our presentation the professor commented that initially he was unclear on what our device was meant to be. However, through our demonstration we were able to tie everything together to clearly illustrate the intended purpose and function of the product. Even his early uncertainty represented a kind of interaction with our presentation, which then served to resolve any questions about how our solution aimed to address the connection issues presented by the prompt. This suggests our artifact aligned with established interaction norms while also effectively conveying its value proposition, showing how it could help to resolve the paradox described.

our lovely professor in question

While our artifact related to established interaction norms, it could have better communicated its capabilities. Like the professor’s initial confusion, the audience may not have realized without our demonstration that the device implanted within the body and could open to reveal an emergency button. Only through watching our performance portraying intended use did its proper function and operation become clear. Rather than the design intrinsically indicating its features, understanding relied more on our supplemental presentation. This suggests the product itself was not fully self-explanatory and required less explanation through improved communication of its affordances in form alone.

first iteration of product (no emergency button. no proper coloring)

However, technology that far in the future may inherently be less intuitive, as norms will have shifted from today. Being set in 2124, over a century from now, people’s natural habits for interacting with devices may have changed dramatically by that point. As such, what seemed unintuitive now could align well with expectations of that more advanced era. Given the substantial technological progress likely to occur between now and then, it is difficult to see what forms of communication and instruction would be standard. Our artifact, while requiring explanation presently, could very well mesh appropriately with norms of its own period far in the future.

---

SHOWCASING DETAILED ARTIFACT INTERACTION

While our performance effectively showcased the artifact’s interactions and cleared confusion, opportunities remained. Through demonstration, we conveyed its uses and resolved others’ uncertainties. However, with aspects I would like changed discussed later, I believe its presentation could have been strengthened. Our enactment sufficiently explained interactions but room for improvement existed in how the artifact was featured.

TIDE AI performance

---

ILLUSTRATING COMPLEX NATURE OF TECHNOLOGY

Features and the Nature of our Product:
Our demonstration illustrated technology’s complex physical nature by showing the artifact implanted in the body and connecting personal devices.

How technology affects the world and yourself:
We depicted technology’s nuanced impacts. The device was displayed potentially changing socializing and relationship quality. Its effects on the economy additionally were exhibited at a macro level. Implantable technology could jeopardize privacy if data is accessible without consent. Physical interaction may also be viewed negatively if chiefly damaging businesses. While progress benefits, considering advantages and implications ensures developments aid lives without unintended effects.

---

CHANGES:

Artifact Changes
While the current artifact provides a basic representation of a futuristic implanted technology, some improvements could further illustrate its intended design as an and make it appear more polished.

• Decreasing the overall size to reflect a more futuristic style (with more compact technology prevalent).
• Additional interactive elements like buttons or sliders cut into the artifact could demonstrate how a user might control or receive feedback from the device.
• Since it is non-functional, designating a specific area for the AI would represent its auditory output abilities.
• Refining the cut lines and implementing a cleaner work in coloring would make the project appear more professionally produced.
• Making the design look more intuitive to avoid confusion on its usage.

Performance Changes

I felt our performance effectively conveyed the product’s utility, strengths, and limitations. However, developing the setting of the play could have been improved through a more “show, don’t tell” approach. Rather than narrating placing the artifact in the future- mandated by government, a news skit could have depicted this event in a more engaging manner. Additionally, the concluding summary of benefits and advantages as simple discussion lacked impact – though alternate ending scenes were not thought off, a more interactive format may have resonated better. While effective overall, enriching setting and conclusion with greater visualization could have strengthened impact of our performance and our artifact.

**Here are some random documentation shots showing the changes we made overtime

initial fabrication of artifact

cutting some stuff

artifact first taking shape

prop making

initial coloring

recolor of artifact

---

CRITICAL ANALYSIS OF GROUP (TELEPHONE)
Meeting Criteria: 9/10

The group was able to provide a direct and clever solution to the “Connection Paradox” problem. Contrasting to our project, they gave the user more control and authority in order to foster relationships that are not forced, a very smart idea with a strength that contrasts ours. 

The use of the telephone and the performance were very creative. It clearly showed how the phone works, it’s utility in connecting people, as well as the limitations that comes with it. Through the various scenes and interaction with the device, the group was able to help the audience understand the artifact clear enough.

Suggestions

Despite the wonderful performance of the group. I feel that they should have placed more emphasis on the phone itself, rather than including a VR. There is a limited amount of connectedness you can feel through VR, and being able to develop a relationship solely through talking can strengthen said relationship if both parties plan on continuing the partner they “matched” with.

Other than that, the performance and the artifacts complement each other very well and I have nothing but praise for the group. 

---

TEAMWORK/ROLES/ETC

Original Task Allocations and Roles: FROM ORIGINAL DOCUMENT

1. Research and Ideation
   • Responsible Member(s): Constance, Alice, Yancy, Tim
2. Design and Artifact Construction
   • Responsible Member(s): Yancy, Tim
3. Performance Planning
   • Responsible Member(s):  Constance, Alice, Yancy, Tim
4. Documentation 
   • Responsible Member(s): Constance, Alice

Teamwork Dynamics

Our team demonstrated effective collaboration on this project. We understood that each member would have strengths and areas for growth, so we worked interdependently to complement each other’s skills. For example, after Alice drafted the initial script, Constance meticulously revised it to better align with the assignment expectations, such as incorporating more showing over telling. I then reviewed the final script.

Given my heavier involvement in creating the Artifact itself, I opted to play a supporting role in the performance, allowing Tim to take a leading position in showcasing our product.

Throughout the whole process, open communication and feedback were priorities. We checked in frequently with one another and provided multiple perspectives on the project or goal, recognizing how valuable diverse viewpoints can be. This collaborative approach helped ensure we produced quality work by leveraging our collective strengths.

Design and Artifact Construction
In creating the artifact, while I took a lead role in directing the design, Tim provided helpful support by sending inspirational photos that I could draw from for visualization purposes. The rest of the group assisted in cutting out components from cardboard under my direction for construction. I occasionally solicited feedback from everyone, asking for their input on desirable features to include, then made adjustments accordingly based on their suggestions. Their collaborative efforts and thoughts contributed to strengthening various aspects of the final product.

Task Allocations

The task allocation was balanced reasonably well. Alice and Constance concentrated their efforts more on developing the script, while Tim and I focused more heavily on constructing the artifact, with both sides occasionally reviewing each other’s work and providing suggestions. We also aimed to distribute responsibilities evenly, such as while I committed significant time to designing the product, Tim took a larger role in the live performance section compared to my involvement, aiming to compensate so work was shared fairly across team members and skills.

Communication

Communication within the team was very effective due to a dedicated group chat created for the project. Through the chat, we often exchanged photos of our work and scheduled meetings. Additionally, we regularly convened at my dorm room where we would rehearse, progress further on the project, and enhance our relationships as a team. Both the group chat and in-person meetings permitted well-organized collaboration and strengthened unity through sharing ideas and deliberate coordination.

completed shots of all props made for the performance

---

PERSONAL CONTRIBUTIONS:

There were 3 main parts to this whole process in general, Brainstorming, Creation of Prototype, Performance

Brainstorming

For brainstorming, I proposed tackling prompt 1 as it offered the most straightforward response. I suggested ideas around limiting device usage, which Constance expanded on by outlining a gadget to deactivate all devices after a set duration. I built on her contribution by suggesting users must socialize to re-enable access. Tim and Constance then recommended physical design inspirations like the arc reactor, aiding our conceptual development of how the gadget might appear and function. Together we were able to bounce related concepts off each other to iteratively refine our artifact approach.

Creation of Prototype

I largely led the prototype development, with occasional assistance from Tim and Constance. Regarding the creation of said prototype, I designed the final design (with Tim helping visualize it), cut most of the cardboard (though the whole team assisted), assembled the design primarily on my own, made the locking mechanism, and painted it the product along with Constance. I also created props like the cardboard laptop and phones to complement the performance. Tim aided visualization while the team supported cutting, but the bulk of the making and conceptual design was carried out under my lead.

Performance
As the narrator for our performance, I also created sound effects for the scenes and played background music with the guitar. I also served as the “Tech Helper” role in the performance. By taking on more supporting roles during the live presentation, I aimed to balance out my leadership in creation of the artifacts themselves. Wanting to distribute responsibilities equally across our team, I opted to contribute in supporting roles for the performance having focused much of my work on developing the prototype.

 

me n gang

好可爱