Do you find yourself consistently wearing the same few clothing items while neglecting others in your wardrobe? This project aims to address this common user struggle through the design of a user-friendly app.

Using Figma, I perform a UX workup including surveys, interviews, personas, and user flows. Once I have a fount of user information, I wireframed the app and built a usable prototype in Figma.

To gain insights into users' dressing habits and motivations, I conducted both online surveys and in-person interviews with friends and acquaintances.

The interviews were enlightening, and encouraging. Here are some highlights.

The initial research phase revealed varying levels of user engagement with wardrobe organization and style. By crafting user personas, empathy maps, and user flows, I identified distinct user groups.

In crafting personas for Dressure, Lara emerged as a pivotal figure. Her fashion-forward mindset influenced the app's design, balanced with a commitment to inclusivity for users like John S.

Anchoring decisions around Lara's needs, Dressure empowers users to navigate wardrobe choices confidently. The app's features facilitate experimentation and self-expression, ensuring accessibility for all users, regardless of their fashion expertise.

To help construct an MVP list, I did a competitive analysis of five services. Here's a breakdown of the three most relevant.

My competitive analysis confirmed that the concept was strong, and that there was room to compete. Functionality and productivity would be most important to this app.

I sat down with a pad of Bristol paper and drew out key screens.

Once I had my laughably-not-close-to-16-by-9 sketches, I began to wireframe in Figma.

In early designs, I aimed for a harmonious blend of sophistication and friendliness. I selected shades of blue-green and orange to evoke vibrance and elegance, avoiding colors used by competitors. The chosen typefaces, Merriweather and Work Sans, prioritize readability and versatility.

As the project progressed, the visual design became more sophisticated. I created a component library, and revised my style guide. I switched the type to San Francisco for a more sleek look, and even better readability and versatility.

From the navigation, users can always access the Create screens. Create (Item) is selected by default, but changing the dropdown can bring you to the three other screens: Create (Outfits), Create (Collections), and Create (Events). These screens vary by the content they facilitate.

For example, Create (Item) features an upload link. In my imaginary app, our fabulous dev team implemented automatic background removal for item uploads.

Additionally, Create (Outfit) features an extra button to visit the Outfit Preview screen. This screen lays selections together for users to help them analyze their outfits and save time trying out combinations.

From the navigation, users can always access the Create screens. Create (Item) is selected by default, but changing the dropdown can bring you to the three other screens: Create (Outfits), Create (Collections), and Create (Events). These screens vary by the content they facilitate.

The Home Screen greets users, provides them an immediate reminder of their scheduled outfits, and then provides helpful analysis and statistics on their wardrobe.

The Calendar visualizes a users scheduled events, and even prompts them to create more.

I conducted user testing with an initial participant. The user successfully navigated the app and expressed enthusiasm for its potential usefulness.

Subsequent refinements will include additional screens such as Date screens that show all events scheule on a given date, and upload and error screens.