Project Overview

Introduction

“Evar.ware“ is a music events app that combines informational, ticketing, and social aspects into one app. It aims to give newcomers and regular ravers alike the opportunity to form and engage in communities, and share music in a way that is safe and fun.

My Role

UX/UI Design, Research, Visual design, Prototyping, Testing

Tools

Figma, Zoom, Google Forms

Goal

The goal of this case study was to make a hi-fidelity prototype of an events app. In local rave communities, the informational, ticketing and social aspects are disconnected. Also, there are many miscommunications between event goers and promoters. The target audience is local music event goers and collectives. Newcomers to the local events scene were important because the barrier to entry can oftentimes be daunting.

Competitive Audit

I began the project with an exploration of current market trends and user needs by conducting a competitive audit of three other local music events apps. This audit gave me a sense of the pros and cons of existing apps, as well as their target audiences and value propositions.

Survey/Interviews

To gain a better understanding of the community, I first conducted a survey to get a broad insight into users’ pain points with existing user flows. From there, I selected a few participants to interview in depth, allowing me to focus on individual experiences. I wanted to understand:

• What are the primary challenges rave-goers face in their user journey for a night out?
• What features would users find valuable in an rave events app?

After conducting user interviews, I compiled results highlighting the most prominent challenges and features. Many participants expressed concern about the multiple apps being used in the scene, causing a disconnect or lack of communication between collectives and event-goers.

<aside> 📌

primary challenges

• Constant switching between multiple apps
• Lack of communication between collectives + event-goers
• Concerns about safety, especially within BIPOC and LGBT communities
• Difficulty breaking into the scene and finding friends
• Issues with refunds/ticket transfer </aside>

<aside> 📌

desired features

• To access information quickly and efficiently
• To feel safe at raves and have BIPOC and LGBT-friendly spaces
• Be able to share event photos in events folders </aside>

User Personas

With these results, I created user personas to represent primary user groups. By imagining the user journey these personas, I was able to better understand the preferences of the average events app user.

Luca

age: 26

pronouns, gender: he/him, trans-masculine

occupation: babysitter, student

family: single, two roommates

location: Chicago, IL

• about

<aside> 📌

challenges

• Frustrated by the constant switching between multiple apps
• Lack of communication between collectives + event-goers
• Issues with refunds/ticket transfer </aside>

<aside> 📌

goals

• To access information quickly and efficiently
• To feel safe at raves and have LGBT-friendly spaces </aside>

May

age: 24

pronouns, gender: she/her, woman

occupation: artist

family: living with partner

Location: Chicago, IL

• about

<aside> 📌

challenges

• Unsure how to break into the local scene
• Struggles to find time to navigate event information </aside>

<aside> 📌

</aside>

Scoping

As an app combining multiple components, there were multiple features I wanted to incorporate.

Paper Wireframes