Fandango Events

 

 
 

OVERVIEW

Problem

Fandango wants to create a new application featuring local events, as there is no current user-friendly application where users can seek events, share them, buy tickets, and enter; all in once place. 

Solution

To create a mobile application redesign for Fandango, featuring local events. A user will be able to: (1) find events, (2) buy tickets, (3) share with friends, and (4) get into an event using the QR code in the app.

Tools

Whiteboard, Pen & Paper, Sketch, Axure

Project Duration

2 weeks


research

Comparative Analysis

     IMAGE EXPLAINED:       After we analyzed seven other event-related applications, we wrote down all the features, functions, and designs we came across on post-it's. We then categorized them into "Must-Have", "Should have", "Could Have", and "Won't Have", for our application. 

 

IMAGE EXPLAINED:

After we analyzed seven other event-related applications, we wrote down all the features, functions, and designs we came across on post-it's. We then categorized them into "Must-Have", "Should have", "Could Have", and "Won't Have", for our application. 

Our thought process: To eventually conduct surveys and find out what our users wanted from the should, could, and must haves that we listed.  

Surveys

One crucial part of our research process was conducting surveys, eventually leading to one persona, representing the result majority.

Our goal of handing out these surveys was to yield valuable findings on what features our persona would use the most, how, and why. 

I created visual depictions of our survey results, to make the findings clear and concise:

Findings

The surveys revealed: (1) The value and need for this application, (2) What features were most wanted, (3) Search filtering options, and (4) The importance of an interactive application with social media / sharing. 


persona

Our designs were based on a persona, created from our survey results.

Sadiya is young, social, tech savvy, and goes to events often.

Goals

When Sadiya uses the app, she wants to: 

1. FIND EVENTS

2. SHARE EVENTS

3. BUY TICKETS

4. ACCESS & ENTER

Finding A Solution

As UX designers, our ultimate goal is to make sure Sadiya's painpoints will be solved by giving her all the right solutions. 

Sadiya's painpoints were to be solved by having a user-friendly mobile app where she can: (1) Customize events to her interests, (2) Narrow down event types based on filters (time, venue, location, price, etc.), (3) Share easily, and (4) Send easy pay-me-back reminders for her friends.


Scenario & User Flow

Scenario

Sadiya's friends are coming to visit her in LA from out of town. She would love to take them to a concert while they're here. She opens the Fandango Events app. She has an existing account with Fandango for movies, so her account information and social media accounts are already connected. She opens the "EVENTS" feature, and gets taken to an onboarding process. 

User Flow

  IMAGE EXPLAINED:     Sadiya opens the app and receives onboarding with a value proposition. She then picks her interests, so the app can reveal only events that are customized to events she likes.      She hits the homepage and filters events by: (1) the necessary time period, (2) the cost ("free" or "all"), and (3) the type. She chooses an event, see's "Who's Going", and shares it through text message with her friends coming to town, to make sure they want to go, too.     Once they confirm (not pictured), she opens the app again to buy the tickets. She recieves a confirmation, and then sends pay-me-back reminders to her friends.     *She can eventually access her tickets in the QR code by clicking on "My Tickets" in the navigation bar. This is not pictured, but is clickable in the prototype. 

IMAGE EXPLAINED:

Sadiya opens the app and receives onboarding with a value proposition. She then picks her interests, so the app can reveal only events that are customized to events she likes.  

She hits the homepage and filters events by: (1) the necessary time period, (2) the cost ("free" or "all"), and (3) the type. She chooses an event, see's "Who's Going", and shares it through text message with her friends coming to town, to make sure they want to go, too.

Once they confirm (not pictured), she opens the app again to buy the tickets. She recieves a confirmation, and then sends pay-me-back reminders to her friends. 

*She can eventually access her tickets in the QR code by clicking on "My Tickets" in the navigation bar. This is not pictured, but is clickable in the prototype. 


application evolution

Continuous user testing helped our flow and designs evolve, for a more user-friendly experience.

Since we had so much content, information architecture was a big factor in our design. Features, buttons, and text were constantly being moved to make it more intuitive, and to not overwhelm the user.

Here are the iterations just on our homepage, based on our users' feedback, starting with whiteboard, then pen & paper, then MyBalsamiq, and lastly, Axure. 

Below is a video of our first user test on paper prototypes, on the first day of the project: 


deliverables & next steps

  PICTURED:  Part of the onboarding process. To see the whole prototype,   test it here.

PICTURED: Part of the onboarding process. To see the whole prototype, test it here.

Through research, persona building, and testing, my team delivered high fidelity prototypes that solve all the painpoints my user experienced, allowing her to achieve all of her goals and needs.

As we only had two weeks to conduct research, create wireframes, and test prototypes, we were able to create something we are proud of...but not a finished product. Our next steps if we were to pursue this project would be to consistently test, update our designs accordingly, and  add more features our users mentioned that were not viable options at this point in time.