← All projects
E-commerce·UX Designer·2 Weeks

AURA

Slowing the scroll for intentional style.

AURA app concept — slowing the scroll for intentional style, showing outfit compatibility match score
Problem Context

The problem in context

Fashion e-commerce is optimised for one number: conversion. Recommendation engines learn what you'll click, not what you'll actually wear. Trend feeds refresh faster than any wardrobe can absorb. The result is a generation that owns more clothes than any before it and still opens the closet each morning unsure of what works.

The interviews kept returning to the same feeling — wardrobe blindness. Users knew their closet was full, but couldn't picture what they had. So they bought again, on impulse, chasing a trend they'd already half-owned. AURA started from a stubborn premise: the real problem isn't buying clothes. It's not knowing what already works inside your wardrobe.

History

History — what came before

Every step of fashion's digital evolution optimised discovery — and quietly worsened decisions.

Fast fashion→Trend algorithms→Impulse purchases→Unused clothes→Purchase regret→Wardrobe clutter→Decision fatigue→Smarter shopping

Pinterest boards, mirror selfies, and friends on WhatsApp are the workarounds people invented because no product actually helps them decide. Recommenders solved discovery. They never solved compatibility.

More recommendations weren't the answer. Better decisions were.

Geography

Geography — where it lives

The problem lives on the phone of a 19–28 year old in urban India — college students, early-career professionals, creators. Myntra, Instagram, and Pinterest are the fashion operating system; a purchase decision is usually made in bed, in under two minutes, against a wardrobe the user can't currently see.

Friction concentrates in three places: on the product page (does this go with anything I own?), at checkout (am I sure?), and forty-eight hours later (why did I buy this?). AURA had to sit inside that journey, not beside it — mobile-first, Myntra-parity, and fast enough not to become the reason a user abandoned the flow.

Physics

Physics — forces at play

Every purchase decision is a tug-of-war between forces pulling toward the cart and forces pulling back.

Driving
  • Trend pressure and social proof
  • Fear of missing out on limited drops
  • Sale timers and price anchoring
  • Influencer aesthetics as aspiration
  • Curiosity — the pull of the new
Opposing
  • Wardrobe blindness — not remembering what's owned
  • Decision fatigue from infinite scroll
  • Doubt about fit, colour, and pairing
  • Return friction and refund anxiety
  • Guilt about unused clothes at home

AURA doesn't try to kill the driving forces — trend curiosity is human. It amplifies the opposing ones with intelligence: a compatibility score, an outfit that already uses three items you own, a moment of clarity right before "Add to bag."

Chemistry

Chemistry — what reacts together

The old loop runs on autopilot: a reel triggers desire, the app makes purchase effortless, doubt arrives after delivery, the item is worn once and forgotten. Regret quietly compounds; the next trend resets the cycle before the last one is understood.

Trend exposure→Impulse add-to-cart→Doubt→Purchase→Wear once→Regret→Repeat

AURA breaks the chain at the third link. The compatibility check surfaces beforethe doubt does — turning a private hesitation into a visible answer. Curiosity survives; the loop that ends in regret does not.

Compatibility decision tree
New item consideredScore ≥ 80Score < 80Buy with confidenceOutfit exists?No matchSuggest pairingSuggest owned alternative
Compatibility Score = wardrobe fit × style match × occasion
Biology

Biology — the living system

Shopping is a habit loop, not a decision. Cue, routine, reward — repeated until the wardrobe overflows. Changing behaviour meant changing what the reward feels like.

WardrobeUserAICompatibility scoreOutfitsRewardsSocial layer
Old loop

Trend → Buy → Wear once → Forget → Repeat.

New loop

Need → Compatibility check → Outfit suggestions → Confidence → Purchase → Reuse → Reward.

The reward shifts from the dopamine of buying to the confidence of wearing. Gamification reinforces reuse, not acquisition — the streak you're proud of is styling what you own.

Mathematics

Mathematics — the numbers

Validated in hackathon research + prototype testing
18
user interviews (Gen Z + young millennials)
12
prototype usability participants
89%
task success on compatibility flow
−42%
average decision time vs baseline
Target metrics for pilot
+38%
self-reported purchase confidence
+55%
wardrobe utilisation
−30%
reported impulse purchases
4.5/5
trust in AI outfit suggestions
Future KPIs (needs longitudinal study)
  • Repeat usage of wardrobe intelligence beyond 30 days
  • Reuse rate — outfits generated from existing wardrobe vs new purchases
  • Return-rate reduction on AURA-assisted purchases
  • Sustained engagement with the gamification loop
"I already own something like this — I just couldn't remember. That's the thing I keep needing."
— Participant, 23, prototype session 07
Design Engineering

Design engineering

Core user flow
OnboardingWardrobe ScanProduct ScanCompatibility ScoreConfident DecisionOutfit SuggestionsReuse / SavePrimary pathSecondary paths

