Desktop & iOS

Dressr Clothing App

Tired of feeling clueless when you're getting dressed? Try Dressr!

Tasked with developing a solution to a problem people in our lives face daily, I drew inspiration from several people in my life that struggle with getting ready for work in the morning, often trying on several outfits before deciding on one. I proposed a system designed to assist users in determining what to wear for the day, thereby reducing stress, increasing efficiency and decreasing unnecessary spending.

Case Overview

Case Overview

Project Type: Responsive Web Design


Timeline: 3 Week Sprint


My Roles: UX Researcher, UX Designer, UI Designer


My Teammates: Hannah Garrett, Katlyn Maloney


Tools Used: Figma, Google Workspace, Trello

The Problem

Getting dressed before work or a night out causes people stress and takes up too much time. We have observed that existing solutions aren’t improving users’ efficiency or inspiration in utilizing their existing wardrobes. How might we help users quickly select a fashionable outfit they’re satisfied with?

The Solution

 Dressr was designed to decrease the amount of time getting ready everyday, be it for work or social outings, by helping users inventory their wardrobe and pre-plan outfits.

The Research

For the first step of our interview plan, we created a Google Forms survey that we sent to approximately 15 users. Questions ranged from how often they struggle getting dressed to what influences their outfit choices. We tailored the questions to understand what our users were frustrated with when getting dressed and how we can assist with a solution.

After sending out the survey, we conducted user interviews with three users. We used 5 of the same questions on the survey, adjusting them to be more open ended. We also asked follow up questions during the interviews to get more information from the users.

Competitor Analysis

We completed a competitor analysis on three direct competitors (Combyne, Pureple, Smart Closet), finding their advantages, disadvantages, and determining what we could do better. 


Some of our competitors focused on a social media approach where users can post outfits they have created and share those with other people in a community. This seemed to be more of a distraction and an afterthought than a benefit to the apps. 


All of our competitors had a lot of ads and/or poor user experience and interfaces that lacked anything exciting or new. There was a lot of room for improvement.

We completed a competitor analysis on three direct competitors (Combyne, Pureple, Smart Closet), finding their advantages, disadvantages, and determining what we could do better. 


Some of our competitors focused on a social media approach where users can post outfits they have created and share those with other people in a community. This seemed to be more of a distraction and an afterthought than a benefit to the apps. 


All of our competitors had a lot of ads and/or poor user experience and interfaces that lacked anything exciting or new. There was a lot of room for improvement.

We completed a competitor analysis on three direct competitors (Combyne, Pureple, Smart Closet), finding their advantages, disadvantages, and determining what we could do better. 


Some of our competitors focused on a social media approach where users can post outfits they have created and share those with other people in a community. This seemed to be more of a distraction and an afterthought than a benefit to the apps. 


All of our competitors had a lot of ads and/or poor user experience and interfaces that lacked anything exciting or new. There was a lot of room for improvement.

Affinity Diagram

We compiled our research into an Affinity Diagram, organizing the results into four categories: Frustrations, Occasions, Organization/Filtering, and Suggestions/Inspirations:

User Insight & Persona

Through the distribution of our survey and individual user interviews, we discovered that the majority of users struggle to decide what to wear at least 2-4 days a week and primarily choose what to wear based on occasion/situation. Therefore, users may benefit from an app that enhances their organization and inspiration practices when it comes to getting ready for the day.


Meet Shelby Krane. She taught us that users want to wear clothes they already own in a stylish way.

Storyboard & User Flow

The team did some brainstorming and landed on two key features to focus on: cataloging and organizing users’ clothing items, and being able to combine items into visually displayed outfit. We developed a storyboard and user flow that would put these features into action as efficiently as possible:

I spearheaded developing the user flow, breaking it up into basic onboarding, a process for adding new clothing items to the app, and one for assembling an outfit.

I spearheaded developing the user flow, breaking it up into basic onboarding, a process for adding new clothing items to the app, and one for assembling an outfit.

Wireframes

Next we began laying out the UI elements that would facilitate our features and their related work flows:

We built our basic wireframes using our newly established flow and navigation. This included the event calendar and account creation pages.

Design Style

Dressr’s style has a warm, vintage 70s tone which is accomplished through color and typography. Rounded lines and bold patterns throughout the design contribute to the sleekness and visual interest on various pages. 

Usability Testing and Iterations

After conducting multiple usability and A/B tests and reviewing and organizing our user testing notes, we laid them out in a prioritization matrix to see what changes and updates we needed to focus on first and which ones could come later. We decided to focus on fixing the mannequin process, adding confirmation screens at the end of work flows, and the tone of copy

Before

After

Final RWD Prototypes

Additional changes made after another round of mid-fidelity testing were removing the navbar from the homepage, as users determined they wouldn't need to navigate back to the onboarding flow, and our hamburger menu was redundant with the homepage buttons. The hamburger menu stayed in on other screens, as users said they might want to switch work flows at will.

Concerning the desktop version, the team realized that some of the app's functionality would not translate to a laptop or desktop computer. Instead, I designed a landing page that encourages the user to download the app. I also added additional functions and information to the homepage, such as the weather report and being able to schedule what outfits the user would wear for the week, and included a "Sync To App" button that would allow uploading items added via the phone.

The Result

Future steps would be to build out the features in the mobile app we identified as valuable but recognized there wouldn't be enough time to get to, such as the calendar and weather-based suggestions, and fleshing out some more of the desktop version's functionality.


Dressr's mission was to allow users to get dressed efficiently by helping them organize their wardrobes and plan outfits, giving them more free time in their lives and confidence that they look good. We succeeded by effectively working as a team on every aspect of the development, from research and feature brainstorming, through the testing and design. Challenged with wildly different personal time constraints, we overcame that by openly and constantly communicating, identifying and playing to each other's strengths, and being truly accepting of the groups ideas and decisions.

Let's make something.


Shoot me an email at chefdonjorge@gmail.com


Find me on LinkedIn

Resume


630.280.9212


George Lomotan© 2023

Resume


630.280.9212


George Lomotan© 2023

Resume


630.280.9212


George Lomotan© 2023