Digital Pool

Role

UI/UX Design Intern

Timeline

June – Sep 2024

Tools

Figma

Team

Piper Yu

Emily Tsai

Christopher Clark

Tim Traver


PROBLEM

Inconsistent cards made the tournament feed chaotic and hard to use.

Digital Pool connects 18,000+ players to pool tournaments worldwide.

Every card varied in layout, sizing, and structure.

Important information like prize amount, entry fee, and game type was difficult to parse quickly, creating a chaotic browsing experience at scale.

Previous tournament cards varied wildly in size from event to event.

Three previous tournament cards in different sizesThree previous tournament cards in different sizes

Redesigned the tournament card to be structured, scalable, and data-flexible.

As the UI/UX Design Intern, I redesigned the tournament card system.

I focused on building a clearer information hierarchy that helped users compare tournaments at a glance.

The goal was not just visual consistency, but to make browsing faster and more reliable.

Old tournament card designBEFORE
Redesigned tournament cardAFTER
PROCESS

Tested multiple iterations before finding a clean, scalable design.

I explored several directions before arriving at the final design.

Each iteration exposed different tradeoffs between clarity and technical constraints.

I balanced user feedback with engineering limitations like performance to shape the final experience.

01. Vertical card

First iteration, focused on testing basic structure and information grouping.


FEEDBACK

Cards were too tall to scale across 45,000+ tournaments.

Scrolling through a feed of vertical cards made the browsing experience even more overwhelming.


TAKEAWAYS

The vertical structure created unnecessary friction and reduced scanability.

Vertical card iteration

02. Horizontal card

Second iteration, shifting to a more compact structure.


FEEDBACK

Engineers flagged performance concerns.

Gradients slowed rendering on a high-frequency browsing interaction.


TAKEAWAYS

Performance constraints pushed the design toward a simpler direction.

Horizontal card iteration

03. Google M3 list component

Engineering pushed for heavier use of native Material 3 components to simplify implementation.


FEEDBACK

Met engineering requirements.

In user testing, users still struggled to scan key details and hesitated before registering.


TAKEAWAYS

Meeting system constraints alone wasn’t enough.

Material 3 list component iteration

04. Custom tournament card

I walked engineers through user testing results and articulated where M3 fell short.

We aligned on a custom card that reused core M3 components.

Performance preserved.

Scanability improved.

Custom card final design
OUTCOME

The redesign introduced a unified tournament card system built for long-term scale.

The final solution improved browsing clarity across 45K+ tournaments.

Even the smallest components deserve systems thinking.

4.2

App Store rating after redesign shipped

45k+

Tournaments now displayed with one consistent card

18k+

Players browsing tournaments through the redesigned experience