Eight decisions shaped the product.

  • Mobile-first, Myntra-parity
    Users already know the mental model. Fighting it would have burnt every second we needed for the AURA-specific surfaces.
  • Wardrobe-first onboarding
    The first screen after sign-up isn't the store — it's the closet. The product's core signal has to exist before it can help anyone.
  • Compatibility score as first-class UI
    A single number, visible on every product card, becomes the shortcut for a decision users used to outsource to friends.
  • Outfit generation over product recs
    Recommend combinations, not items. An outfit answers the actual question — 'what do I wear this with?' — that a product page never does.
  • Gamified reuse, not acquisition
    Streaks and rewards reinforce styling what you own. The mechanic rewards the behaviour the product is trying to build.
  • Explainable AI surface
    Every suggestion carries a plain-language 'because'. Trust in AI collapses the moment it feels arbitrary.
  • Empty, loading, success, error states
    A wardrobe with three items has to feel possible, not embarrassing. Each state was designed, not defaulted.
  • Design tokens + accessibility
    AA contrast, tap targets sized for one-thumb use, and a token system so the AI surfaces still feel like the shopping app around them.
STAR

STAR — situation, task, action, result

Situation

A 2-week hackathon brief on sustainable fashion. Every competing team went straight to 'buy less' messaging. Interviews told us users didn't need a lecture — they needed a decision tool.

Task

Design a mobile-first shopping experience that reduces impulse purchases without sacrificing the fun of discovery, and prove it inside a working prototype in under two weeks.

Action

As Junior Product Designer in a team of five, I owned the wardrobe and compatibility flows. Ran interviews, mapped the impulse loop, wireframed the compatibility score, prototyped the outfit generator, and iterated twice against usability sessions.

Result

A validated concept where users made faster, more confident decisions and reported fewer regretful buys. The bigger shift was internal: we stopped designing for more purchases and started designing for better ones.

Before & After

Before & after

The shift is structural, not cosmetic.

BeforeAfter
Shopping driven by trendsShopping guided by wardrobe intelligence
No visibility into what's ownedCompatibility score on every product
Impulse add-to-cartConfident, considered purchase
Regret after deliveryReuse and remixing at home
Wardrobe clutterGamified reuse of existing pieces
Decision fatigueGuided decision in under a minute
Final Screens

Final screens

Fifteen surfaces do the work — from first launch to a purchase the user won't regret.

  • Splash
    A quiet opening — sets the tone that this is a tool for decisions, not a store racing to sell.
  • Onboarding
    Three screens that reframe the product: this app knows your closet first, the store second.
  • Wardrobe Upload
    Photo or manual add — the lowest-friction path to a usable wardrobe on day one.
  • Closet Scan
    AI parses images into categories, colours, and silhouettes so the user isn't tagging everything by hand.
  • AI Analysis
    A transparent 'thinking' state that shows what's being extracted. Trust starts with visibility.
  • Wardrobe Dashboard
    The user's closet, made searchable and browsable — often the first time they've truly seen it.
  • Product Details
    Standard Myntra-style page, with one new anchor: the compatibility score at the top.
  • Compatibility Score
    A single number plus a plain-language 'because' — the decision moment, made legible.
  • Outfit Suggestions
    AI-generated outfits that pair the product with items already in the wardrobe. This is the pitch.
  • Alternative Recommendations
    If the item scores low, the app suggests better-matching alternatives — respecting intent, not blocking it.
  • Gamification Dashboard
    Streaks, missions, and levels tied to reuse and confident buys, not spend.
  • Achievements
    Badges reward wardrobe utilisation — the metric that actually maps to buying better.
  • Purchase Confirmation
    Closes the loop with the outfits this new piece unlocks. The reward is the wear, not the ring.
  • Profile
    Style DNA, preferences, and history — the foundation the AI keeps learning from.
  • Settings
    Controls for notifications, data, and AI transparency — the user stays in charge of the intelligence.
AURA onboarding screen inviting the user to build a private 3D avatar and try clothes on before buying
Avatar Onboarding
AURA digital wardrobe with 24 synced items, outfit counts and match tags across tops, bottoms and shoes
Digital Wardrobe
AURA confidence score of 82 out of 100 with reasons the item works and AI outfit previews
Confidence Score
AURA trend decay chart showing popularity over time alongside similar fashion cycles and their duration
Trend Decay
AURA seven-day virtual wear simulation with a rent-instead option before buying
Live With It First
AURA monthly summary showing 12 impulse purchases skipped and rupees 8,000 retained
Saved, Not Spent
Learnings

Learnings

Research

The brief said 'sustainability'; the interviews said 'confidence'. Following the users, not the brief, changed the entire product.

Design

A compatibility score works only because it's a single number. Every additional layer we prototyped diluted the decision it was meant to make.

Behavioural psychology

Impulse isn't defeated by friction; it's defeated by a better answer arriving before doubt does. AURA had to be faster than hesitation.

Product

Optimising for confidence is a different product than optimising for conversion. You can't do both from the same screen — we picked.

Technical

Even a hackathon-scale AI has to explain itself. An unexplained suggestion tested worse than no suggestion at all.

Business

Buying less isn't anti-commerce. Users who trust the tool return more often and return fewer items — the economics quietly work.

Team

Five people, two weeks, one insight to defend. The value of the project came from what we agreed to leave out.

Future scope

Validate reuse and return-rate impact over a real cohort. Extend the wardrobe model to shoes, accessories, and second-hand marketplaces. Test social features carefully — the last thing this product should become is another feed.

People don't need more fashion choices. They need more confidence in the choices they make.

Want the full walkthrough?

Happy to share process docs, decisions, and tradeoffs over a call.

Start a conversation →