Remo App for Netflix June 2020

Web app prototype for the Adobe × Netflix Creative Jam, a 46-hour design sprint

Recognition: Top 10 finalist of 985 teams and nearly 700 submissions

(Clickable Adobe Xd prototype at bottom)

Problem & Objective

Prototype a non-Netflix third party web app that “celebrates shared stories through communal and authentic experiences.” How can we help families and friends utilize this platform and share their experience with content such as series television shows and movies they love, given the forced physical separation of the pandemic?


In around 46 hours, Team 808 (Angie Wijaya, Jiayi Ma and I) created and pitched Remo—derived from the word “remote” and inspired by the phrase “recapturing lost moments”. A solution, validated by 60 survey respondents, to address a critical need for users to connect and share with their communities.

Remo offered a package of three features that tackled different levels of relationship to community and entertainment: staying connected through viewing Parties with built-in video and text chat, keep discovering new content and streams with rePlug, and diving into fan culture through curated forums and followings in moFeeds.

Video Walkthrough of Final Solution


In this exercise, we knew that our team of three had to step into the shoes of several different people from product manager to designer. This spreadsheet was crucial in organization, as we allocated necessary time for ideating, researching, concept refining, identity, and building a presentation. And sleep, obviously.

Before we even began narrowing down our options for our exact product, we knew we wanted to create a prototype that mimicked the user journey of a new user, from onboarding to feature discovery, as well as priorities in building any sort of “social network”. In the final presentation and in our task, this would be easiest to prioritize our app needs in an inquiry format that sought to answer the user’s questions about the app in a systematic way.

This document was important to reference throughout our process as we needed to check against our solution for something that users had control over, while being able to guide them toward certain features. 

The first thing was creating a form to survey the needs and wants of 57 people ages 18-49, or the bulk of the demographic that streams content. From there, we could evaluate the issues people were having with existing products that accomplished some of the features we included into the application.

Next we created a full brainstormed list of features we might want to include, and used a red-yellow-green marker systems to discern features that were not either complete not viable in functionality, needed discussion, or were sure-fire. We also used this system to determine value-adds, so we could hone in on which could be the main features to build our MVP on. We then compiled the slimmed list into a “sticky note”.

After that, we began to arrange our features into certain pages that they could live on. There was a balancing act, given we didn’t want to have an interface that overwhelmed the user, but also felt intuitive toward the functionality of the web app’s features. Given the time constraints, we immediately jumped into arranging screenflows that could fit the needs of a new user, and then began iterating lo-fi wireframes.

After we constructed assets, logos, finalized typography choices and collected that into a visual identity, we began iterating our hi-fi wireframes. Along the way, we also validated our product by conducting five user testing interviews over Zoom.

After building all the screens, we connected them into a flow that allowed the judges to evaluate the onboarding experience rather than get lost into a different intended user flow. This meant that we weren’t wasting time connecting every single thing backwards to different screens, but rather in a presentation format that limited that full usuability to communicate the unique features we had come up with.

Clickable Prototype of Remo

Home ☖                 Top ⇡