Euphonic Concert Discovery
HOW CAN WE FACILITATE THE PROCESS OF DISCOVERING AND ATTENDING LIVE SHOWS of FAMILIAR AND UP-AND-COMING ARTISTS?
Euphonic Concert Discovery App | UX / UI Design
Duration: 5 weeks
The concert business has steadily increased over the past several years. The boost in ticket sales can be attributed to various factors, including the rise of mobile-ticket sales, a surge in global entertainment event growth, and the influence of people who prefer spending disposable income on experiences rather than objects. Although the industry is booming, there is a lack of resources facilitating the process of finding and purchasing tickets for events.
For my User Interface Design and Development project, I chose to explore this problem space and create a potential solution for concert goers.
DATA RICH, KNOWLEDGE POOR.
In order to gain context and define the problem space, I conducted lightning interviews, surveys, and secondary research. From my research, I learned that people who go to at least one concert a month juggle several platforms to learn about upcoming events and purchase tickets as soon as they are announced (see graphs below). Respondents emphasized the need to monitor events closely because tickets especially for larger shows are often sold out within minutes, which can be attributed to bots (i.e., computer programs) and reserved tickets. Reserved tickets, which constitute up to half the available tickets on average, are ‘on hold’ for industry insiders, brokers, and ‘pre-sale events’ for non-public groups. Despite it being time-consuming and overwhelming, users insisted on monitoring various platforms to ensure they can purchase a fairly-priced ticket directly from the venue.
Rather than introducing yet another platform that artists could use to promote events, I decided to aggregate the large amount of information currently available and create a more seamless concert discovery and ticket purchasing experience.
CONCERT GOERS + CONCERT SEEKERS
People who attend shows regularly (at least once
a month) and/or frequently monitor various platforms
for upcoming events (e.g., Facebook, SongKick)
I created a high-level user flow to detail the concert goer experience and determine product features.
Design Round 1: What do users want?
LOW FIDELITY PROTOTYPES
With low-fidelity prototypes, I was interested in understanding how users learn about events, what information they seek in this discovery process, and what terms or filters they utilize in their search–location, venue, genre, artist, date, popular with friends, etc. I also was interested in evaluating the concert recommendation feature.
User Feedback Highlights
“Show me the concerts already!”
Multi-screen onboarding flow
The onboarding flow required several user inputs, from name and city to favorite
genres and artists. Users, especially those who intended to use the app to search for a specific artist or event, were frustrated by the several steps (seven, to be exact), illuminating the lack of flexibility and efficiency of use.
Additionally, users felt the screen wherein they are asked to connect social media accounts should be shown upfront and be used to auto-populate music interests. All users were comfortable signing in with an account rather than continuing as a guest in service of receiving a personalized dashboard.
“I’m not sure what these [icons] mean.”
Tab bar with icons to enable fast and easy switching between screens, and place bar at bottom to make it easier to reach on mobile devices
The icons on the bottom navigation were shown without text, thereby relying entirely on the user’s interpretation and past experiences. Some users, for example, thought the ticket icon meant where they could buy tickets while others thought it was where they could see purchased tickets.
What was more interesting was that only a few users interacted with the bottom navigation without being prompted, and some didn’t even notice it! Rather, users were navigating via content on page rather than the toggling between pages featured on the navigation bar, revealing a more linear flow. On the page, users expected the events to automatically be chronologically sorted, and preferred to browse by events popular in their social network or genre rather than artist or location.
“I don’t know where to start”
Card-based layout to aid scannability and encourage discovery
At first sight, users were overwhelmed by the amount of information on the dashboard. If they had a specific event in mind, they started in the browse section. If they did not have a specific event in mind, they started by reviewing the recommendations. Users preferred the list view for recommendations because it enabled them to clearly view the events. They preferred the grid view for browsing because it enabled them to quickly scan the available options.
On the event cards, users confirmed the key information to display: artist photo, artist name, and event date. They expected all the events to be near them, based on the earlier screens, and therefore did not require the event location to be listed upfront.
“How much are tickets?”
Clear call to action (“Buy Tickets”) with secondary information — event details and related events — listed below in a card-based layout
Users found little value in seeing a description of the concert — instead, they preferred to see a starting value for tickets, and if applicable, any opening acts.
Users also preferred to see a list of related events, not necessarily at the same venue.
To alleviate the frustration experienced by users during a multi-step on-boarding approach, I introduced a hybrid login with social media (Spotify or Facebook) or e-mail (to ensure accessibility).
First-time users who sign in via Spotify or Facebook only need to fill out one screen — location — before seeing their personalized dashboard. Artist and genre preferences would be gathered through the platforms and be used in the customization of the dashboard.
In order to facilitate a more seamless and intuitive navigation within and between pages, I included a side menu that expands when needed rather than a fixed bottom navigation bar to toggle between the three main components of the app: events, purchased tickets, and favorited artists, genres, and venues. I also included a tab bar for navigation within each page, as shown on the screens below.
Dashboard > Recommendations
To avoid overwhelming users with too many options and facilitate user flow, I chose to utilize a card-based layout that displays key information at-a-glance and features a larger visual to increase attractiveness. I also included a heart icon to demonstrate favorited artists.
Dashboard > Browse
The browse page includes a horizontal list for each filter (e.g., Popular with Friends) to display featured items and encourage users to see all options within the category. Users can also choose to view curated lists, such as “Up and Coming Artists”.
Check back soon for my reflection on this process, the product, and next steps!