Streamlining the seller upload experience to reduce drop-offs while maintaining database integrity.
Concept case study — not affiliated with Yaga. Based on observing the public listing flow and how I would approach a redesign.
In a secondhand marketplace, the listing form is the primary revenue touchpoint. Sellers who abandon mid-form mean lost inventory and lower GMV. Three friction points drove the most drop-offs.
UK-only size — invisible to US/EU search
The key insight: a size isn't one value — it's a set of equivalents. The picker adapts to category (clothing, shoes, jeans), and the moment a seller taps one size, Yaga resolves it to its UK / US / EU equivalents so buyers can search in whichever system they know.
Every branch mapped — including the image compression edge case — to create an error-proof, database-aware mobile experience.
Jeans, vintage, and jacket listings reuse the clothing or shoe schema — each mapped to its own UK / US / EU size chart.
The back-end constraint that makes conditional logic essential: size_id is a foreign key constrained by category_id, and resolves to a size_equivalents row — so a UK, US, or EU value all point back to the same listing.
category_id constrains valid size_id values — and designed the UI to enforce that visually, before it's an API error.