Fandango Movieclips

An app that let’s you watch endless movie trailers

Role
product designer, Carbon Five project lead

Team & Duration
ux designers, art director, researcher, product manager, and developers (12 weeks)

The Problem
Fandango had recently acquired Movieclips, Youtube’s #1 channel for movie previews. They wanted to re-launch the channel as a native Android app to debut at Comi-Con 2015. My team at Carbon Five was tasked to train Fandango’s young product team in agile processes, while augmenting their development and design teams to meet their launch goals.

The Challenge
To help the Fandango team identify and prioritize critical release features, and design a fully functioning app for Android and iOS in 12 weeks. I was also tasked with setting up processes at Fandango to help their design team work more efficiently.

Research
Fandango’s in house researcher recruited 40 participants through usertesting.com, to test competitor apps, and high fidelity prototypes, so that we could learn about:
• user sharing behavior on video apps
• how and when users watch mobile videos
• horizontal orientation usability (we solely used horizontal orientation in the app, and wanted to make sure this was not disruptive for users and/or difficult to navigate)

Team Process
I spent the first week on the project shadowing their design team of three (two junior UX designers, one art director). I did this to identify pain points for their team, and how I could help them build a process to collaborate with their product stakeholders.

The Outcome
We released native iOS and Android experiences in time for Comi-Con 2015. The app launched to four star reviews on the Google and iOS app stores.

I was also able to setup a process for the design team, which successfully allowed them to:

• Share often - meet weekly with stakeholders (NBC Universal Executives)

• Share early - show wireframes or sketches of full flows rather than visually designed single screens in isolation

• Document and share design interdependencies to non-technical stakeholders (e.g. how a button in the header on one screen would not work on another)