Hoolii helps iPhone users plan casual hangouts by providing all-in-one tool to input availabilities and begin plans.
I conducted research interviews and usability tests, and I designed the invitation flow, onboarding screens, avatar creation, and the desktop version of Hoolii.
I designed the mascot and visuals for thumbnails, onboarding, and error screens.
Communication is key, especially when it comes to making plans. However, planning for group hangouts consists of back and forth messages confirming and reconfirming times, locations, and availabilities. This scrolling through message histories makes planning frustrating and difficult to follow, especially for large groups and those making plans via messaging apps.
Simplify hangout planning with an in-chat bulletin board
By creating a central platform with all plan details and options, we can make planning less stressful by eliminating the need to constantly scroll through chat histories and followup with attendees.
Hoolii simplifies the process of planning casual hangouts by being the group chat's bulletin board for availabilities and hangout details.
This first “real” team design sprint made me realize how important it is to work with other designers as we bounce off ideas, give honest critiques, and support each other in our shortcomings. We grew closer as a team and as friends, and that positive environment is where design projects thrive.Â
It was only after taking a break from UniMate that I realized how important breaks were to prevent burnout. From then on, I made mental notes to pause and step back every so often to reevaluate and breathe. Breaks are necessary to make sure a project runs and launches smoothly!
It was difficult coordinating work sessions with our schedules and the sudden change to remote work. This was our first team project as designers as well, so it took a bit to get used to working alongside designers and fostering team dynamics.
We came to realize that not all our ideas were realistic with our time frame and experience. We had many sessions where we circled back to features and discussions in hopes of implementation, but we came to understand the necessity of limits.
