Designing trust into a system that broke it

Limited sneaker releases are one of the most emotionally charged purchasing experiences in consumer retail. Demand massively outstrips supply. The window to enter is minutes long. And for most real users, the outcome is always the same: they lose.

That loss is tolerable. What isn't tolerable is not understanding why.

Across platforms like SNKRS, GOAT, and StockX, the experience is structurally broken in three specific ways. Raffles are scattered across dozens of retailer apps and sites, so users miss deadlines and lose track of what they entered. Raffle outcomes are announced with zero explanation: no context, no entry count, no selection logic. And after repeated failure, users disengage entirely, not because they stopped wanting the product, but because the system stopped feeling worth engaging with.

My job wasn't to solve scarcity. It was to design a system where losing felt fair, and where users wanted to come back anyway.

I conducted competitive analysis across SNKRS, GOAT, and StockX, ran one on one interviews with sneaker enthusiasts, and ran task based walkthroughs of existing drop flows. The research validated the three core problems users faced: raffles scattered across dozens of retailer apps and sites with no single place to track them, the complete lack of transparency around how outcomes were decided, and the spiral of disengagement after repeated failures with no explanation.

The visible problem was trust. Users entered drops and the experience went silent, no confirmation, no fairness signal, no sense of what came next. But that silence pointed to something deeper. Sneaker releases were scattered across SNKRS, Adidas Confirmed, Foot Locker, GOAT, StockX, and dozens of boutiques. No single product owned the path from finding a drop to learning the result. The broken trust was a symptom. The root cause was fragmentation.

So the real decision was about what Snix should be.

The obvious direction was a traditional sneaker storefront: product browsing, detail pages, checkout at the center. Familiar, but it solved the wrong problem. Limited drops do not behave like normal ecommerce. Users were not short on places to shop. They were short on a place that could show them where raffles were available, get them entered before deadlines, track their status, and tell them what happened after selection.

I rejected the storefront model because it would have made Snix one more place to buy sneakers. The stronger direction was to treat Snix as a raffle coordination layer across platforms, the single place that owned the full arc from discovery to result.

That reframe is what made trust solvable. Once Snix owned the whole journey, the transparency layer, the tracked entry confirmation, the plain language outcome, had somewhere to live. You cannot design trust into a moment you do not own. The coordination decision is what gave the trust work a home.

Every meaningful design decision in this project involved a real tradeoff. I made these explicitly, not as compromises, but as intentional choices with documented reasoning.

The trust problem was not solved with visual polish. It was solved by making the raffle process visible and easy to follow. Snix showed users where raffles were available, confirmed the entries they tracked, surfaced live raffle status pulled from the source, counted down to each deadline, and gave clear next steps after a win or loss. The transparency layer, showing users exactly where each raffle stood and what the source platform's stated rules were, directly addressed the suspicion that raffles were rigged.

After launch, App Store reviews pointed to the same themes, confidence, clarity, and visibility:

The measured impact was entry speed and flow simplification. The trust impact is supported qualitatively, through what users wrote about confidence, clarity, and knowing the result was fair.