Breeze

Reflection Question #1
Reflection Question #2
Mini-Game #3

Inspiration

Reflection and meditation on our daily lives are becoming increasingly more significant tools in mental health and wellness spaces; the influx of data and the pressures of life, however, can sometimes make it difficult to feel grounded and create a routine around this. As students with busy class schedules and work, our team understands the feeling of wanting to check in with ourselves but having a hard time finding the time or energy. We designed Breeze to flip the script about mobile devices and internet use by creating an application that offers an accessible and individualized platform for people to engage in this daily reflection in a user-friendly and lighthearted way.

What it does

Breeze is a fun game where the users reflect upon and savor the joyful moments of their day, and ruminate on the possible setbacks. The purpose of the game is to encourage users to sit with themselves for a moment and enjoy the process of examining the day and its range of emotion and energy. The gameplay offers simple and artful side-scroller features with opportunities to collect points to be used to further customize the experience. By providing a unique journal system combined with a simple and fun series of games, users will find their daily reflection to be an accessible and pleasant experience.

How we built it

We developed a 2D video game in Unity by creating scenes and C+ scripts, exploring integrations with Firebase Auth, and exporting our project as WebGL to host it on itch.io.

Challenges we ran into

We struggled to integrate Unity with Firebase Authentication due to incompatibility issues.

Accomplishments that we're proud of

Creating a user-centered game that improves mental health and encourages conversation with oneself! Designing aesthetic scenes with Unity while experimenting with Firebase and Velo by Wix. Working on a team with a range of skills and joining forces to create a project we love and are proud to have made!

What we learned

We learned to create a multi-level game in Unity and discovered new technologies that are suitable for each stage of the app development process; we learned to implement the basics of gameplay–collisions, creating and navigating between scenes, etc.

What's next for Breeze

There are many other ideas to pursue! For one, using Spotify's API to personalize a daily song suggestion based on user input and offer monthly playlists based on the cataloged data. Another is to increase the number of mini-games and questions while developing our back-end with Firebase Realtime Database so the player can see a monthly summary of their mood fluctuations and personal growth.

We are excited to expand the functionality of Breeze. Our goal is to make the user experience as pleasant and breezy as possible!

Built With

Submitted to

HopHacks Fall 2022
- Winner Best Use of Velo by Wix
- Winner Best Use of AR App (Quest2Learn)
- Winner Best Use of Unity (Quest2Learn)

Created by

I helped design the video game by using Unity for my first time and exploring other tools like Firebase and Velo by Wix.

Annika Lin
Senior studying CS/Econ at Georgetown University
I worked on designing and implementing scenes in Unity; as an animation/computer science major, this project was so much fun for me! I worked on setting up the scenes and navigation system, built asset libraries, worked on the gameplay aspects and the aesthetics of the game, etc. I have experience creating VR/XR games and simulations in 3D, but this was my first 2D project!

Margaret Neely
Interdisciplinary Studies major in Art, Film and Computer Science at Georgetown University
I worked in Unity to build the game! My primary focus was on the C# scripting, but I also did a lot of asset work, including all the audio editing. My magnum opus is the collectible bones in the game into which I poured blood, sweat, and bone. I would die for our little dinosaur and I like to imagine that each collectible bone comes from someone who tried to cross him.

Palmer Hudson
I worked with the back-end data components, including the creation of Player and Game classes that would separately store data for each individual and day on which they played while conducting verification of variables to ensure that one did not "overplay" on any given day while also storing all information for future reference.

Anthony Duan