Case Study

UI/UX

Mezur

The Challenge

I had a client come to me with a problem. She was a seamstress managing multiple concurrent projects for a growing list of clients. Her success had created a new bottleneck: organizing and retaining accurate measurements. Too often she’d show up to a fitting only to realize she’d missed key data, or worse, lost it entirely. She needed a better system. Not another paper scrap or half-filled note. Something centralized. Something usable.

When I showed her the early workflow, she responded:

"Yoooo that looks awesome. The workflow sounds exactly like what I was hoping for!"

That's when I knew we were on the right track.

Discovery & Research

User Persona - Kat Fiero

  • Age: Mid-thirties

  • Education: GED

  • Status: Married

  • Occupation: Seamstress

  • Location: Las Vegas

  • Tech Literacy: High

Bio

Kat is a skilled seamstress and maker based in the southwest, specializing in custom clothing and cosplay commissions for both friends and clients. Highly creative and detail-oriented, she juggles multiple artistic hobbies that demand strong organizational systems to manage her time, materials, and project workflows effectively.

Core Needs

  • Store and manage individual client measurements for future use

  • Create reusable measurement templates tailored to specific garment types

  • Quickly identify which measurements are missing for any given project

Frustrations

  • Forgets which measurements she’s already taken for returning clients

  • Worries about seeming disorganized or unprofessional

  • Lacks an easy way to determine which measurements are needed for different garment types

Empathy Map

User Does

  • Writes measurements on paper scraps or notes app

User Thinks

  • What measurements did I already take?

  • What measurements am I missing?

  • Where did I save the measurements I have?

  • What measurements are needed for specific clothing?

User Feels

  • Unconfident

  • Confused

  • Curious

  • Excited

User Says

  • “I keep losing track of what measurements I have”

  • “I don’t want to bother my clients“

  • ”I know I had their measurements somewhere, I just don’t know where I put it”

Journey Mapping

Making a Shirt for a New Client

Stage

Goal

Actions

Thinks

Feels

Pain Points

Opportunities

Open App

Quick access to tools

Launches app, logs in

"Hope this doesn't take long."

Neutral

Login friction

Auto-login, Face ID support

Add Client

Store new measurements

Taps Add Model, enters name

“Let’s set this up now.”

Focused

May forget style preferences

Prompt: "Add client notes/preferences?"

Select Garment

Load required measurements

Chooses Shirt template

“Which ones do I need?”

Slightly unsure

Doesn’t know what’s required

Visual checklist, garment-specific templates

Take Measurements

Complete data entry

Fills fields while measuring

“Did I get everything?”

Cautious

Skipping/duplicating fields

Dynamic progress bar + "You're missing these" alerts

Save & Confirm

Store info for reuse

Hits save, sees confirmation popup

“Done for now.”

Confident

Fear of data loss

Auto-sync, reminder to set follow-up fitting

Reuse Later

Leverage old data for new garments

Loads client profile, selects new garment

“Do I need anything else?”

Productive

Unsure if more info is needed

“Only 3 more measurements! Add the rest now?” contextual prompt

Information Architecture

Model Profiles

  • Create, read, update, delete

  • Stores name and known measurements

  • Can optionally toggle to show unknown measurements

Garments

  • Create, read, update, delete

  • Stores list of required and optional measurements

  • Shared among model profiles

  • Auto-flags if required data is missing

Measurements

  • 25+ tracked fields with detailed descriptions

  • Organized by body region (neck, bust, arm, leg, etc.)

  • Measurement templates for Shirts and Pants

Prototyping

Flowchart

user journey flowchart


The client asked for a simple way to track measurements across people and garments. At first glance, the data seemed straightforward, but once I began digitally mapping the process, the underlying complexity came into focus. There were multiple use cases, each with its own needs.

To simplify the experience, I split the app’s architecture into two primary flows: the Model Workflow and the Garment Workflow. This gave users the flexibility to either focus on capturing measurements for individuals or to build garments and flag what was missing.

Crucially, I designed both workflows to interconnect fluidly. No dead ends. If a user started from a model but wanted to begin a garment project; the transition was intuitive and seamless.

Low-Fidelity Prototype / Wireframe

Before adding polish, we needed proof of concept.

The low-fidelity prototype was a critical step in validating the core structure and user flows of the app without getting distracted by visuals or UI refinements. In the spirit of Design Thinking, this phase emphasized ideation and rapid iteration. Wireframes allowed us to quickly simulate real user behavior, test assumptions, and identify gaps in logic or flow before investing time in high-fidelity design or engineering.

This approach minimized risk, reduced potential technical debt, and saved effort by exposing dead ends, redundant steps, or underused features early. Every decision here shaped the final product’s clarity, usability, and effectiveness. By focusing on function first, we laid the groundwork for a user experience that felt intentional. Not improvised.

low fidelity prototype of the mezur app

Branding, Visuals, and UI

As a designer, functionality isn’t enough. This app needed to feel inviting. Seamstresses work in tactile, detail-rich environments, so I drew inspiration from cozy, craft-driven aesthetics like Animal Crossing and Stardew Valley. The result is a visual language rooted in softness: paper textures, cloth tones, and subtle UI elements that never overwhelm.

This wasn’t about whimsy for whimsy’s sake, but about creating a calm, focused workspace, which is especially important in a data-heavy app. The final design uses generous whitespace, warm neutrals, and lightweight visual cues to reduce fatigue and keep the experience approachable, even during long sessions.

Branding Notes:

  • Animal Crossing × Stardew Valley aesthetic

  • Paper and cloth-inspired textures

  • Calm, unobtrusive UI

  • Designed to support long-form use with reduced eye strain

High Fidelity Prototype

With the visual direction locked, I moved into systems thinking. I established design tokens, reusable components, and scalable layout patterns early, this let me build high-fidelity screens quickly without sacrificing consistency. The result was a fully interactive prototype that not only showcased clean typography and thoughtful whitespace, but also served as a practical foundation for developer handoff and future iteration.

See the Figma File

See the Figma Prototype

Final Thoughts

Once the app was in use, it quickly gained traction within the client’s network. Word spread among fellow seamstresses and makers that this tool addressed a real, shared pain point: managing multiple clients, garments, and measurement sets without chaos.By centralizing key workflows into a single, intuitive interface, the app gave users more than just organization. It gave them confidence. It freed up mental bandwidth, increased efficiency, and positioned them to take on more clients with greater professionalism and ease.



© 2025 Anthony D. Humphreys Jr. All Rights Reserved.