01 · Product design case study

MatchMind

Making complex football insights easier to explore

I designed and built a multilingual football analysis platform that helps users browse matches, understand access levels and purchase individual analyses or a monthly subscription.

Role
Product Designer & Front-end Contributor
Timeline
2026
Team
Independent project
Tools
Figma, FigJam, Next.js, Adobe Creative Cloud
Status
Live product
MatchMind · Matches
MatchMind desktop matches listing showing date and timezone filters, latest matches and today matches
MatchMind mobile today matches experience with match details, AI recommendation, confidence and View Details actions
Overview

A clear layer between dense match data and the people exploring it.

MatchMind is an AI-assisted football analysis platform that presents match information, access states and analysis content across multiple languages and devices. It supports analysis without suggesting or guaranteeing match outcomes.

Challenge

The challenge

Users need to scan dense information while also understanding dates, time zones, language and access.

01

How might we make dense football information easier to scan?

02

How might we clearly communicate free, single-match and subscription access?

03

How might we maintain a consistent experience across languages, devices and time zones?

Role

My contribution

I was responsible for product direction, information architecture, interaction flows, interface design, visual system, localisation decisions, design QA and front-end implementation guidance.

Product directionInformation architectureUser flowsInterface designDesign systemLocalisationDesign QAFront-end implementation guidance
Process

A practical product process

Discover → Define → Structure → Design → Build → Iterate

Discover

Mapped the product model, content constraints and required access states.

MatchMind original requirements covering product scope, users, access model and constraints

Define & Structure

Turned requirements into navigable information and an end-to-end flow.

MatchMind information architecture diagram

Design

Tested hierarchy and responsive behaviour from low to high fidelity.

MatchMind early layout and hierarchy wireframes

Flow

Connected browsing, entitlement and analysis into one coherent journey.

MatchMind access interaction flow from browsing to analysis

Build

Worked through implemented states and production constraints.

MatchMind responsive production interface composition

Iterate

Used production QA to find inconsistencies in loading, access and language.

MatchMind iteration notes for access consistency and loading experience
Key decisions

Clarity at every state

Decision 01

Access states

The interface needed to communicate access clearly without forcing users to understand the underlying entitlement system.

Locked
Locked match row with an Unlock Match action
Unlocking
Match row showing the unlocking progress state
Available
Available match row with a View Details action
Locked MatchMind detail page with blurred premium analysis and a purchase panel
Decision 02

Multilingual navigation

A selector that only displayed “简中” was difficult for English-speaking users to recognise. The revised direction prioritises universally recognisable language names and clearer switching behaviour.

Simplified Chinese · Traditional Chinese · English

Before
MatchMind interface before redesign showing only the current language as 简中

Only “简中”Difficult for non-Chinese speakers

After
MatchMind interface after redesign showing a recognisable language selector with clear language names

Recognisable current languageClear language names

Decision 03

Loading experience

Repeated loading feedback one clear content state

The page shell was already available, but multiple loading messages and repeated skeleton groups appeared within the content area. This made the experience feel slower and visually fragmented.

Design responseI kept the page structure stable and consolidated loading feedback into one content-level state.

Before
MatchMind page showing repeated loading messages and skeleton groups inside an already visible page shell
After
Improved MatchMind loading experience with one clear content-level loading state
Iterations

Before / After

Production revealed mismatches that static screens could not.

BeforeMonthly members still saw locked matches in the listing.
AfterAccess states are consistent between listing and detail pages.
BeforeTwo consecutive skeleton screens.
AfterA stable page frame with one clear loading state.
BeforeThe language selector only displayed “简中”.
AfterLanguage options are recognisable across locales.
BeforeEnglish prompts blocked the entire publishing flow.
AfterChinese content can publish independently while English appears when available.
Final solution

One system, many contexts

Varied compositions are ready for final screenshots.

Outcome

A working multilingual product with a reusable interface system.

  • Launched a working multilingual product
  • Created a complete match browsing and purchase flow
  • Designed multiple access and subscription states
  • Established a reusable interface system
  • Improved the experience through production-based iteration
Reflection

Product design continues after the interface is implemented.

Some of the most valuable improvements came from observing inconsistencies in real states, such as loading behaviour, localisation and access permissions.

Next: Conduct structured usability testing and continue improving clarity across the purchase and analysis experience.

MatchMind

Explore the live product.

Explore MatchMind live
Contact

Let’s create something useful together.