Designing a lightweight social fashion experience from the ground up

Overview

OOTD is a social fashion app where users share their outfit of the day and engage with friends through likes, comments, and daily challenges. As the Lead Designer, I owned the product design end-to-end — from UX flows and interaction design to visual identity and core feature design — while collaborating closely with developers to bring the product to life.


This is the description of the photo

This is the description of the photo

This is the description of the photo

The Mission

Why outfit sharing needed its own space

Existing platforms like Instagram weren't built around the specific rhythm of daily outfit sharing. They were too broad, too performative, and too polished. OOTD was designed to fill that gap — a focused space where showing up daily is celebrated, and where community, not clout, is the point.


Image of original OOTD team before I was added winning Zero Waste Award at Spartahack @ MSU

OOTD team with 2 friends tabling at UMich V1 Demo Day

Image of original OOTD team before I was added winning Zero Waste Award at Spartahack @ MSU

OOTD team with 2 friends tabling at UMich V1 Demo Day

Key Terms

OOTD

Outfit of the DAy, the core sharing mechanic of this app

Engagement Loop

The cycle of post -> react -> return that drives daily active use

Alpha/Beta

Staged launch phases used to test and iterate with real users before full release

Key Terms

OOTD

Outfit of the DAy, the core sharing mechanic of this app

Engagement Loop

The cycle of post -> react -> return that drives daily active use

Alpha/Beta

Staged launch phases used to test and iterate with real users before full release

Key Terms

OOTD

Outfit of the DAy, the core sharing mechanic of this app

Engagement Loop

The cycle of post -> react -> return that drives daily active use

Alpha/Beta

Staged launch phases used to test and iterate with real users before full release

Our Research

What makes daily content apps actually stick?

The process began with lightweight competitive analysis of platforms like BeReal, Tinder, and Instagram — examining how users engage with daily content, swipe-based interactions, and community-driven feedback loops. These insights directly shaped OOTD's core interaction patterns and onboarding flow.


Research Findings

Daily Habit Formation

Apps that demand daily posting need near-zero firction to post and immediante social reward

Performance Pressure

Public metrics can discourage casual users from sharing

Discover vs. Connection

Most fashion platforms optimize for discover, not close-friend engagement

Research Findings

Daily Habit Formation

Apps that demand daily posting need near-zero firction to post and immediante social reward

Performance Pressure

Public metrics can discourage casual users from sharing

Discover vs. Connection

Most fashion platforms optimize for discover, not close-friend engagement

Research Findings

Daily Habit Formation

Apps that demand daily posting need near-zero firction to post and immediante social reward

Performance Pressure

Public metrics can discourage casual users from sharing

Discover vs. Connection

Most fashion platforms optimize for discover, not close-friend engagement

Design Approach

Building for fun, familiarity, and community!

The design direction focused on approachability over aspiration. Every interactino was chosen to feel familiar yet fresh.


— User Flows

Our Process

We mapped out the infrastructure of how we wanted the app to be layed out

FigJam of the layout of our app

FigJam of the layout of our app

FigJam of the layout of our app

Sneak peak at our Figma file

Sneak peak at our Figma file

Sneak peak at our Figma file

Insight One

How to evaluate a good outfit

Our initial idea was to have users vote on each outfit via swipe left or swipe right.




User Testing

Lets ask the audience

Though our discord community we interviewed some of our heavy and casual beta testers.


  • Was it clear what the app was for and how to use it after signing up/onboarding? If not, what was confusing?


  • What part of the app felt most intuitive or easy to use? What part felt the most confusing or frustrating?


  • Did you feel motivated to post, tag friends/locations, or interact with others? Why or why not?


  • How would you describe the app’s vibe or aesthetic to a friend? Did it feel aligned with your expectations?


  • What’s one thing you would change or improve right now to make the app better?


This is the description of the photo

This is the description of the photo

This is the description of the photo

So we changed it up

We introduced a different but familiar rating system

5 Star system

Users are able to rate each outfit out of 5 stars. This introduces nuance in rating rather than a binary like or dislike, which gives a more true relfection of the quality of outfit

5 Star system

Users are able to rate each outfit out of 5 stars. This introduces nuance in rating rather than a binary like or dislike, which gives a more true relfection of the quality of outfit

How we tackled problems with 5 star ratings

  • New posts with less 5 rated votes can result in a star average compared to outfits with lots of 4 star ratings, but does that mean the newer post deserve that 5 stars?


We introduced a Bayesian average


This is the description of the photo

This is the description of the photo

This is the description of the photo

Learnings

Moral of the story

Community over users

Treating early adopters like people, not data points, turns casual testers into invested contributors.

Ship before you're ready

A rough feature in front of real users teaches you more than any internal planning meeting ever could.

Share the journey publicly

Posting progress connected us with other builders in the same space and kept momentum alive when it was hard.

Moral of the story

Community over users

Treating early adopters like people, not data points, turns casual testers into invested contributors.

Ship before you're ready

A rough feature in front of real users teaches you more than any internal planning meeting ever could.

Share the journey publicly

Posting progress connected us with other builders in the same space and kept momentum alive when it was hard.

Moral of the story

Community over users

Treating early adopters like people, not data points, turns casual testers into invested contributors.

Ship before you're ready

A rough feature in front of real users teaches you more than any internal planning meeting ever could.

Share the journey publicly

Posting progress connected us with other builders in the same space and kept momentum alive when it was hard.

This is the caption for the picture

This is the caption for the picture

This is the caption for the picture

This is the caption for the picture