Startup MVP Design
YOYO Marketplace
Chinese international students in the US share a persistent friction: eBay doesn't understand how they trade, and WeChat groups are chaotic and risky. YOYO was built to fill that gap — a 0-to-1 mobile marketplace designed to make two strangers trust each other, and trust the platform, enough to complete a transaction.
Role
UX/Product Designer (Sole Owner)
Timeline
5 Months (Concept to Launch)
Team
1 PM, 3 Engineers
Core Responsibility
0-to-1 MVP, Interaction Design, Trust System
The Challenge
The brief was twofold:
- Get the buy/sell transaction flow working end-to-end
- Make both sides trust the platform
For a brand-new marketplace entering a community that had only ever traded through chaotic WeChat group chats, trust wasn't a feature to add at the end — it was the core design problem.
Constraints
5-month timeline. 1 PM, 3 engineers. Sole designer. No existing design system.
Starting Point
A primary blue, a brand mascot, and a product spec. No wireframes, no precedent.
My Scope
0-to-1: IA, user flows, design system, UI, and interaction specs for all core flows.
Research Findings
From user personas, competitive analysis, and community observations at project kickoff.
Two distinct trust gaps
The research surfaced two separate anxieties: buyers and sellers didn't trust the platform as a fair intermediary, and they didn't trust each other as strangers. These aren't the same problem — and a single solution would have left one gap unaddressed.
Bargaining is a social ritual, not just price negotiation
For Chinese users, the offer-counteroffer exchange is a trust signal — a way of testing willingness and establishing rapport before committing. Platforms that replaced this with a sterile "Make Offer" button felt cold, not efficient.
A logistics gap hiding in plain sight
Graduating students urgently needed to offload large furniture. Incoming students needed it but had no cars. Supply and demand were both there — but no existing channel connected them in time.
Design Challenge 01
Making the Transaction Visible
When a stranger holds your money and your item, invisibility breeds anxiety. The solution was radical transparency at every step.
The Problem
Transactions Are a Black Box
Once a buyer placed an order, both sides entered a waiting period with no visibility. Did the payment go through? Has the item shipped? Is anyone watching? Anxiety at each of these moments erodes trust in the platform — not just the other person.
Hidden Process Flow
The Solution
7-Stage Transaction Transparency
I mapped the full transaction lifecycle into 7 explicit states, each with a clear status label, timestamp, and contextual next step. Customer service access is embedded at the highest-anxiety transitions — not as a fallback, but as a visible safety net.
Visible Process Flow
Embedded Trust Touchpoints
At the three highest-risk transitions — payment confirmation, shipment handoff, and delivery — I embedded a direct support entry point inside the status card itself. The goal: users should never have to leave their current context to get help.
Step 1: Granular Status Tags
Step 2: Real-time Logistics
Step 3: Embedded Support
Design Challenge 02
Building Trust Between Strangers
Platform trust is only half the problem. Users also needed to trust each other before committing to a transaction with a stranger.
Culturally-Adapted Negotiation
Replaced the sterile 'Make Offer' with a playful 'Show Your Price Card' (亮出您的价格牌) modal. Bargaining is a natural trust-building ritual for Chinese users — removing it made the platform feel foreign. Keeping it, with a softer framing, reduced social anxiety while preserving the cultural interaction pattern.
Public Q&A + Social Proof
Moved buyer inquiries from private DMs to a public comments section on each listing. When a potential buyer sees that three other people already asked 'Still available?' and got a prompt reply, the seller's credibility is established without any extra effort. Peer interactions do the trust work.
Reputation at a Glance
Designed a credit score system surfaced directly on buyer and seller profiles — visible before any negotiation begins. Transaction history, response rate, and completion rate compound into a single trust signal that lets users make an informed decision about who they're dealing with.
Design Challenge 03
The Listing Form Tension
Sellers want to publish fast — every extra field is friction that kills conversion. But buyers need enough information to trust an item from a stranger. These two needs are structurally in conflict.
The solution wasn't fewer fields or more fields — it was smarter fields. I matched each data point to the right input type: free text for descriptions, single-select for condition, multi-select for included accessories, date picker for purchase date. The form collects the same data density, but the cognitive load drops significantly.
Community Insight → Feature Decision
An early community initiative documented a recurring pattern: graduating students urgently offloading large furniture, while newly arrived students — most without cars — couldn't transport it even when they wanted it. I added an "Eligible to Deliver" toggle to the listing form: sellers who can personally drop off an item unlock a larger buyer pool. One checkbox. One real logistics problem solved.
Execution & Systems
With no prior design system to build on, I created a component library from scratch — scoped to what the MVP actually needed, not a hypothetical future. Working directly with 3 engineers throughout, I kept specs tight and feasibility-aware. In the absence of dedicated UX research, I ran a heuristic evaluation to systematically audit interaction logic before handoff.
Component Library
Built for speed and consistency: color tokens, type scale, icons, and core UI patterns — all derived from the brand blue and mascot identity.
Heuristic Evaluation
10 Nielsen heuristics applied across all core flows. Caught 12 interaction gaps before engineering handoff.
Results
The Impact
2,500+
Active Users
Active users in Boston MVP
4.9/5.0
App Store Rating
High user satisfaction score
"Finally, a second-hand app that feels safe and understands how we trade."
User feedback · Boston MVP
Reflection
Being the sole designer on a 0-to-1 product taught me to treat constraints as design inputs, not obstacles. The 5-month timeline forced ruthless prioritization — every feature had to earn its place by solving a specific trust problem, not just adding capability. If I were to revisit this project, I would push earlier for lightweight user testing before launch: our heuristic evaluation caught logic gaps, but real users surfaced friction patterns we hadn't anticipated. The 4.9 rating validated the direction; earlier feedback would have sharpened it.
Next Project
IKEA Food Mobile — O2O Experience Redesign