Chance.live - Pokémon Startup
Preventing $5,000 accidental swipes, fixing a critical retention issue in my first 15 hours
I joined Chance.live as its first in-house designer shortly after the company secured $3M+ in funding and launched its beta. In my first 15 hours, I identified a critical user drop-off point, challenged the proposed solution, and redesigned a high-risk transaction flow that protected users from costly mistakes while preserving the product's magical luxury experience.
Company
Chance.live
ROLE
Growth Designer
Product Strategist
Team
Front-end Developer
8 Person Company
Duration
15 Hours (part-time)
May 2026
Context
Chance.live is a startup reimagining how people buy, open, collect, and trade Pokémon cards online.
Instead of browsing listings like a traditional marketplace, users purchase digital packs, experience the excitement of opening them, and then sort each card by swiping it into different outcomes.
The challenge wasn't simply digitizing a transaction. The product was trying to recreate a physical experience that collectors already love and make it feel just as magical digitally.
Shortly after launching beta in April 2026, Chance.live brought me on as their first in-house designer while I was still a full-time student. Prior to this, the company relied on external design studios for visual work, but there was a disconnect between the product's goals, business goals, and user needs.
My first task was to improve one of the most important moments in the product: card sorting.
The Problem
A single accidental swipe could cost users $5000+. This irreversible action was causing them to leave.
When users open a pack, they sort cards by swiping them toward different outcomes.
At the time, selling a card was an irreversible action.
A user could accidentally sell a valuable card worth $5000+ with a single swipe and receive no confirmation before the transaction occurred. I identified this moment as a significant drop-off point in the user journey.
The original card opening process
Users would:
Open a pack
Accidentally swipe a card (in this demo, worth $5,100)
Realize the mistake too late, selling is irreversible
Lose trust in the platform
Stop using Chance entirely
This issue also generated support tickets, which created additional operational costs for an already lean team of eight people.
Define the opportunity
How might we make card swiping resilient to human error while still feeling sleek, premium, and magical?
Users needed confidence that they wouldn't accidentally sell a valuable card with a single swipe, while the team needed to improve retention and reduce the support burden that came with those mistakes. At the same time, Chance wasn't trying to feel like an e-commerce app. The goal was to capture the excitement of opening a real pack of Pokémon cards and make it feel even more magical digitally.
The Solution
Instead of teaching users not to make mistakes, I redesigned the workflow to recover from mistakes.
Rather than interrupting users with onboarding overlays and tutorial screens, I designed a lightweight confirmation system built directly into the experience. The result was a redesigned results stage that allows users to review their choices before transactions are finalized. Only one extra click was added to the workflow.
The New card opening process
Added a confirmation layer without using popups
Most products solve this problem with modal windows. I intentionally avoided that approach. Popups felt transactional and e-commerce-like. Instead, I designed a review stage that feels like part of the pack-opening experience itself. Users can now verify their decisions before transactions are executed. The experience stays immersive while significantly reducing costly mistakes.
The New card opening process
Added replay and undo functionality
One of the concepts I explored was a replay button that allowed users to rewatch the pack opening animation. As the designs evolved, this became something more useful: Undo. Users could recover from mistakes before finalizing their decisions. This added a layer of safety while keeping the interaction lightweight.
Renamed "Vault" to "Collection"
The original language felt heavily influenced by crypto products. While technically accurate, "Vault" felt impersonal and restrictive. We renamed the feature to Collection.
This language:
Better matched trading card culture
Felt more approachable
Created opportunities for future features
Thinking beyond the immediate release, Collection creates room for:
Profile customization
Collection sharing
Social features
Personal curation
A small naming decision became a foundation for future product expansion.
Designed for all card scenarios
Users can open varying numbers of cards depending on the pack. Instead of designing a single state, I created flows for 1-5 cards. This ensured consistency regardless of pack contents and made implementation easier.
Optimized specifically for mobile for majority of users, while maintaining a luxury desktop view for streamers.
One of the biggest constraints was screen size.
The mobile experience had:
Limited space
Small tap targets
Dense information
Rather than simply scaling down desktop designs, I created dedicated mobile layouts. I also kept critical actions in consistent locations across screens to reduce cognitive load and improve usability.
research
I wanted to gain a solid understanding of the company's vision before designing anything.
Specifically, product goals, brand vision, business priorities, future roadmap. I met with the team and reviewed website copy, Instagram content, and existing product flows to determine our brand ethos and identify any disconnects. I also reviewed our competitor's websites and features, and determined our key differentiators.
My overarching business goals:
Transform a physical experience into a magical digital experience
Make collecting more collaborative
Achieve a high quality, luxury, streamlined UX
My original task was to design tutorials, onboarding flows, or tooltips that would explain the card sorting experience more clearly.
I spent time researching:
Video game onboarding systems
Trading card platforms
Tutorial patterns
Hover states
Inline guidance systems
The more I researched, the more I felt that tutorials weren't solving the real problem. Adding explanations felt like putting a band-aid on a workflow that lacked feedback. Users weren't making mistakes because they didn't understand the product. They were making mistakes because the system wasn't communicating the consequences of their actions.
UX audit
Where are the gaps between our product, our user's goals, and our business goals?
After gaining access to analytics and the beta environment, I audited the entire workflow. I found high-risk irreversible actions, lack of user feedback, limited confirmation mechanisms, and user drop-off after accidental sales.
the full UX audit
key findings when going through the flow as a potential user
Design exploration
Designing feedback instead of adding friction
I wanted to experiment with spacing and various flows, while being mindful of how elements changed on desktop and mobile, as well as how the placement of elements changes depending on how many cards are opened.
some wireframes
I briefly explored a layout where cards went to the side they were swiped to, and users could drag them around, similar to the physical sensation of opening a card pack.
mid-fidelity exploration
However, this layout would require element changes for mobile, which we wanted to avoid to reduce lag and system complexity.
Design exploration
Building high-fidelity prototypes to test features and validate theories
I built 4 high-fidelity prototypes for desktop and mobile, that looked and felt like the real product.
systems design
Building edge cases and systems, not one-off screens
One thing I noticed quickly was that there wasn't just one version of this experience.
Users can open anywhere from 1-5 cards at a time. Every state needed to account for different card counts, different screen sizes, and different user actions. At the same time, Chance is a small team moving quickly. I didn't want to design a solution that would need to be reinvented every time a new feature shipped.
how does the intro page look different depending on how many cards there are?
A component library allowed me to make iterations 10x faster and makes future feature launches exponentially efficient
As I designed the confirmation flow, I simultaneously built reusable foundations that future work could build on.
This included:
Reusable interaction patterns
Consistent button behaviors
Shared visual treatments
Custom iconography
Mobile and desktop variants
Defined states for all 1-5 card scenarios
This project became an opportunity to introduce more consistency into the product.
Good design systems aren't just UI kits. They're shared decisions. They reduce ambiguity, speed up development, create consistency across the product, and make future features easier to build.
For a startup, that leverage compounds quickly.
Some of the reusable patterns and states I created
Technical Considerations
Designing with desktop + mobile implementation in mind
Because I was working directly with the front-end developer, implementation was part of the design process from day one.
For example, I explored a concept where cards physically moved to different piles depending on where users swiped them, mimicking the feeling of sorting real trading cards on a table.
While the interaction felt playful, it introduced additional complexity across mobile layouts and multiple card-count scenarios. The additional engineering effort and state management didn't justify the value it created for users.
Instead, I focused on solutions that delivered the same feeling of confidence and control while remaining technically lightweight.
This project reinforced something I strongly believe:
The best design solution isn't always the most visually impressive one. It's the one that creates the most value for users and the business relative to its implementation cost.
On mobile, the minimum height of this element should be 440px (max height) so that the confirm button is in the same place each time, for a consistent UX
Impact
A safer transaction flow that still feels magical
In approximately 15 hours, I delivered:
Complete results-stage redesign
Confirmation flow explorations
Replay and undo functionality
Custom iconography
Desktop and mobile variants
All UI states for 1-5 card scenarios
Four interactive prototypes
Reusable component foundations
The redesign transformed an irreversible action into a recoverable one while preserving the premium experience that makes Chance unique.
User Impact
Users can now review decisions before transactions are finalized.
Accidental sales become preventable instead of permanent.
The experience provides clearer feedback while maintaining the excitement of opening a pack.
Business Impact
Addressed a major retention issue identified through analytics.
Reduced support burden for an 8-person startup.
Reduced unnecessary backend processing by finalizing transactions later in the workflow.
Created reusable foundations that make future product development faster and more consistent.
Product Impact
Preserved Chance's premium and collectible identity.
Avoided default e-commerce patterns that would have cheapened the experience.
Created a scalable interaction system rather than a one-time feature.
Takeaways
Measure twice. Cut once.
The original request was a tutorial.
The real problem was trust.
Rather than immediately executing on the proposed solution, I spent time understanding the business, the users, the product vision, and the data. That extra upfront effort allowed me to move quickly with confidence once the problem was clear.
This project reinforced why I believe in-house design is so valuable for startups.
A designer embedded within the company develops context that external agencies often don't have. They understand the product vision, technical constraints, user behavior, and long-term roadmap simultaneously.
The result isn't just better screens.
It's better decisions.
In 15 hours, I wasn't just able to redesign a workflow. I was able to identify a retention issue, align a solution with Chance's brand vision, think through implementation constraints, and create reusable foundations for future growth.
That's the type of impact I want to continue bringing to Chance as the product scales.